Skip to main content
Vaulting Customer Cards Adds a Custody Question to Approval

Vaulting Customer Cards Adds a Custody Question to Approval

Get started with SeamlessChex
Written by
Lily Flanigan
Staff member logging graded trading cards into a vault inventory system in a secure storage room
Summarize this article with AI
Open it in your preferred AI engine for an instant summary.

Quick Answer

Yes. Holding customers' physical cards adds a custody obligation underwriters weigh separately from sales, and a vault-inventory reconciliation tying each card to a customer and a transaction answers it.

Our underwriting team reads delayed fulfillment, stored balances and buybacks as parts of that obligation. One honest trade-off: a processor's token vault can take card data off your hands. Nobody can take the cards themselves. No published figure yet shows how much faster a clean vault file clears.

Did this answer your question?

Key Points

  • Stanford University IT's breakdown of PCI DSS 3.2.1 lists 329 questions on SAQ D for merchants storing card numbers, against 22 on SAQ A.
  • In September 2026, the SeamlessChex underwriting team set out five priced elements for rip and break platforms, including delayed physical fulfillment of vaulted cards.
  • Writing in 2023, Rajat Deshpande reported one SaaS company saw a 60% decrease in active Indian subscriptions after merchants were barred from storing card details.
Three things platform operators believe. Myth or fact?
Call each one, then see how other readers called it.
1 Tokenizing stored payment cards removes custody from the merchant entirely.
2 Underwriters price a vaulted physical card as delayed fulfillment, separate from the sale itself.
3 Buybacks get reviewed as a cash-out path, not just a resale feature.
Staff member logging graded trading cards into a vault inventory system in a secure storage room

Every vaulted card should tie back to a customer and a transaction.

For a platform that vaults customer cards, the strongest fit is a high-risk credit card merchant account whose underwriter can see your custody controls beside your sales.

Our underwriting team prices rip, mystery-pack and break platforms on five elements. Of those, I watch delayed physical fulfillment most closely, because that is where a card sitting in your vault becomes a promise still open. Stored-card rules can also shift under a merchant. In 2023, the Reserve Bank of India's recurring-payment guidelines required customers to re-authenticate recurring card transactions under Rs 15,000. Physical cards have no rulebook like that. Your own file has to carry the proof.

Custody rules can change faster than a business model. Writing in 2023, Rajat Deshpande described how India's central bank barred merchants from storing card details from January 2022, and one SaaS company reported a 60% decrease in active Indian subscriptions as cards stopped working. That was payment data. Physical cards are different. No rulebook covers a vault of graded cards held for customers. Underwriters still have to price it, and they start with who answers when a card goes missing.

Ready to put your vault file in front of an underwriter?

SeamlessChex boards rip and break platforms for high-risk credit card processing, with ACH as a supporting rail for payouts. Bring your three ledgers. We'll review them with you.

What are underwriters actually pricing when a platform holds cards?

Our underwriting team prices five elements at rip and break platforms, and one of them is delayed physical fulfillment: the pulled card ships later or stays vaulted.

Here is the full shape our team laid out in September 2026, in the order I'd map it on an application:

  • Prepaid credit: the customer funds a balance before buying.
  • Randomized outcome: the pack or break spot delivers an unknown card.
  • Delayed physical fulfillment: the card ships later or stays in the vault.
  • Stored balances: customer money held on the platform.
  • Buybacks: the platform repurchases pulled cards, which is a cash-out path.

The common assumption is that custody means payment data. That half can largely be handed off. In 2025, Mastercard described its model as one where the token service provider, not the merchant, stores saved card data and keeps it up to date. NHI Mgmt Group adds that the underlying data stays with "the issuer or another authorised tokenization service." One question worth asking an underwriter early is how they treat cards a customer has left unclaimed, since that is where delayed fulfillment and stored balances overlap. PCI DSS, as Stanford University IT summarizes it, already expects physical security measures and a named contact person wherever card data is held.

Across 4 sources, one pattern holds. Each source treats custody as something a named party must answer for. The question to settle before you apply is which of the five elements your file already documents, and which still rests on your word. That is why a platform should apply for high-risk credit card processing as what it is, not as a card shop, because the vault is where the underwriter's next question lands.

Why does custody outlast the customer relationship?

Stored relationships keep running after customers forget them. A saved credential or a vaulted card can still trigger charges, claims and disputes long after the buyer stopped paying attention.

A May 2025 r/Banking thread shows how this plays out on the payment side. The poster cancelled a credit card after a scam charge and was issued a new number. A new unauthorized charge appeared before the replacement card had even arrived. Chase's fraud team, per the poster, traced it to merchants linked to the account, including some the poster had not used in years.

The plumbing explains it. Processor vault tokens have been described as "blind to card lifecycle changes such as reissues and BIN migrations." Network tokens work the other way: one payments vendor pitches them as following the cardholder automatically to the new credential. Neither model asks whether the customer still wants the link.

