Blockchain in Payments

A distributed, append-only ledger where records (blocks) are cryptographically linked in sequence. Each block contains the previous block's hash, a timestamp, and a Merkle root of transactions — making history tamper-evident without a central authority.

A broad category of shared databases maintained across multiple nodes with no single point of control. Blockchain is one DLT type; Directed Acyclic Graph (DAG) structures used by Hedera Hashgraph and Nano are others.

A computer that maintains a complete copy of the blockchain and independently validates every transaction and block against the consensus rules. Full nodes are the backbone of decentralization — no single node is trusted over another.

A network participant that proposes and attests to new blocks. In PoW chains these are miners; in PoS chains they are validators who stake collateral. Validators earn block rewards and transaction fees in return for securing the network.

The algorithm by which distributed nodes agree on the canonical state of the ledger. Bitcoin uses Proof of Work (PoW); Ethereum uses Proof of Stake (PoS). Consensus defines throughput, finality latency, and energy profile — key constraints for payment use cases.

A consensus mechanism where miners compete to find a nonce such that SHA-256(block header) < target. The winner earns the block reward. Provides the highest security guarantees but is energy-intensive and limits throughput (~7 TPS for Bitcoin).

A consensus mechanism where validators lock up (stake) native tokens as collateral to earn the right to propose and attest to blocks. Slashing penalizes dishonest validators. Used by Ethereum (post-Merge 2022), Cardano, and Solana.

A property of a distributed system that can reach consensus even if up to 1/3 of nodes are malicious or fail. PBFT and Tendermint (Cosmos) are BFT protocols; the Ripple Consensus Protocol is a federated variant. Critical for permissioned chains used in wholesale payments.

The point at which a transaction is irreversible. Bitcoin uses probabilistic finality (6 confirmations ≈ 60 min); Ethereum provides economic finality after two checkpoint epochs (~12.8 min); XRPL achieves 3–5s finality. A critical metric for payment settlement design.

The number of blocks added on top of the block containing a transaction. More confirmations make a double-spend attack exponentially more expensive. Bitcoin payment processors typically require 1–6 confirmations; high-value transactions up to 30.

An attack where the same UTXO is spent in two conflicting transactions. Consensus prevents this in the main chain; payment channels and Layer 2 systems require additional guards (HTLCs, time locks) to prevent off-chain double-spends.

The process of creating new blocks in a PoW blockchain. Miners bundle pending transactions, construct a candidate block, and hash it with different nonces until finding a valid hash. The winner proposes the block and earns the reward plus fees.

The queue of unconfirmed transactions on each node waiting to be included in a block. Miners prioritize higher-fee transactions. During congestion the mempool grows and fees spike — a key variable in payment cost modelling.

The first block in a blockchain (block 0). It has no predecessor and is hard-coded in the node software. Bitcoin's genesis block (3 Jan 2009) includes Satoshi Nakamoto's message: "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks."

A protocol rule change. A soft fork is backwards-compatible (old nodes still accept new blocks). A hard fork creates an incompatible chain split (Bitcoin Cash from Bitcoin, Ethereum Classic from Ethereum). Payment integrations must monitor planned forks to avoid replay attacks.

The hash function at Bitcoin's core: used in PoW (mining), Merkle trees (transaction IDs), and address derivation (hash160 = RIPEMD160(SHA256(pubkey))). Produces a 256-bit digest; second-preimage resistance makes history forgery computationally infeasible.

Ethereum's primary hash function. Used for address derivation (last 20 bytes of Keccak-256(pubkey)), EVM storage slot keys, event topic IDs, and Solidity ABI encoding. A variant of SHA-3 using the Keccak sponge construction.

A binary tree where leaf nodes are transaction hashes and each parent is the hash of its two children. The Merkle root (32 bytes) stored in the block header binds all transactions. Enables SPV proofs — lightweight clients can verify a transaction was included without the full block.

The elliptic curve used by Bitcoin, Ethereum, and most blockchains for key generation and ECDSA signing. A 256-bit curve providing ~128-bit security. The same private key generates different addresses on different chains due to different encoding and derivation.

The signing algorithm authorizing blockchain transactions. A transaction signed with the private key proves ownership of the corresponding address without revealing the key. Ethereum adds EIP-155 chain ID to prevent cross-chain replay attacks.

