A payment blockchain is a network designed mainly to move stablecoins, with the payment features that general-purpose networks leave to apps built into the protocol: fees paid in a stablecoin instead of a volatile token, fast final settlement and room for payment references. Tempo, Arc and Plasma are three of the networks launched for this.
This post covers what each of the three does, which are live and what that means for a business that pays suppliers in local currency. The split between the blockchain as a rail and crypto as an asset is in blockchain payments vs crypto payments. If the asset itself is new, start with what a stablecoin is. How a payment moves end to end is in how stablecoin payments work.
What a payment blockchain changes
A general-purpose network is built to run any program, and a stablecoin transfer is one program among thousands. Sending USDC (what USDC is) on Ethereum means holding ETH in the same wallet to pay the network fee, and that fee moves with demand for the whole network, not only for payments. Treasury teams end up topping up fee balances across wallets, and a payout fails when one runs dry.
Payment blockchains change three things.
The fee token. The fee token is the currency the network charges its fee in. Here it is a stablecoin, so a wallet that holds only dollars can send dollars. Some also let a third party sponsor the fee, so an app can pay on behalf of its users.
Finality. A block is either final or not, with no waiting for a number of confirmations. Arc's documentation puts Ethereum's finality at 12 to 15 minutes and a typical layer 2 (a network that settles on top of Ethereum) at about 7 days for withdrawals, against under one second for Arc.
Payment features in the protocol. Reserved capacity so that payment fees stay steady when other activity spikes, and fields that carry an invoice or order reference so that a transfer can be matched to a record.
None of this changes what the stablecoin is, only the road it travels on. The definition of the stablecoin leg, and of where the dollar token sits between two local-currency legs, is in what a stablecoin corridor is.
Which payment blockchains are live today?
Status matters more than design here. Tempo's mainnet is from March 2026 and Arc's from September 2026, so both have months of history, not years, and Plasma's documentation gives no launch date. Plasma's own network page also says its public RPC endpoint is rate limited and not for production systems. This table is from each project's own documentation, read on November 1, 2026.
What each of Tempo, Arc and Plasma says about its status, its fee token, how it settles and who validates, from its own documentation. Fee and finality figures are each project's own claim, not measurements.
Tempo | Arc | Plasma | |
Status | Mainnet, live since March 18, 2026, with a separate public testnet | Mainnet, live since September 16, 2026 | Public network labelled "Mainnet Beta"; its public RPC is not for production systems |
Built by | Incubated by Stripe and Paradigm | Circle | Plasma, which also runs the Plasma One dollar account |
Dollar token named in the docs | pathUSD, issued by Bridge | USDC, issued by Circle | Anchored on USDT |
Fee paid in | Supported USD stablecoins, with optional fee sponsorship | USDC | XPL today, with stablecoin fee payment documented as coming |
Settlement | Near-instant, and a settled block is not reversed, in Tempo's words | Deterministic, under one second | Deterministic, typically within seconds, about 1 second per block |
Validators | Include MoneyGram, Stripe, Visa and Zodia Custody, on a path to permissionless | A known institutional set | Trusted validators at launch, then expansion, then permissionless |
Fee design | Sub-cent for standard stablecoin transfers, Tempo's figure | About $0.001 per token transfer under normal load, a design target of Circle's | Under a cent for most standard transactions, Plasma's figure |
Works with Ethereum tooling | Yes | Yes, with documented differences | Yes |
The Validators row decides how much weight to give a chain. All three launched with curated validator sets, which suits regulated payments and is a different trust model from a fully open network. Two of the three say plainly that the set is meant to widen. Plasma's own consensus page adds that its proof-of-stake mechanism is still under active development. Whether a network is safe for payments depends on who issues the token, who validates and who holds custody, which are stablecoin payments safe covers.
Lumx wallets today are the five networks listed in the wallets docs: Ethereum, Polygon, Base, Tron and Stellar, where Stellar carries only the BRL to USDC on-ramp. The blockchain-by-currency matrix is on the Coverage page.
Tempo, Arc and Plasma one at a time
Tempo
Tempo is a payments-first layer 1 incubated by Stripe and Paradigm. Stripe's announcement is in our weekly digest, Stripe unveils Tempo. Tempo's FAQ lists dedicated payment lanes, fees paid in supported USD stablecoins, fee sponsorship, payment references and sub-cent fees for standard stablecoin transfers. It is fully compatible with Ethereum tooling, and it describes MPP, an open standard co-authored with Stripe for machine-to-machine payments, as a separate protocol that is not limited to Tempo.
Arc
Arc is Circle's purpose-built layer 1, and USDC is its fee token. The fee market is the Ethereum model with smoothing, which Arc's documentation says keeps costs stable: a design-time target of about $0.001 per token transfer under normal load, a floor and a ceiling on the base fee. Arc also ships a predeployed memo contract so that a wallet, an exchange or an indexer can match a transfer to an invoice or order reference. Its home page describes opt-in privacy as a future feature.
Plasma
Plasma is a network and a product at once. The network is a layer 1 for stablecoin payments, and Plasma One, the flagship product, is a dollar account with a card. The documentation anchors the design on USDT. Most standard transactions cost under a cent, in the docs' words, and fees are paid in the native XPL token for now, with a protocol-run paymaster for custom gas tokens listed as in development. The pages we read give no launch date, so this post does not either.
On Lumx each customer gets a wallet on each supported network, provisioned together with the customer, and a wallet is enabled once the customer reaches APPROVED.
Does the network matter if the payout ends in a bank account?
Usually less than the pitch suggests. When a company sends dollars and its supplier receives reais or pesos, the local rail at the receiving end and the compliance checks along the way decide most of the time, and on the three networks above, by their own documentation, the network in the middle finishes in seconds. The last mile runs on Pix (Brazil's instant payment system, run by the Central Bank), SPEI (Mexico's interbank transfer system, run by Banxico) or Bre-B (Colombia's instant payment system), and none of them cares which network carried the dollars.
The network matters in three cases: when the sender already holds USDC on a specific network, when the receiving wallet or exchange accepts only certain networks, and when a team runs many wallets and wants to stop managing fee tokens. Moving funds between an older network and a newer one takes a bridge step, which is one more thing to check before a payout. If none of those applies, the network is an implementation detail and the question for a business is the quote and the rail at the end, which is what what an off-ramp is covers.
On Lumx an off-ramp from a wallet moves through TRANSFERRING_STABLECOIN, TRADING, TRANSFERRING_FIAT and SUCCESS, with a webhook at each step. The success receipt carries the transaction hash and a block explorer link, so a payment can be checked on the network that carried it.
How to choose a network for payouts
I would choose the network last. I start from the two ends of the payment, where the sender's money sits and what the receiving provider credits, and only then look at fee token and finality, because a network the receiver cannot credit is a failed payout whatever its fees, and the money is then stuck on the wrong network until someone moves it. Before the first payment, I confirm the exact network and stablecoin pair with the provider in writing, not after.
That order produces a short checklist.
Find where the money sits today. If balances are in USDT on one network, start there.
Check the receiving side supports the network and the token on it.
Compare total cost, not the network fee. Ask for the all-in cost of a quote for the real corridor and amount, and compare that number.
Decide whether the features matter: fee in the stablecoin, sponsorship, payment references, reserved capacity. They pay off at high volume or across many wallets.
Test on a test network before moving real balances. All three projects publish one.
The ranking of networks for routing, with supply and fees next to finality, is in the network comparison for stablecoin payments. This post does not rank them, because a ranking of the older networks and a description of the newer ones answer different questions.
On Lumx the network is the blockchain field on a request, on any on-ramp, off-ramp, transfer or exchange-rate call. When the field is left out, the project default applies.
When a payment blockchain is the wrong tool
Three cases come up. The counterparty already holds stablecoins elsewhere, and moving to a new network adds a bridge step for no gain on the dollars that matter. The amount is large and the pair is thin: depth is something to measure for the pair and the size, and Plasma's documentation claims one of the deepest stablecoin liquidity bases of any blockchain, so test with the real amount before relying on it. And the payment is a SWIFT wire in USD, where the network is not involved at all.
There is also the matter of track record. A network with months of mainnet history has not been through a full market cycle, and a business that books payments against finality should read the validator model and the incident history before it commits volume. Validator sets on all three are curated and still widening, so the trust model is part of that read.
What this looks like on a Pix payout with Lumx
Take a company that holds USDC and pays a supplier in Brazil. The USDC leaves the company's custodial wallet, becomes reais at the USDC to BRL rate and lands over Pix in the supplier's bank account. The same balance can pay a supplier in Mexico over SPEI at the USDC to MXN rate. The dollar leg is a network transfer, and the last leg is a local rail.
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.
Lumx wallets carry USDC on Ethereum, Polygon and Base, USDT on Ethereum, Polygon and Tron, plus USDC on Stellar, used only for the BRL to USDC on-ramp (as of November 2026, from the Lumx docs). On the legs Lumx runs (on-ramp, off-ramp and transfer) it subsidizes the network fee, so the customer needs no ETH or TRX. Rates come floating, as a reference with no lock, or locked for 30 seconds, one minute or five minutes, and a locked quote returns an exchangeRateId that is passed on the transaction. The off-ramp request also takes an optional memo, a reference for wire transfers, and a metadata object attached to the transaction.
What fails shows up as a status, not a silence. A transaction that does not complete reaches FAILED and fires a failed webhook, and a purpose that does not match what the funds are for can hold a payment or open an RFI (request for information, a compliance hold that asks for a document before a transaction clears). A payout larger than the wallet balance fails with an insufficient-balance error. More on the corridors the platform covers is on the global payments page.
Methodology and sources
Every project fact in this post was read on the project's own documentation on November 1, 2026. Nothing is taken from press coverage.
Tempo: Tempo FAQ, for status and chain ID, then fee token, then validators, then compatibility.
Arc: Arc documentation, for the mainnet launch entry, deterministic finality, gas and fees and transaction memos, plus the Arc home page for the privacy and validator wording.
Plasma: network connection details, mainnet details, network fees, consensus, overview and start here.
Lumx: wallets, coverage, transactions, exchange rates, webhooks and the off-ramp reference.
Design claims are the projects' own and were not tested. Figures such as fee targets and finality times are the ones each project publishes, not measurements.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Yakov Leonov on Unsplash.
What are payment blockchains?
A payment blockchain is a network built mainly to move stablecoins, with fees paid in a stablecoin, fast final settlement and payment references built into the protocol instead of left to each app. Tempo, Arc and Plasma are three of the networks launched for this, and all three work with Ethereum tooling. On Lumx the blockchain-by-currency matrix for every supported network is on the Coverage page.
Are Tempo, Arc and Plasma live on mainnet?
Tempo's own FAQ says its mainnet has been live since March 18, 2026. Arc's documentation lists its mainnet launch on September 16, 2026. Plasma's documentation calls its public network Plasma Mainnet Beta, so it carries a beta label. On Lumx each wallet carries a block explorer deep link to its address on the explorer for its network.
Are payment blockchains better than general-purpose networks for business payments?
Not automatically. They remove fee-token chores and give final settlement quickly, which helps a payments team. General-purpose networks have longer histories and are what most receiving wallets and providers already support, and for a payout that ends in a bank account the local rail usually decides the arrival time. On Lumx a payout debits the customer's own wallet on whichever supported network it sits, and the local rail then does the last leg.
Do I need to hold a fee token to send stablecoins on a payment blockchain?
It depends on the chain, and on Lumx's own legs (on-ramp, off-ramp and transfer) it does not: Lumx subsidizes the network fee. Tempo takes fees in supported USD stablecoins and allows a third party to sponsor them, Arc uses USDC as the fee token, and Plasma uses XPL today with stablecoin fee payment documented as in development.
Does the network change how fast a supplier gets paid in local currency?
Very little. The network step finishes in seconds on the chains with fast finality, and the local rail and the compliance checks decide the rest. On Lumx each off-ramp step fires a webhook, so the supplier's payment can be followed from the wallet to the bank.