I read that as a warning for anyone holding physical goods. A graded card that sits untouched in your vault is still your obligation. The customer who forgot it may remember it during a dispute. Unclaimed inventory is the physical version of a dormant stored credential, and it lands on the same desk when an acquirer reviews your merchant payment processing file for the questions underwriters ask next.

How much card custody can a rip or break platform hand off?

Store your customers' card numbers yourself and the annual PCI self-assessment runs to 329 questions. Hand them off, and the shortest version has 22. So what exactly gets handed off, and what stays?

The figures come from Stanford University's IT office, which lays out the eight PCI self-assessment questionnaires for its campus merchants under version 3.2.1 of the standard. Every questionnaire except SAQ D carries the label "no electronic cardholder data storage," so a platform that keeps card numbers in its own systems lands on the long form. The shortest, SAQ A, fits merchants who send buyers to a third-party processor and "cannot impact the security of the payment transaction."

SAQ A: redirect to a third party 22 questions
SAQ C-VT 79 questions
SAQ C 160 questions
SAQ D: stored card data 329 questions
What storing card data costs in paperwork. Questions on four PCI self-assessment forms, from Stanford University IT's breakdown citing PCI DSS 3.2.1 (undated page).

Tokenization is how the card number moves. Mastercard helped introduce the tokenization standard in 2013. It says that once a saved card is tokenized, the token service provider "stores the card data and keeps it up to date," and the merchant "never sees or stores" the real number. That provider can be a network, the issuer or another company that meets industry standards. Adnan Masood, PhD, in a December 2025 technical guide to tokenized payments, writes that earlier processor vault tokens did the same for an older generation of merchants, "shifting compliance and security responsibilities to PSPs."

The two kinds of token behave differently when a card changes. Masood calls processor vault tokens "blind to card lifecycle changes such as reissues," while network tokens get updated centrally when a card is reissued, suspended or replaced.

Handing off the number moves the risk to a new place without removing it. NHI Mgmt Group, a publisher focused on identity and access security, warns in a glossary entry updated October 31, 2026, that tokens "can also create false confidence if organisations treat tokens as harmless placeholders." The targets shift to token vaults, detokenization APIs and callback paths. The group's guidance reads like a custody checklist: manage issuance, rotation, expiry and revocation, limit redemption to the fewest roles possible, and "inventory and govern tokens throughout their lifecycle." Masood agrees that after tokenization, the main risks are a breach of the vault or token provider and account takeover.

Stored credentials also outlast customers' attention. In May 2025, a cardholder on a banking forum described cancelling a card after a scam charge, then seeing a new unauthorized charge before the replacement even arrived. Their issuer's fraud team said the new details had gone to merchants they had not used in years. One post cannot show how often this happens, and commenters disputed who controls those updates. Still, it shows what a stored credential can do when nobody keeps track of it.

A rip or break platform holds a second kind of custody. Our underwriting team prices delayed physical fulfillment as its own element: the pulled card ships later or stays in the vault. None of our sources discuss physical collectibles, so what follows is our inference. No token service provider exists for a graded card on a shelf, so custody of that card starts and ends with the platform. PCI already treats physical custody as a duty when card data is on paper. Stanford requires documents holding card data to sit in locked storage open only to trained, authorized staff, and each merchant names a PCI contact to "monitor, document, and manage" card acceptance. The same idea fits a vault of pulled cards: a named owner, a locked room and a record.

What the platform holdsWho has custodyWhat the platform still answers for
Raw card numbers in its own systemsThe platformSAQ D, the 329-question form
Processor vault tokenThe payment provider's vaultSaved cards that may break on reissue, since Masood calls vault tokens "blind" to reissues
Network tokenA token service provider: network, issuer or another standards-compliant companyA token inventory, who can redeem tokens and how lifecycle events are handled, per NHI Mgmt Group
Pulled card held in the vaultThe platformEvery item tied to a customer and a transaction (our inference; no outside custodian exists)

A card number can leave your systems. The inventory stays with you. Even when a provider holds every saved card, the guidance still expects the merchant to know which tokens it has, who can redeem them and what happens when a bank reissues a card. Nobody outside the platform can take over that work for pulled cards in the vault. A reconciliation that ties each card to a customer and a transaction is the platform's own version of a token inventory.

  • Before you pick a self-assessment form, list every place a card number could end up, including support tools, spreadsheets, logs and backups.
  • Ask your processor or gateway whether your saved cards sit behind vault tokens or network tokens, and who holds the underlying card numbers.
  • Write down who can redeem a stored token, cut that list to the fewest roles possible, and confirm that card lifecycle events reach your billing system.
  • Ask your provider whether tokens for dormant customers keep updating when banks reissue cards, and set a rule for expiring or revoking them.
  • Keep a vault ledger that ties each pulled card to a customer and a transaction, and treat it the way the guidance treats a token inventory.

How we checked this