An efficient signature scheme activated in Bitcoin with Taproot (BIP-340). Enables key aggregation (multiple signers produce one compact signature), batch verification, and simpler multi-sig. Smaller witness data reduces transaction fees.

A random 256-bit number that fully controls a blockchain address. Anyone holding the private key can sign transactions and spend funds. Never transmitted on-chain; loss means permanent loss of funds. Custody (hardware wallet, HSM, MPC) is the critical security decision.

Derived from the private key via elliptic curve scalar multiplication on secp256k1. Not secret — it is used to verify signatures. The blockchain address is a compressed encoding of the public key (hash + checksum).

A human-readable identifier for a receiving endpoint. Bitcoin uses Base58Check (P2PKH: starts with 1) or Bech32 (P2WPKH: starts with bc1). Ethereum uses 20-byte hex with EIP-55 checksum casing. Addresses are not accounts — they hold UTXOs or EVM state.

A 12 or 24-word backup of an HD wallet's master seed (BIP-39). The mnemonic deterministically re-generates all private keys. Anyone with the seed phrase controls all funds across all derived addresses. The highest-value secret in a crypto payment system.

A wallet deriving all key pairs from a single root seed using a tree of child keys (BIP-32). One seed phrase backs up infinite addresses. BIP-44 standardizes the derivation path: m/44'/coin'/account'/change/index — enabling account isolation across coins and chains.

Three interdependent Bitcoin Improvement Proposals: BIP-32 defines HD key derivation, BIP-39 defines mnemonic encoding of the seed entropy, BIP-44 standardizes coin-type derivation paths. Universally adopted across hardware wallets (Ledger, Trezor) and mobile wallets.

A key management technique where the private key is never assembled in one place — multiple parties each hold a share; signatures are computed jointly using threshold ECDSA or Schnorr without reconstructing the full key. Used by Fireblocks, Coinbase Prime, and Anchorage for institutional custody.

A model where the user holds their own private keys (or seed phrase) and signs transactions directly, with no third party able to move or freeze their funds — "not your keys, not your coins". The opposite is custodial holding, where an exchange or provider controls the keys on the user's behalf. Self-custody removes counterparty and exchange-insolvency risk but shifts the full burden of key security and backup onto the user: lose the seed phrase and the funds are unrecoverable. Implementations range from hardware wallets (Ledger, Trezor) and mobile/browser non-custodial wallets to MPC and multisig setups that reduce single-point-of-failure risk.

A cryptographic method proving a statement is true without revealing underlying data. ZK-SNARKs (succinct, trusted setup) and ZK-STARKs (transparent, larger proofs) are used in ZK rollups (validity proof for batch of transactions) and CBDC privacy designs.

A lightweight method (BIP-37) for a client to verify a transaction was included in a block using only block headers and a Merkle proof, without downloading the full chain. The basis for most mobile Bitcoin wallets and payment verification in low-resource environments.

Bitcoin's accounting model. Every transaction consumes previous outputs (UTXOs) as inputs and creates new outputs. Your "balance" is the sum of UTXOs locked to your addresses. This model enables parallel validation, simplifies auditing, and is analogous to physical coins.

Ethereum's ledger model: each address has a balance and nonce. Transactions debit/credit balances directly (like a bank account). Simpler for smart contracts than UTXO but requires nonce ordering to prevent replay and imposes sequential execution constraints.

The unit of computational work in the Ethereum EVM. Each opcode costs a fixed gas amount; the sender sets a max fee (EIP-1559: base fee + priority tip). Total fee = gas used × effective gas price. Gas prevents infinite loops and aligns economic incentive with resource consumption.

Ethereum's fee reform (August 2021). A protocol-managed base fee is automatically adjusted per block and burned (making ETH deflationary). Users add a priority tip to incentivize validators. Fees become more predictable for payment integrations — replacing the unpredictable first-price auction.

The incentive paid to block producers for including a transaction. In Bitcoin: fee = sum(inputs) − sum(outputs). In Ethereum: fee = gas used × effective gas price. Fees spike when block space is scarce. Fee estimation is a critical component of payment gateway UX.

