A Bridge alternative depends on which Bridge product you are replacing: payments orchestration between fiat and stablecoins, custodial wallets, branded stablecoin issuance or Visa-backed cards. For the payments job, the main alternatives are Lumx, BVNK and Conduit; issuance and cards need different providers. The right pick follows your corridors, not a ranking.
Lumx wrote this guide and competes with Bridge on payments, so read our rows with that in mind. Bridge facts come from its API documentation read on November 2, 2026; other dates are in the methodology. The case that sends most teams searching: a Brazilian customer has to pay a US supplier, and your product needs to show the exact amount before they confirm. Quick answer by Bridge product:
Payments orchestration, to convert fiat to and from stablecoin and pay out locally: Lumx, BVNK or Conduit.
Custodial wallets: Lumx custodial wallets or BVNK.
Branded stablecoin issuance: none of the payment providers in this guide.
Stablecoin-backed cards: a card issuer such as Rain, with a payments provider that supplies the wallet balance the card spends.
The one-to-one detail is on Lumx vs Bridge.
What does Bridge sell, and which part are you replacing?
Bridge's documentation lists four products. Orchestration converts between fiat and stablecoins and moves the money in and out, with transfers, virtual accounts and liquidation addresses. Wallets are custodial. Issuance launches a branded stablecoin. Cards issues Visa cards that spend from stablecoin balances. Stripe has owned Bridge since February 2025.
On the fiat side, Bridge's supported-rails page lists ACH, FedNow, wire, SEPA, SPEI (Mexico's interbank transfer system), Pix (Brazil's instant payment system), Faster Payments (the UK's real-time bank transfer network), and Bre-B (Colombia's instant payment system) with bank transfer for COP. Its route explorer shows 19 blockchains.
Most teams searching for a Bridge alternative are replacing orchestration, where Lumx collects and pays out in BRL, MXN, COP, USD, EUR and GBP over local rails.
Five documented Bridge behaviors that send teams looking elsewhere
As of November 2, 2026. Bridge column from Bridge's API documentation; Lumx column from docs.lumx.io.
Behavior in Bridge's documentation | Where it bites | What Lumx does at that point |
The exchange rate endpoint refreshes roughly every 30 seconds, and Bridge states it does not offer a quote that locks a rate; it is an estimate | Showing an end user the exact amount before they confirm | A locked quote returns an |
The supported-rails page lists no SWIFT | Paying a supplier in a country with no local rail | SWIFT in USD, 1 to 5 business days, with UETR and MT103 confirmations on every payout |
Sandbox access starts with an email to Bridge support to be onboarded as a developer, and the sandbox is API-only | Time to a first test payment | The sandbox is open and self-serve, covers all currencies and rejects an invalid destination |
BRL and Pix access goes through Bridge sales, with a customer limit of $1,000,000 a month in USD equivalent until enhanced KYB or KYC is approved | How fast a large customer can move volume | Bridge's default is the higher one. Lumx defaults: KYB Standard $50,000 per transaction and $100,000 daily and monthly, KYC Standard $15,000 monthly. Enhanced limits are set per customer from the documents submitted. Limits apply per transaction type, and an increase request goes through the dashboard or the API |
Developer fees are withheld per transfer and paid out monthly, always in USD | Platform revenue timing | A partner fee in basis points or a flat amount, sent to the wallet address you choose, and part of the locked quote when you lock |
On limits, Bridge's default is higher, so a team with large single customers should ask for the Enhanced limit before choosing. None of these decides the choice alone. Together they describe a platform built for a US-first developer who wants issuance, cards or many chains.
Which provider replaces which part of Bridge?
As of November 2, 2026 for Bridge and Lumx; as of September 2026 for the other providers, per each provider's public documentation as summarized on the linked Lumx comparison pages.
Bridge product | What it does | Alternatives to look at | Who it fits |
Orchestration | Converts between fiat and stablecoin and pays out over local rails | Lumx global payments, Lumx vs BVNK comparison, Lumx vs Conduit comparison | Payments teams that choose by corridor: which rails and which accounts are live today |
Wallets | Holds stablecoin balances for customers or the company | Lumx custodial wallets, BVNK | Products that hold a balance for their own users and pay out from it |
Issuance | Launches a branded stablecoin | None of the payment providers here; start from the issuers themselves, as in Circle alternatives by job and Lumx vs Circle | Companies that want their own dollar token |
Cards | Visa cards that spend from a stablecoin balance | A card issuer such as Rain, with a payments provider for the wallet balance | Fintechs launching a card; the payments provider supplies the wallet balance the card spends, and the issuer stays your own provider |
BVNK and Conduit only replace orchestration, and the comparison pages above cover each against Lumx. See BVNK alternatives.
Lumx fits the first two rows and supplies the balance for the fourth. A deposit in local currency becomes stablecoin in a custodial wallet, and the wallet pays out over any rail. A Rain card can spend straight from the Lumx wallet balance. The top-up is a local deposit over Pix, SPEI or PSE (Colombia's online bank-transfer network) that converts to stablecoin in the wallet, and the cash-out is an off-ramp from the wallet. The card issuer stays the customer's own provider.
Rails and accounts: Bridge and three payment providers side by side
Bridge and Lumx cells as of November 2, 2026, from Bridge's API documentation and docs.lumx.io. BVNK and Conduit cells as of September 2026, per each provider's public documentation, from the Lumx comparison pages verified on September 16 and 17, 2026.
Criterion | Bridge | Lumx | BVNK | Conduit |
Brazil (BRL) | Pix; the BRL virtual account returns a Pix BR Code; access through sales | Pix in and out; named BRL account | No BRL | Pix on the marketing site, not in the payouts API |
Mexico (MXN) | SPEI | SPEI; named MXN account | No MXN | MXN marketed through FX pages; no MXN account |
Colombia (COP) | Bre-B and bank transfer | Collect over Bre-B and PSE; pay out over Bre-B or ACH Colombia | No COP | COP marketed through FX pages |
USD to countries with no local rail | No SWIFT on the rails page; ACH, FedNow and wire | SWIFT in USD, 1 to 5 business days | SWIFT in USD, EUR and GBP | SWIFT in any correspondent currency |
Wallets | Custodial, 19 blockchains | Custodial, segregated per customer, on Ethereum, Polygon, Base and Tron, plus Stellar for BRL on-ramps | Custodied wallets, USDC on six chains | Custodial, plus a separate non-custodial product |
Published rate card | None in its docs; developer fees are configurable | Monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans | None; a stated monthly volume minimum | None |
Brazil is the clearest split: Bridge and Lumx document Pix and a BRL account. The rate cards are collected in stablecoin API pricing compared.
Lumx runs Pix, SPEI, Bre-B, ACH Colombia, ACH, Fedwire, SEPA and Faster Payments plus SWIFT in USD, with virtual accounts in six currencies, named in five and, for Colombian customers, in COP. See the coverage page and supported countries.
Who is regulated, and how do Bridge and its alternatives compare?
Bridge as of September 2026, per the Lumx comparison page on Bridge. Lumx as of November 2, 2026.
Regulatory point | Bridge | Lumx |
United States | FinCEN-registered MSB (money services business) with money transmitter licenses in 32+ states; conditional OCC approval to organize a national trust bank, February 17, 2026 | Lumx US OP LLC, a FinCEN-registered MSB |
European Union | MiCA and EMI (electronic money institution) authorizations across 27 member states, July 2, 2026 | EUR and GBP legs run through a banking partner |
Brazil | Not covered by the pages read | Lumx SPSAV Ltda filed its SPSAV authorization request and operates in the transition regime under Resolution BCB 520/2025, Art. 88. It is not yet authorized and is not a bank |
Screening and custody | Not covered by the pages read | KYB and KYC through Sumsub, Chainalysis KYT for blockchain activity, wallets custodied by BitGo, which carries insurance, each customer segregated, no omnibus account |
Bridge's license footprint in the US and EU is broader than Lumx's. In Brazil, Lumx has a filed application under a transition rule, not an authorization. More in are blockchain payments legal.
How to choose by corridor, not by vendor
Start from the three countries where most of your money lands, and find the rail, account type and limit each provider documents.
When a team already runs on Bridge, I ask for the list of corridors where the local rail or the account in their customer's name is missing, and I suggest a second provider only for those. A second integration is a cost of its own, so if the list comes back empty, a switch buys nothing.
Then run the same test payment through each sandbox and compare the amount that lands in the recipient's bank. The vocabulary is in what a stablecoin API is and the criteria in choosing a stablecoin infrastructure provider.
For Brazil, Mexico and Colombia, Lumx's answer at this step is a named account in the customer's own name in BRL and MXN, a COP account that is named for Colombian customers, a payout over the local rail and a locked quote before the customer confirms. Wider rankings: the best stablecoin APIs in 2026 and stablecoin APIs for Latin America.
Can you run Bridge and an alternative together?
Yes, and it is the right answer when your product is built around Bridge's issuance, card program or 19-blockchain footprint. No payment provider in this guide replaces a branded stablecoin or a Visa card program. The split follows the job: Bridge keeps issuance, cards and multi-chain balances, and the alternative holds the fiat legs where Bridge's documentation shows no rail or account type you need. Both sides settle in USDC on Ethereum, Polygon and Base, so moving a balance between them is a transfer, not an FX event.
Reconciliation costs the most time. Bridge requires an idempotency key on creates. Lumx accepts an Idempotency-Key on every create and caches the response for 24 hours, so send one on all of them. Lumx's own legs report through onramp.success, offramp.success and transfer.success webhooks, so one ledger can follow them next to Bridge's events with a field for the provider.
Lumx's transfer endpoint sends stablecoin from a customer wallet to any external wallet address, and transfer.success confirms the Lumx leg. That is the hand-off point between the two providers.
What to test when moving a Bridge integration
Map the objects first. Bridge customers, virtual accounts and external accounts become customers, then accounts, then destinations on Lumx. Both platforms verify a customer first: KYB (know your business, company verification) for companies and KYC (know your customer, individual verification) for people. Lumx adds a holder relationship and a purpose code on each payout, so collect those fields up front.
Then test the behaviors that differ. Request a locked quote and confirm inside the window instead of reading an estimate. Subscribe to the on-ramp, off-ramp and transfer webhooks and run both ledgers in parallel for one cycle. The wider checklist is in migrating a stablecoin payout provider.
Lumx's API integration typically takes two to three weeks to go live, and Lumx targets one business day for KYB review. The sandbox is open, so run the test payment first: create an account on the dashboard and start from the environments page.
What this looks like on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
Take the Brazilian customer paying a US supplier. The platform requests a BRL account and an on-ramp for the exact amount, and Lumx returns a Pix payload to show the payer. When the deposit matches, the BRL converts to USDC in the customer's wallet and the platform gets an onramp.success webhook. An off-ramp to the supplier's approved destination follows over Fedwire or SWIFT in USD. A payout held for a compliance check surfaces as an RFI (request for information).
Wallets are custodial and segregated per customer, held by BitGo. The balance is stablecoin, not a deposit, because Lumx is not a bank. See named virtual accounts and global payments.
Methodology and sources
Bridge facts come from Bridge's API documentation, read on November 2, 2026: rails, exchange rates, sandbox, BRL guide, developer fees and products. The Stripe ownership date and Bridge's license footprint come from the Lumx comparison page on Bridge, verified on September 16, 2026, which cites Bridge's announcements of February 17 and July 2, 2026. BVNK and Conduit facts come from the Lumx comparison pages for each, verified on September 16 and 17, 2026 against each provider's public documentation. Rain's real-time funding comes from Rain's own site, read on October 29, 2026.
Lumx facts come from docs.lumx.io, read on November 2, 2026: coverage, exchange rates, accounts, wallets, transaction limits, partner fees, idempotency and payment rail cut-off times. No provider was contacted. Bridge, Visa and Stripe are trademarks of their owners, and Lumx is not affiliated with them.
Verified on November 2, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Humberto Santos on Unsplash.
What are the best Bridge alternatives for stablecoin payments?
It depends on the Bridge product you are replacing. For payments orchestration the alternatives are Lumx, BVNK and Conduit; for cards, an issuer such as Rain; for a branded stablecoin, none of these. Lumx covers the orchestration and wallet jobs, with accounts in six currencies, named in five and for Colombian customers in COP, and payouts over local rails in Brazil, Mexico and Colombia.
Which Bridge alternatives can wire USD to a country with no local rail?
Bridge's supported-rails page lists no SWIFT. Per the Lumx comparison pages, BVNK lists SWIFT in USD, EUR and GBP and Conduit in any correspondent currency. Lumx sends SWIFT in USD, settles in 1 to 5 business days and returns UETR and MT103 confirmations on every payout.
Which Bridge alternatives pay out to a Brazilian bank account over Pix?
Bridge and Lumx document Pix. BVNK lists no BRL, and Conduit shows Pix on its marketing site but not in its payouts API, per the Lumx comparison pages. Lumx pays out over Pix to a destination registered with a CPF (Brazilian individual taxpayer ID) or CNPJ (company taxpayer ID) key, and Pix runs 24 hours a day.
How long does it take to test a Bridge alternative?
Bridge issues sandbox access after an email to its support team. Lumx opens a self-serve sandbox on sign-up with every currency, and API integration typically takes two to three weeks to reach production.
Are Bridge alternatives regulated?
Per the Lumx comparison page, Bridge holds FinCEN MSB registration, state licenses, a conditional OCC approval and MiCA and EMI authorizations. Lumx US OP LLC is a FinCEN-registered MSB, Lumx SPSAV Ltda has filed its SPSAV request and operates under the Article 88 transition of Resolution BCB 520/2025, and Lumx is not a bank. It runs KYB and KYC through Sumsub, Chainalysis KYT for blockchain activity, and wallets custodied by BitGo.
