Payment Glossary: 70+ Payment Terms and Definitions for 2026

Cart abandonment in payments happens when a buyer reaches checkout but drops off because of authentication friction, missing payment methods, or declines. It signals lost revenue and fixable checkout issues.

cart abandonment, checkout abandonment, abandoned checkout

An account range helps payments teams identify the exact card product behind a BIN so they can improve routing, manage fees, and respond to declines more effectively.

card range, PAN range, issuer account range

Account Updater refreshes stored card details when issuers replace cards, helping merchants reduce failed recurring charges, protect revenue, and limit involuntary churn.

card account updater, automatic card updater, billing updater

An acquirer is the financial institution that connects merchants to card networks, settles funds, and carries processing risk. The right setup can improve approvals and reduce payment friction.

acquiring bank, merchant acquirer

AML adds identity checks, sanctions screening, and transaction monitoring to payments. For merchants and PSPs, it can prevent illicit flows but also create false declines that hurt conversion.

AML, anti money laundering, AML compliance

A payment API connects checkout systems to gateways, processors, and banks so transactions, declines, and refunds move in real time. Strong API design supports smarter routing and better recovery from failed payments.

payments API, payment processing API, payments interface

An Application Identifier tells a terminal which card or wallet application and network to use. For payment teams, that choice affects routing costs, decline outcomes, and checkout performance.

AID, EMV AID, Application ID

Approval rate shows how many payment attempts issuers authorize. It helps payment teams spot decline drivers, improve routing, and recover revenue that would otherwise be lost.

authorization rate, payment approval rate, transaction approval rate

Payment authorization is the issuer decision that approves or declines a card transaction before capture. Strong authorization performance helps merchants reduce failed payments and protect revenue.

card authorization, auth, authorization request

AVS checks a shopper’s billing address against issuer records during authorization. Used well, it helps payment teams cut fraud without creating unnecessary false declines.

AVS, billing address verification, address verification

A backoff algorithm spaces failed payment retries over time instead of sending them immediately. Used well, it helps recover revenue, avoid false fraud signals, and control retry costs.

retry backoff, payment retry pacing, decline retry logic

A balance inquiry checks available funds on a card account without moving money. For payment teams, it helps prevent avoidable declines, support partial payments, and limit unnecessary processing costs.

balance check, available funds inquiry, balance request

Batch processing groups approved card transactions and submits them for settlement later, helping merchants simplify reconciliation, manage costs, and support workflows like delayed capture.

batch settlement, batch capture, end-of-day settlement

A billing descriptor is the statement text tied to a card transaction. Clear, recognizable descriptors help merchants cut friendly fraud, reduce chargebacks, and support stronger recurring payment performance.

statement descriptor, merchant descriptor, billing statement descriptor

A BIN identifies the card issuer, network, and product type at the start of a transaction. Payment teams use BIN data to refine routing, diagnose declines, and reduce false rejections.

Issuer Identification Number, IIN, card BIN

Payment capture is the step that converts an approved card hold into collected funds. Getting the timing right helps merchants secure revenue, avoid expired authorizations, and reduce refund overhead.

card capture, payment settlement request, capture request

A card network connects acquirers and issuers to authorize, route, and clear card payments. For payment teams, network rules and response codes can directly influence approval rates and retry strategy.

card scheme, payment network, card rail

Card Not Present refers to remote card payments made online, in apps, or through recurring billing. It affects fraud controls, interchange costs, and the data issuers use to approve or decline a transaction.

CNP, card absent transaction, remote card transaction

Card Present refers to an in-person payment where a physical card is read by a terminal. It usually brings lower fraud risk, stronger issuer trust, and better authorization performance.

CP, card-present transaction, face-to-face transaction

Cascading automatically sends a declined transaction to another processor or acquirer during checkout. Used well, it can recover soft declines and reduce revenue loss from outages or routing gaps.

payment cascading, cascaded payment processing, multi-acquirer cascading

CAVV is the cryptographic proof that a 3D Secure check succeeded. When payment systems pass it correctly, merchants reduce fraud exposure and avoid declines caused by broken authentication data.

Cardholder Authentication Verification Value, 3DS authentication value, 3D Secure cryptographic value

A chargeback is a bank-forced payment reversal after settlement. For merchants, it creates revenue loss, fees, and operational pressure that can hurt dispute ratios and future approval performance.

payment dispute, dispute reversal, issuer dispute

Credential on File lets merchants charge saved cards with issuer-visible consent data. When COF flags and linkage are correct, teams see fewer declines and smoother recurring billing.

COF, stored credentials, card on file

A customer-initiated transaction happens while the buyer is on session and actively completing checkout. Getting this first payment right supports stronger authentication, cleaner tokenization, and better downstream billing performance.

CIT, on-session transaction, cardholder-initiated transaction

CVV is the card security code used in online payments to help issuers verify card possession. For merchants, capturing it correctly can reduce false declines, block fraud, and support stronger authorization outcomes.

CVC, CID, card security code

A payment decline happens when an issuer refuses an authorization request. For merchants, understanding soft vs hard declines helps recover revenue, reduce false declines, and improve checkout performance.

