Use Cases

• The merchant manages the card list and payment interaction directly, without using PingPong checkout
• The merchant already maintains a local mapping between token and stored card information
• Subsequent payments are triggered while the cardholder is present, which fits one-click checkout scenarios

Prerequisites

• Completed the First Payment and Save Card flow and obtained a payment credential token that can be used for repeat purchases
• You know whether bizType=CardOnFile was passed in the first saved-card transaction
• You have completed merchant-side notice and consent for card storage and subsequent use

Interaction Flow

Integration Steps

1. Client places the order

   The shopper starts order creation on the merchant platform.

2. Merchant server requests order and payment

   Call the Order and Pay API

   • Pass the payment credential token
   • If bizType=CardOnFile was passed when the token was first created, every subsequent transaction using that token must continue to pass bizType=CardOnFile

   PingPong platform rule: bizType=CardOnFile inheritance

   First payment passed bizType=CardOnFile → all subsequent token payments must also pass bizType=CardOnFile. First payment did not pass it → do not pass it on subsequent payments either.

   Example key fields for a CardOnFile token repeat purchase:

   Key fields in bizContent (CardOnFile scenario)

   {
     "merchantUserId": "USER_12345",
     "token": "TOKEN_123456",
     "bizType": "CardOnFile"
   }

Note

No CVV input for subsequent payments does not mean extra authentication will never be required. Whether 3DS, challenge, or declines occur still depends on issuer risk controls, regulatory requirements, and transaction risk.

Field distinction

The token passed here is the payment credential token returned after the first saved-card payment succeeds. For subsequent server-side repeat purchases, continue passing it in the token field of the uniformly request.

3. The Order and Pay API synchronously returns the payment result

   The Order and Pay API immediately returns the processing result.

4. Async notification pushes the final result

   The final payment result will be pushed through the async notification mechanism. See Async Notification for details.

:::

Related Documentation

• First Payment and Save Card - Save card information during the first payment and obtain a reusable payment credential
• Checkout Repeat Purchase (Stored Card + CVV) - Collect CVV in checkout for repeat purchases
• Order and Pay API - Core API for Non-Hosted mode

Previous pageCheckout Repeat Purchase (Stored Card + CVV)

Next pageCodeGrant