Card On File Requirements

Credit Card Storage - Card On File Requirements

Card on File requirements apply when storing cardholder credentials for future use, or when processing subsequent transactions with previously stored credentials. Use the transflags values below to identify the transaction type.

Types of Card on File

CIT — Cardholder Initiated

Any transaction in which the cardholder is actively participating and giving permission to store card data for future use, or using a card that is already on file. This can be in-store, an online checkout experience, or a subsequent stored credential transaction.

MIT — Merchant Initiated

Any subsequent transaction with previously stored credentials. The cardholder previously consented to the merchant storing payment credentials for future use, without active engagement from the cardholder on the subsequent charge.

Variable Names and Usage

Sending one of the values below as transflags indicates a Card on File transaction.

`transflags` value	Description
`cit,init`	The merchant is storing the cardholder credentials for the first time in anticipation of future unscheduled stored credential transactions.
`cit,init,recurring`	The cardholder initiates the first in a regularly scheduled recurring series of transactions.
`cit`	The cardholder initiates a transaction using a credential currently stored with the merchant.
`mit`	A transaction initiated by the merchant. This is not a recurring transaction that occurs at a scheduled interval.
`mit,recurring`	A subsequent transaction in a series of transactions processed at fixed, regular intervals.

Payment Method Integration Note

For Remote API, use fields transflags and origorderid.
For REST API, use flags (for transflags) and initialOrderID (for origorderid).

When to Include `origorderid`

`transflags` value	`origorderid` requirement
`cit`	Include `origorderid`. Use the `orderID` from the transaction that was sent with `cit,init`.
`mit`	Include `origorderid`. Use the `orderID` from the transaction that was sent with `cit,init`.
`mit,recurring`	Include `origorderid`. Use the `orderID` from the transaction that was sent with `cit,init,recurring`.

AVS-Only Initial Authorization

An avsonly transaction can be used as an initial authorization (for use as origorderid) by sending one of the following. Send amount 0.00.

`transflags` value	Amount
`cit,init,avsonly`	`0.00`
`cit,init,recurring,avsonly`	`0.00`