PayEase Google Pay API submission interface

Description

The Google Pay API submission interface is used to select the payment method of Google Pay at the merchant end, and the communication deploys HTTPS protocol. The merchant sends the request parameter data to the URL specified by PayEase, and receives the response results returned by Payease simultaneously, and receives asynchronous notification results, etc.

Request Endpoint

https://apis.5upay.com/icc/gpayApi

Name Type& Max Description Requirement
merchantId varchar(9) The unique identity of the merchant ID in Payease system. After the merchant completes Payease system registration, the merchant can log in the merchant background to check M
orderAmount decimal(18) UNIT: Yuan. Keep 2 decimal places, for example 10.00 M
orderCurrency varchar(15) CNY is RMB, USD is US dollar, EUR is Euro, GBP is pound, JPY is yen, KRW is Korean dollar, RUB is rouble, CHF is Swiss franc, HKD is Hong Kong dollar, SGD is Singapore dollar, MOP is Macao dollar, CAD is Canadian dollars, NZD is New Zealand dollars, TWD is nt dollars, AUD is Australian dollars M
requestId varchar(50) Format is date(yyyymmdd)-merchant id-merchant flow number e.g.: 20170101-888-12345 The flow number is numeric, not repeated within 24 hours and only be number and “-”. It can be single or multiple. M
paymentData TEXT An encrypted payment token obtained from Google M
notifyUrl varchar(200) Server notification: Successful notification will be sent to the address after payment is successful. This address can take parameters(Send mechanism see response mechanism) example: “https://www.5upay.com/callback.actio n?test=test”. Note: if the parameter value of notifyUrl is not filled, your server will not receive the notice of successful payment after payment is successful. M
shipInfo Json Please refer to the table "Request Fields (shipinfo)" M
billInfo Json Please refer to the table "Request Fields (billinfo)" M
terminalNo varchar(20) A website corresponds to a terminal number, no more than 20 digits M
remark varchar(300) Remarks parameter will return along with payment status. O
ordip varchar(15) The IP address used by the customer when entering cardholder information M
hmac varchar(500) The method for obtaining hmac is shown in "Developers," The parameter sequence is spliced from A-Z with the initials of key name, and The corresponding key values are separated by #. M

Request Fields (shipinfo)

Name Type& Max Description Requirement
shipStreet String (300) The street of shipping address, Contains a maximum of 60 characters M
shipCity String (300) The city of shipping address, Contains a maximum of 50 characters M
shipState String (300) The state or province of shipping address(e.g.2 digits code for USA and Canada.The standard can refer to "state code") M
shipPost String (100) The post code of shipping address.(The length should not exceed 100 characters) It is mandatory for USA with 5 or 9 digits(like NNNNN or NNNNN-NNNN) and Canada with 6 digits(like ANA NAN) M
shipCountry String (20) A three-digit code of shipping country, can refer to 《country code》 M
shipPhone String (15) Shipping phone number; The length should not exceed 15 characters M
shipEmail String (100) Shipping email; The length should not exceed 100 characters M

Request Fields (billinfo)

Name Type& Max Description Requirement
billStreet String (300) The street of bill address, The length cannot exceed 60 characters M
billCity String (300) The city of bill address, The length cannot exceed 50 characters M
billState String (300) The state or province of bill address(e.g.2 digits code for USA and Canada.The standard can refer to "state code") M
billPost String (100) The post code of bill address.(The length should not exceed 100 characters) It is mandatory for USA with 5 or 9 digits(like NNNNN or NNNNN-NNNN) and Canada with 6 digits(like ANA NAN) M
billCountry String (20) The 3 digits code of bill country,can refer to "country code" M
billPhone String (15) bill phone number; The length should not exceed 15 characters M
billEmail String (100) bill email; The length should not exceed 100 characters M

Sample