A Layer 2 payment channel network on Bitcoin. Two parties lock funds in a multi-sig UTXO (channel open), exchange signed off-chain state updates at near-zero fee, then settle on-chain by broadcasting the final state (channel close). Enables sub-second Bitcoin micropayments at millions of TPS.

A mechanism where two parties lock funds on-chain in a multi-sig or smart contract, then exchange off-chain signed state updates. Only the channel open and close transactions are broadcast. Used by Lightning (Bitcoin), Raiden (Ethereum), and general state channel designs.

A smart contract primitive for conditional payment. Funds are locked until the recipient reveals a secret (hashlock) within a deadline (timelock). Lightning uses HTLCs for multi-hop routing — all hops complete or all refund atomically, enabling trustless payment routing across third-party nodes.

A trustless cross-chain exchange using paired HTLCs. Two parties swap assets on different blockchains without a custodian: each locks funds with the same hashlock; revealing the secret on one chain reveals it on the other, completing both legs atomically.

Off-chain protocols inheriting the security of a Layer 1 blockchain while extending throughput and reducing fees. Types: payment channels (Lightning), optimistic rollups (Arbitrum, Optimism), ZK rollups (zkSync, Starknet), and state channels. Critical for reaching payment-scale TPS.

A Layer 2 that executes transactions off-chain and posts either compressed data (optimistic rollup) or validity proofs (ZK rollup) to Layer 1. Optimistic rollups (Arbitrum, Optimism) have a 7-day challenge period; ZK rollups (zkSync, Starknet) provide instant finality via cryptographic proofs.

An independent blockchain with its own consensus linked to a parent chain via a two-way peg. Assets move via locking/minting (bridge). Polygon PoS is an Ethereum sidechain. Sidechains are faster to launch than rollups but have weaker inherited security.

A protocol moving assets between two blockchains: lock asset on source chain, mint wrapped version on destination. Bridge smart contracts hold large TVL and are a frequent exploit target (Ronin Bridge $625M, Wormhole $320M). Trust assumptions (centralized vs. light-client-based) vary widely.

Transferring value or messages between separate blockchains. Approaches: bridges (lock/mint), atomic swaps (trustless, slow), IBC protocol (Cosmos), Chainlink CCIP (message passing), and XCMP (Polkadot). Essential for multi-chain payment routing and stablecoin portability.

The Cosmos standard for passing authenticated messages and tokens between IBC-enabled chains. Uses light-client proofs to verify state without trusting a third party. The de facto standard for the Cosmos ecosystem and a blueprint for trustless cross-chain payment networks.

A digital asset designed to maintain a stable value relative to a reference currency (usually USD). Types: fiat-backed (USDC, USDT — off-chain reserves), crypto-backed (DAI — over-collateralized), and algorithmic (undercollateralized; historically volatile). The primary medium for crypto-native payments.

A fiat-backed stablecoin issued by Circle, regulated in the US. Each USDC is backed 1:1 by USD (cash + short-term T-bills), with monthly attestations. Available on Ethereum, Solana, Avalanche, Base, XRPL, and others. The dominant stablecoin for institutional payments and DeFi.

The largest stablecoin by market cap (~$190B), issued by Tether Ltd. Dominant in trading pairs and cross-border remittances in emerging markets (Philippines, Nigeria, Argentina). Deployed across ~10 chains — Tron (TRC-20) and Ethereum (ERC-20) hold the bulk of supply. Reserves are now ~80% US Treasury bills plus cash, gold, and BTC, attested quarterly by BDO Italia. Not MiCA-authorised, so delisted for EEA users since 2025. See the dedicated Tether (USDT) guide tab.

A decentralized crypto-collateralized stablecoin issued by MakerDAO. Users lock ETH or RWA in vaults and mint DAI at > 150% collateralization. Soft-pegged to USD via a stability fee. Censorship-resistant — no issuer can freeze a wallet.

A digital currency issued and backed by a central bank — the digital equivalent of fiat cash. Retail CBDCs target consumers (e-CNY, Digital Euro); wholesale CBDCs target interbank settlement (Project mBridge). Key design decisions: token vs account-based, privacy model, programmability, and intermediary role.

