|
@@ -65,7 +65,7 @@ This field is a list of common fields, sending, every channel needs some channel
|
|
|
|
|
|
3.Jump transformation Purchase interface response message
|
|
|
|
|
|
- The merchant needs to provide an HTTP/HTTPS protocol interface that is included in the parameters passed to the SDK, the backURL. After the payment is complete, the AllPay server will call the backURL as a POST, informing the payment result (JSON). When merchant receive the notification, the merchant is required to return "OK".
|
|
|
+ The merchant needs to provide an HTTP/HTTPS protocol interface that is included in the parameters passed to the SDK, the backURL. After the payment is complete, the AllPay server will call the backURL as a POST, informing the payment result (JSON). When merchant receive the notification, the merchant is required to response String "OK".
|
|
|
|
|
|
If we didn't receive "OK" from merchant,AllPay will resend the response message to merchant.Time interval is[15, 15, 30, 180, 1800, 3600, 7200, 14400, 14400], the unit is second.
|
|
|
|
|
@@ -272,7 +272,7 @@ Parameters as follows:
|
|
|
|
|
|
3.Response message
|
|
|
|
|
|
- The merchant needs to provide an HTTP/HTTPS protocol interface that is included in the parameters passed to the SDK, the backURL. After the payment is complete, the AllPay server will call the backURL as a POST, informing the payment result (JSON). When merchant receive the notification, the merchant is required to return "OK".
|
|
|
+ The merchant needs to provide an HTTP/HTTPS protocol interface that is included in the parameters passed to the SDK, the backURL. After the payment is complete, the AllPay server will call the backURL as a POST, informing the payment result (JSON). When merchant receive the notification, the merchant is required to response String "OK".
|
|
|
|
|
|
If we didn't receive "OK" from merchant,AllPay will resend the response message to merchant.Time interval is[15, 15, 30, 180, 1800, 3600, 7200, 14400, 14400], the unit is second.
|
|
|
|