---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/features/tokenization/cardOnFileOverview/index.md
description: >-
  Helps merchants choose the right subsequent-payment path for international
  card saved-card scenarios: regular saved-card repeat purchase, or
  cardholder-initiated stored credential payments using the CardOnFile model. In
  PingPong, the latter typically enables a CVV-free one-click checkout
  experience.
---
## What saved cards enable

After saving the cardholder's card information during the first payment, subsequent payments can display the saved card directly — no need to re-enter the full card number.

Depending on your repeat-purchase experience requirements, there are two paths:

## Choose your repeat-purchase path

Both paths display saved cards during checkout. The difference is how subsequent transactions are classified and processed.

**Choose CVV repeat purchase if:**

- You want each repeat purchase to require CVV as confirmation of user intent, reducing the risk of unauthorized payments
- Your business requires an additional verification step in the payment flow
- You prefer a more conservative risk control approach

**Choose one-click payment (CardOnFile) if:**

- You want the cardholder to select a saved card and complete payment immediately, with minimal checkout friction
- You have completed cardholder notice and consent for card storage and subsequent use, and have assessed the business risk of a CVV-free flow
- You have high repeat-purchase frequency and a smoother checkout experience meaningfully impacts conversion

### Another benefit of one-click payment (CardOnFile)

`CardOnFile` is first and foremost a stored credential transaction classification. In PingPong, it identifies a cardholder-initiated `CIT CoF` scenario.

After you pass `bizType=CardOnFile` on the first payment and complete card storage, card networks and issuers recognize subsequent payments as stored credential follow-on transactions. Card networks have dedicated risk models for stored credential transactions, and issuers can make authorization decisions based on the previously authorized transaction context.

In comparison, stored-card payments without `bizType=CardOnFile` may be treated by the issuer as a first-time or new-card transaction due to insufficient transaction context, which could lead to higher decline rates.

If you only want to save card information and improve the repeat purchase experience, a regular saved-card transaction is sufficient. If you care about payment conversion rates for repeat purchases, we recommend the CardOnFile mode.

::: note Note
Both paths use the same first-payment setup. The only difference is whether you pass `bizType=CardOnFile` on the first payment. In the PingPong platform, once a path is chosen on the first payment, subsequent repeat purchases must continue to follow that same path.
:::

## Cardholder-not-present scenarios (Recurring / MIT)

If you need to charge the cardholder when they are not present, use `bizType=Recurring`.

In card network standards, both CIT (cardholder-initiated) and MIT (merchant-initiated) fall under the Card-on-File umbrella. PingPong splits them into separate integration paths:

| Scenario | bizType | Cardholder present | Reference |
|:---------|:--------|:------------------|:----------|
| One-click payment | CardOnFile | Yes | This page |
| Merchant-initiated charge | Recurring | No | Recurring documentation |

`Recurring` is also an MIT charge capability: the merchant keeps the authorization relationship and decides when to trigger each subsequent charge. Charge plans and retry policies are managed by the merchant.

::: warning 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.
:::

## Supported card brands

Currently supported for Visa and Mastercard.

## Prerequisites

- PingPong Checkout acquiring service enabled
- Merchant onboarding and account configuration completed
- Contact technical support to confirm enablement if you need to use `bizType=CardOnFile`
- If you plan to use subsequent stored-card charges, make sure you have completed cardholder notice and defined the scope of later use on the merchant side

## Documentation navigation

| Document | Description |
|:---------|:------------|
| [First Payment and Save Card](/en/notes/onlinePayment/features/tokenization/cardOnFile/) | Save card information during the first payment; first-payment setup for both paths |
| [Checkout Repeat Purchase (Stored Card + CVV)](/en/notes/onlinePayment/features/tokenization/cardOnFileCVV/) | CVV path: Hosted mode displays saved card and collects CVV |
| [Server-side Repeat Purchase (Token Payment / One-click)](/en/notes/onlinePayment/features/tokenization/cardOnFileNonHosted/) | One-click path: Non-Hosted mode uses a token for subsequent payments and typically does not require CVV |
| [Bind Card and Get Credential](/en/notes/tokenization/cof/bind/) | Bind a card separately and obtain a reusable credential outside the payment flow |