Card on File (COF) Guide
Last updated:August 7, 2026
Card on File (COF) framework allows merchants to create a COF agreement with the cardholder during the initial payment (CIT), when he is present, and securely store his credit or debit card. Reference to this COF agreement in all the future merchant initiated (MIT) payments, is very important for the Issuer bank of the cardholder to validate the future payment requets as sanctioned by the cardholder, even though are initiated by the merchant without active cardholder presence.
Our Card on File framework consists of three types of COF agreements
CIT agreements
CIT agreement implies, that the cardholder is storing his card only for his own convenience of initiating payment by himself, as a single click payment later, without a need of entering his card data every time he visists the merchant's app or website.
MIT agreements
MIT agreement implies, that the cardholder has authorized the merchant to initiate multiple future payments on his behalf, based on a predefined recurring or unscheduled basis for a fixed or variable amount.
Industry Practice MIT agreements
Industry Practice MIT agreement is a type of agreement, where cardholder allows merchant to initiate a once-off payment later, when carholder will be off-session.
- Store the Scheme ID from the initial CIT in your systems to support acquirer migrations and cross-connector continuity.
Use cases
One-click agreement
The merchant collects card data from the shopper during a cardholder-present purchase and stores it for future one-click payments. Every later purchase is still cardholder-initiated, so each one-click charge is sent the same way as the first, just switching standingInstruction.mode to REPEATED.
Use case: Anna stores her card at marketplace for quick purchases in future. When time comes, she makes an order and pays for it in a single click choosing the card she stored.
How it works
Store the payment data
Tokenize the card during the initial, cardholder-present purchase.
Send the payment
Use the stored registration for every later cardholder-initiated payment.
Review the agreement
Query the registration to confirm the stored one-click agreement.
createRegistration=true standingInstruction.type=UNSCHEDULED standingInstruction.mode=INITIAL standingInstruction.source=CIT
standingInstruction.type=UNSCHEDULED standingInstruction.mode=REPEATED standingInstruction.source=CIT
Try it out
Pick the integration and the token type you use, and test the Card on File scenarios step by step with sample requests.