BitPay vs Apa: Who Should Hold Your Crypto Payments?

With BitPay, a customer checks out and is shown a hosted invoice with an exchange rate locked at the moment of creation. They pay crypto to a BitPay-controlled address. BitPay receives the funds, converts them if you've chosen fiat settlement, and adds the amount to your next daily account settlement. Because BitPay holds and converts funds in the middle of the transaction, it operates as a regulated money-services business with KYC/AML onboarding for merchants.

With Apa, the checkout is non-custodial. The customer pays and the funds settle on-chain directly to a wallet address you control, in the asset and on the chain you selected. There is no intermediary balance, no conversion desk, and no waiting on a processor's settlement batch. Apa's role is to generate the checkout, route the payment along the cheapest path, and confirm finality — not to hold your money.

The practical difference: BitPay is closer to a traditional payment processor that happens to accept crypto and can hand you clean fiat in your bank account. Apa is closer to accepting a bank transfer that arrives instantly and irreversibly in a wallet only you can open.

This is the core distinction. BitPay is custodial. Per BitPay's own documentation, once a customer pays, "BitPay converts the cryptocurrencies to your preferred currency and adds the full amount of the payment to your next BitPay account settlement." The customer's crypto lands in BitPay's wallets first; you receive a settlement afterward. That model is what allows BitPay to offer fiat payouts and rate locking, but it also means your funds pass through a third party that must comply with money-transmission regulation.

Apa is non-custodial by design. Funds settle directly to your own wallet and Apa never holds a balance. There is no processor float, no settlement account, and no counterparty that could freeze, delay, or lose access to your money. You hold the keys from the moment the payment confirms.

If your priority is regulatory hand-holding and a familiar processor relationship, BitPay's custody is a feature. If your priority is sovereignty over your funds and removing counterparty risk, Apa's non-custodial model is the point.

BitPay accepts 100+ coins and tokens, including Bitcoin (and the Lightning Network), Ether and ERC-20 tokens, Solana, Polygon (POL), Dogecoin, Litecoin, Bitcoin Cash, Shiba Inu, and a range of stablecoins (USDC, USDT and others). Supported networks include Bitcoin, Bitcoin Lightning, Ethereum, Litecoin, Bitcoin Cash, Solana, XRPL, Dogecoin, and the Ethereum L2s and sidechains Base, Arbitrum, Optimism, and Polygon.

On settlement, BitPay is flexible: merchants choose any percentage split between fiat and crypto — for example 30% USD, 50% BTC, 20% BCH, or 100% of either. Settlement runs automatically every business day. Crypto settles to a wallet address you specify, typically arriving within about an hour of being sent; fiat settles to your bank.

Apa accepts BTC, ETH, SOL, USDC, USDT, POL, BNB, AVAX, and TRX across roughly ten chains (Bitcoin, Ethereum, Solana, Base, Polygon, BNB Chain, Avalanche, Tron, and more). Its settlement is on-chain and direct: the payment lands in your chosen wallet, in your chosen asset and chain, without a processor batch in between. The asset menus differ — BitPay's is broader on long-tail coins, Apa's is focused on the majors and leading stablecoins — but the settlement mechanics are fundamentally different: custodial batch versus direct on-chain.

BitPay's pricing is volume-tiered and published on its pricing page. As of early 2026, merchants processing under $500,000 per month pay 2% + 25¢ per transaction; $500,000 to $999,999 per month pays 1.5% + 25¢; and $1,000,000 or more per month pays 1% + 25¢. BitPay notes higher fees apply for high-risk industries. Monthly transaction counts are unlimited, and the processing fee is the headline merchant cost.

Apa charges a flat 1.5% that is final and all-in — and 0% for direct, same-asset settlements where no conversion is needed. Because settlement is non-custodial and on-chain in a single step, that rate is the whole cost: funds land straight in your own wallet with no separate withdrawal fee and no conversion desk baked into the percentage.

The distinction that matters is all-in versus headline. BitPay's 2% + 25¢ is the processing fee, but it isn't the full cost of getting money into a wallet you control: the customer's crypto first lands in your BitPay settlement, and taking a crypto payout to a self-custody address still carries the on-chain network (miner) fee on top. So the real cost to reach your own wallet is higher than the advertised rate — whereas Apa's 1.5% already includes the single on-chain hop to your wallet.

