Repeat Purchase Non-Hosted
About 346 wordsAbout 1 min
2025-05-15
Use Cases
- Merchants managing their own card list and payment interaction, without needing the PingPong checkout page
- Merchants maintaining token-to-card mapping locally
Prerequisites
- Completed the CardOnFile first-time binding flow and obtained a card token
- Know whether
bizType=CardOnFilewas passed during initial binding
Interaction Flow
Integration Steps
Client places order
Customer initiates order creation on merchant platform
Merchant server requests order and payment
Call Place order and pay API
- Pass
token - If
bizType=CardOnFilewas passed when creating token, then every subsequent transaction using token needs to be sent
- Pass
Order and pay API synchronously responds with payment result
Place order and pay API will immediately return processing result
Async notification pushes final result
System will push final payment result through async notification mechanism, see Async Notification for details
Related Documentation
- CardOnFile Binding Flow — Create card token and basic binding flow
- Repeat Purchase CVV Collection (Hosted) — Collect CVV through checkout for repeat purchases
- Place Order and Pay API — Core API for Non-Hosted mode
