CardOnFile Overview
About 590 wordsAbout 2 min
2025-05-15
Product Introduction
CardOnFile (CoF) is a tokenized payment solution that allows merchants to securely store cardholder credit card information after authorization and reuse it for subsequent transactions. By replacing sensitive card data with tokens, merchants can offer a fast checkout experience without handling raw card data.
Core Capabilities
| Capability | Description |
|---|---|
| Secure Binding | Create a card token during the first payment; card information is securely managed by PingPong |
| Quick Repeat Purchase | Subsequent payments only require the token — no need to collect full card details again |
| CVV Collection | Securely collect CVV through the checkout for repeat purchases to meet security verification requirements |
| Multi-Card Management | Support binding multiple cards per user, with card list query and selection APIs |
Integration Modes
| Mode | Description | Use Case |
|---|---|---|
| Hosted | Payment interaction handled by PingPong checkout, including card display and CVV collection | Merchants who want to reduce PCI compliance burden and launch quickly |
| Non-Hosted | Merchant manages payment interaction directly, calling APIs to complete payment | Merchants with PCI DSS certification who need full control over the payment experience |
Overall Integration Flow
Phase 1: First-time Binding
The cardholder completes card binding during their first payment. PingPong creates a card token and securely stores the card information.
- Hosted mode: The checkout automatically handles
createToken; the merchant only needs to passmerchantUserId - Non-Hosted mode: The merchant sends
createToken=Y; the API returns a card token
Phase 2: Repeat Purchase
The cardholder uses the stored card token for subsequent purchases.
- Hosted — CVV Collection Checkout: Display stored card information and collect CVV through the embedded checkout
- Non-Hosted — Direct API Call: The merchant server uses the token to call the order API directly, no checkout page needed
Key Parameters
| Parameter | Type | Description |
|---|---|---|
bizType | String(64) | Pass fixed value CardOnFile when binding and transacting (contact technical support to enable) |
merchantUserId | String(64) | Unique cardholder ID on the merchant side, used to associate tokens |
createToken | String(1) | Pass Y during first-time binding |
token | String | Card token returned after successful binding, used for repeat purchases |
cardToken | String | Pass the stored card token during repeat purchases; the checkout will display the corresponding card information |
Documentation Navigation
| Document | Description |
|---|---|
| Binding Flow | Detailed steps for first-time binding (create token, verify card elements, display card list) |
| Repeat Purchase CVV Collection | Hosted mode: Collect CVV through the embedded SDK checkout for repeat purchases |
| Repeat Purchase Non-Hosted | Non-Hosted mode: Use token to call the API directly for repeat purchases |
Prerequisites
- PingPong Checkout acquiring service enabled
- Merchant onboarding and account configuration completed
- Contact technical support to enable
bizType=CardOnFileif needed
