Open API
English
  • English
  • 简体中文
API DOC
API DOC
English
  • English
  • 简体中文
  1. Asynchronous notification description v2
  • Open API
    • 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
      • Attachment upload interface
      • Interface for obtaining payment address
      • Order batch query interface
    • 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 v2

[Order Status Change] Asynchronous notification parameter description for order status change

CAUTION
Please note that the asynchronous notification interface does not use a universal request data template
FieldTypeDescRemark
notify_typeStringNotify TypeThe current type of asynchronous notification is: order_status_change
order_idStringOrder IDET Order ID
datetimeStringOrder status change datetimeString type, example 2024-12-12 10:00:00 Beijing Time (utf-8)
order_statusStringOrder StatusFor details, see the constant description order_status description.
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"
}
Modified at 2024-12-16 04:00:08
Previous
Asynchronous Notification Signature Generation Process
Built with