Vault upstream of each child merchant account
The short answer
A merchant-scoped vault keeps token ownership and access boundaries aligned to each connected merchant. The platform can coordinate requests without assuming tokens or consent transfer across accounts.
Where does the vault sit?
Upstream of the parent platform account: a platform-managed token layer with explicit per-merchant permissions.
Upstream of each child merchant account: merchant-scoped storage and forwarding boundaries.
Neither design makes tokens interchangeable or changes merchant-of-record and settlement responsibilities.
What your team needs to do
- Define a separate vault tenant or equivalent enforced merchant boundary for each connected account.
- Bind token access, customer consent, credentials and endpoint rules to that merchant.
- Design merchant offboarding, export rights and reconciliation so account isolation persists through migration.
Before you build
- Vault placement alone does not determine merchant of record, charge ownership, settlement, liability or PCI scope. Confirm the gateway account model and permitted token/data flow.
- Use merchant-scoped permissions, destination allowlists, idempotency, redacted logs and explicit consent. A vault does not override underwriting or business restrictions.
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.
Integration considerations
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 eligibility depends on jurisdiction and provider underwriting.
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.