The comparison depends on your mix. A merchant who genuinely needs fiat in their bank account is buying that convenience in BitPay's percentage. A merchant comfortable receiving crypto (or a stablecoin) on-chain can settle through Apa at a lower effective cost, because they aren't paying for custody and fiat off-ramping they don't use.

BitPay's volatility protection comes from rate locking: the merchant is held to the exchange rate calculated when the invoice was generated, using rates sourced from openexchangerates.org. That means if you settle to fiat, you're insulated from price movement during the payment window. Fiat payouts run via ACH for US banks (USD), international USD via wire (minimum 10,000 USD), and EUR via SEPA in select countries. Most fiat transfers arrive in about two business days, SEPA/EUR in about one, and crypto settles daily.

Apa handles payout control differently: it decouples pay-in from payout. A customer can pay in BTC while you receive USDC, so you choose your payout asset and chain independently of what the customer used. Settling into a stablecoin like USDC gives you the same volatility protection as BitPay's fiat lock, without routing through a custodial processor or waiting on a bank rail.

So both solve volatility, but by different routes: BitPay converts to fiat and locks the rate at invoice time; Apa lets you receive a dollar-pegged stablecoin on-chain instantly. If you need money in a traditional bank account, BitPay's payout rails are the fit. If a stablecoin in your own wallet is acceptable, Apa gives you the same price certainty with fewer intermediaries.

Both products eliminate card-style chargebacks, and for the same underlying reason: on-chain crypto payments are final and non-reversible. BitPay markets this directly as "eliminate fraud chargebacks." There is no card network dispute mechanism a fraudster can invoke after paying.

Refunds under BitPay are merchant-initiated: you authorize a refund on a fully paid invoice, and BitPay automatically refunds under- or over-payments to the customer. Apa treats finality the same way — confirmed on-chain payments are final, and there are no chargebacks.

For high-risk or high-ticket merchants, this is one of the strongest shared arguments for crypto acceptance over cards: the money that arrives is the money you keep, without a months-long window in which it can be clawed back.

BitPay offers a mature integration surface: hosted invoices with locked exchange rates, a REST API with client libraries, website payment and donation buttons, recurring and one-time billing, and in-store point-of-sale through the BitPay Checkout app for iOS and Android. It ships e-commerce plugins for Shopify, WooCommerce, Magento 2, BigCommerce, Wix, and WHMCS, which covers most off-the-shelf storefronts.

Apa provides a hosted checkout, shareable payment links, and a developer API with webhooks. The payment-link flow is well suited to invoices, social selling, and one-off charges without building a full integration, while the API and webhooks cover programmatic checkout and real-time payment status.

Both are quick to stand up for a standard storefront. BitPay's plugin catalog is broader if you run a mainstream CMS and want a one-click install; Apa's payment links plus API give a lean, developer-friendly path when you'd rather compose the checkout yourself.

BitPay fits a business that wants crypto acceptance to feel like a traditional processor: fiat settled to a bank account, an exchange rate locked at checkout, a broad plugin catalog, and a regulated custodial counterparty that handles conversion and compliance. It suits merchants who need clean fiat in the books and are comfortable with KYC onboarding and a percentage that pays for that convenience.

Apa fits a business that wants to own its funds end to end: non-custodial settlement straight to its wallet, the ability to pay in one asset and receive another, a lower effective fee, and the option to self-host. It suits crypto-native operators, teams that want to remove counterparty risk, and businesses comfortable receiving stablecoins on-chain instead of fiat in a bank.

Neither is strictly better; they optimize for different priorities. The deciding question is whether you value a custodial fiat bridge (BitPay) or direct, self-custodied on-chain settlement (Apa).

Getting started with Apa is a matter of pointing it at a wallet you control and creating your first checkout. Because settlement is non-custodial, there's no processor account to be approved for before funds can flow to you — payments settle on-chain directly to your address.

Create a hosted checkout or a shareable payment link for a quick sale, or integrate the API and webhooks for a programmatic flow. Choose your payout asset and chain — for example, receive USDC even when a customer pays in BTC — so you get price certainty without a custodial conversion desk.

If self-hosting matters to you, Apa is self-hostable, so you can run the checkout inside your own infrastructure. From there you accept BTC, ETH, SOL, USDC, USDT, POL, BNB, AVAX, and TRX across roughly ten chains, with confirmed payments final and no chargebacks to manage.