Background

PingPongCheckout V4 provides two ways to synchronize the state between merchant server and PingPongCheckout server:

1. Asynchronous Notification
2. Transaction Query

If relying solely on asynchronous notifications, due to network exceptions or system fluctuations, it may cause situations where user payments succeed but merchants fail to successfully receive payment result notifications, resulting in displaying orders as unpaid. Untimely updates of order status on the merchant side can easily lead to customer complaints.

Solution

1. Merchant frontend page redirects to payResultUrl page, merchant needs to call merchant order inquiry API to confirm order status, and display query results to user.
2. Merchant backend needs to accurately and efficiently process asynchronous payment result notifications sent by PingPongCheckout V4, and return processing results according to interface specifications.
3. When merchant backend does not receive asynchronous payment result notification, merchant should proactively call Transaction Query to synchronize order status.

Note

The above solution best fits the checkout integration method. If integrating in Non-hosted mode, you can directly obtain order status from the synchronous return result of Place Order and Pay. If the obtained result is not a final state, you can execute according to the above process.

Order Closure Initiated by PingPongCheckout

For orders where users have not paid for an extended period, PingPongCheckout V4 will perform order closure processing. After closing the order, users cannot continue to make payments, and merchants can obtain the CLOSED status through query interfaces or asynchronous notifications.

Note

If a custom order closure notification address closeNotificationUrl was provided, an order closure notification will be sent when the order reaches the CLOSED status.

Previous pageSubscription Notification Integration Guide

Next pageCurrency Exchange Guide