Three protocol upgrades later, Concordium's payment infrastructure is built for the way business actually operates.
Protocol 10 is live on Concordium Mainnet. The sender and the fee payer are no longer the same party. That single change closes the last gap between how blockchain payments work and how payments are supposed to work.
However, reliable payments start with a reliable network, and that is what Concordium has been building. A previous update, Protocol 8, hardened validator accountability — nodes that go inactive without consequence degrade finality and throughput. P8 fixed that.
Built-In, Not Bolted On
Protocol 9 introduced Protocol-Level Tokens. Those are chain-native assets built directly into the protocol, not layered on through smart contracts. The practical difference: no custom contract code, no fragile logic between the asset and the chain's core rules. Minting, compliance controls, and identity verification are built in from the start. The result was ten stablecoins across live on mainnet.
The payment assets were there. What remained was removing the last point of friction for the people using them.
Fees That Stay Out of Sight
In traditional payments, the merchant covers the processing fee. The customer never sees it. Web3 has worked the other way: fees land on the user before they've done anything. For most businesses, that's where the conversion stops. Protocol 10 changes the default. A customer pays with a stablecoin. They sign the transaction. The merchant platform covers the fee. The customer never needs to hold CCD.
Two signatures, two roles: the sender authorises the transfer, the sponsor commits to the fee. Separate cryptographic commitments, validated independently, protocol-enforced. Concordium fees are fiat-pegged and consistently in the €0.01–€0.02 range, with no congestion pricing. Fee abstraction exists on other chains. What's different here is the identity layer underneath it. On most networks, a sponsor covers a fee for an anonymous address.
On Concordium, every wallet is tied to a verified real-world identity. A merchant sponsoring a transaction isn't flying blind. The accountability is already there, invisible at the surface, which is exactly where it should be.
Where This Changes the Calculation
A subscription platform wants to let users pay in stablecoins. Today, every subscriber needs a separate CCD balance just to process their own payment. With sponsored transactions, the platform covers the fee. The subscriber pays in stablecoin. The CCD requirement disappears from the user journey entirely.
An online retailer sells age-restricted products. The customer's wallet is tied to a verified identity. The retailer sponsors the transaction fee, knowing they are not covering costs for an anonymous address. The auditability check is already built into the chain.
A business making regular cross-border payments to suppliers wants cost predictability. The sponsor controls the fee side of the transaction.
Three different contexts. The same underlying logic: fee responsibility sits with the business, not the customer.
Built for How Business Actually Works
P8 made the network dependable. P9 put auditable assets on it. P10 removes the last point of friction between those assets and the people using them. The result is infrastructure that sits inside the apps, platforms, and distribution channels businesses already operate.
Not a parallel financial system that requires buy-in before it becomes useful — payment infrastructure that works in the background while the experience up front looks like everything else.
Join the Concordium Community, follow us on X.