MoonPay vs Apa: Ramp-Plus-Payments vs Pure Non-Custodial Checkout

MoonPay built its name on ramps: the widget that lets a user buy crypto with a Visa card or sell it back to fiat is embedded across hundreds of wallets and apps. MoonPay Commerce is the merchant-facing product that reuses that infrastructure so a business can accept crypto at checkout. According to MoonPay, a customer pays in crypto, the payment is settled peer-to-peer to the merchant's wallet, and the merchant can optionally auto-convert and offramp to fiat. It is a hosted, managed platform: you work through MoonPay's dashboard, checkout widget, and pay links.

Apa is narrower and, for a merchant, more direct. There is no ramp business wrapped around it — Apa's only job is checkout. A customer scans or clicks, pays on-chain, and the funds settle to a wallet you already control. Apa is not a place you park money; it is the rail between your customer and your wallet. Because there is no platform balance, there is no 'withdraw' step and nothing for Apa to hold.

The practical upshot: with MoonPay you are adopting a broad crypto-payments suite from a company whose center of gravity is buying and selling crypto. With Apa you are adopting a focused checkout whose center of gravity is settling merchant payments non-custodially.

MoonPay's Commerce FAQ describes Commerce transactions as direct peer-to-peer payments: crypto moves from the customer's wallet to the merchant's wallet, and MoonPay states that once a payment is made it cannot be reversed or reclaimed by MoonPay. In that sense the Commerce checkout flow is designed not to custody the merchant's proceeds.

It is worth stating plainly, though, that MoonPay as a company is not a non-custodial-only business. Its flagship on-ramp and off-ramp services involve MoonPay handling fiat and crypto conversion, and the company has expanded into institutional custody. So 'MoonPay' and 'MoonPay Commerce' are not the same custody story — the merchant Commerce flow is peer-to-peer, while other MoonPay products are custodial by nature.

Apa has no such split. It is non-custodial across the board: funds settle directly to your own wallet and Apa never holds a balance. There is no product tier where Apa takes custody of your money. If that single-mode simplicity matters for your compliance or treasury posture, it is a genuine structural difference rather than a marketing line.

MoonPay Commerce supports a broad, multi-chain set of assets. Its documentation lists USDC, SOL, ETH, and BTC alongside what MoonPay describes as hundreds of other tokens, with the ability to add unlisted tokens for a fee. On the network side, MoonPay Commerce names Solana, Bitcoin, Ethereum, Base, BNB Chain, Arbitrum, and Polygon among the chains it supports, as of early 2026.

Settlement has two modes. In the default, crypto is received directly in the merchant's wallet — the peer-to-peer path. Alternatively, a merchant can set an auto-offramp to a nominated bank account, converting to fiat (MoonPay lists USD and EUR) through its Iron partner. That fiat path is what makes MoonPay attractive to merchants who ultimately want money in a bank rather than tokens in a wallet.

Apa covers nine assets — BTC, ETH, SOL, USDC, USDT, POL, BNB, AVAX, and TRX — across roughly ten chains including Bitcoin, Ethereum, Solana, Base, Polygon, BNB Chain, Avalanche, and Tron. Apa's settlement is single-mode and on-chain: the payment lands in your wallet in the asset and chain you selected. Apa does not offramp to a bank; if you want fiat, you convert on your own terms. The two products therefore serve different end-states — MoonPay optionally ends in a bank account, Apa always ends in your wallet.

MoonPay Commerce publishes a clear headline: 2% per transaction as the standard rate, dropping to 1% per transaction for HelioX Pass holders, per its Commerce FAQ as of early 2026. On top of that base rate, MoonPay lists optional features priced separately — swaps at 0.25% and auto-offramp to a bank at 0.50%. So a merchant who accepts a token and offramps it to fiat is effectively stacking the 2% (or 1%) base with the 0.50% offramp.

That is a real, stated number, and it compares favorably to the roughly 2.9% plus a fixed per-transaction fee that card networks charge. But it is still a percentage taken on every sale, and the offramp and swap add-ons raise the effective rate when you use them.

Apa's model is a flat 1.5% that is final and all-in, dropping to 0% for direct same-asset settlements. The word all-in matters here: because Apa settles in a single on-chain step straight to your own wallet, that 1.5% is the whole cost — there is no platform balance to withdraw from afterward and no separate withdrawal fee. To be fair to MoonPay, its 2% (or 1% with HelioX) is also largely all-in for the direct peer-to-peer path, since Commerce delivers crypto to your wallet without a withdrawal step; the difference is the headline rate itself and the 0.50% you add only if you choose the bank offramp. So the fair comparison is Apa's 1.5%-and-final (0% direct) versus MoonPay's 2% base plus optional offramp — both avoid the custodial trap of a withdrawal fee, and Apa lands lower on the headline.

