Notification mechanism description for orders' result

To ensure data consistency, after transaction processing is completed, Geoswift system notifies the merchant system with oders' processing results in the form of POST request according to the asynchronous notification address parameter "notifyUrl" passed by the merchant.

When your system receives the final order status notification from Geoswift (via server-to-server communication), the response must include the keyword success (case-insensitive). If this keyword is detected, Geoswift will consider the notification successfully delivered. Otherwise, the system will retry the notification up to four additional times at increasing intervals of 20, 30, 40, and 50 seconds (a total duration of 140 seconds) to ensure successful delivery.

Notice 1:

  • The status returned by the synchronous callback only represents the order submission status and cannot be used to judge the order's status. The order status is subject to the asynchronous callback response and the query interface response of all the orders.
  • When receiving duplicated asynchronous notification message for many times, be sure to do a good job in judging the status of the order and do not repeat billing.
  • Asynchronous callback is a notification behavior. After receiving the notification, the merchant needs to respond as required. Redirection is not supported.

    • Notice 2:

  • In rare cases, asynchronous notifications may not reach your server properly.So be sure to integrate the "query order" interface。
  • Set a reasonable request interval according to the service scenario. For example, if there is no asynchronous notification after completing payment for 1 minutes, then you can initiate an "order query" request.
  • The query interface has a limit of 200 times per minute. If the limit is exceeded, an error will be returned.