Open API
首页
首页
  1. Asynchronous notification description v1
  • Document Revision History
  • Overview of Study Abroad Payment API Access
  • API Call Address
  • Request for serial number generation instructions
  • API Request Parameter Description
  • API Response Parameter Description
  • Interface encryption and signing steps
  • Interface decryption and verification process
  • Constant Description
    • pay_type description
    • order_status description
    • status_code description
    • fee_type description
    • attachment_type description
    • country_code description
    • currency_code description
    • Gender Description
    • ID type Description
  • API
    • Order interface
      POST
    • Attachment upload interface
      POST
    • Interface for obtaining payment address
      POST
    • Order batch query interface
      POST
  • Asynchronous notification description v1
    • [Successful Payment] Asynchronous notification parameter description for successful payment
    • Explanation of Asynchronous Notification Signature Generation Process
  • Asynchronous notification description v2
    • Asynchronous Notification Description
    • Asynchronous Notification Signature Generation Process
    • [Order Status Change] Asynchronous notification parameter description for order status change
  1. Asynchronous notification description v1

[Successful Payment] Asynchronous notification parameter description for successful payment

If users make real-time payments online, this notification service will notify merchants in real time.
If the user makes an offline transfer, the notification may be sent to the merchant 1-2 days later (ET operators manually modify the order success status).
Asynchronous notifications use the POST method.
When requesting, use the FormData form to pass data, and when responding, return data in JSON format.
Asynchronous notification period: An asynchronous notification will be sent when the order payment is successful. If we do not receive a notification with an OK result, we will send another asynchronous notification one minute later. If we have not received it yet, we will send it five minutes later, and so on. A total of seven notifications will be sent in ten minutes, half an hour, one hour, and two hours.
Please note that the asynchronous notification interface does not use a universal request data template
FieldTypeDescRemark
order_idStringorder idET Order Id
pay_resultIntPayment results1 payment successful, 0 failed
pay_amountFloatpayment amountFloating point number, example 10000.00.
pay_currency_codeStringPayment currency codeDefault RMB, Please refer to the constant description and currency code description for details.
pay_datetimeStringPayment timeString type, example 2017-10-12 10:00:00 Beijing Time (utf-8)
extend_infoStringextend infoSubsequent reserved use。
signStringsignatureUse MD5 to generate signatures. For detailed procedures, please refer to the asynchronous notification signature generation process instructions
Response:
FieldTypeDescRemark
notify_resultStringnotify resultIf "OK" is returned, the notification is successful and no more notifications are sent. If other result are returned, the notifications continue to be sent.
Sample Response Json:
{
    "notify_result": "OK"
}
Previous
Order batch query interface
Next
Explanation of Asynchronous Notification Signature Generation Process
Built with