交易请求报文

JSON:

  1. {
  2. "request_type": "bind_pos_request",
  3. "isspid": "39493002",
  4. "pos_id": "1511300001",
  5. "pos_seq": "1511300000001",
  6. "user_id": "user01",
  7. "system_id": "8888",
  8. "store_info": {
  9. "store_id": "1511300001",
  10. "store_name": "门店名称",
  11. "store_addr": "门店地址",
  12. "contact": "门店联系人",
  13. "contact_tel": "13900000000",
  14. "contact_email": "11@qq.com",
  15. "province": "福建",
  16. "city": "福州",
  17. "town": "鼓楼"
  18. },
  19. "sign": "B973E02223C49798CDCBCEE48FC323EF"
  20. }

XML:

  1. <?xml version="1.0" encoding="GBK"?>
  2. <business_trans>
  3. <request_type>bind_pos_request</request_type>
  4. <isspid>39493002</isspid>
  5. <pos_id>1511300001</pos_id>
  6. <pos_seq>1511300000001</pos_seq>
  7. <user_id>user01</user_id>
  8. <system_id>8888</system_id>
  9. <store_info>
  10. <store_id>1511300001</store_id>
  11. <store_name>门店名称</store_name>
  12. <store_addr>门店地址</store_addr>
  13. <contact>门店联系人</contact>
  14. <contact_tel>13900000000</contact_tel>
  15. <contact_email>11@qq.com</contact_email>
  16. <province>福建</province>
  17. <city>福州</city>
  18. <town>鼓楼</town>
  19. </store_info>
  20. </business_trans>

交易请求报文说明

节点名称中文名称类型说明是否必填
sign报文签名String(32)请求报文格式为JSON时必填计算签名方式请看2.1章节可选
request_type请求类型String(32)标识请求报文的类型,固定为bind_pos_request必填
system_id系统平台号String(4)由翼码提供必填
isspid商户号String(8)接入SP的ID号,为翼码平台的提供的业务商机构号必填
pos_id终端号String(20)终端号(对方自定义的终端号)必填
pos_seq终端流水号String(32)该接口流水号可选填,便于日志定位可选
user_id操作员标识String(20)终端操作员号,对应于外部POS终端的操作员编号可选
store_info->store_id门店编号String(20)门店编号必填
store_info->store_name门店名称String(100)门店名称(50个中文)门店名称已存在时不会新增门店在原门店下新增终端,门店信息不会修改必填
store_info->store_addr门店地址String(100)门店地址可选
store_info->contact门店联系人String(32)门店联系人可选
store_info->contact_tel门店联系电话String(32)门店联系电话可选
store_info->contact_email门店联系邮箱String(64)门店联系邮箱可选
store_info->province门店省份String(32)门店省份可选
store_info->city门店城市String(32)门店城市可选
store_info->town门店城镇String(32)门店城镇可选

交易返回报文

JSON:

{
    "response_type": "bind_pos_response",
    "isspid": "39493002",
    "pos_id": "123456789",
    "pos_seq": "000000000001",
    "trans_time": "20181214113740",
    "result": {
        "id": "0000",
        "comment": "操作成功"
    },
    "sign": "EADFE430D0E856CF5F818690155F1258"
}

XML:

<?xml version="1.0" encoding="GBK"?>
<business_trans>
    <response_type>bind_pos_response</response_type>
    <isspid>39493002</isspid>
    <pos_id>123456789</pos_id>
    <pos_seq>000000000001</pos_seq>
    <sys_seq>000000000244</sys_seq>
    <trans_time>20090405010104</trans_time>
    <result>
        <id>0000</id>
        <comment>成功</comment>
    </result>
</business_trans>

交易返回报文说明

标准接口会因业务升级需要而新增节点,请在解析返回报文时避免新增未知节点产生的程序出错!

节点名称中文名称类型说明是否必填
sign报文签名String(32)返回报文格式为JSON时必填计算签名方式请看2.1章节可选
response_type返回类型String(32)标识返回报文的类型,固定为bind_pos_response必填
isspid商户号String(8)接入SP的ID号,由翼码平台分配给ipos接入受理商户的机构号必填
pos_id终端号String(20)终端号(对方自定义的终端号)必填
pos_seq终端流水号String(32)终端交易流水号和请求报文的交易流水相同可选
trans_time交易时间String(14)交易时间,格式:yyyyMMddHHmmss必填
result->id响应码String(4)翼码平台返回的处理结果,0000-成功,其它失败,错误信息说明见“响应码解释”字段必填
result->comment响应码解释String(64)响应码对应中文注解,用于显示提示必填

标准接口会因业务升级需要而新增节点,请在解析返回报文时避免新增未知节点产生的程序出错!