Conduit alternatives for B2B stablecoin payments, by use case

For B2B stablecoin cross-border payments into Brazil, Mexico and Colombia, the best Conduit alternative with named BRL and MXN accounts and local payouts is Lumx, which also runs COP accounts. Bridge and UnblockPay list Brazil and Mexico rails, and BVNK lists USD, EUR and GBP rails.

Lumx wrote this post and competes with Conduit, so our row comes from our own documentation, and each competitor fact was read at its provider on November 10, 2026. For the two-sided view, see Lumx vs Conduit. For the same exercise on two other providers, see Bridge alternatives and BVNK alternatives.

What does Conduit document today?

Conduit (founded 2021) says on its About page that it is registered with FINTRAC in Canada and with FinCEN in the US as a money services business, and that it is not a bank: banking services come from third-party banking partners. Its home page offers USD accounts and wallets for a customer's own customers, routed across 8 US banking partners, with tiered pricing based on volume.

The home page lists SPEI (Mexico's interbank transfer system, run by Banxico) and Pix (Brazil's instant payment system, run by the Central Bank) among its rails and shows a Pix tile marked instant. The API documentation is narrower.

• Rails: the payout guide ties each fiat rail to a currency, with Fedwire, RTP, FedNow, ACH and same-day ACH for USD, SEPA for EUR, Faster Payments and CHAPS for GBP, and SWIFT for any currency the correspondent chain carries. The API reference also lists Pix, TED (Brazil's same-day bank transfer, business hours only), SPEI, ACH Colombia and NIBSS (Nigeria) as payout rail values.

• Accounts: named virtual accounts are offered in USD, EUR and GBP. The reference adds a Brazil deposit block for Pix and TED that collects on a shared account needing a payment reference, a Mexican block with a CLABE (the 18-digit Mexican bank account number) and a Colombian block over ACH Colombia that names the collecting institution rather than the customer.

• Production routes: the whitelist-recipient page says a Pix, Brazilian bank-account or UK sort-code registration is refused with a 503 RAIL_UNAVAILABLE error while Conduit has no payout route open on that rail. The documentation lists no per-corridor availability.

If Conduit refuses a Pix recipient at registration, the supplier you meant to pay this week stays unpaid, and your customer is the one asking you why. The home page also gives volume tiers and no rate card.

Lumx starts from the currency: a customer is created with an accounts array, and BRL, MXN, EUR, GBP and USD accounts are requested in one call, with COP available to any customer.

Which Conduit alternative fits which use case?

Each row from the provider's own documentation, read on November 10, 2026. Lumx row from docs.lumx.io and Lumx's own statements.

For a wider ranking, see the best stablecoin APIs in 2026 and Circle alternatives by job.

On every row Lumx works the same way: a deposit in local currency becomes stablecoin in a custodial wallet, and the wallet pays out over the rail you register. We built it that way because the rail should be a setting, not a new integration.

How do Conduit and its alternatives compare on rails and currencies?

Conduit: docs.conduit.financial and its home page. Bridge: apidocs.bridge.xyz. Due: due.readme.io. UnblockPay: docs.unblockpay.com. BVNK: docs.bvnk.com. Lumx: docs.lumx.io and Lumx's own statements as of November 9, 2026. All read on November 10, 2026.

Bre-B (Colombia's instant payment system, launched in 2025) is the third rail after Pix and SPEI. Lumx and Bridge list all three, and Lumx pairs the first two with a named account in the customer's own name. By Lumx's own statements, Bre-B is enabled per customer. It carries a cap of 1,000 UVB per transaction (COP 12,110,000 for 2026) for every provider, set by the Banco de la República's Circular Reglamentaria Externa DSP-465, and ACH Colombia has no per-payment limit, so a larger invoice goes over ACH Colombia.

BVNK's home page says it works with businesses processing at least $500,000 a month, with six months of operating history. Conduit states volume-based tiers. Lumx charges a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding, and publishes no plans. The standard agreement has a monthly minimum, with a ramp-up period that waives it in the first months. Every payout has a per-transaction limit, listed on the transaction limits page. The published rate cards are collected in stablecoin API pricing compared.

On the account behind the rail, Lumx issues a named virtual account, a local account number in the customer's own name, so a Pix payer sees the customer and not Lumx. Lumx's settlement targets, per its cut-off page: Pix, SPEI and Faster Payments instant, 24/7/365; Fedwire the same business day, with a 3:00 PM ET cut-off; ACH in one to two business days; SWIFT in one to five.

Choose by corridor before features

I recommend that a team leaving a provider write down its three biggest corridors before it opens a single sandbox. A rail listed in a schema tells you what an API accepts, and a route open in production tells you what the provider will settle, and only the second one moves money. I would ask every provider in the first call which of the two is true for each corridor, and drop the ones that cannot answer.

We think a provider should answer that question in public, so Lumx lists the live rails per currency on the coverage page. A rail is enabled for a customer by requesting its currency when the customer is created.

When switching from Conduit is the wrong move

Lumx is the wrong pick when you need a non-custodial wallet. Conduit documents both kinds, and a non-custodial payout there needs two signatures, the customer's and Conduit's. Lumx wallets are custodial, held by BitGo, which carries insurance, with each customer segregated and no omnibus account. A second integration also costs a vendor review, a KYB (know your business, the verification of a company and its owners) cycle for every customer and a parallel ledger, so it pays only where a corridor is missing.

Two more cases. Lumx has no FedNow, RTP or CHAPS rail. And it holds no license in the EU or the UK: SEPA and Faster Payments run through a banking partner, and UK customers are onboarded by reverse solicitation, with no marketing by Lumx there. In Brazil, Lumx Sociedade Prestadora de Serviços de Ativos Virtuais Ltda filed its SPSAV (the company type under the Brazilian virtual asset rules) authorization request with the Central Bank on October 27, 2026, and operates under the Article 88 transition regime of Resolution BCB 520/2025 until the Central Bank decides. Lumx is not a bank. In the US, Lumx US OP LLC is a FinCEN-registered MSB (money services business), with a sponsor bank behind the USD account.

Keep Conduit where it already settles every corridor you serve. Pick Lumx when the payees are in Brazil, Mexico or Colombia and your customer needs an account in its own name.

Testing an alternative against Conduit before you move

We suggest moving one corridor at a time and keeping the old provider running on the rest, so a failed first payment costs one corridor and not the whole book.

1. List every payee and corridor you pay today, and mark the ones that ride a SWIFT wire for lack of a local rail.

2. Ask each provider, in writing, to name the payout routes it will run for you, per rail.

3. Register one payee as a destination and wait for approval before the first payout.

4. Request a quote and confirm inside its window. Conduit's quote response carries an expiry time, and Lumx holds a locked rate for 30 seconds at no fee, or for 1 or 5 minutes for a fee.

5. Fund the new wallet. Conduit's payout guide documents crypto payouts to an external address with an attestation of who holds it, so confirm the purpose and attestation it requires for a custodian address before the first transfer.

6. Run both ledgers for one full cycle, then move the next corridor.

Lumx's sandbox is self-serve and covers every currency, so steps 3 to 5 can be rehearsed on testnet before a contract, and a real payee is the production check. Create an account on the dashboard and start from the environments page. The API integration typically takes two to three weeks to go live, and Lumx targets one business day for KYB review.

What this looks like on Lumx for a team coming from Conduit

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.

Picture your platform, with a Brazilian customer who has to pay a US supplier by Friday. The platform creates the customer with a BRL and a USD account and requests an on-ramp for the exact amount, and Lumx returns a Pix payload to show the payer. When the deposit lands, the BRL converts to USDC in the customer's wallet, and the platform receives an onramp.success webhook. An off-ramp to the supplier's approved destination follows over Fedwire or SWIFT in USD, with a UETR and an MT103 on every SWIFT payout. A payout held for a compliance check surfaces as an RFI (request for information, a compliance hold that asks for a document before a transaction clears).

In Mexico the same flow runs over SPEI. In Colombia the payout runs over Bre-B or ACH Colombia, chosen when the destination is registered. Lumx deducts no fee from what the recipient receives on a Pix, SPEI or Bre-B payout. A foreign company can hold a named BRL or MXN account without a local entity. Where Conduit's reference shows Pix collecting on a shared account with a payment reference, the Lumx account carries the customer's own name. The balance is stablecoin, not a deposit, because Lumx is not a bank. Product pages: named virtual accounts and global payments.

Methodology and sources

Conduit facts come from conduitpay.com (home and About pages), docs.conduit.financial (getting started, virtual accounts, add virtual accounts, send a payout, whitelist recipients, rail unavailable, non-custodial wallets, quote guide and the OpenAPI file for the payouts endpoint) and its sandbox API reference, all read on November 10, 2026. Bridge facts come from the supported-rails page on apidocs.bridge.xyz. Due facts come from its supported payment methods page on due.readme.io, updated November 5, 2026. UnblockPay facts come from docs.unblockpay.com, fiat payment methods and supported rails. BVNK facts come from the payment-schemes reference on docs.bvnk.com and the home page on bvnk.com. All of these were read on November 10, 2026. No provider was contacted.

Lumx facts come from docs.lumx.io, read on November 10, 2026: coverage, payment rail cut-off times, accounts, exchange rates, wallets and environments. The Colombia rails and the entity and license statements are Lumx's own, as of November 9, 2026, and the Bre-B cap comes from the Banco de la República circular read on November 1, 2026. Resolution BCB 520/2025 is cited as Lumx states it in its legal text, without a link, because bcb.gov.br serves only a JavaScript shell and the norm could not be read today. All names are trademarks of their owners, and Lumx is not affiliated with them.

Verified on November 10, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Ján Jakub Naništa on Unsplash.