At MPE Berlin this year, something kept happening in conversations with payments companies. We'd walk through how WalletConnect Pay works — the checkout flow, the integration model, the settlement, and the response was some version of: "Oh. So it's just another APM."
Not "that's interesting." Not "how does the blockchain work?" Just: it looks like a payment method.
Three different companies, a payment orchestrator, a PSP, and an acquirer, reached the same conclusion independently. None of them were crypto companies. They looked at the demo and immediately mapped it to how they already think about payment methods.
That reaction tells us more about where crypto payments are heading than any market forecast.
The distinction that changes everything
There are two ways to add crypto to a payment stack.
The first treats crypto as a separate product. It requires a dedicated integration, a new compliance workflow, staff training on wallets and chains, a different reconciliation process, and a merchant education campaign. Most crypto payment solutions work this way. The PSP builds a parallel system, runs it alongside their existing stack, and hopes merchants care enough to adopt it.
The second treats crypto as another payment method. It plugs into the existing stack the way any alternative payment method does — same integration pattern, same settlement format, same compliance framework. The merchant's checkout gets a new option. The operations team doesn't learn a new system. The finance team reconciles the same way they already do.
WalletConnect Pay was built for the second approach. A PSP integrates once, through a standard API pattern they already recognise. Their merchants get access to 500M+ users across 700+ wallets. No new operational overhead. No parallel system.
The difference sounds semantic. In practice, it determines whether crypto payments actually ship or sit on a roadmap for another 18 months.
Why the framing matters for rollout
The payment method framing isn't just positioning. It has direct operational consequences.
Staff training drops to near zero. When a PSP adds a card scheme or a local bank transfer method, their support team doesn't need to understand the underlying clearing network. The same applies here. The merchant's customer selects crypto at checkout, scans a QR code, confirms in their wallet, and the payment settles. The merchant sees a completed transaction in their existing dashboard. There's nothing new to explain to front-line staff.
Merchant adoption accelerates. The biggest drag on crypto payment adoption isn't technology — it's the pitch. Telling a merchant "we've added crypto payments and here's what you need to change" is a fundamentally different conversation from "we've added a new payment method and you don't need to change anything." The second version doesn't require a separate sales cycle. It ships as part of the next product update.
Compliance stays familiar. WalletConnect Pay runs sanctions screening and collects Travel Rule data before any funds move — the PSP doesn't need to build a separate compliance pipeline for crypto. Merchant KYB is handled by the settlement provider, not by the PSP or WalletConnect Pay. The PSP isn't adding regulatory exposure — they're adding a payment method where compliance responsibilities map to the same structure they already work with.
What the APM reaction actually signals
The fact that payments professionals immediately categorise WalletConnect Pay as an APM isn't a simplification. It's the clearest sign that the conversation has moved on.
For years, crypto payments required PSPs to think differently — different technology, different compliance, different mental model. That's why adoption stalled. Not because PSPs didn't see the opportunity, but because the integration cost was out of proportion to the near-term volume.
When payments people stop asking "how does blockchain work" and start asking "can I turn this on for my merchants next quarter" — you know something's changed. The integration cost drops to the level of any other payment method. The compliance burden is handled. The merchant rollout follows existing distribution channels.
That's not a crypto payments story. It's a payments story. And payment companies know how to move fast when a new payment method fits their existing model.
What this means for PSPs evaluating crypto
If you're a PSP or acquirer looking at crypto payments, the question isn't whether your merchants will want it. Stablecoin transaction volume hit $46 trillion in 2025 — more than triple Visa's annual card volume. Of that, roughly $390 billion was real-world payments: vendor payments, payroll, remittances, merchant settlements. That's still early. The demand side isn't just settled — it's growing.
The question is whether adding crypto requires you to build something new or extend something you already have.
WalletConnect Pay is built so the answer is the second one. One integration. One compliance model. Access to the world's largest wallet network. The same APM-style pattern your team already knows how to deploy.
What is a crypto APM?
A crypto APM (alternative payment method) is a way for PSPs and merchants to accept crypto and stablecoin payments through the same integration pattern they use for cards, bank transfers, and mobile wallets. WalletConnect Pay is built as a crypto APM — it connects to 500M+ wallet users across 700+ wallets through a single API, without requiring crypto-specific infrastructure.
How long does it take a PSP to integrate crypto payments?
PSPs that integrate WalletConnect Pay typically go from decision to live launch in weeks, not months. The integration follows a standard APM pattern — single API, no crypto-specific logic, existing settlement and reconciliation flows stay the same.
What compliance does WalletConnect Pay handle?
WalletConnect Pay provides pre-execution sanctions screening (OFAC, UK, EU, UN lists) and Travel Rule data collection — both run automatically before any funds move. KYB is handled by the settlement provider, not by WC Pay or the PSP. KYC and AML risk scoring are handled by the entities required to perform them.
Do merchants need to change their checkout to accept crypto?
No. Crypto appears as another payment option in the merchant's existing checkout. The merchant sees completed transactions in their existing dashboard. No new systems, no staff training, no separate reconciliation.
How does crypto payment settlement work?
Funds land in a merchant-owned transit account. Settlement routes to fiat (via an offramp provider) or crypto (direct to merchant wallet), depending on merchant preference. Confirmation happens in seconds on-chain.