MoonPay gives merchants flexibility on the back end: receive crypto instantly, or auto-convert and offramp to fiat (USD or EUR) into a nominated bank account. For volatility management, a merchant worried about holding a volatile token can lean on the auto-offramp or the 0.25% swap feature to move into fiat or a stablecoin. Timing on the fiat path depends on MoonPay's Iron banking partner rather than being instant on-chain.

Apa handles volatility differently and, for many merchants, more elegantly: it decouples pay-in from payout. A customer can pay in BTC while you receive USDC on the chain of your choice. You choose your payout asset and chain up front, so if you want to avoid volatility you simply nominate a stablecoin as your settlement asset and every payment lands that way — no separate swap fee, no offramp, no waiting on a banking partner.

So both products let you end up in something stable, but the mechanics differ. MoonPay converts and can send fiat to your bank for added fees and partner-dependent timing. Apa settles you straight into your chosen stablecoin on-chain, instantly and as part of the same payment.

This is one area where MoonPay and Apa fully agree, and it is a genuine advantage of crypto checkout over cards. MoonPay's Commerce FAQ is explicit: once a payment is made it cannot be reversed or reclaimed by MoonPay, owing to the blockchain's irreversible nature. There is no chargeback mechanism to weaponize against the merchant.

Apa is identical in substance: confirmed on-chain payments are final, and there are no chargebacks. For businesses that have been burned by friendly-fraud disputes on card rails, both products remove that entire class of loss.

The distinction is not finality itself but what surrounds it. With MoonPay's optional fiat offramp, the crypto leg is final but the fiat leg introduces a banking partner into the flow. With Apa the whole path is on-chain and final end-to-end, because there is no fiat leg unless you add one yourself later.

MoonPay Commerce offers a rich integration surface, consistent with its scale. It provides a hosted crypto checkout that works across web, app, and Shopify (via Solana Pay), pay links for products and subscriptions, an embeddable checkout widget with dynamic pricing, headless APIs with webhooks, and no-code/low-code options. If you want to drop crypto acceptance into an existing storefront quickly, the breadth here is a strength.

Apa's integration set is deliberately focused on the same core jobs: a hosted checkout, shareable payment links, and a developer API with webhooks. It covers the paths most merchants actually use — a hosted page for non-technical setup, links for ad-hoc or social selling, and an API for custom flows — without the surrounding ramp and widget ecosystem.

The decisive developer-experience difference is self-hosting. MoonPay Commerce is a managed, hosted platform that requires dashboard access; it is not self-hostable or open source. Apa is self-hostable, so a team that wants to run the checkout inside its own infrastructure — for control, data residency, or resilience — can do so. That is a capability MoonPay simply does not offer.

MoonPay Commerce is a strong fit for merchants who want a broad, batteries-included suite from a large, well-known brand, who value the option to auto-offramp proceeds into a bank account in USD or EUR, and who want to accept a very wide range of tokens — including long-tail assets they can add for a fee. If your goal is 'accept anything and end up with fiat in the bank,' MoonPay's ramp heritage is exactly the strength you want, and the 2% (or 1% with HelioX) headline is competitive with cards.

Apa is the better fit for merchants who want the payment to be non-custodial end-to-end, who want funds on-chain in a specific asset and chain, and who care about decoupling pay-in from payout so a customer can pay one asset while they receive another. It also wins outright for anyone who needs to self-host the checkout, since MoonPay cannot be self-hosted.

In short: choose MoonPay if you want a ramp-backed suite that can deliver fiat to your bank; choose Apa if you want a focused, non-custodial rail that puts crypto straight into your wallet on your terms.

Getting started with Apa is deliberately short because there is no custody to set up and no balance to fund. You connect the wallet you want to receive funds in, choose your default payout asset and chain — for example USDC on Base if you want stable, on-chain settlement — and you are ready to accept payments.

From there you can create a hosted checkout for your storefront, generate shareable payment links for one-off or social sales, or integrate the API and webhooks for a fully custom flow. Because pay-in is decoupled from payout, you can let customers pay in whatever they hold — BTC, ETH, SOL, and the rest of Apa's nine assets — while you consistently receive the single asset you nominated.

And because Apa is self-hostable, teams that want full control can run it inside their own infrastructure rather than depending on a managed dashboard. Whether hosted or self-hosted, every payment settles on-chain, directly to your wallet, with no chargebacks and no platform float in between.