Working draft · For review · Not yet search-indexed
merchant workflow

An independent vault before your merchant payment accounts

Atlas of Payments · Draft prepared November 12, 2026

The short answer

An independent vault can separate your stored-card reference from one processor. The value depends on supported downstream flows, lawful reuse and the cost of operating more than one payment route.

The operating model

An independent vault before your merchant payment accountsToken references stay in the merchant or platform application. A vaulting provider resolves permitted fields in its controlled environment and forwards to an authorized endpoint. A filtered response returns for reconciliation. Dashed lines indicate setup or response, not raw data.ATLAS OF PAYMENTS / CONTROL THE DATA PATH01 Merchant / platformToken reference + operation + account contextTokenized request02 Vaulting providerCONTROLLED SENSITIVE-DATA ENVIRONMENTForward proxy + vaultResolve permitted fields. Keep credentials scoped.Setup: allowed host + path + fields + callerApproved payload · TLS03 Payment gatewayValidate operation, account and permission04 Filter response + reconcileReconciled payment outcomeToken ≠ plaintext. Forwarded ≠ completed. PCI duties remain.
Illustrative forward-proxy path. Secure card collection occurs directly with the vaulting provider before this request. Dashed outcome path carries a filtered response, not permission to return card data.

What your team needs to do

  1. Inventory stored cards, current consent and processor export rights.
  2. Confirm each target gateway can accept the supported delivery or tokenization flow.
  3. Pilot a small eligible cohort; reconcile payments, recurring schedules, refunds and disputes.

Before you build

  • Card portability is not universal. Network tokens, processor tokens and vault tokens have different scope and lifecycle rules.
  • This is a research draft, not legal advice or a claim of provider availability. Validate current rules and the exact business model before implementation.

Measure the right outcome

Eligible completed orders, net cost and reconciled outcomes by approved route.

Questions operators ask

Will a vault guarantee payment acceptance?

No. A vault changes storage and data delivery. It does not change underwriting, law, provider terms or issuer decisions.

What should the team prepare next?

A one-page map of the business, jurisdictions, account ownership, consent, required operations and failure handling.

Validation notes

These vendor-neutral drafts describe architectural patterns, not certified integrations. A forward proxy can resolve token references for permitted outbound requests; inbound capture typically uses a separate collection or reverse-proxy flow. Validate exact behavior, endpoint contracts and permission. Some workflows need asynchronous batch transfer rather than HTTP forwarding. Industry outlines still need jurisdiction-specific review.

Make the next decision concrete

Write down the business model, account owner, required operation, permitted data and proof of completion. Resolve those five points before comparing providers.

Compare another use case →