BVNK alternatives for cross-border payments in 2026

BVNK alternatives for cross-border payments are stablecoin APIs that pay and collect over bank rails, and the right one depends on the corridor. Lumx and Bridge document local rails in Brazil, Mexico and Colombia. Conduit and Due document US, UK and EU accounts, and Crossmint documents smart-contract wallets. BVNK documents a $500,000 monthly floor and lists cards and yield.

Lumx wrote this post and is one of the options, so our row comes from our own documentation, and every competitor fact is attributed to its provider. For the full ranking of thirteen providers, see the best stablecoin APIs in 2026. For how money crosses two currencies, see what a stablecoin corridor is.

What BVNK does today, and where teams outgrow it

BVNK (London, founded 2021) sells one API for payments and balances in stablecoins and fiat. Mastercard completed its acquisition on August 3, 2026, and the BVNK documentation now carries the Mastercard Global Money Platform name. Its payment-schemes reference lists ACH, ACH Same Day, FedNow, Fedwire, RTP and SWIFT for USD, SEPA Credit Transfer and SEPA Instant for EUR, and Faster Payments for GBP. Local payouts in BRL, MXN, ARS and COP are listed as upcoming and not available yet. The Brazil and Mexico ones would run over Pix (Brazil's instant payment system, run by the Central Bank) and SPEI (Mexico's interbank transfer system, run by Banxico), though BVNK's page names neither.

Three constraints send teams elsewhere:

• Geography: a payment into Latin America has no local rail on BVNK today, so it is a SWIFT wire.

• Eligibility: the BVNK home page says it works with businesses looking to process at least $500,000 a month, with a minimum of six months of operating history.

• Onboarding: the get-started guide starts with an account manager and a sandbox requested from that manager, and the pricing page returns a 404.

None of this is a defect for the customer BVNK is built for: a large enterprise settling USD, EUR and GBP also gets card issuing, rewards on idle balances and a self-managed model that runs under the customer's own licences. The two-way view is on Lumx vs BVNK.

Which BVNK alternative covers which cross-border job?

Lumx appears in one row of seven, because most jobs here never touch a Latin American rail. For the region, see the best stablecoin APIs for LATAM.

How do the alternatives compare on rails and accounts?

BVNK, Lumx and Due Pix status: provider documentation, read on November 2, 2026. Other rows: the comparison pages, verified in September 2026, with Crossmint re-read on October 8, 2026.

Only two providers in the table, Lumx and Bridge, run live rails in all of Brazil, Mexico and Colombia (Bridge alternatives). The region rail by rail is in Latin America payout rails compared.

How long a payment takes on each rail

The rail decides how fast a payment lands, not the provider.

BVNK: docs.bvnk.com payment-schemes reference. Lumx: docs.lumx.io coverage and cut-off pages.

So ACH is one business day on BVNK and one to two on Lumx, while Faster Payments is minutes to hours on BVNK and instant on Lumx. For a payment that crosses a border, the rails at each end matter more than the provider in the middle, as real-time cross-border settlement shows.

Lumx publishes a cut-off and a settlement target for each rail and calls them processing targets, not guarantees. It routes each SEPA payment to the right scheme automatically, and a webhook reports every status change, including a hold for an RFI (request for information, a compliance hold that asks for a document).

Custodial or non-custodial: who holds the keys

A custodial provider holds the keys and the fiat accounts; a non-custodial one leaves signing to the customer, an MPC (multi-party computation) signer or a smart contract. Changing the model later means moving every balance.

Due is non-custodial and Crossmint is non-custodial by default for embedded wallets. BVNK, Conduit and Bridge are custodial, with BVNK adding a self-managed model, Conduit a separate non-custodial wallet product and Bridge external wallets. A business that pays suppliers usually wants a custodian that also runs the payout, so the balance and the rail sit behind one API.

Lumx is custodial. The wallets are held by BitGo, which carries insurance, and each customer is fully segregated, with no omnibus account: balances never mix between customers or with Lumx's own. The balance is stablecoin, not a deposit, because Lumx is not a bank.

Who is licensed to do what?

Compliance asks this first, and a regime differs by country, so read the table by corridor.