declined payment, transaction decline, authorization decline

Decline codes explain why a card payment failed and whether it is worth retrying. For payment teams, they are a key input for reducing false declines, controlling retry costs, and recovering revenue.

issuer response code, payment decline code, authorization decline code

A digital wallet stores payment credentials as secure tokens and passes authenticated data into checkout. For merchants, that means faster payment flows, fewer false declines, and better conversion.

mobile wallet, e-wallet, digital payment wallet

Dispute resolution is the post-settlement process for handling contested card payments. Strong execution helps merchants limit revenue loss, control fees, and protect processor standing.

chargeback management, dispute process, payment dispute handling

Dunning helps subscription merchants recover failed recurring payments through timed retries and customer outreach, reducing involuntary churn and keeping valid subscribers active.

payment dunning, failed payment recovery, retry management

Dynamic routing uses real-time payment logic to send each transaction to the best acquirer or network. It helps teams lift approvals, reduce costs, and maintain checkout continuity during outages.

payment routing, intelligent routing, transaction routing

E-commerce payments are card-not-present transactions processed through gateways, acquirers, networks, and issuers. Getting them right helps merchants reduce declines, recover revenue, and protect checkout conversion.

online commerce, digital commerce, card-not-present commerce

EMV is the chip-based payment standard that replaces static card data with dynamic cryptograms. For merchants and PSPs, it reduces counterfeit fraud risk and supports more trusted transaction approvals.

chip card standard, EMV chip, Europay Mastercard Visa

Encryption protects payment data as it moves between checkout, gateways, networks, and issuers. Strong implementation helps teams prevent breaches, reduce avoidable declines, and keep transactions flowing reliably.

payment encryption, cryptographic protection, data encryption

An expiry date tells issuers whether a card credential is still valid. For merchants, stale expiry data can drive avoidable declines, especially in recurring billing and card-on-file flows.

card expiration date, card expiry, expiration date

Failover automatically reroutes transactions to a backup processor when the primary path fails. It helps merchants protect checkout continuity, reduce revenue loss, and avoid technical payment disruptions.

payment failover, processor failover, gateway failover

A false decline blocks a legitimate payment during authorization, often because issuer or fraud rules lack context. For merchants, that means lost sales, lower approval rates, and more checkout friction.

insult rate, incorrect decline, wrongful decline

A floor limit lets a merchant approve low-value card payments offline when speed or connectivity matters. The trade-off is higher exposure to delayed declines and unrecovered revenue.

offline limit, authorization floor limit, zero floor limit

Fraud detection screens transactions across checkout, gateways, networks, and issuers to stop unauthorized payments. Well-tuned controls reduce chargebacks without unnecessarily hurting conversion or approvals.

transaction fraud screening, payment risk screening, fraud checks

A payment gateway securely captures and routes payment data at checkout. Its setup can influence fraud controls, decline handling, routing quality, and overall payment performance.

gateway, payment gateway service, online payment gateway

Geographic blocking limits payments by IP, BIN, or address to reduce fraud and meet compliance rules. Poorly tuned rules can block valid cross-border customers and lower approval rates.

geo-blocking, location-based blocking, country blocking

A grace period keeps a subscription active after a failed renewal so billing systems can retry payment. Used well, it helps recover revenue and reduce involuntary churn.

payment grace period, billing grace period, recovery window

A hard decline means the issuer has permanently rejected a card or account. Merchants should stop retries, suppress avoidable costs, and ask the customer for a new payment method.

permanent decline, terminal decline, issuer hard decline

A high-risk merchant is a business banks and processors treat with tighter controls, higher fees, and more scrutiny, often leading to lower approval rates and reserve requirements.

high-risk business, high-risk merchant account, high-risk MCC merchant

An authorization hold temporarily reserves card funds before capture. For payment teams, managing holds well helps prevent false declines, support issues, and missed revenue.

pre-authorization hold, card authorization hold, funds hold

Installment payments split a purchase into fixed scheduled charges instead of one upfront payment. For merchants, the key challenge is recovering failed off-session charges without hurting approval rates.

instalment payment, payment installment plan, merchant-managed installment plan

Interchange is the issuer fee built into card settlement. For payment teams, it affects margins, card mix, routing choices, and how issuers behave on approvals and declines.

interchange, issuer fee, interchange rate

An issuer is the bank behind a customer’s card and the final authority on approval or decline. For payment teams, issuer behavior shapes retries, routing, and revenue recovery.

issuing bank, card issuer, issuer bank

Load balancing spreads transactions across multiple processors or acquirers so checkout stays available during spikes or outages. It helps reduce technical failures and protect revenue.

payment traffic distribution, transaction load distribution, processor load balancing

The Luhn Algorithm checks whether a card number is structurally valid before it reaches the network. For merchants, that means fewer typo-driven failures, lower processing waste, and smoother checkout flows.

Luhn check, mod 10 check, checksum validation

A Merchant Category Code classifies what a business sells and travels with each card transaction. The right code helps payment teams manage interchange, issuer risk checks, and avoid unnecessary declines.

