Crypto payment processing explained: every stage from checkout to settlement

Card payments hide almost everything from the merchant. You see "approved", and banks, card networks and acquirers settle the rest over the following days. Crypto payment processing works differently. The money moves on a public blockchain, every step is visible, and the processor's job is to turn a raw transfer into a clean, trustworthy order.

This guide follows a single crypto payment from the moment a customer clicks "Pay with crypto" to the moment the funds are settled. Along the way it covers confirmations, the edge cases that break simple setups, where the money sits in between, and what the fees really are.

What is crypto payment processing?

Crypto payment processing is everything that happens between a customer choosing to pay with cryptocurrency and the merchant treating that payment as final revenue. A processor quotes the price in crypto, creates a unique payment request, watches the blockchain, decides when the payment is final, and records the result so the order can be fulfilled, refunded and reported.

The biggest difference from card processing is who moves the money. With a card, the merchant asks the customer's bank for the funds and a network of intermediaries delivers them later. With crypto, the customer pushes the payment themselves, so the processor's main job is verification rather than collection.

The five stages of crypto payment processing

Every crypto payment passes through the same stages, whichever coin the customer uses. A good processor automates all of them, so neither you nor the customer has to think about what happens in between.

1. Quote

The customer sees your price in your currency, for example $89. The processor converts it into an exact amount of the chosen coin, fixes that amount for a limited time and issues payment details for this invoice only. The fixed quote protects both sides: the customer knows exactly what to send, and you know exactly what you will receive.

For tokens that exist on several blockchains, such as USDT and USDC, the quote must also fix the network. "120 USDT" is not a complete instruction; "120 USDT on Tron (TRC20)" is.

2. Broadcast and detection

The customer sends the transfer from their wallet or exchange, and it is broadcast to the network. The processor watches for transactions to the invoice's address and matches them to the order. Detection shouldn't depend on a single data source, because one slow or unavailable blockchain provider would otherwise leave paid orders looking unpaid.

3. Confirmation

A detected transaction isn't final. Each block added after the one that contains it is a confirmation, and each confirmation makes the payment harder to reverse. The processor waits for the coin's required number of confirmations before treating the payment as settled, and re-checks pending payments automatically so invoices move forward on their own.

4. Settlement

Settlement is the moment the funds count as yours. Depending on the processor, that means a balance credited in the processor's books or coins already sitting in a wallet you control. The difference matters more than it sounds, and it gets its own section below.

5. Fulfilment and recording

Once the invoice completes, the order is released. A license key is delivered, a file becomes downloadable, or a webhook tells your own system to activate an account. The transaction is recorded with every other sale, including its transaction hash, so anyone can audit it later.

Why confirmations matter, and how many are enough

It is tempting to release an order the moment a transaction appears. Don't. Until it is confirmed, a transaction can still be dropped, or replaced by one that pays someone else, and some fraud relies on exactly that window. Confirmations are what turn "seen" into "final".

How many confirmations are enough depends on the chain and on what is at stake. Bitcoin targets a new block roughly every ten minutes, so several confirmations take a while. Ethereum adds a block roughly every twelve seconds, and chains such as Tron, BNB Smart Chain and Solana produce blocks within seconds as well. A processor should set sensible thresholds per coin, so you never have to decide order by order.

• –Low-value digital goods can usually rely on the processor's default threshold.
• –High-value orders justify waiting longer, especially on chains with slower blocks.
• –In-person sales favour fast-confirming networks, so the customer isn't left waiting at the counter.

The edge cases that break simple crypto setups

Accepting crypto with a single wallet address works until the first unusual payment. These are the situations a processor has to handle without a human watching every transaction.

Wrong-network payments cause more support threads than any other stablecoin issue. Ethereum and BNB Smart Chain use the same address format, so a wallet will happily send to the right address on the wrong chain. Asking for the network before showing any address prevents most of them, and our guide to accepting USDT payments explains the networks in detail.

Late payments deserve a deliberate rule. If a customer pays after the quote has expired, the locked amount may no longer match your price. Silently accepting it can cost you money, and silently ignoring it creates an angry customer. Holding it for a quick human decision is the fair middle ground.

Crypto settlement: where the money sits between paid and withdrawn

This is the question that separates processors most clearly. In a custodial model the processor receives the coins into its own wallets and credits your account balance; you then request a withdrawal, on the processor's schedule and terms. In a non-custodial model the customer's payment goes straight to a wallet you control, and the processor only verifies and records it.

PapelShip Crypto POS settles this way. Each payment is sent directly to your own wallet, with no intermediary holding the funds. Digital orders are delivered once the blockchain confirms the payment, and each delivery is linked to its payment record. Incoming payments, transaction histories and wallet balances sit in the same dashboard as your card orders, and blockchain payment confirmations reach you as they happen.

Direct settlement gives you one job in return: the wallet's security. PapelShip secures the checkout, the order records and the payment notifications; you secure the wallet and its private keys. Treat its credentials like the keys to a safe, because that is exactly what they are.

Whichever model you choose, all of this complexity should collapse into a record your team can read in seconds. If answering any of these questions means opening a block explorer, the processor isn't doing its job.

Refunds run the process in reverse. A confirmed payment can't be pulled back, so a refund is a new transfer from your wallet to the customer. Ask for a refund address on the same network the customer paid on, rather than sending to the address the payment came from, which often belongs to an exchange, and record the refund against the original order so your revenue reports stay correct.

The real costs of crypto payment processing

Three different costs are often blurred together in sales pages. Separate them when you compare providers, because they are charged by different parties for different things.

• –Network fees are paid to the blockchain to move funds. The customer pays them when they send, and you pay them when you later move coins. They vary by chain and by how busy the network is, and each chain charges in its own coin.
• –Platform fees are what the processor charges for quoting, monitoring, recording and tooling, usually a percentage per transaction.
• –Conversion costs apply when a processor converts crypto into fiat for you, through a spread on the rate or a separate fee.

On PapelShip, the Free plan costs €0, Vaultie is €5.99 a month, and PapelShip+ is €14.99 a month, which brings crypto and card fees to 0%. The crypto fee for each plan is listed on the pricing page. Network fees are set by each blockchain, not by any processor, so be wary of any offer that claims to remove them.

A checklist for choosing a crypto payment processor

• –Fixed quotes with a visible expiry timer
• –One invoice and payment address per order
• –Explicit network selection for stablecoins
• –Automatic detection and confirmation tracking, with the count visible to you
• –Defined outcomes for partial, late and overpaid payments
• –Webhooks and an API, so your own systems hear about every payment
• –Refunds recorded against the original order
• –Cards in the same checkout for customers who prefer them, as covered in card and crypto payments in one checkout
• –A clear answer to who holds the funds
• –Fees you can read on a single page

If you are building your own integration, the crypto POS API guide shows how to wire these stages into your backend. For the wider picture of channels, custody and features, start with what a crypto POS system is.

Let the processor do the waiting

Crypto payment processing is mostly invisible when it works. The customer pays, the invoice completes and the coins are in your wallet before anyone has opened a block explorer.

That is the standard to hold a processor to: fixed quotes, automatic confirmations, defined edge cases, clear custody and fees you can read in one place. Everything else is detail.