September 4, 2026
Does Stripe accept crypto payments? What you get, and what to do if you can't switch it on
Read article
A crypto channel is not cheap card acquiring. It's a different trade of risks, and the mistake most owners make on this search is comparing channels by the headline percentage on a pricing page. Card acquiring, a bank transfer and a crypto payment each charge you in a different place. Some of that cost lands up front, some of it only when something goes wrong. The channel that looks cheapest in the first line can end up costing more once every layer is counted.
This piece compares crypto payments vs bank transfers and card acquiring channel by channel — fees, speed, and what happens when a customer disputes a payment. The goal is to work out which is the best method for the specific problem that sent you here, not crypto in general. If some of your customers simply can't pay you today, the answer looks different than if disputes are eating your margin, and different again if you're just tired of the percentage on your statement.
Look past the marketing and every channel is really a stack of separate charges. The stack is what differs — a single number never tells the whole story.
With card acquiring, you're paying for several things that show up separately:
None of these are optional extras. They're standard line items on a real statement.
With a bank transfer, the visible cost looks simple: your own bank quotes a fee. But a second cost hides behind it. A correspondent bank sitting in the middle of an international wire can take its own cut — and it does so after the money has already left your account.
With a crypto channel — sometimes called crypto acquiring — the stack gets shorter. There's a processing fee, charged by whoever handles the payment for you. There's a network fee, paid by the buyer to move the funds on-chain. That's the entire cost side.
Two costs that don't exist with cards appear instead. One is exposure to the exchange rate between the moment the customer pays and the moment the value is fixed. The other is the manual work of handling a payment that arrives short of or over the invoiced amount — nobody can adjust an on-chain transfer once it's sent.
Put numbers on that stack and the differences get concrete.
Stripe's published rate for a domestic card charge is 2.9% + $0.30 per successful payment. That's before anything unusual happens. An international card adds another 1.5% on top of the base rate, and a sale that needs currency conversion adds a further 1%.
PayPal's merchant fee schedule, current as of its September 1, 2026 update, lists 3.49% + $0.49 for a domestic transaction and adds 1.50% for an international one. A foreign customer checking out with PayPal can cost close to 5% of the sale before a single dispute even happens. Card acquiring is a stack of surcharges. The number on the sign is the floor, not the ceiling. The real cost of accepting payments walks through the rest of that stack, reserves and minimums included.
A bank transfer hides that same second cost, and it's not theoretical. Chase's published fee schedule for personal accounts carries a footnote confirming it: other financial institutions in the payment chain may deduct their fees from an incoming or outgoing wire before it lands. There's no way to look that fee up in advance. The number you're quoted up front is not the number that arrives.
A crypto channel replaces both stacks with two fees, one of which the business never pays. The network fee — commonly called gas — is charged by the blockchain itself and paid by the customer's wallet. It moves by the minute, so treat every figure below as a snapshot:
On top of the network fee sits the processing fee — what a provider charges for accepting the payment and settling funds into your account. How crypto fees are put together is worth reading for the full breakdown of what's inside it.
Providers price this differently. CryptumPay, for one, charges 1% per successful payment, down to 0.5% at large volumes, and lets the merchant pass that fee on to the customer instead of absorbing it.
Confirmation on the blockchain and money you can actually spend are two different clocks. Conflating them is the second most common mistake in this comparison.
On the card side, Stripe's default payout schedule pays out to your bank account two business days after the card payment clears. Faster schedules exist, but aren't granted to every account. An instant payout — arriving in about 30 minutes — is a paid option with its own eligibility conditions.
Whether a reserve holds back part of that money depends on the provider and your account. Adyen documents a configurable reserve that can be set aside to cover refunds, chargebacks and other operating costs. A provider configures this individually, for a specific merchant. Size and duration are set per account and aren't published as a standard rate. Ask your provider whether one applies to you before you sign — the terms are individual.
On a bank transfer, the transfer itself can take days in transit before it arrives at all. Once it does, your own bank's posting rules decide when it's usable.
On a crypto channel, the blockchain confirms in seconds to minutes, as the figures above show. But confirmation isn't the same question as "can I withdraw it." That's decided by the processor's own status ladder and withdrawal terms:
Get those terms in writing before signing anything. With CryptumPay, for instance, manual withdrawal from the dashboard is available at any time with no minimum, and the merchant sets any recipient address. Withdrawing through the API instead requires an IP whitelist tied to the API key, which is worth planning for if that's how you intend to move funds.
With a card, a dispute costs you twice: once when the payment itself gets pulled back, and again as a flat fee just for the dispute existing. Stripe's published rate for that second charge is $15 per disputed payment, regardless of whether you eventually win it.
The process itself follows a set path. Visa's Dispute Management Guidelines for Visa Merchants (June 2024) describe the sequence: the cardholder raises it with their issuing bank, the issuing bank routes it to your acquirer, and the acquirer brings it to you. From there, you can accept the debit or contest it with evidence.
Visa sorts disputes into four categories — fraud, authorisation, processing errors and consumer disputes — but the guidelines don't state how many days you have to respond. Those deadlines live in your own acquirer's operating guide. They're set by contract and differ from one provider to the next. Don't assume a number here — ask your acquirer for the actual clock.
Crypto removes this mechanism entirely. Once a transaction confirms on-chain, nobody can reverse it — not the buyer, not you, not the processor. There's no arbiter sitting between you and the customer to rule on who's right.
If you sell a digital product or a service delivered instantly and can't be taken back, that's real money you stop losing to disputes on transactions you already fulfilled. But it's also a new problem: the tool for fixing your own mistakes is gone too. A refund on a crypto payment is a voluntary transfer you send back by hand. That means you need a written refund policy and someone on staff who actually executes it.
The dispute section above already named one trade-off. Three more sit alongside it — and none of them show up on a table of percentages.
The first is rate exposure: the value of what a customer sent can move between the moment they pay and the moment it's converted into something stable. Ask any provider at exactly what point the rate becomes final, and get that answer before you sign.
With CryptumPay, for instance, incoming funds are converted to USDT as soon as they arrive. Underpayments and overpayments — amounts that don't match the invoice to the cent — are processed automatically, without manual reconciliation each time. Protecting revenue from rate swings covers the mechanics in more depth if that's the actual worry.
The second is issuer risk. A "dollar" sitting on a balance as a stablecoin is still somebody's obligation to redeem. It isn't cash, and its reliability depends on whoever issues it. Know who that is before you rely on the balance.
The third is the dispute problem from a different angle, and it's worth being precise about which mistakes it actually covers. A payment that lands short of or over the invoice because a network fee ate into it, or the rate moved between invoice and payment, is a reconciliation problem — a processor can close that gap on its own, the way CryptumPay does above. A customer sending to the wrong address, or on the wrong network entirely, is a different animal: the funds went somewhere that isn't your deposit address at all, and no arbiter, and no processor, can pull them back. Choosing a network for USDT is worth reading before you tell customers which chain to use: a payment sent on the wrong one is exactly the kind of mistake nobody can undo for you.
The fourth is tax treatment, and it catches people off guard because it doesn't feel like a payments question. In the US, the IRS treats virtual currency received as payment as property, not currency, under Notice 2014-21. It's valued in dollars at fair market value on the date you receive it. The taxable event happens on receipt, regardless of when you eventually cash out — so plan your books around the receipt date.
The legal picture depends entirely on where your business and your provider sit. It also moves fast enough that "crypto is legal" or "crypto is banned" is rarely the real answer.
In the European Union, Regulation (EU) 2023/1114 — MiCA — was published in the Official Journal on 9 June 2023. Since 30 December 2024, any business providing crypto-asset services in the EU has needed authorisation as a Crypto-Asset Service Provider.
MiCA doesn't decide whether accepting crypto is legal or illegal for your business. It regulates the issuers and service providers sitting between you and the customer. The question it actually raises for you is narrower and more useful: is your provider MiCA-authorised, and in which member state?
In the US, the clearest federal rule on the books is the tax one already covered above — IRS Notice 2014-21 sets out how a crypto payment is taxed on receipt, not whether a business is allowed to accept one in the first place.
Rules can also flip entirely at a border, and the same border can change its mind. Since 1 September 2026, Russia has been under a new digital-currency law — 282-FZ of 4 August 2026, paired with a companion law that retires the old one. The ban on paying with crypto for goods and services inside the country carries straight through with no gap; it now lives in part 6 of article 1. What's new is a conditional door the old law didn't have: a resident and a non-resident can now settle in digital currency under a foreign-trade contract. Conditional, because the currency-control rules for it are still being written, the central bank can restrict or attach terms to specific operations, and nobody has settled yet where a foreign customer's checkout ends and a genuine foreign-trade contract begins.
None of this is legal or tax advice. The rules above are stated as they stand on 3 September 2026, and they differ by jurisdiction. Check what actually applies to your company with your own lawyer and accountant before you commit to a channel.
Put the layers, the timing, the disputes and the trade-offs together. The decision comes down to which of four situations actually describes your business.
None of this makes cards obsolete. The channels aren't mutually exclusive. For almost every business, the right setup is cards plus a crypto channel for the specific segments cards don't reach well — not one replacing the other.
Before you sign with any provider, get five things in writing: withdrawal terms and timing, the exact moment the rate becomes final, what happens on an underpayment, whether a reserve applies to your account, and whether the provider is authorised in the jurisdictions where that's required.
However you connect to CryptumPay — a payment link generated from its console with no website involved, a checkout widget added with a script, or an API and Node.js SDK for a custom build — the answers to those five questions matter more than which integration method you pick.
Blockchain confirms in seconds to minutes on most chains. An international bank transfer can take days in transit before your bank's own posting rules even apply. But "confirmed" and "available to withdraw" are different questions on both sides — the provider's terms decide the second one.
Only if you count the full stack. Card acquiring adds surcharges for foreign cards, currency conversion and disputes on top of the base rate. A crypto channel replaces that stack with a processing fee plus a network fee the buyer pays. But rate exposure and manual handling of mismatched payments are new costs of their own. Compare layer by layer.
The customer's wallet pays the network fee directly to the blockchain. The processing fee, by contrast, is billed to the business.
No. Once it confirms on-chain, nobody can reverse it, including the business. A refund is a separate, voluntary transfer you send back by hand — there's no chargeback mechanism to fall back on.
If customers you can't currently charge are the actual problem, add a crypto channel. It's close to the only one of the four situations that creates new revenue. If it's cost alone, work your acquiring rate down first. A crypto channel isn't automatically cheaper once every layer is counted.
Create an account and connect the checkout yourself, or talk to sales and we will plan the integration with you.
