Ask three vendors what they're selling you and you'll get three different answers. Fintech and ERP platforms scoping crypto payment acceptance hit this constantly: RFPs use "gateway" and "processor" interchangeably, and the mismatch only surfaces after integration, when a platform realizes it bought a checkout tool when it needed settlement infrastructure, or the reverse.
Then there’s a third function crypto payments add that traditional card processing never had to deal with.
At a glance
| Payment gateway | Payment processor | |
| Core job | Capture and encrypt payment data at checkout | Authorize the transaction and settle funds |
| Customer-facing? | Yes | No — works behind the scenes |
| Handles money? | No — data only | Yes |
| Talks to | The customer and the processor | Banks, card networks, or on-chain settlement layers |
How a payment flows
- Capture. Customer enters card details or sends crypto from a wallet; the gateway encrypts the data.
- Routing. The gateway passes the data to the processor.
- Authorization. The processor checks with the relevant bank, network, or on-chain settlement layer to confirm funds or a valid transfer.
- Settlement. Funds move from payer to payee, or in crypto's case, land in the merchant's account for conversion.
- Confirmation. The processor reports back to the gateway, which shows the customer a success or decline.
What a payment gateway does
A gateway sits at the front end. It captures payment details, whether that's a card number typed into a checkout form or a wallet address scanned at point of sale, encrypts it, and passes it along. According to the ++PCI Security Standards Council's official glossary++, a payment processor is "sometimes referred to as 'payment gateway,'" which is precisely why the two terms get used loosely even by people who should know better.
The gateway is a secure conduit for data without actually touching it.
What a payment processor does
The processor sits behind the gateway and deals with authorization and settlement. It talks to card networks and issuing banks in traditional payments, or to on-chain settlement layers and fiat banking rails in crypto. The PCI glossary bundles this under "service provider," the same category that includes gateways, because in practice the line between transmitting and settling data has always been thinner than the clean two-box definition suggests.
Most providers bundle both
Stripe, Square, and Adyen all sell gateway and processor as one product. The useful question for a buyer is: for the vendor in front of me, do I already have one of these covered, or do I need both?
Where crypto adds a third function
Traditional card payments already involve more than two parties: acquirer, issuer, network, gateway, processor. Crypto's real difference is narrower than a headcount comparison: a card transaction never requires converting an asset class. The customer pays in the currency the merchant already holds.
Crypto payments do require that conversion. A customer might pay in USDT; the merchant wants euros. Something has to actually exchange one for the other. That's a genuinely separate function from either gateway or processor:
- The exchange/settlement desk — buys, sells, and converts crypto to fiat, functionally similar to what a processor does for card payments, but for an asset that isn't already the currency either party wants to hold.
- The payment processor — authorizes the transaction and moves the resulting value into the merchant's account.
- The payment gateway — the customer-facing checkout: redirect to a hosted page, pick a currency, pay within a locked-rate window, confirm.
++BitPay's own developer documentation++ sets a 15-minute expiration on locked invoice rates; other providers run closer to 10 minutes. The window exists because a customer taking a few minutes to scan a QR code shouldn't cost either side money because of market movement in the meantime.
The ++FATF's 2021 updated guidance on virtual asset service providers++ treats exchange, transfer, and custody as three of its five recognized VASP activity categories, each distinct from the others. It’s a useful regulatory confirmation that the crypto side of this splits further than the traditional payment role set, and it's also why a single provider offering all three often needs more than one type of license or registration to do it legally.
What to actually ask a vendor
| Your situation | What you're really missing | Question to ask |
| You have a checkout, no crypto settlement | Processor (and possibly the exchange function) | "Do you handle authorization and fiat settlement, or is that a separate integration?" |
| You have crypto inflows, need them usable | Processor, possibly exchange | "What's your settlement time from crypto received to fiat in my account?" |
| Starting from zero | All three, ideally from one provider | "Are checkout, authorization, and fiat conversion native to your platform, or are you reselling pieces from other vendors?" |
| Any of the above | PCI/compliance ownership | "Who owns PCI scope on this integration, and who do I call if authorization or settlement breaks?" |
A vendor stitching together a gateway from one company and settlement from another adds operational risk and often latency that a single regulated provider running all three natively doesn't carry.
FAQ
Can one company be both a payment gateway and a payment processor?
Yes. This is the norm for modern payment providers. Stripe, Square, and Adyen all bundle both. In crypto, a single provider can also add the exchange/settlement function, so the same question applies: are all three native to the platform, or assembled from multiple vendors?
What is the difference between a digital wallet and a payment gateway?
A wallet stores payment credentials or crypto assets for later use. A gateway transmits payment data at the point of a specific transaction. A wallet can fund a payment that a gateway processes, but they do different jobs.
How does a crypto payment gateway work?
The merchant's checkout redirects the customer to a payment page. The customer picks a currency and sends payment within a locked rate window (commonly 10–15 minutes, per provider). Once confirmed on-chain, funds land in the merchant's account to convert or hold.
Do I need a payment gateway?
If you're accepting payments through a website or app, yes. But a gateway alone can't complete a transaction; you also need a processor behind it, whether that's bundled with the same vendor or separate.
Are payment gateways safe?
Card-based gateways operate under PCI DSS. Crypto gateways don't have a direct PCI DSS equivalent since that standard specifically governs cardholder data; look instead for SOC 2 or ISO 27001 certification and clear custody/security practices from the specific provider.
How do I accept crypto payments for my business?
Choose a provider that covers checkout, authorization/settlement, and fiat conversion, ideally natively rather than stitched together. See our guides on pay-by-crypto solutions and crypto payment gateways.
Related reading: Pay-by-Crypto for B2B · What is a crypto payment gateway? · How to choose a crypto payment gateway