{ "merchantId": "888", "orderAmount": "1.00", "orderCurrency": "CNY", "requestId": "20190813-888-123456", "paymentData ": "********", "notifyUrl": "http://www.baidu.com", "terminalNo": "123456", "remark": "test", "ordip": "127.0.0.1", "hmac": "af291df5d288690d2b7d7bcff7dc5a74447ce1502c1edcc9293051bb6a517d68 6fbb31de72bfd14938d474fa6dd0afb82a2c222a6a345e41683d456a142e3376 c5c8f07dc5bc92dd5b09af316fa478a003189ed4d4c956d33162de11a8aec8ab 6abcf66b19833302780cffaa25c7e40bb9b2ccc59adc44e3fcb4632bce5d9cf9", }

Returned Fields

Note: When the response is normal, which is when the status parameter value is SUCCESS, then the packet will include the merchant ID, order number and other information.

Name Description
status SUCCESS
ERROR
merchantId Same as the merchantId of the request parameter
paymentModeAlias Returned value includes: VISA、MASTER、AE、JCB、Diners、Discover
requestId Same as the requestId of the request parameter
bankNumber bank order number
serialNumber Payease system transaction serial number
pstatus Payment status: INIT
SUCCESS
FAILED
PROCESSING
statusDescription See the table "payment status code"
orderAmount Same as the order amount of the request parameter
orderCurrency Same as the order currency of the request parameter
submissionTime Format: yyyy-MM-dd HH:mm:ss
completeTime Format: yyyy-MM-dd HH:mm:ss
remark Same as the remark of the request parameter
hmac The method for obtaining hmac is shown in "Developers," The parameter sequence is spliced from A-Z with the initials of key name, and The corresponding key values are separated by #.

Sample

{ "status": "SUCCESS", "merchantId": "888", "paymentModeAlias": "MASTER", "requestId": "20190813-888-123456", "bankNumber": "3456789098", "serialNumber": "123456", "pstatus": "SUCCESS", "pstatusDescription": "0000", "orderAmount": "1.00", "orderCurrency": "CNY", "submissionTime": "2019-08-13 01:12:30", "completeTime": "2019-08-13 01:12:31", "remark": "test", "hmac": " af291df5d288690d2b7d7bcff7dc5a74447ce1502c1edcc9293051bb6a517d68 6fbb31de72bfd14938d474fa6dd0afb82a2c222a6a345e41683d456a142e3376 c5c8f07dc5bc92dd5b09af316fa478a003189ed4d4c956d33162de11a8aec8ab 6abcf66b19833302780cffaa25c7e40bb9b2ccc59adc44e3fcb4632bce5d9cf9", }

Asynchronous Return Fields

Note: the parameter of this form is the NotifyUrl server return parameter

Name Description
merchantId Same as the merchantId of the request parameter
requestId Same as the requestId of the request parameter
bankNumber Bank Order ID
serialNumber Payease System transaction serial number
orderCurrency Same as the order currency of the request parameter
orderAmount Same as the order amount of the request parameter
pstatus Payment status: SUCCESS
FAILED
pstatusDescription See the table "payment status code"
submissionTime Format: yyyy-MM-dd HH:mm:ss
completeTime Format: yyyy-MM-dd HH:mm:ss
paymentModeAlias The return value is VISA MASTER AE JCB
remark Same as the remark of the request parameter
hmac The method for obtaining hmac is shown in "Developers," The parameter sequence is spliced from A-Z with the initials of key name, and The corresponding key values are separated by #.

Sample

{ "merchantId": "888", " requestId": "20190813-888-123456", "bankNumber": "3456789098", "serialNumber": "123456", "orderCurrency": "CNY", "orderAmount": "1.00", "pstatus": "SUCCESS", "submissionTime": "2019-08-13 01:12:30", "completeTime": "2019-08-13 01:12:31", "paymentModeAlias": "MASTER", "remark": "test", "hmac": " af291df5d288690d2b7d7bcff7dc5a74447ce1502c1edcc9293051bb6a517d68 6fbb31de72bfd14938d474fa6dd0afb82a2c222a6a345e41683d456a142e3376 c5c8f07dc5bc92dd5b09af316fa478a003189ed4d4c956d33162de11a8aec8ab 6abcf66b19833302780cffaa25c7e40bb9b2ccc59adc44e3fcb4632bce5d9cf9", }