Payment comparison
Bitcoin vs. Apple Pay: What Merchants Should Know
Apple Pay feels like its own payment method, but for a merchant it is really the customer's existing card in a secure, tap-to-pay wrapper. That single fact answers most questions about fees and chargebacks. Accepting Bitcoin is a genuinely different rail. Here is the honest comparison. The same logic applies to Google Pay and Samsung Wallet.
The most useful thing to understand up front is that Apple Pay is not a new payment network. When a customer taps their phone, the payment runs over their Visa, Mastercard, or other card behind the scenes. Your fees, your settlement, and your chargeback exposure are the card's, not something Apple sets.
So comparing Bitcoin with Apple Pay is really comparing Bitcoin with a very convenient way of tapping a card. This page keeps that framing clear and shows where a final-settlement option like Bitcoin fits beside it. Google Pay and Samsung Wallet work the same way.
Quick comparison
A side-by-side look at the practical differences. Because Apple Pay rides on the customer's card, its merchant costs match your card processing.
| Apple Pay | Accepting Bitcoin | |
|---|---|---|
| What it is | The customer's card in a secure tap-to-pay wrapper, not a separate network | A payment over the Bitcoin network, held directly or via a processor |
| Merchant fee | Equal to the underlying card's rate; no extra fee from Apple | Network fee only if self-custodied; often cents over Lightning. A processor typically charges around 1% |
| Settlement | Same as the card: usually 1–3 business days | Minutes on-chain; seconds over Lightning. Final |
| Chargebacks | Same as the underlying card; disputes possible | None. A confirmed payment cannot be reversed |
| Hardware | An NFC-capable contactless terminal | None required; a phone or printed QR code is enough |
| Security | Strong: a token and device authentication, not your card number | No card data at all; you secure a wallet instead |
| Works offline | No; still an online card authorization | Customer can broadcast from their own connection; you confirm later |
| International use | Wherever the underlying card and contactless work | Borderless by design |
| Best fit | Fast, secure card taps at a modern terminal | A low-fee, final option beside cards for those who prefer it |
Apple Pay, Google Pay, and Samsung Wallet are tokenized wrappers over the customer's existing card. Merchant fees equal the underlying card's processing fees; there is no separate merchant charge from the wallet provider. Confirm rates with your processor.
What Apple Pay actually is for a merchant
When a customer pays with Apple Pay, their card is stored on the device as a secure token, not the real card number. At checkout the phone or watch sends that token over NFC to your contactless terminal, and the payment settles over the customer's card network exactly like any card transaction.
For you, this means the fee is the underlying card's fee. Apple does not add a separate merchant charge; neither do Google Pay or Samsung Wallet. A credit card tapped through Apple Pay costs your credit rate; a debit card costs your debit rate. Settlement and chargebacks are the card's too.
The real merchant benefit is security and speed. You never handle the actual card number, which reduces the value of any data breach and can lower certain fraud disputes, since payments are authenticated on the customer's device. You do need an NFC-capable terminal to accept it.
Bitcoin, by contrast
Accepting Bitcoin is a genuinely separate rail, not a wrapper over a card. A customer sends money over the Bitcoin network to a destination you choose. Lightning settles in seconds for cents, on-chain in minutes, and stablecoins like USDC hold a steady dollar value.
You decide whether to self-custody, holding funds directly with no company able to freeze them, or use a processor that converts to dollars for around 1%. See our guide to self-custody versus a payment processor. Unlike Apple Pay, there is no card underneath and no card fee.
What actually separates them
A card in disguise versus a different rail. Apple Pay is your card processing with a nicer tap. Bitcoin is a separate network with its own economics.
Card fee versus low fee. Apple Pay costs whatever your card rate is. A Lightning Bitcoin payment often costs cents.
Reversible versus final. Apple Pay inherits the card's chargeback system. A confirmed Bitcoin payment cannot be reversed.
Terminal versus no hardware. Apple Pay needs an NFC terminal. Bitcoin needs only a phone or a printed QR code.
Who each option is for
Apple Pay is worth supporting if
- You already accept cards and have or can get an NFC-capable terminal.
- Your customers increasingly tap to pay and expect the option.
- You value the security of tokenized, device-authenticated payments.
Accepting Bitcoin is worth adding if
- You want a lower-fee, final-settlement option beside your card taps.
- You have customers who prefer to pay in Bitcoin, or sales beyond your area.
- You want an option that does not depend on card networks at all.
When there's nothing to add
If you already take cards, there is little reason not to enable Apple Pay; it costs you no more and customers like it. Bitcoin is the more considered addition: add it when you have demand or a cost case, and only if you will handle refunds and, with self-custody, key security.
Typical costs
Apple Pay. No separate cost beyond your normal card processing. You do need an NFC-capable terminal, which most modern readers already are.
Bitcoin. Self-custody has no monthly cost and no percentage, just the network fee. A processor that converts to dollars typically charges around 1%. No terminal is required.
Since Apple Pay costs your card rate, the free credit card fee calculator is a good way to see what those taps cost you across a year.
Operations and security
What if Wi-Fi goes down? Apple Pay still needs an online authorization. A Bitcoin customer can broadcast from their own connection and you confirm later; wait for confirmation on larger amounts.
Security. Apple Pay is strong because you never touch the card number. Bitcoin has no card data either; instead you protect your wallet keys and back up your seed phrase offline. The Merchant Security Playbook covers wallet security.
Refunds and staff. Apple Pay refunds go through the card. Bitcoin refunds are manual; see how to refund a crypto payment. Give staff a simple procedure either way, per our staff training guide.
Accounting implications
Apple Pay reconciles exactly like card sales, because that is what they are, with clean processor statements. Bitcoin requires recording the dollar value at receipt, which a processor automates. Settle your approach up front and involve your accountant.
The short version
Turn on Apple Pay if you take cards. It costs you nothing extra, speeds up checkout, and improves security. The same goes for Google Pay and Samsung Wallet.
Add Bitcoin as a separate, lower-fee, final option when you have demand or a cost case. It is not a replacement for card taps; it is an alternative rail for the customers and sales where its strengths matter.
Remember the core point: Apple Pay is your card processing wearing a better coat. Bitcoin is a different rail. Offer both and let customers choose.
If you decide to go further, the Merchant's Guide to Cryptocurrency Payments explains how to accept Bitcoin to a wallet you control rather than leaving it in an app: choosing self-custody or a processor, handling volatility, and keeping clean books. Plain language, no hype.
Common questions
- Does Apple Pay cost merchants extra?
- No. Apple Pay rides on the customer's existing card, so you pay your normal card processing rate with no separate charge from Apple. The same is true of Google Pay and Samsung Wallet. You do need an NFC-capable terminal to accept it.
- Is Apple Pay a different payment method from cards?
- For the customer it feels different, but for a merchant it is the same card underneath, wrapped in a secure token and a tap. Fees, settlement, and chargebacks all follow the underlying card. Bitcoin, by contrast, is a genuinely separate rail with its own economics.
- Is accepting Bitcoin cheaper than Apple Pay?
- Since Apple Pay costs your card rate, a Lightning Bitcoin payment is usually cheaper per transaction, and self-custody avoids a percentage entirely. But Apple Pay works for nearly every card-carrying customer, while Bitcoin reaches only those who hold it.
- Do Apple Pay payments have chargebacks?
- Yes, the same as the underlying card, though device authentication can reduce some fraud disputes. A confirmed Bitcoin payment has no chargebacks at all, which removes that risk but means you handle refunds yourself.
- What about Google Pay and Samsung Wallet?
- They work the same way as Apple Pay: a tokenized wrapper over the customer's card, with no extra merchant fee beyond your card processing. Everything on this page about Apple Pay applies to them as well.
Keep comparing
More payment-app comparisons
Learn the fundamentals