If you are trying to cascade or fail over a payment between two different Stripe accounts, you have probably already hit the core problem: a PaymentMethod ID or card token created under one Stripe account is scoped to that account. Try to reuse it on a second Stripe account, and the transaction will fail.
The fix is not a Stripe-specific workaround. It is a different approach to how you store and forward card data in the first place.
The problem: cascading payments between two Stripe accounts
When a customer pays through Stripe, their card details are tokenized into a PaymentMethod object tied to that specific Stripe account. If you then try to route the same payment to a second Stripe account during a cascade or retry, that token is meaningless to the second account. It cannot read or process credentials issued by another account.
The only way to cascade reliably across two Stripe accounts is to store the card independently of both, in an agnostic vault that can generate and forward the right credentials to whichever account you route to. That requires a payment orchestration layer sitting above Stripe, not within it.
The solution: Primer
Primer is built precisely for this problem. Its Agnostic Vault is PCI DSS Level 1 certified and processor-independent by design. Card details and network tokens are stored centrally, not tied to any individual PSP or Stripe account.
When a transaction is routed to Stripe account A and fails, Primer can immediately retry via Stripe account B using the same vaulted token, with no dependency on either account's native tokenization.
If tokens are stored with a payment processor, they are often locked to that processor's environment and cannot be reused with another provider. Primer's vault eliminates that constraint entirely.
The practical setup for two Stripe accounts is straightforward:
- You configure both accounts as separate processor connections in Primer, each with its own API keys.
- You then define a Fallback workflow in Primer's no-code workflow builder that routes to Stripe account A first, and automatically retries via Stripe account B on decline or failure.
- No engineering is required to change the routing logic once it is set up, and the workflow can be adjusted in the dashboard without touching code.
For network tokens specifically, Primer registers as a token requester directly with Visa and Mastercard, generating network tokens that are stored in its agnostic vault and can be used across any connected processor, including multiple Stripe accounts. Stripe requires accounts to be gated in for Bring Your Own Token (BYOT) before processing external network tokens, so that step needs to be completed with your Stripe account manager before enabling network tokens in a Stripe cascade.
Beyond the cascade itself, Primer gives payments and finance ops teams full visibility: every transaction, retry, and decline reason appears in a single dashboard with breakdown by processor, BIN, MID, and decline code. That makes it straightforward to monitor how each Stripe account is performing and tune the cascade logic accordingly.
To see how Primer would work for your specific Stripe setup, book a call
FAQ
Can Stripe PaymentMethod IDs be shared across multiple Stripe accounts?
No. A PaymentMethod ID or card token created under one Stripe account is account-scoped and cannot be reused under a separate Stripe account. Attempting to do so will result in a resource or token error because the second account has no access to the original credential. To enable cascading between two Stripe accounts, the payment method must be stored outside both accounts in a processor-agnostic vault.
Is Stripe Connect a solution for cascading between two Stripe accounts?
Not in this context. Stripe Connect allows platforms to operate on behalf of connected accounts, but PaymentMethod objects are still scoped to the account in which they were created. Cascading between two standalone Stripe accounts requires an orchestration layer that stores card data independently and can provision credentials dynamically to each account.
FAQ
Do network tokens automatically solve cross-account Stripe cascading?
No. Network tokens improve authorisation performance and lifecycle management, but they must be provisioned in a way that is not locked to a single processor environment. To cascade between multiple Stripe accounts, network tokens need to sit inside an agnostic vault that can generate and forward credentials to whichever Stripe account is selected in the routing logic.
.png)