We used a university PCI compliance page, a card network's explainer on tokenization, a technical guide by an independent author, a security publisher's glossary entry, a consumer forum thread and our own underwriting team's notes. The five-element pricing framework, including delayed physical fulfillment, is ours and comes from our underwriting team in September 2026. Stanford's page was written for campus merchants and cites PCI DSS 3.2.1, so question counts may be different under later versions. The forum post is one unverified person's account. Mastercard runs a token service and has an interest in promoting tokenization. We board rip and break platforms, so we have a stake here too. Still unknown: none of our sources cover custody of physical collectibles, and none measure whether a clean vault reconciliation shortens underwriting review.

  1. Stanford University IT, PCI DSS requirements and SAQ types, undated, citing PCI DSS 3.2.1.
  2. Mastercard, explainer on what tokenization is, March 18, 2025.
  3. Adnan Masood, PhD, guide to building a tokenized payments stack, December 3, 2025.
  4. NHI Mgmt Group, glossary entry on card on file tokenization, updated October 31, 2026.
  5. r/Banking, forum thread on reissued cards reaching old merchants, May 1, 2025.
  6. SeamlessChex underwriting team notes on rip, mystery-pack and break merchants, relayed by Chris Daniels, September 4, 2026.

What should a vault-inventory reconciliation show an underwriter?

A clean reconciliation ties every vaulted card, every stored balance and every buyback to a customer and a transaction, so custody is provable before anyone asks.

Our underwriting team's view is that the application should describe each element of the business and how it is controlled. For the vault, I'd build the routine around three ledgers that reconcile to each other:

  1. Vault inventory: every physical card held, matched to one customer and one status (vaulted, shipped, sold back).
  2. Stored balances: every customer balance matched to the card transaction that funded it.
  3. Buybacks: every repurchase matched to the vault item it removed and the payout that settled it.
LedgerWhat it provesUnderwriting concern it answers
Vault inventoryEach held card has an owner and a statusNon-receipt disputes from delayed fulfillment
Stored balancesCustomer money traces to a funded saleFuture-delivery and refund exposure
BuybacksCash leaving matches inventory leavingMoney-movement and cash-out review

The payment side offers a useful template. Adnan Masood's 2025 breakdown of tokenized payment stacks says robust vaulting needs strict access control and lifecycle events fed into billing systems. Before you apply, run the three ledgers against each other and clear every unmatched item, so the file you hand over shows no open questions. Access to the vault should be limited to named staff. Every status change should post to the ledger the same day.

No published standard tells you which fields an acquirer will accept, and I won't pretend one exists. What the routine does is answer the delayed-fulfillment and buyback questions up front. It also gives you a fair test when choosing a high-risk credit card processing company: ask whether it already boards platforms of this shape. If you settle buybacks by ACH bank transfer, that payout trail belongs in the third ledger too.

Will custody become a standard approval question?

For platforms that hold customer cards, it already is one. The operators who document their vault before an underwriter asks give the underwriter something concrete to approve.

A quick self-test helps here: can you list, in one sitting, every card detail your own systems still hold? A typical card-on-file setup still keeps expiry and cardholder name beside each token, even when the raw card number lives elsewhere. Tokens shrink custody. So ask your processor which of those fields it holds for you, and which ones your own systems still keep.

Physical cards make that plainer still. In our underwriting team's framing, delayed fulfillment and buybacks sit inside the profile being priced, not beside it. I can't give you an approval-time figure for platforms with custody controls versus those without, because that data isn't on record. What I can say is where I'd start: three ledgers that reconcile, a named custodian, and a vault an underwriter can audit from the file alone.

Frequently Asked Questions

What else do operators ask about card custody and approval?

Most follow-up questions come down to three things: who carries the custody risk, how dormant stored cards turn into disputes, and how quickly an application can move.

Does a processor's token vault take the custody question off my application?

Only for card data. Adnan Masood's 2025 breakdown notes that vault tokens (stand-ins a processor issues for stored card numbers) shrink PCI DSS scope but lack network-wide lifecycle intelligence. The physical cards sitting in your vault stay your responsibility.

Can a stored card the customer forgot about turn into a dispute?

Yes. Issuers can pass new card details to merchants linked to an account, so a charge can land on a card the customer thought was dead. That customer is far more likely to call it unauthorized than to remember the original permission.

How quickly can a platform that vaults cards get started with SeamlessChex?

SeamlessChex offers same-day onboarding with no contracts for established businesses processing $25,000 or more per month. Underwriting still reviews your custody file. Bring the vault reconciliation to the conversation on our contact page.

Written by

Lily Flanigan

Operations Manager, SeamlessChex

Lily Flanigan is Operations Manager at SeamlessChex, a credit card processing and fintech payments platform recognized on the Inc. 5000, where she focuses on operations and process optimization.

Connect on LinkedIn

SeamlessChex works with established businesses processing a minimum of $25,000 per month.

Need a processor?
Credit card processing that gets you approved—and keeps you processing.
Open a merchant account