A CBDC restricted to financial institutions for large-value settlement and cross-border payments. Project mBridge (BIS) tested multi-CBDC payments across 5 central banks. Seen as a near-term application that does not disintermediate retail banks.

A representation of an asset from one blockchain issued as a token on another. WBTC (Wrapped Bitcoin) on Ethereum is an ERC-20 backed 1:1 by BTC held by a custodian. Enables Bitcoin liquidity in Ethereum DeFi. Introduces custodial risk.

The international standard (2020) defining official vocabulary for blockchain and DLT: DLT, distributed ledger, permissioned / permissionless chain, smart contract, node, consensus, genesis block. Used in regulations, contracts, and technical specifications to ensure interoperability of terminology.

The Ethereum token interface standard defining 6 required functions (transfer, transferFrom, approve, allowance, balanceOf, totalSupply) plus 2 events. All compliant tokens are interoperable with any ERC-20-aware wallet or exchange. The foundation of the DeFi token economy — USDC, DAI, and thousands of payment tokens implement ERC-20.

The Ethereum standard for non-fungible tokens — each token has a unique ID and owner. Used for ticketing, identity credentials, loyalty programs, and proof-of-payment NFTs. Smart contract royalties (EIP-2981) enable new merchant revenue models on secondary sales.

FATF Recommendation 16 applied to virtual assets. VASPs must collect and share originator/beneficiary information (name, address, wallet address) for transactions ≥ USD 1,000/EUR 1,000. Implemented via TRISA, OpenVASP, Notabene, and similar VASP-to-VASP messaging protocols.

FATF's category for entities that exchange, transfer, safeguard, or administer virtual assets on behalf of others. Includes exchanges (CEX), custodians, and some DeFi protocols. VASPs are subject to AML/CFT registration, KYC requirements, and the Travel Rule.

Know Your Customer and Anti-Money Laundering requirements for crypto VASPs. Exchanges must verify user identity (passport, proof of address, source-of-funds). On-chain analytics platforms (Chainalysis, Elliptic, TRM Labs) trace fund flows and screen against OFAC sanctioned addresses.

EU regulation (effective 2024–2025) establishing a comprehensive framework for crypto asset issuers and service providers. Covers e-money tokens (stablecoins pegged to a currency), asset-referenced tokens (ARTs), and Crypto Asset Service Providers (CASPs). The first major unified jurisdiction-wide crypto regulatory framework.

The formal process for proposing Bitcoin protocol changes. Key BIPs: BIP-32 (HD wallets), BIP-39 (mnemonics), BIP-44 (derivation paths), BIP-141 (SegWit), BIP-340/341 (Schnorr/Taproot), BIP-370 (PSBT v2). Consensus requires broad miner and full-node adoption — no single party controls it.

The governance process for Ethereum protocol changes. Core EIPs: EIP-1559 (fee market), EIP-4844 (blob transactions for rollups), EIP-4337 (account abstraction), EIP-2612 (ERC-20 permit). ERCs are the application-layer token standard subset of EIPs.

An Ethereum standard allowing smart contract wallets (not just EOA private keys) to initiate transactions. Enables gasless transactions (paymaster pays fee), social recovery (replace lost key via guardians), batched operations, and spending limits. Critical for mainstream crypto payment UX.

Self-executing code stored on a blockchain running deterministically when called. Written in Solidity (Ethereum), Rust (Solana, Near), or Cairo (Starknet). Enables programmable money: escrow, lending, DEX, subscriptions, and conditional payments — without custodians or intermediaries.

The sandboxed, deterministic, stack-based runtime that executes smart contract bytecode identically on every Ethereum node. EVM-compatible chains (Polygon, Avalanche, BSC, Arbitrum, Base, zkSync) share tooling and Solidity contracts. Gas metering prevents resource abuse.

Financial services built on smart contracts with no custodial intermediary: lending (Aave, Compound), DEXs (Uniswap, Curve), derivatives (dYdX), yield aggregators, and stablecoin issuance. DeFi replaces intermediaries with auditable open-source code but introduces smart contract, oracle, and liquidity risk.

A DEX design where liquidity is pooled in a smart contract instead of matched in an order book. Price is set algorithmically (Uniswap v2: x·y = k; Curve: stable-swap invariant). Liquidity providers earn trading fees. Enables instant token swaps useful for payment FX conversion.

