Stripe Issuing Transition — FAQ

Last updated: April 22, 2026

Cards & Migration

Will existing cards continue to work after the migration, or will they need to be reissued?

Card reissuance will be required for existing cards. The target date for all new card creation and card reissuance will be July 31, 2026. During the migration period, we will provide on-call engineering support to minimize disruption to your cardholders. All fees associated with reissuing cards will be waived.

Will there be any BIN change?

The new cards will be issued on a new BIN. Note that all 18 existing countries remain available under the new Stripe integration, so there is no reduction in coverage as a result of any BIN changes.

What happens to recurring subscriptions and saved payment methods when cards are reissued?

We are working with Visa on confirming the plan for recurring subscriptions, including whether a mechanism like Visa Account Updater can propagate new card details to merchants automatically. We will share more information once this is confirmed. 

Will cards already tokenized in Apple Pay / Google Pay need to be reactivated?

Stripe Issuing has full support for push provisioning card details to mobile wallets, enabling cardholders to add their card directly to Apple Pay and Google Pay without manually inputting details. Stripe provides an SDK that integrates seamlessly with both Apple Pay and Google Pay, and we will work with Apple to update your push provisioning approvals to include the new card.

All existing marketing and card art will also be migrated to the new instance, and our team will complete this migration on your behalf.

For your cardholders, cards will likely need to be re-tokenized.

Is there a way to avoid running two parallel card programs simultaneously during the migration?

The target date for all new card creation and card reissuance will be July 31, 2026. Our goal is to make the migration as seamless as possible and reduce the need to manage two card programs at once. We will work with you to reissue cards for the existing cardholder population and coordinate timing to ensure a smooth cutover from old card closure to new card activation. 

KYC & Identity Verification

Will existing users need to re-KYC, and are there any changes to the KYC or endorsement flow on our end?

No. The end-to-end KYC experience will remain entirely with Bridge — Stripe will primarily be used to power card issuance and management. Existing KYC'd cardholders will not need to re-verify, and no additional endorsement requirements are introduced by this migration. There are also no expected changes to your KYC implementation. New cardholders will continue to use the existing Bridge KYC flow as before.

Will there be any changes to the KYC/endorsement flow or implementation on our end?

No changes are expected to the KYC or endorsement flow as part of this migration. The Bridge team will also work on migrating your 3DS preferences over to the new integration, so no action will be required from your team there either.

Balances & Wallets

How will existing balances be handled during the migration, and how will consistency be maintained between our wallet and Stripe Issuing?

There is no separate Stripe Issuing balance — the card will remain linked to the existing Bridge Wallet. No funds need to be moved, and there will be no cost associated with the transition. Customers will not need to take any action regarding their balances or wallet setup. Cardholders can continue to spend from any stablecoin balance, custodial or noncustodial, exactly as they do today.


Will customers need to take any action during the transition, such as re-approving a new delegate or moving funds?

No. There will be no changes to the existing model, and no action will be required from customers regarding their balances or wallet setup.

Transactions & Settlement

How will the settlement cycle work under the new integration?

Settlements remain the same. The card's wallet does not change, and Bridge's interaction with it remains consistent. At the time of authorization, funds will be pulled from the linked wallet. When the authorization is captured (typically the next business day), if the final amount differs from the authorized amount, funds will be returned to the wallet if the final amount is lower, or additional funds will be pulled if the final amount is higher.

Features & Parity

Will there be full feature parity with the current integration?

Yes. We do not anticipate any feature degradation with this new integration. Cardholders will be able to spend with the same usage limits, and mobile wallet support including Apple Pay and Google Pay push provisioning will be fully supported from day one — see the Cards & Migration section above for details on re-tokenization. 

Are there any new features or improvements included in this migration?

Yes. This migration introduces several meaningful improvements:

  • Disputes API: You can now submit disputes via the Stripe Dashboard or through the Disputes API for a more custom experience. Provisional credits and refunds will be pushed directly to the end cardholder's wallet. This allows for easier handoff between your support team and Bridge's internal dispute investigations. For cardholders who prefer phone support, a new number will be provided.

  • Physical Cards: Stripe Issuing enables you to issue fully custom or standard physical cards, with delivery to cardholders in as little as 2 days.

  • ATM Access: ATM access is now supported as a new capability.

  • Expanded Geo Coverage: All 18 existing countries remain available, with Angola, Jamaica, Cayman Islands, and BVI coming imminently. Bridge is on track to be in 100 countries by the end of year.

  • More Robust APIs: Stripe Issuing offers richer endpoints (e.g. card reissuance), better documentation, faster iteration cycles, and advanced spend controls and velocity limits — reducing the need for custom internal tooling.

  • Support as a Service: Stripe's trained support agents can handle cardholder phone support on your behalf, either under a generic greeting or customized to your brand.

Please refer to the Transition Guide for a full feature comparison and additional details.

Timeline

What is the expected timeline for the migration?

The timeline for migration is July 31, 2026.