Transaction Status Flow Pattern

PingPongCheckout provides two transaction idempotency modes:

• Failure Non-Final State (default)
• Failure Final State (requires notification to PingPongCheckout for configuration during integration)

Failure Non-Final State

Failure Non-Final State is the default setting, in this mode:

• FAILED status can still continue to be paid until the order expires and is closed. You can initiate payment again without changing the order number.
• Duplicate payments may occur with low probability, which can be handled with manual refunds

Status	Description	Status Type
SUCCESS	Payment successful, transaction completed successfully	Final State
CLOSED	Transaction result due to timeout/closure	Final State
FAILED	Payment failed, user can pay again	Intermediate State
PROCESSING	Intermediate state, merchant should wait for PingPongCheckout's asynchronous result before processing business.	Intermediate State
INIT	Order initialization	Intermediate State

Failure Final State

Failure Final State requires manual configuration, in this mode:

• FAILED status is final, the payment order status will not change anymore, you need to change the order number to initiate payment again.
• PROCESSING initiating payment request again will prompt duplicate transaction

Status	Description	Status Type
SUCCESS	Payment successful, transaction completed successfully	Final State
CLOSED	Transaction result due to timeout/closure	Final State
FAILED	Payment failed, user can pay again	Final State
PROCESSING	Intermediate state, merchant should wait for PingPongCheckout's asynchronous result before processing business.	Intermediate State
INIT	Order initialization	Intermediate State

Previous pageTokenization

Next pageDisputes