BVNK: its home page, read on November 2, 2026. Lumx: our own entities. Other rows: the comparison pages, verified in September 2026.

Lumx has no EU licence, and its Brazilian regime matches UnblockPay's, which is parity, not an edge. For your own EU or US state licences, the others are ahead of us. Inside the API, Lumx runs KYB (know your business) on each customer, verifies each destination and converts stablecoin to local currency.

How to pick, and when switching is the wrong move

I would choose by corridor before features. List where your payments actually go, mark the corridors that need a local rail rather than a wire, and drop every provider that cannot show that rail live in its documentation today. Only then compare accounts and custody, and last the price. Test accounts and rails separately, because they fail in different ways: an account problem blocks a balance, and a rail problem blocks a payout.

A switch away from BVNK buys nothing when your flows are USD, EUR and GBP between businesses, above BVNK's $500,000 monthly floor, and every corridor you serve already has a rail in its documentation. BVNK states 40+ licences worldwide on its home page, which a regulated institution's procurement checklist will ask about. A move changes the vendor, the integration and every customer's onboarding. A stablecoin rail is also the wrong tool for a business that makes a handful of payments a month, where a bank transfer is cheaper to set up.

How to switch, or run two providers side by side

Teams rarely cut over in one step: they run in parallel on one corridor, then move corridor by corridor. Each customer goes through KYB or KYC (know your customer, for an individual) once.

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. Onboard each customer and request the currency accounts they need.

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

4. Fund the new wallets with a stablecoin transfer. BVNK's currencies reference lists USDC on Ethereum, Polygon and Base and USDT on Ethereum, Polygon and Tron, among other networks, and Lumx supports exactly these, so a balance moves between them as a transfer.

5. Request a quote, show it to the user, confirm within the window and listen to webhooks for the final status.

6. Run both providers on one corridor for a full cycle, reconcile both ledgers, then move the next corridor.

On Lumx, step 2 is one call: the customer is created with an accounts array of currencies, and BRL, MXN, EUR and GBP accounts go active right after approval, while a USD account can take up to one business day. The sandbox is open, so test the sequence before a contract. Lumx targets one business day for KYB, and the API takes two to three weeks to go-live. A locked quote lasts 30 seconds at no fee, and every mutation accepts an idempotency key so a retry cannot pay twice.

What cross-border payments look like with 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.

For a business paying into Latin America, the difference is what the account is. A named virtual account (a local account number issued in the customer's own name) in BRL or MXN lets a foreign company collect from local payers without a local entity, and on a Pix payout the recipient sees the customer's name as the payer, not Lumx. In Colombia the payout runs over Bre-B (Colombia's instant payment system) or ACH Colombia, chosen when the destination is registered. Bre-B has a cap of 1,000 UVB per transaction, set for every provider by section 3.2 of the Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18 (sheet of March 31, 2026). For 2026 that is COP 12,110,000, using the 2026 UVB (basic value unit) of COP 12,110, set by the Ministry of Finance in Resolution 3488 of December 31, 2025. A Bre-B payout above the cap is refused, not split, and ACH Colombia has no per-payment limit. Lumx deducts no fee from what the recipient receives on a Pix, SPEI or Bre-B payout.

Outside Latin America, the same wallet pays over ACH, Fedwire, SEPA and Faster Payments, or by SWIFT in USD with a UETR and an MT103 on every wire. Product pages: named virtual accounts and global payments. The live rail list is on the coverage page, and the countries are in the supported countries list.

Methodology and sources

We read BVNK's payment-schemes reference, currencies reference, delivery-models page and get-started guide on docs.bvnk.com, and its home page, on November 2, 2026. The acquisition date comes from BVNK's announcement, read on September 17, 2026. Due's payment-methods page was re-read on November 2, 2026. Lumx facts come from Coverage, Payment rail cut-off times, Accounts, Stablecoin Wallets, Exchange Rates, Environments and Partner Fees, all read on November 2, 2026. Other providers' rows come from the comparison pages on this site, verified in September 2026, with Crossmint rail status re-read on October 8, 2026.

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

Cover photo: Bent Van Aeken on Unsplash.