MCC, merchant category code, merchant category

A merchant is the business that starts a card or digital payment by capturing customer details and sending an authorization request. How it manages declines, retries, and routing can directly affect recovered revenue.

seller, business merchant, merchant of record

Merchant Discount Rate is the total card processing cost deducted at settlement. Knowing its components helps payment teams control margin, compare pricing models, and spot how declines raise effective costs.

MDR, discount rate, merchant service charge

Merchant-initiated transactions let merchants charge stored payment methods when customers are off-session. Correct setup and retry logic can reduce declines and recover recurring revenue.

MIT, off-session payment, merchant initiated payment

MOTO payments let merchants key in card details from phone or mail orders. They support remote sales but need correct flagging, tighter risk controls, and careful decline handling to protect approvals.

mail order/telephone order, MOTO transaction, mail order payment

Network fees are card-brand charges for routing payment messages. They affect every authorization attempt, so poor retry logic and avoidable declines can quietly raise processing costs.

assessment fee, brand fee, card network assessment

NFC payments let customers tap cards, phones, or wearables to send tokenized credentials at the point of sale. For merchants, that means faster checkout, lower exposure to card data, and more reliable authorizations.

contactless payments, tap-to-pay, near field communication payments

Offline authorization lets a terminal approve a card transaction locally when no issuer connection is available. It helps merchants keep accepting payments, but shifts delayed-decline risk to the merchant.

offline auth, EMV offline approval, offline approval

An optimization engine evaluates transaction data, routing, and retry timing in real time to reduce avoidable declines, recover failed payments, and improve approval performance.

payment optimization engine, authorization optimization engine, payment decision engine

Payment rails are the networks that move transaction data and funds between banks. For merchants, rail selection shapes cost, settlement speed, and how often payments get approved.

payment network, payment scheme, funds transfer network

PCI DSS sets the security rules for handling card data across checkout, storage, and transmission. In practice, reducing PCI scope with tokenization lowers risk and supports smoother payment performance.

Payment Card Industry Data Security Standard, PCI compliance, PCI standard

A point of sale is the hardware or checkout flow that captures payment details and starts authorization. Its setup affects decline handling, fraud controls, and transaction success.

POS, payment terminal, checkout system

A payment processor routes transaction data between merchants, card networks, and issuers. Its uptime, data quality, and routing logic can affect approvals, costs, and resilience.

card processor, payment processing engine, processor

Queue management controls when payment requests reach gateways and issuers, helping merchants avoid rate-limit drops, reduce false declines, and protect checkout performance during bulk billing.

transaction queueing, payment queueing, request throttling

Retry logic automatically resubmits eligible declined payments based on issuer response codes and timing rules, helping merchants recover revenue while avoiding unnecessary network fees.

payment retries, intelligent retries, automated payment retries

A risk score helps payment teams judge whether a transaction should pass, be reviewed, or be blocked before authorization. Used well, it reduces false declines and protects revenue.

transaction risk score, fraud score, payment risk rating

Settlement is the stage where approved card payments actually reach the merchant. For payment teams, it shapes cash flow timing, reconciliation, and visibility into funding issues.

payment settlement, funding, clearing and settlement

A soft decline is a temporary issuer rejection that can often be recovered with better authentication, corrected request data, or well-timed retries to protect revenue.

temporary decline, recoverable decline, conditional decline

Strong Customer Authentication requires two-factor verification for many EEA online payments. Getting exemptions, 3D Secure flows, and retries right helps reduce false declines and protect conversion.

SCA, PSD2 SCA

Ticket size is the value of a single payment transaction. Payment teams use it to tune fraud rules, manage fees, and decide how to handle declines across low- and high-value payments.

transaction amount, order total, average ticket size

Tokenization replaces card numbers with safe identifiers merchants can store and reuse. It reduces data exposure, supports flexible routing, and helps recurring payments survive card updates.

card tokenization, payment tokenization, payment tokens

Merchant underwriting is how acquirers and PSPs assess a business before and during processing. It influences limits, reserves, account holds, and how safely merchants can scale transaction volume.

merchant risk assessment, merchant account underwriting, acquirer underwriting

A velocity check monitors how often a card, user, device, or IP attempts payment in a set window. Done well, it helps stop card testing without creating avoidable declines or retry failures.

velocity rule, velocity limit, transaction velocity check

Webhooks send real-time payment status updates to your systems so teams can automate fulfillment, manage declines, and keep transaction data aligned without constant polling.

event callback, HTTP callback, payment notification webhook

Yield optimization helps payment teams recover more approved transactions by improving routing, data quality, and retry timing. Done well, it lifts revenue and reduces avoidable payment failures.

payment optimization, authorization optimization, payment yield management

A zero-dollar authorization verifies a card without placing a hold, helping merchants safely vault credentials, reduce avoidable declines, and support smoother recurring billing.

account status inquiry, $0 authorization, zero amount authorization

3D Secure adds cardholder authentication before authorization, helping merchants reduce fraud and shift certain chargeback liability while managing checkout friction and approval performance.

3DS, 3DS2, payer authentication