Stripe Crypto vs Apa: Custodial Stablecoins vs On-Chain Checkout

Stripe's Stablecoin Payments plug into the same Stripe machinery merchants already use for cards. A customer pays with a stablecoin such as USDC; Stripe accepts the on-chain payment, converts it, and settles the value into your Stripe balance in your local currency, from which it pays out to your bank on Stripe's normal schedule. To you it looks and reconciles much like any other Stripe payment method — which is precisely the appeal for a business already living inside Stripe.

Apa is a standalone non-custodial checkout. A customer pays in crypto, and the payment settles on-chain directly to a wallet you own, in the asset and chain you nominate. There is no Stripe-style platform balance in the middle and no conversion to fiat unless you choose to receive a stablecoin. The money and the settlement are the same event.

So Stripe crypto is 'crypto in, fiat in your Stripe account,' while Apa is 'crypto in, crypto to your wallet, on your terms.' One keeps you inside a custodial card platform; the other keeps you on-chain and in control of the funds.

Stripe's crypto product is custodial. Per Stripe's own Stablecoin Payments terms, the settlement services include custody of the stablecoins and fiat by Stripe's settlement-services providers — named as Paxos Trust Company and Bridge — before the value is transferred into your Stripe account. In other words, your payment passes through regulated custodians and lands in a Stripe balance you then draw down; you rely on those parties and on Stripe's payout process to actually receive the money.

Apa is non-custodial. Payments settle straight to a wallet you own, and Apa never holds a balance on your behalf. There is no intermediary account your funds sit inside.

This is the fundamental divide. With a custodial model you get the convenience of a familiar balance-and-payout flow, but the provider is in the path of your money and its compliance status and schedule govern your access to it. With Apa's non-custodial model, receipt and settlement are simultaneous and the funds are yours the moment the transaction confirms.

Stripe's crypto product accepts stablecoins only. Its documentation lists USDC as the primary asset (plus USDP and USDG for US accounts) across Ethereum, Solana, Polygon, Base and Tempo, and it caps transactions at roughly $10,000 each. There is no BTC, ETH or SOL as a spendable asset — this is a stablecoin rail, not a general crypto rail.

Apa accepts 9 assets — BTC, ETH, SOL, USDC, USDT, POL, BNB, AVAX and TRX — across roughly 10 chains (Bitcoin, Ethereum, Solana, Base, Polygon, BNB Chain, Avalanche, Tron and more). That includes the major volatile assets Stripe does not take, and it does not impose the same per-transaction ceiling.

Settlement diverges just as sharply. Stripe converts the incoming stablecoin to your local fiat and settles it into your Stripe balance (holding a USDC balance is available where that is enabled), then pays out to your bank. Apa settles on-chain to your wallet in the asset and chain you choose, and lets pay-in be decoupled from payout — a customer can pay in BTC while you receive USDC directly to your wallet.

Stripe charges a flat 1.5% per stablecoin transaction, per its published stablecoin pricing as of early 2026. That is notably cheaper than Stripe's headline card pricing of roughly 2.9% + a fixed fee, which is much of the point — moving a customer from cards to stablecoins nearly halves Stripe's cut. It is worth being clear-eyed that 1.5% is a platform fee sitting on top of an on-chain transfer whose network cost is often a fraction of a cent; you are paying for Stripe's abstraction, conversion and custody, not for the blockchain.

Apa's headline fee is also a flat 1.5%, but with two structural differences that matter for total cost. First, it is final and all-in: the payment settles straight to your own wallet in a single on-chain step, so there is no platform balance and no separate withdrawal or payout fee to actually take possession of the money. With Stripe, by contrast, the 1.5% gets the value into your Stripe balance as fiat, and a standard Stripe payout — on Stripe's schedule — is still needed to move it to your bank, so the headline rate is not the end of the cost or the wait. Second, Apa drops to 0% for direct same-asset settlements, whereas Stripe always converts to fiat and never delivers crypto to a wallet you control.

For a merchant, then, the honest comparison is 1.5% into a custodial fiat balance you must then pay out (Stripe) versus a final, all-in 1.5% — or 0% for direct same-asset payments — settled on-chain straight to your own wallet (Apa). If staying on-chain, keeping custody and minimising total cost matters, Apa's model is structurally leaner; if you value settling to fiat inside Stripe's ecosystem, the 1.5% plus payout is the price of that convenience.

