Processors & Crypto Cards — How Payments Work in the Wild
See how merchant invoices, confirmations, and refunds actually work. Learn the pros/cons of custodial processors and crypto cards. Finish with your own 'How I will pay invoices' flowchart.
- Understand custodial vs self-hosted payment processors and the typical invoice flow.
- Know how amount locks, network selection, and confirmations affect success and timing.
- Recognize how processors handle under/over/late payments.
- Evaluate crypto cards: convenience, fees, KYC, regional availability, custodial risk.
- Practice a mock payment and capture the confirmation flow for your notes.
- Produce a printable flowchart for how you'll pay invoices safely.
9.1 Processors 101: custodial vs self-hosted
A processor generates a time-limited invoice and detects your payment on-chain (or Lightning). Some hold your funds (custodial), others let merchants self-host (e.g., BTCPay-like).
Custodial Processors
Quick setup, multiple networks, compliant features (KYC/AML), but add counterparty risk and fees/spreads.
Self-hosted Processors
More control, lower fees, higher operational complexity; merchant bears infrastructure and compliance responsibilities.
Invoice Anatomy
Amount in fiat, exchange rate lock for X minutes, QR code (address+amount), supported networks, countdown timer.
Confirmations
Varies by network/amount/risk policy (e.g., 0–1 for Lightning, 1–3 for on-chain small payments). Processor shows: Pending → Confirmed → Credited.
Volatility Handling
Rate is locked for the invoice window; after expiry, a new rate applies.
Network Requirements
Match network exactly; some chains require tags/memos (e.g., destination tag/memo on certain networks); processors show these fields explicitly.
- Pay from a wallet you control, on the exact network shown
- Send within the countdown window; wait for required confirmations
- If unsure, send a small test first and then the remaining amount
- Paying after expiry or on the wrong network
- Sending from exchanges with slow withdrawals when timer is short
- Ignoring required memo/tag fields on networks that use them
9.2 Under/over/late payments
Underpayment
Sent less than required
Outcome: Processor may request a top-up within the window or mark invoice as underpaid and offer a refund path (minus fees).
Overpayment
Sent more than required
Outcome: Excess may be refunded to your sending address per policy. Expect delays and identity checks for larger amounts.
Late Payment
After timer expired
Outcome: Payment detected but rate lock expired → refund or manual review.
Wrong Network/Token
Sent on unsupported chain
Outcome: Often unrecoverable. Some processors can't see funds on unsupported chains. Always double-check chain and token standard.
9.3 Crypto cards (virtual and physical): convenience vs control
Crypto cards feel like normal cards. They are convenient but typically custodial and require KYC.
Funding
Top-up crypto → provider converts to fiat on swipe; or auto-sell at POS.
Fees
Spread on conversion, card/FX/ATM fees, possible monthly/issuance fees.
Custodial Risk
Provider can freeze funds or block transactions due to policy/region compliance.
Availability
KYC, residency, and regional rules apply; virtual cards may work for online subscriptions.
Privacy
Transactions are card-network visible; not private crypto payments.
Spread Fee
$2.50
Total Fee
$4.00
Effective Rate
4.00%
- Keep small balances on card accounts; use 2FA; lock card in app when idle.
- Separate funding wallet from your main holdings.
- Read fee schedules; beware 'cashback' bait that hides spreads.
- Keep small balances; top-up as needed
- Use 2FA and lock card when not in use
- Separate funding wallet from main holdings
- Read and compare fee schedules
- Storing large amounts on card accounts
- Ignoring conversion spreads and hidden fees
- Using card for large purchases without fee awareness
- Trusting 'cashback' promises without reading terms
9.4 Practice: mock invoice walkthrough
Walk through a simulated invoice, choose a network, and record the confirmation flow (screenshots or printable steps).
Amount
$49.00 USD
Lock Time
15 minutes
9.5 Deliverable: 'How I will pay invoices' flowchart
Define your default decision path for paying crypto invoices and when you'll use a card instead. No secrets are collected; generated locally.
Decision Flow Nodes
Exceptions: Under/over/late → follow processor's refund/top-up instructions; document tx hash and support ticket ID.
This is for your operational workflow. Do not enter seeds, private keys, or full card numbers.
- • Processor documentation (invoice, confirmations, refunds): check your provider's official help center.
- • Self-hosted payments: BTCPay-style docs and guides.
- • Card programs: official fee schedules and region availability pages.
Compliance Notice
Educational content only — not financial, legal, or tax advice. Policies, fees, and availability change. Always verify the invoice network and timer; use small test amounts if possible. Crypto cards are custodial: your access can be restricted by provider policy.
9.6 Quick Quiz
Mini-Quiz
Test your understanding with 6 questions. Pass with 4/6 correct.