Callback notification( Customized by merchant)

Submission method: POST

When receiving point-to-point communication from the server, the interface returns "OK" (without double quotes, OK is in capital letters), otherwise point-to-point notifications will be sent repeatedly (default 16 times).

OK

Content-Type

application/json

Verify signature

Use the TarsPay public key to verify the signature of [return data](#return description).

Request parameters

Name	Type	Required	Description
bizType	number	Y	Business type: 1-Collection 2-Payment
payOrderId	string	Y	payment order number
mchNo	string	Y	merchant number
mchOrderNo	string	Y	Merchant order number (customized by merchant, cannot be repeated)
orderAmount	string	Y	original transaction amount of bill
payAmount	string	Y	payment amount
currency	string	Y	three-digit currency code
state	number	Y	payment status: 2-payment successful, 3-payment failed, 9-partial payment (collection)
fee	string	Y	merchant fee
failReason	string	N	Failure reason

Callback signature verification description: X-RESP-SIGNATURE request header carries signature

Signature rules: After JSONizing the request parameters, put the obtained signature in the header, and obtain the signature directly from the response header. To verify the signature, use verifyEcdsaSignature() in the ECSDAKit tool class below.

Example:

OrderNotifyDTO.class

Request

Header Params

Body Params application/json

Example

{
    "bizType": 2,
    "currency": "IDR",
    "failReason": "payment failed",
    "fee": "6973",
    "mchNo": "M1696154848",
    "mchOrderNo": "1184196902791413760",
    "orderAmount": "31500",
    "payAmount": "31500",
    "payOrderId": "P1734517376779485186",
    "state": 3
}

Request samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Callback notification( Customized by merchant)

Submission method: POST#

Content-Type#

Verify signature#