Stripe's crypto product all but removes volatility for you by converting incoming stablecoins to your local fiat on receipt and crediting your Stripe balance, from which you pay out to your bank; where enabled, you can instead hold a USDC balance. Because it is stablecoin-only, the volatility question is already muted — you are receiving a dollar-pegged asset, not BTC — and the conversion finishes the job.

Apa manages volatility at the checkout layer without going to fiat. Pay-in is decoupled from payout, so a customer can pay in a volatile asset like BTC while you elect to receive a stablecoin such as USDC directly to your wallet. You end up holding dollars-on-chain the instant the payment confirms, with no bank in the loop and no exit from crypto rails.

The end states differ meaningfully. Stripe lands you in fiat in a Stripe balance headed for your bank; Apa lands you in the stablecoin of your choice in your own wallet. If your operations run on fiat and you want money in the bank through Stripe, Stripe's flow fits; if you want stable value on-chain under your own keys, Apa's payout selection delivers it natively.

Neither product exposes you to card-style chargebacks. Stripe's own documentation states that Stablecoin Payments do not support disputes, so a settled stablecoin payment cannot be reversed through the dispute mechanism that applies to cards. That is a genuine advantage of the crypto rail over Stripe's own card products.

Apa reaches the same outcome structurally: confirmed on-chain payments are final, because once a transaction is confirmed there is no network or bank that can claw it back.

For both, the trade-off is identical — you give up the buyer-protection machinery of cards and, in exchange, you eliminate chargeback fraud and the associated fees. Refunds become a deliberate action you choose to make rather than something a customer can force after the fact. The difference is only where finality sits: for Stripe it is a settled entry in your custodial balance; for Apa it is a confirmed transfer into your own wallet.

Stripe's crypto product inherits Stripe's mature developer surface. You can accept stablecoins through Stripe Checkout (hosted), Payment Links, Elements, Invoicing and Billing, Connect for platforms, and the Stripe API — the same primitives you would use for cards, with stablecoins added as a payment method. For teams already integrated with Stripe, enabling crypto is largely a configuration step, which is a real strength.

Apa offers a focused checkout surface: a hosted checkout page, shareable payment links for when you have no site, and a developer API with webhooks to embed on-chain payments into an app or store. It is narrower than Stripe's sprawling platform, but it is purpose-built for non-custodial crypto settlement rather than adapted from a card platform.

The developer-experience choice mirrors the product choice. If your app is already on Stripe and you want to add a stablecoin option inside that ecosystem, Stripe's DX is the path of least resistance. If you want on-chain settlement to your own wallet, without adopting a custodial platform, Apa gives you hosted, link and API options built for exactly that.

Choose Stripe crypto if you are already a Stripe merchant, you primarily sell with cards, and you want to offer stablecoin payments as one more method that settles into the same Stripe balance and bank payout you already rely on. The flat 1.5% undercuts card fees, the integration is trivial if you are on Stripe, and settling to fiat inside a familiar dashboard is exactly what many finance teams want. You accept, in return, a custodial model, stablecoin-only assets, a ~$10,000 per-transaction cap, and a closed, non-self-hostable platform.

Choose Apa if you want non-custodial crypto checkout where funds settle on-chain to a wallet you own, across a broader asset set that includes BTC, ETH and SOL, with the freedom to receive a stablecoin regardless of what the customer paid — and at an effective fee below the card norm. It is also self-hostable, which Stripe is not.

The deciding question is where you want the money to land and who holds it on the way. Stripe: fiat, in a custodial Stripe balance. Apa: crypto, in your own wallet, non-custodially.

Getting started with Apa is fast precisely because there is no custodial account to provision and no balance to reconcile before funds can reach you. You connect the wallet you want to be paid into, choose which of Apa's 9 assets and roughly 10 chains you will accept, and select the asset and chain you want to receive — for example, accept BTC, ETH or anything else, but settle to USDC.

From there you can share a payment link right away, embed the hosted checkout on your site, or integrate the API and webhooks for programmatic charges and real-time settlement notifications. Every confirmed payment settles directly to your wallet, with no platform balance and no forced conversion to fiat.

If you are moving off a card-first setup and want crypto without handing custody to a processor, Apa is the most direct route to a non-custodial, self-hostable checkout — and unlike a stablecoin-only rail, it lets you accept the major crypto assets while still choosing to hold stable value on-chain.