How does credential on file work?
The first payment is customer-initiated: the customer enters the card and agrees to store it. Visa Acceptance Solutions’ guide says all credential-on-file transactions begin with a customer-initiated transaction, that the merchant must get the customer’s consent to store payment credentials and disclose how they will be used, and that later merchant-initiated transactions reference the transaction ID of the original. Storage is usually a token, either in a provider’s or platform’s vault or as a network token issued by the card scheme.
Why does credential on file matter for approval rate?
Correctly flagged stored-credential payments look familiar to issuers, and repeat customers skip the card form. The weak point is staleness: cards expire and are replaced. Adyen’s documentation says a network token stays the same when the shopper receives a new card because the old one expired or was lost. As an illustrative example: a merchant with 30,000 saved cards and 2% reissued each month would see 600 saved cards a month start failing without network tokens or an updater.
What are the risks?
Storing card numbers brings PCI DSS obligations, which tokens reduce. Mis-flagging merchant-initiated payments as customer-initiated, or the reverse, can cause declines. And customers must be able to see and remove saved cards.
Where does Omno use it?
Omno’s saved cards let customers save a card in the hosted checkout and pay with it next time. Cards are stored as tokens in Omno’s PCI DSS compliant environment at the orchestration layer, so a saved card can be routed and cascaded to eligible providers like a newly entered one, and issuers can still request 3-D Secure in the same flow.