A service bridging real-world data (exchange rates, payment status, identity) to smart contracts. Chainlink is the dominant decentralized oracle network. Payment contracts need oracles to trigger settlement on fiat events, verify off-chain delivery, or access currency exchange rates.

A wallet requiring M-of-N key signatures to authorize a transaction. Bitcoin native multi-sig (P2MS, P2SH); Ethereum smart contract multi-sig (Gnosis Safe). Used for corporate treasury, exchange hot wallets, payment escrow requiring multiple approvals, and DAO governance.

A unique on-chain token (ERC-721 or ERC-1155) representing ownership of a digital or physical asset. Payment use cases: event ticketing, loyalty credentials, subscription passes, proof of payment, and royalty-bearing digital goods. Smart contract royalties enable programmable revenue splits.

The ability to embed spending conditions in currency via smart contracts. Examples: conditional release on delivery confirmation (escrow), automatic royalties on secondary NFT sale, time-locked salary streaming (Superfluid, Sablier), multi-party approval workflows, and CBDC spending restrictions.

The set of wallet features enabling consumer-grade payment experiences: QR-code payment (Solana Pay, Lightning invoices), sign-in with Ethereum (EIP-4361), gasless meta-transactions, one-click bridging, and fiat on-ramp integrations. ERC-4337 account abstraction is the key enabler.

The first and largest blockchain by market cap. PoW (SHA-256), UTXO model, ~10-min blocks, ~7 TPS base layer. Primary use case: censorship-resistant value storage and payment rail. Lightning Network extends it for micropayments. BIP-341 Taproot (2021) enables complex spending conditions with smaller footprint.

The largest smart contract platform. PoS (post-Merge 2022), account model, ~12s blocks, ~15–30 TPS base layer. Hosts DeFi, stablecoins (USDC, DAI), and ERC-20 tokens. Rollups extend it to thousands of TPS. EIP-4844 (blobs) reduced rollup data costs 10×.

A payment-focused blockchain using a federated BFT consensus. ~3–5s finality, 1,500 TPS, < $0.001 fees. Built-in DEX and issued-currency ledger. Used by RippleNet for cross-border bank payments as a SWIFT correspondent banking alternative. Native CBDC and stablecoin issuance features.

A payment-focused open network using the Stellar Consensus Protocol (SCP, federated BFT). Supports issued assets (CBDCs, stablecoins), built-in DEX, and path payments (multi-hop FX conversion in one transaction). Used by MoneyGram and Circle for remittances. Hosts USDC.

A high-throughput blockchain using PoS + Proof of History (a verifiable delay function as a global clock). ~400ms block time, 65,000 TPS theoretical, < $0.001 fees. Used for high-frequency DeFi, NFTs, and merchant payments via USDC and Solana Pay.

Blockchain eliminates correspondent banking chains by enabling direct wallet-to-wallet settlement in seconds rather than 1–5 days. Stablecoins (USDC, USDT) and networks like Stellar and XRPL are used by remittance providers (MoneyGram, Bitso, Strike) to settle value across borders at < 1% cost vs. traditional wire transfers.

Finalizing financial obligations by transferring blockchain assets. DvP (Delivery vs. Payment) can be atomic in a smart contract — both legs settle simultaneously with no counterparty or settlement risk. JP Morgan's JPM Coin and BNY Mellon pilots use permissioned blockchains for intraday USD settlement.

A service accepting crypto payments and optionally converting to fiat for merchants (BitPay, Coinbase Commerce, Stripe Crypto, Strike). Key features: QR checkout, automatic fiat conversion at spot rate, stablecoin settlement, on/off-ramp liquidity. Shields merchants from crypto price volatility.

Services converting between fiat and crypto. On-ramp: fiat → crypto (exchange or bank ACH/card buy). Off-ramp: crypto → fiat (sell/withdraw to bank). Critical for real-world utility. Regulated as money services businesses (MSBs) in most jurisdictions; KYC/AML required.

A custodial platform where users deposit funds and trade against an order book (Coinbase, Binance, Kraken). The primary on/off-ramp. Subject to VASP regulations and Travel Rule. Internal settlement is off-chain; only net withdrawals hit the blockchain.