Payments glossary

Definitions and usage guidance for 255 payment terms. Search a term, compare its meaning, and check the source scope before using it in a procedure.

The collection contains 56 single-word headwords and 199 multiword terms. These are Atlas editorial proposals, not approved additions to the ASD-STE100 dictionary. They are terminology entries, not a complete general-English vocabulary.

One meaning needs a context. Network rules, provider APIs and operational stages can use similar words differently. Keep source names, editions and exact technical identifiers when that distinction matters.

Use the glossary with Atlas Payments English · See wording examples · Download the glossary as JSON · MIT license

#

3-D Secure (3DS)

Protocol framework for authenticating cardholders in supported remote card-payment flows.

Recommended usage and sources

Usage: State the EMV 3DS version, result, and implementation. Authentication does not guarantee authorization or a universal liability shift.

Atlas editorial proposal · G109. Source scope matters; this entry is not an ASD vocabulary approval.

3DS server

Merchant-side or provider-side component that initiates and manages 3DS authentication interactions.

Recommended usage and sources

Usage: Name the provider and protocol version. Distinguish its reference from Directory Server and ACS identifiers.

Atlas editorial proposal · G112. Source scope matters; this entry is not an ASD vocabulary approval.

A

access control server (ACS)

Issuer-side 3DS component that assesses authentication and may conduct a cardholder challenge.

Recommended usage and sources

Usage: Use ACS for the authentication component; it is not the acquirer or a payment authorization server.

Atlas editorial proposal · G111. Source scope matters; this entry is not an ASD vocabulary approval.

account

Record and contractual relationship used to hold a balance or process financial activity.

Recommended usage and sources

Usage: Name the account type and its holder; distinguish a card account from a merchant or platform account.

Atlas editorial proposal · G001. Source scope matters; this entry is not an ASD vocabulary approval.

account holder

Person or entity that holds the specified account.

Recommended usage and sources

Usage: Specify whether this means a cardholder, merchant, platform user, or bank-account holder.

Atlas editorial proposal · G002. Source scope matters; this entry is not an ASD vocabulary approval.

account range

Defined subset of account numbers with specified processing or product attributes.

Recommended usage and sources

Usage: State the range length and data source. Do not call every longer card prefix a separate BIN.

Atlas editorial proposal · G048. Source scope matters; this entry is not an ASD vocabulary approval.

account takeover (ATO)

Unauthorized control or use of an existing customer or user account.

Recommended usage and sources

Usage: Separate account compromise, payment-credential theft, and the later payment outcome; one does not automatically prove the others.

Atlas editorial proposal · G138. Source scope matters; this entry is not an ASD vocabulary approval.

account updater

Service that supplies changes to stored card-account details.

Recommended usage and sources

Usage: Name the network or provider service. An update does not guarantee approval of a later payment.

Atlas editorial proposal · G003. Source scope matters; this entry is not an ASD vocabulary approval.

account verification

Assessment of specified account details, ownership, status, or usability.

Recommended usage and sources

Usage: State what is verified and by which mechanism. A zero-value card check is not the same as bank-account ownership verification.

Atlas editorial proposal · G238. Source scope matters; this entry is not an ASD vocabulary approval.

ACH

US Automated Clearing House system and associated payment arrangements.

Recommended usage and sources

Usage: Specify ACH credit or debit and the applicable entry and return rules. Do not use ACH chargeback as a substitute for an exact ACH return code.

Atlas editorial proposal · G242. Source scope matters; this entry is not an ASD vocabulary approval.

ACH return

Return of an ACH entry using the applicable return process and code.

Recommended usage and sources

Usage: Retain the precise code and return context. Do not apply card-network dispute stages or deadlines to ACH returns.

Atlas editorial proposal · G243. Source scope matters; this entry is not an ASD vocabulary approval.

acquirer

Institution acting for the merchant in acquiring card transactions.

Recommended usage and sources

Usage: Use the role name when responsibilities matter. A gateway or processor is not automatically the acquirer.

Atlas editorial proposal · G004. Source scope matters; this entry is not an ASD vocabulary approval.

acquirer reference number (ARN)

Reference used to trace a card transaction or refund through acquiring and network processing.

Recommended usage and sources

Usage: Write the full name before ARN. Keep it distinct from a provider payment ID and a Visa Transaction Identifier.

Atlas editorial proposal · G006. Source scope matters; this entry is not an ASD vocabulary approval.

acquiring

Activity of accepting and submitting merchant transactions into the applicable payment system.

Recommended usage and sources

Usage: Identify the acquirer, processing route, and market. Do not equate acquiring with software gateway services.

Atlas editorial proposal · G005. Source scope matters; this entry is not an ASD vocabulary approval.

address verification service (AVS)

Service that compares supplied address information with issuer-held address information.

Recommended usage and sources

Usage: Report the actual result and supported fields. An AVS match does not prove identity or eliminate fraud risk.

Atlas editorial proposal · G007. Source scope matters; this entry is not an ASD vocabulary approval.

aggregator merchant

Intermediary that performs specified merchant-acquiring functions under an acquirer arrangement.

Recommended usage and sources

Usage: Describe the contracted functions. Do not assume all aggregators, marketplaces, and payment facilitators have identical roles.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Aggregator merchant

Atlas editorial proposal · G008. Source scope matters; this entry is not an ASD vocabulary approval.

allow list

List of entities or attributes given a specified permitted treatment by a risk system.

Recommended usage and sources

Usage: State the matching scope and action. Listing a customer does not override issuer declines or every provider control.

Atlas editorial proposal · G150. Source scope matters; this entry is not an ASD vocabulary approval.

application programming interface (API)

Defined interface through which software requests data or operations from another system.

Recommended usage and sources

Usage: Use exact endpoint, field, and enum names. Distinguish submitting a request from receiving its final outcome.

Atlas editorial proposal · G009. Source scope matters; this entry is not an ASD vocabulary approval.

application status

Recorded state of an object in a specified provider or application lifecycle.

Recommended usage and sources

Usage: Preserve exact enum names and distinguish them from network stages and financial outcomes.

Atlas editorial proposal · G255. Source scope matters; this entry is not an ASD vocabulary approval.

attempt response

Visa Secure response indicating that the authentication request reached an attempts-related outcome defined by the network.

Recommended usage and sources

Usage: Keep the exact result and eligible transaction context. Do not promise liability shift from the word attempts alone.

Atlas editorial proposal · G117. Source scope matters; this entry is not an ASD vocabulary approval.

authentication

Assessment of identity or credential authenticity using the applicable authentication method.

Recommended usage and sources

Usage: Specify shopper, device, credential, or chip authentication. It is separate from financial authorization.

Atlas editorial proposal · G010. Source scope matters; this entry is not an ASD vocabulary approval.

authentication request

Message requesting an authentication assessment.

Recommended usage and sources

Usage: For EMV 3DS, preserve the exact message name and version; do not call it an authorization request.

Atlas editorial proposal · G011. Source scope matters; this entry is not an ASD vocabulary approval.

authentication response

Message carrying the result or next step of an authentication assessment.

Recommended usage and sources

Usage: Preserve the protocol result and any challenge requirement. Do not translate it into payment approval.

Atlas editorial proposal · G012. Source scope matters; this entry is not an ASD vocabulary approval.

authorization

Decision by an authorized issuer, processor, or stand-in service to approve a transaction.

Recommended usage and sources

Usage: Name the decision-maker and outcome. Approval is not capture, clearing, settlement, or a guarantee against disputes.

Atlas editorial proposal · G013. Source scope matters; this entry is not an ASD vocabulary approval.

authorization approval rate

Proportion of the stated authorization-request population that received approval.

In practice: Choose a payment-performance baseline

Recommended usage and sources

Usage: Specify counting unit, attempts or unique payments, dates, exclusions, and partial approvals. This is a measurement definition, not a universal network formula.

Atlas editorial proposal · G220. Source scope matters; this entry is not an ASD vocabulary approval.

authorization code

Code returned to indicate authorization approval.

Recommended usage and sources

Usage: Retain the exact value. It is not a generic payment ID or proof that the merchant received funds.

Atlas editorial proposal · G017. Source scope matters; this entry is not an ASD vocabulary approval.

authorization hold

Reservation of available funds or credit associated with an approved authorization.

Recommended usage and sources

Usage: Separate the approved amount, held amount, hold release, and final debit. Do not promise a universal expiry period.

Atlas editorial proposal · G018. Source scope matters; this entry is not an ASD vocabulary approval.

authorization request

Request for authorization of the specified transaction.

Recommended usage and sources

Usage: Identify the amount, currency, and transaction context. A submitted request does not establish that approval occurred.

Atlas editorial proposal · G014. Source scope matters; this entry is not an ASD vocabulary approval.

authorization response

Reply to an authorization or applicable account-verification request.

Recommended usage and sources

Usage: Keep approval, decline, and other response outcomes separate; preserve provider and network codes.

Atlas editorial proposal · G015. Source scope matters; this entry is not an ASD vocabulary approval.

authorization reversal

Message that cancels or reduces a prior authorization under the applicable network rules.

Recommended usage and sources

Usage: Specify full or partial reversal. Do not call it a refund or promise immediate restoration of available funds.

Atlas editorial proposal · G025. Source scope matters; this entry is not an ASD vocabulary approval.

B

bank identification number (BIN)

Licensed leading digits used to identify an issuing institution or designated account range.

Recommended usage and sources

Usage: Use the applicable network's BIN length; legacy six-digit and eight-digit BINs can coexist. Do not infer arbitrary prefix lengths.

Atlas editorial proposal · G047. Source scope matters; this entry is not an ASD vocabulary approval.

basis point

One hundredth of one percentage point, equal to 0.01%.

Recommended usage and sources

Usage: Use basis points for the unit. A change from 1% to 2% is 100 basis points, not a 1% relative increase.

Atlas editorial proposal · G219. Source scope matters; this entry is not an ASD vocabulary approval.

behavioral biometrics

Analysis of interaction patterns used to distinguish activity or support an identity and risk assessment.

Recommended usage and sources

Usage: Describe the measured behavior and confidence. Do not equate probabilistic behavior analysis with certain identity proof.

Atlas editorial proposal · G159. Source scope matters; this entry is not an ASD vocabulary approval.

BIN attributes

Data describing the issuer, funding source, product, and other attributes associated with a BIN or range.

Recommended usage and sources

Usage: Record provider, range granularity, and update date. An attribute lookup does not prove the cardholder's location or identity.

Atlas editorial proposal · G049. Source scope matters; this entry is not an ASD vocabulary approval.

block list

List of entities or attributes to which a specified blocking rule applies.

Recommended usage and sources

Usage: Name the list owner, matching criteria, and duration. Prefer block list to ambiguous blacklist in Atlas prose.

Atlas editorial proposal · G151. Source scope matters; this entry is not an ASD vocabulary approval.

bot

Software that performs interactions automatically.

Recommended usage and sources

Usage: Describe the activity and evidence. Automation alone does not prove malicious intent or payment fraud.

Atlas editorial proposal · G143. Source scope matters; this entry is not an ASD vocabulary approval.

brute-force attack

Repeated attempts to discover a secret or valid value by trying possibilities.

Recommended usage and sources

Usage: Name the target, such as passwords or card values; do not conflate all automated testing with credential stuffing.

Atlas editorial proposal · G140. Source scope matters; this entry is not an ASD vocabulary approval.

buy now, pay later (BNPL)

Payment arrangement allowing a customer to defer or divide payment under the provider's terms.

Recommended usage and sources

Usage: Name the provider and product. Do not assume that every installment payment is BNPL or has identical fraud and dispute rules.

Atlas editorial proposal · G247. Source scope matters; this entry is not an ASD vocabulary approval.

C

cancel a payment

Stop an uncaptured payment using the provider's cancellation operation.

Recommended usage and sources

Usage: Use the exact provider state and operation. If capture already occurred, assess the refund operation instead.

Atlas editorial proposal · G031. Source scope matters; this entry is not an ASD vocabulary approval.

canceled recurring transaction dispute

Dispute basis concerning a recurring payment processed after the relevant cancellation.

Recommended usage and sources

Usage: Use the network condition and cancellation evidence. Do not infer whether a claim is valid from the merchant's subscription label alone.

Atlas editorial proposal · G201. Source scope matters; this entry is not an ASD vocabulary approval.

capture

Provider operation that submits an authorized payment for financial completion.

Recommended usage and sources

Usage: Name the provider operation and amount. Keep capture distinct from network clearing, settlement, and merchant payout.

Atlas editorial proposal · G028. Source scope matters; this entry is not an ASD vocabulary approval.

card network

Organization and system that defines and supports participation and transaction processing for its card brand.

Recommended usage and sources

Usage: Use the relevant network name when rules differ. Do not describe the network as the issuer merely because its brand is on a card.

Atlas editorial proposal · G060. Source scope matters; this entry is not an ASD vocabulary approval.

card security code

Card verification or validation value used under the relevant network's scheme.

Recommended usage and sources

Usage: Use CVV2 for the applicable Visa value and CVC 2 for the applicable Mastercard value. Do not replace an authentication cryptogram with a card security code.

Atlas editorial proposal · G128. Source scope matters; this entry is not an ASD vocabulary approval.

card testing

Attempts to determine whether card credentials can be used successfully, commonly through payment or setup requests.

Recommended usage and sources

Usage: Identify the tested credentials and request types. Failed attempts can still be relevant attack evidence.

Atlas editorial proposal · G141. Source scope matters; this entry is not an ASD vocabulary approval.

card-not-present transaction (CNP)

Card acceptance in a remote environment, such as ecommerce or mail and telephone ordering.

Recommended usage and sources

Usage: Apply the network's environment classification. A manually keyed transaction or digital wallet is not automatically CNP in every context.

Atlas editorial proposal · G075. Source scope matters; this entry is not an ASD vocabulary approval.

card-present transaction (CP)

Card acceptance in a physical payment environment under the applicable network interaction rules.

Recommended usage and sources

Usage: Describe chip, contactless, or other accepted interaction. Do not infer classification solely from the presence of a physical card.

Atlas editorial proposal · G076. Source scope matters; this entry is not an ASD vocabulary approval.

cardholder

Person to whom a card or account credential is issued, subject to the network's specific definitions.

Recommended usage and sources

Usage: Distinguish the cardholder from the shopper, purchaser, delivery recipient, and account holder when they differ.

Atlas editorial proposal · G050. Source scope matters; this entry is not an ASD vocabulary approval.

cardholder authentication verification value (CAVV)

Visa authentication value associated with the result of a cardholder authentication request.

Recommended usage and sources

Usage: Keep CAVV distinct from CVV2, authorization code, ECI, and a payment token.

Atlas editorial proposal · G129. Source scope matters; this entry is not an ASD vocabulary approval.

cardholder data

Payment-card data classified as cardholder data under the applicable PCI definition.

Recommended usage and sources

Usage: Use the defined data elements and scope. Keep it distinct from sensitive authentication data and general personal information.

Atlas editorial proposal · G170. Source scope matters; this entry is not an ASD vocabulary approval.

cardholder verification method (CVM)

Method used to establish that the person presenting the card or device is authorized to use it.

Recommended usage and sources

Usage: Name the method, such as PIN or an applicable device method; distinguish verification from authorization.

  • Mastercard Rules (M1) — 2 June 2026. Related term lookup: Cardholder Verification Method
  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Cardholder Verification Method (CVM)

Atlas editorial proposal · G077. Source scope matters; this entry is not an ASD vocabulary approval.

cardholder-initiated transaction (CIT)

Transaction initiated through active participation of the cardholder.

Recommended usage and sources

Usage: Identify the initiator and applicable stored-credential framework. CIT is not determined solely by whether a credential was stored.

Atlas editorial proposal · G094. Source scope matters; this entry is not an ASD vocabulary approval.

challenge flow

Authentication interaction requiring the cardholder to complete an additional verification step.

Recommended usage and sources

Usage: Describe the required action and final result. Starting a challenge does not establish that it was completed successfully.

Atlas editorial proposal · G114. Source scope matters; this entry is not an ASD vocabulary approval.

challenge request

3DS protocol message requesting a challenge interaction.

Recommended usage and sources

Usage: Preserve CReq and the version-specific fields. Do not replace it with a financial authorization request.

Atlas editorial proposal · G115. Source scope matters; this entry is not an ASD vocabulary approval.

challenge response

3DS protocol message carrying challenge interaction data or results.

Recommended usage and sources

Usage: Preserve CRes and the final protocol outcome. Do not assume every response indicates successful authentication.

Atlas editorial proposal · G116. Source scope matters; this entry is not an ASD vocabulary approval.

chargeback

Issuer-initiated return of a disputed transaction through a card-network mechanism.

Recommended usage and sources

Usage: Name the network and stage. It is not a merchant refund, an informal complaint, or every pre-dispute alert.

Atlas editorial proposal · G176. Source scope matters; this entry is not an ASD vocabulary approval.

chargeback deflection

Activity or service intended to resolve or prevent an eligible issue before a chargeback progresses.

Recommended usage and sources

Usage: Name the specific service and outcome. Do not promise that an alert, data-sharing service, or refund always prevents a dispute.

Atlas editorial proposal · G195. Source scope matters; this entry is not an ASD vocabulary approval.

chargeback ratio

Ratio of eligible chargebacks to the transaction population specified by the relevant program or measurement policy.

Recommended usage and sources

Usage: State the network formula and periods; the numerator and denominator may use different months. Do not replace it with VAMP ratio.

Atlas editorial proposal · G223. Source scope matters; this entry is not an ASD vocabulary approval.

closed-loop payment arrangement

Payment arrangement restricted to a defined issuer or merchant ecosystem.

Recommended usage and sources

Usage: State the actual redemption and acceptance scope. Do not assume every gift card is closed-loop.

Atlas editorial proposal · G091. Source scope matters; this entry is not an ASD vocabulary approval.

compelling evidence 3.0 (CE3.0)

Visa framework for qualifying evidence in specified card-absent fraud dispute circumstances.

Recommended usage and sources

Usage: State the condition and qualification criteria. It does not apply to every dispute or guarantee that a claim will be prevented or defeated.

Atlas editorial proposal · G186. Source scope matters; this entry is not an ASD vocabulary approval.

compliance case

Process addressing a financial loss attributed to a network-rule violation under the applicable eligibility rules.

Recommended usage and sources

Usage: Do not present compliance as an unrestricted alternative when chargeback rights are unavailable or prohibited.

Atlas editorial proposal · G183. Source scope matters; this entry is not an ASD vocabulary approval.

contactless

Payment interaction using a supported short-range wireless interface.

Recommended usage and sources

Usage: Identify the payment method and acceptance mode. Contactless does not itself specify the cardholder verification method.

Atlas editorial proposal · G078. Source scope matters; this entry is not an ASD vocabulary approval.

credential stuffing

Automated use of previously obtained credential pairs to try to access other accounts.

Recommended usage and sources

Usage: Distinguish it from guessing new passwords, card enumeration, and ordinary failed logins.

Atlas editorial proposal · G139. Source scope matters; this entry is not an ASD vocabulary approval.

credential-on-file transaction (COF)

Transaction using a payment credential previously stored for future use.

Recommended usage and sources

Usage: Use COF only with the payments context stated. It can mean cost of funds in a different financial context.

Atlas editorial proposal · G093. Source scope matters; this entry is not an ASD vocabulary approval.

credit card

Card product that provides access to a credit account under the issuer's terms.

Recommended usage and sources

Usage: Distinguish funding source, product type, and transaction channel; do not infer them from a card-network brand.

Atlas editorial proposal · G086. Source scope matters; this entry is not an ASD vocabulary approval.

credit not processed

Dispute basis alleging that an agreed or required credit was not completed.

Recommended usage and sources

Usage: Check the credit agreement, processing records, timing, and exact network condition. A refund request alone does not establish completed credit.

Atlas editorial proposal · G200. Source scope matters; this entry is not an ASD vocabulary approval.

cross-border transaction

Card transaction whose acceptance country differs from its issuing country under the relevant network definition.

Recommended usage and sources

Usage: State both countries and the network rule. Currency difference alone does not establish a cross-border transaction.

Atlas editorial proposal · G061. Source scope matters; this entry is not an ASD vocabulary approval.

cryptogram

Cryptographic value used to validate specified data, its source, or its integrity.

Recommended usage and sources

Usage: Name the cryptogram type and protocol. It is not a reusable card number, ordinary password, or general approval code.

Atlas editorial proposal · G130. Source scope matters; this entry is not an ASD vocabulary approval.

D

data breach

Unauthorized exposure of or access to protected data.

Recommended usage and sources

Usage: State the data and event scope. A suspicious transaction alone does not establish a breach.

Atlas editorial proposal · G167. Source scope matters; this entry is not an ASD vocabulary approval.

data protection

Controls and obligations used to safeguard data and regulate its processing.

Recommended usage and sources

Usage: State the applicable data category, purpose, access, retention, and governing requirements.

Atlas editorial proposal · G168. Source scope matters; this entry is not an ASD vocabulary approval.

debit card

Card linked to a deposit, debit, or equivalent account as defined by the applicable rules.

Recommended usage and sources

Usage: Specify the funding account or product when relevant. Debit does not imply one universal message or settlement model.

Atlas editorial proposal · G087. Source scope matters; this entry is not an ASD vocabulary approval.

deferred authorization

Authorization submitted after a card-present transaction when online authorization was unavailable at the time.

Recommended usage and sources

Usage: State the permitted context and network rules. Do not replace it with delayed capture.

Atlas editorial proposal · G023. Source scope matters; this entry is not an ASD vocabulary approval.

delayed capture

Capture performed after authorization rather than immediately.

Recommended usage and sources

Usage: Specify the provider's capture timing and authorization validity; do not call it deferred authorization.

Atlas editorial proposal · G030. Source scope matters; this entry is not an ASD vocabulary approval.

delegated authentication

Arrangement in which an approved party performs specified authentication functions under applicable rules.

Recommended usage and sources

Usage: Name the delegating party, authenticating party, and scope. Do not infer delegation merely because a merchant uses biometrics.

Atlas editorial proposal · G122. Source scope matters; this entry is not an ASD vocabulary approval.

device fingerprint

Collection or representation of device and browser attributes used to recognize a device or assess risk.

Recommended usage and sources

Usage: State provider and collection context. A fingerprint is not an infallible person identifier and may change.

Atlas editorial proposal · G152. Source scope matters; this entry is not an ASD vocabulary approval.

device spoofing

Manipulation of reported device or browser attributes to misrepresent the device context.

Recommended usage and sources

Usage: Describe the inconsistent or altered attributes and evidence. A changed fingerprint does not alone establish deliberate spoofing.

Atlas editorial proposal · G237. Source scope matters; this entry is not an ASD vocabulary approval.

digital wallet

Service or application that enables use of payment credentials or stored value.

Recommended usage and sources

Usage: Name the wallet and operating model; distinguish pass-through, staged, stored-value, and merchant wallets where applicable.

Atlas editorial proposal · G082. Source scope matters; this entry is not an ASD vocabulary approval.

direct debit

Payment method in which a creditor or its provider initiates a debit under the applicable authorization framework.

Recommended usage and sources

Usage: Name the scheme and mandate. Card recurring payments and bank direct debits have different rules and return processes.

Atlas editorial proposal · G241. Source scope matters; this entry is not an ASD vocabulary approval.

disposable email address

Email address supplied for temporary or easily replaced use.

Recommended usage and sources

Usage: Describe the identified domain or service. Temporary use alone does not establish payment fraud.

Atlas editorial proposal · G158. Source scope matters; this entry is not an ASD vocabulary approval.

dispute

Challenge to a transaction handled under an applicable provider or network dispute process.

Recommended usage and sources

Usage: Distinguish the customer's complaint from a formally initiated network dispute. For Visa, use its official dispute stage names.

Atlas editorial proposal · G175. Source scope matters; this entry is not an ASD vocabulary approval.

dispute condition

Network-defined basis and requirements for raising and responding to a dispute.

Recommended usage and sources

Usage: Preserve the network, identifier, title, and edition. A similar reason on another network is not automatically equivalent.

Atlas editorial proposal · G177. Source scope matters; this entry is not an ASD vocabulary approval.

dispute response

Submission responding to a formal dispute under the applicable network or provider process.

Recommended usage and sources

Usage: Name the stage and grounds. Supplying evidence does not guarantee acceptance or a reversal of liability.

Atlas editorial proposal · G178. Source scope matters; this entry is not an ASD vocabulary approval.

dispute win rate

Proportion of the stated resolved dispute population with the defined favorable outcome.

Recommended usage and sources

Usage: Define favorable outcome, contested versus all disputes, cohort, reversals, and unresolved cases. Do not count automatic liability acceptance as a contested win.

Atlas editorial proposal · G225. Source scope matters; this entry is not an ASD vocabulary approval.

doing business as (DBA)

Business name under which an entity presents its trading activity.

Recommended usage and sources

Usage: Use the recognizable trading name where the network requires it; distinguish it from the legal entity name.

Atlas editorial proposal · G067. Source scope matters; this entry is not an ASD vocabulary approval.

DPAN

Term used for a device or digital payment account number in tokenized-payment contexts.

Recommended usage and sources

Usage: State the wallet or network context and prefer its official token field name. Do not assume every DPAN is the underlying PAN.

Atlas editorial proposal · G106. Source scope matters; this entry is not an ASD vocabulary approval.

dual message system

Processing arrangement with separate authorization and clearing message stages.

Recommended usage and sources

Usage: Use the network-specific system and message names; do not impose the same sequence on single-message processing.

Atlas editorial proposal · G251. Source scope matters; this entry is not an ASD vocabulary approval.

dunning

Process for recovering an unpaid amount, often through payment retries and customer communication.

Recommended usage and sources

Usage: Describe the permitted recovery actions. Do not confuse dunning with chargeback representment or collections after a dispute.

Atlas editorial proposal · G229. Source scope matters; this entry is not an ASD vocabulary approval.

duplicate refund risk

Risk that a merchant refund and a separate dispute-related credit return value for the same purchase.

Recommended usage and sources

Usage: Check the payment, refund, and dispute records before issuing another credit; do not assume provider offsets are automatic.

Atlas editorial proposal · G196. Source scope matters; this entry is not an ASD vocabulary approval.

E

early fraud warning

Provider notification that an issuer or network has reported suspected or confirmed fraud under that notification system.

Recommended usage and sources

Usage: Name the provider and source system. A warning is not itself a dispute, automatic refund instruction, or guaranteed chargeback.

Atlas editorial proposal · G192. Source scope matters; this entry is not an ASD vocabulary approval.

ecommerce payment

Payment initiated through an online commerce interaction.

Recommended usage and sources

Usage: Identify the acceptance channel, credential, and payment method. Do not assume a universal authentication or liability outcome.

Atlas editorial proposal · G081. Source scope matters; this entry is not an ASD vocabulary approval.

electronic commerce indicator (ECI)

Network data indicator describing the ecommerce authentication or transaction context.

Recommended usage and sources

Usage: Interpret the exact value using the network and protocol version. The same numeric value is not universally meaningful across networks.

Atlas editorial proposal · G131. Source scope matters; this entry is not an ASD vocabulary approval.

email verification

Checks used to assess an email address, domain, or its control by a user.

Recommended usage and sources

Usage: State what was checked: syntax, deliverability, ownership, age, or reputation. Do not claim these checks prove identity.

Atlas editorial proposal · G157. Source scope matters; this entry is not an ASD vocabulary approval.

EMV 3DS

EMVCo's 3-D Secure specifications for cardholder authentication in remote commerce.

Recommended usage and sources

Usage: Use the precise version and message names. Do not treat 3DS 1 and EMV 3DS 2 as interchangeable implementations.

Atlas editorial proposal · G110. Source scope matters; this entry is not an ASD vocabulary approval.

encryption

Cryptographic transformation that makes data unreadable without the required key or process.

Recommended usage and sources

Usage: Distinguish encryption from hashing, truncation, and tokenization. State the protection context rather than claiming complete security.

Atlas editorial proposal · G172. Source scope matters; this entry is not an ASD vocabulary approval.

enumeration attack

Systematic submission of transaction data to discover or validate payment-account information.

Recommended usage and sources

Usage: Use the network's measured event definition when calculating a program ratio. Do not substitute ordinary decline counts for confirmed enumeration.

Atlas editorial proposal · G142. Source scope matters; this entry is not an ASD vocabulary approval.

estimated authorization

Authorization requested for a genuine estimate before the final transaction amount is known.

Recommended usage and sources

Usage: Label the amount as an estimate. Apply the applicable network's eligibility and completion rules.

Atlas editorial proposal · G020. Source scope matters; this entry is not an ASD vocabulary approval.

excessive chargeback merchant (ECM)

Merchant identified in Mastercard's ECM category under the relevant monitoring rules.

Recommended usage and sources

Usage: Keep category, program, month, and MID scope together. Do not treat ECM as the name of a separate universal program.

Atlas editorial proposal · G208. Source scope matters; this entry is not an ASD vocabulary approval.

excessive chargeback program (ECP)

Mastercard program for monitoring merchant chargeback performance under its defined rules.

Recommended usage and sources

Usage: Use Mastercard ECP in this context. ECP can mean electronic check presentment elsewhere, so never expand it without context.

Atlas editorial proposal · G207. Source scope matters; this entry is not an ASD vocabulary approval.

excessive fraud merchant (EFM)

Mastercard merchant classification under the applicable excessive-fraud monitoring provisions.

Recommended usage and sources

Usage: Use the current program definition, market, and date. Do not substitute a generic fraud rate or historical threshold.

Atlas editorial proposal · G212. Source scope matters; this entry is not an ASD vocabulary approval.

F

false decline

Decline of a payment that would otherwise be legitimate under the stated assessment.

Recommended usage and sources

Usage: Identify who declined and why. A false-positive fraud decision and an issuer decline are not necessarily the same event.

Atlas editorial proposal · G162. Source scope matters; this entry is not an ASD vocabulary approval.

false positive

Legitimate case incorrectly classified as fraud or another positive condition in the stated evaluation.

Recommended usage and sources

Usage: Name the label, decision, and ground-truth method. Do not equate all customer complaints or issuer declines with false positives.

Atlas editorial proposal · G161. Source scope matters; this entry is not an ASD vocabulary approval.

false-positive rate

Proportion of actual negative or legitimate cases incorrectly classified as positive in the stated evaluation.

Recommended usage and sources

Usage: Define ground truth and population. Do not divide by all flagged cases and call that the false-positive rate.

Atlas editorial proposal · G226. Source scope matters; this entry is not an ASD vocabulary approval.

FIDO

Family of authentication standards and associated ecosystem identified by the FIDO Alliance.

Recommended usage and sources

Usage: Name the applicable standard or implementation. Do not infer SCA compliance merely from the FIDO label.

Atlas editorial proposal · G254. Source scope matters; this entry is not an ASD vocabulary approval.

final authorization

Mastercard authorization classification for a final amount and expected completion.

Recommended usage and sources

Usage: Use it as a network processing classification; it does not mean that settlement is final or irrevocable.

Atlas editorial proposal · G022. Source scope matters; this entry is not an ASD vocabulary approval.

first-party misuse

Misuse of a purchase or dispute process by a purchaser or another authorized participant.

Recommended usage and sources

Usage: State the observed facts. Do not assume intentional fraud solely because the customer disputed a purchase.

Atlas editorial proposal · G137. Source scope matters; this entry is not an ASD vocabulary approval.

fraud

Deceptive or unauthorized activity intended to obtain value or cause an improper payment outcome.

Recommended usage and sources

Usage: Identify the evidence and fraud type. Do not label every failed payment, dispute, or suspicious signal as confirmed fraud.

Atlas editorial proposal · G135. Source scope matters; this entry is not an ASD vocabulary approval.

fraud loss

Financial loss attributable to the stated fraudulent activity under a defined accounting method.

Recommended usage and sources

Usage: Specify included amounts, recoveries, fees, timing, and loss owner. Do not substitute fraud-report counts for monetary loss.

Atlas editorial proposal · G163. Source scope matters; this entry is not an ASD vocabulary approval.

fraud rate

Ratio expressing fraud frequency or value in a specified payment population.

Recommended usage and sources

Usage: State whether it is count-based or amount-based, the label source, denominator, and period. Do not treat all fraud-rate formulas as equivalent.

Atlas editorial proposal · G224. Source scope matters; this entry is not an ASD vocabulary approval.

fraud report

Record submitted or supplied to identify an event reported as fraudulent.

Recommended usage and sources

Usage: Name the reporting system and label status. A fraud report is not automatically a chargeback or a proven fraud loss.

Atlas editorial proposal · G187. Source scope matters; this entry is not an ASD vocabulary approval.

fraud screening

Evaluation of an account, order, or transaction for indicators of fraud.

Recommended usage and sources

Usage: State whether screening occurs before authorization, after authorization, or during fulfillment.

Atlas editorial proposal · G147. Source scope matters; this entry is not an ASD vocabulary approval.

fraud signal

Observed attribute or event used as evidence in a risk assessment.

Recommended usage and sources

Usage: Separate a signal from a rule decision, model score, and confirmed fraud outcome.

Atlas editorial proposal · G144. Source scope matters; this entry is not an ASD vocabulary approval.

frictionless authentication

3DS flow in which the issuer assesses authentication without an interactive cardholder challenge.

Recommended usage and sources

Usage: Report the actual authentication result. Frictionless does not mean unauthenticated, fraud-free, or automatically exempt from SCA.

Atlas editorial proposal · G113. Source scope matters; this entry is not an ASD vocabulary approval.

full authorization reversal

Reversal that cancels the original authorization request in full.

Recommended usage and sources

Usage: Identify the original authorization and full-reversal operation. Preserve the network's original-data linkage.

Atlas editorial proposal · G026. Source scope matters; this entry is not an ASD vocabulary approval.

G

gift card

Card or credential carrying value for redemption under the issuer's program.

Recommended usage and sources

Usage: State issuer, redemption scope, and balance rules. Distinguish closed-loop merchant value from network-branded prepaid products.

Atlas editorial proposal · G090. Source scope matters; this entry is not an ASD vocabulary approval.

goods or services not received

Dispute basis alleging that agreed goods or services were not provided as required.

Recommended usage and sources

Usage: Use the exact network condition and expected delivery facts. Do not merge it with unauthorized-use or not-as-described disputes.

Atlas editorial proposal · G198. Source scope matters; this entry is not an ASD vocabulary approval.

H

hard decline

Provider or scheme classification for a decline that requires correction or disallows the stated retry path.

Recommended usage and sources

Usage: Interpret the specific code and advice. Do not infer the same retry treatment across every processor from the label hard.

Atlas editorial proposal · G232. Source scope matters; this entry is not an ASD vocabulary approval.

hashing

Transformation of input data into a fixed representation using a defined hash function.

Recommended usage and sources

Usage: Distinguish a hash from reversible encryption and payment tokenization; state the function and use case when relevant.

Atlas editorial proposal · G173. Source scope matters; this entry is not an ASD vocabulary approval.

high excessive chargeback merchant (HECM)

Merchant identified in Mastercard's HECM category under the relevant monitoring rules.

Recommended usage and sources

Usage: Use the exact category and current rule source. Do not infer a current threshold from an old merchant discussion.

Atlas editorial proposal · G209. Source scope matters; this entry is not an ASD vocabulary approval.

I

IBAN

International Bank Account Number used to identify a bank account under the applicable standard.

Recommended usage and sources

Usage: Preserve the value and check format where required. A valid format does not establish ownership, available funds, or payment success.

Atlas editorial proposal · G245. Source scope matters; this entry is not an ASD vocabulary approval.

identity verification

Assessment of evidence linking a person or entity to a claimed identity.

Recommended usage and sources

Usage: Distinguish identity verification from address matching, payment authorization, and customer-account authentication.

Atlas editorial proposal · G132. Source scope matters; this entry is not an ASD vocabulary approval.

incremental authorization

Additional authorization associated with an existing transaction as the expected amount increases.

Recommended usage and sources

Usage: Keep the original transaction linkage and distinguish the increment from the total authorized amount.

Atlas editorial proposal · G021. Source scope matters; this entry is not an ASD vocabulary approval.

installment payment

One payment in an agreed series used to pay for a purchase over time.

Recommended usage and sources

Usage: State the plan, initiator, and provider or network classification. Do not assume every installment plan is BNPL.

Atlas editorial proposal · G098. Source scope matters; this entry is not an ASD vocabulary approval.

interchange

Exchange of clearing records between participating network institutions.

Recommended usage and sources

Usage: Distinguish the processing exchange from interchange reimbursement fees when using the standalone word.

Atlas editorial proposal · G214. Source scope matters; this entry is not an ASD vocabulary approval.

interchange downgrade

Application of a different interchange qualification or category because a transaction does not meet the relevant criteria.

Recommended usage and sources

Usage: Name the network qualification and fee outcome. Do not use downgrade for every higher processor fee.

Atlas editorial proposal · G253. Source scope matters; this entry is not an ASD vocabulary approval.

interchange fee

Fee applied between acquiring and issuing participants under the relevant payment-network fee framework.

Recommended usage and sources

Usage: Name the network, market, product, and fee basis. Do not equate interchange with the merchant's entire processing cost.

Atlas editorial proposal · G215. Source scope matters; this entry is not an ASD vocabulary approval.

interchange-plus-plus pricing (IC++)

Pricing presentation separating interchange, network fees, and the provider's acquiring or processing charge.

Recommended usage and sources

Usage: Specify the contract and included fee categories. Do not assume all providers present identical IC++ components.

Atlas editorial proposal · G218. Source scope matters; this entry is not an ASD vocabulary approval.

involuntary churn

Loss of an otherwise continuing subscription or customer relationship because payment collection fails.

Recommended usage and sources

Usage: Distinguish payment failure from the customer's deliberate cancellation and define how churn is measured.

Atlas editorial proposal · G233. Source scope matters; this entry is not an ASD vocabulary approval.

IP address

Address used to identify a network endpoint in the relevant internet protocol context.

Recommended usage and sources

Usage: Do not treat an IP address as a unique person, payment account, or reliable physical address.

Atlas editorial proposal · G153. Source scope matters; this entry is not an ASD vocabulary approval.

IP geolocation

Estimate of geographic location based on an IP address and a data service.

Recommended usage and sources

Usage: Label the result as an estimate, name the source, and account for proxies, mobile networks, and VPNs.

Atlas editorial proposal · G154. Source scope matters; this entry is not an ASD vocabulary approval.

issuer

Institution responsible for issuing the card or maintaining the relevant card account.

Recommended usage and sources

Usage: Use issuer or issuing bank for this role. A card-network brand alone does not identify the issuer.

Atlas editorial proposal · G051. Source scope matters; this entry is not an ASD vocabulary approval.

K

know your business (KYB)

Verification and due diligence relating to a business customer or counterparty.

Recommended usage and sources

Usage: Identify the business, controlling persons, and applicable requirements. Do not treat a company-name match as complete due diligence.

Atlas editorial proposal · G134. Source scope matters; this entry is not an ASD vocabulary approval.

know your customer (KYC)

Customer-identification and due-diligence activities required for the relevant financial or business relationship.

Recommended usage and sources

Usage: State the obligated entity, jurisdiction, and relationship. Do not imply that an ordinary merchant fraud check satisfies every KYC duty.

Atlas editorial proposal · G133. Source scope matters; this entry is not an ASD vocabulary approval.

L

legal entity

Person or organization recognized as having legal rights and obligations.

Recommended usage and sources

Usage: Name the exact entity and jurisdiction when allocating payment responsibilities. Do not substitute brand or website name.

Atlas editorial proposal · G068. Source scope matters; this entry is not an ASD vocabulary approval.

liability shift

Rule-based transfer of responsibility for specified fraud losses between participating parties.

Recommended usage and sources

Usage: State the network, environment, fraud category, authentication outcome, and exceptions. It is not a guarantee of winning every dispute.

Atlas editorial proposal · G123. Source scope matters; this entry is not an ASD vocabulary approval.

local acquiring

Acquiring arrangement established for the specified local market.

Recommended usage and sources

Usage: Identify the merchant entity, acquirer, and country. Do not promise domestic treatment or higher approval merely from a local route.

Atlas editorial proposal · G062. Source scope matters; this entry is not an ASD vocabulary approval.

local payment method

Payment method with adoption or operation tied to specified markets or customer groups.

Recommended usage and sources

Usage: Name the actual method and market. Local and alternative are contextual labels, not universal method classifications.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Local payment methods (or Alternative payment methods)

Atlas editorial proposal · G248. Source scope matters; this entry is not an ASD vocabulary approval.

M

machine learning

Use of models learned from data to estimate outcomes or classify events.

Recommended usage and sources

Usage: State the model's purpose and evaluation basis. A model prediction is not a confirmed fraud outcome.

Atlas editorial proposal · G160. Source scope matters; this entry is not an ASD vocabulary approval.

mail order/telephone order (MOTO)

Remote card-payment channel in which an order is placed by mail or telephone.

Recommended usage and sources

Usage: Preserve the applicable channel coding. Do not classify every manually keyed ecommerce transaction as MOTO.

Atlas editorial proposal · G080. Source scope matters; this entry is not an ASD vocabulary approval.

mandate

Recorded permission or agreement for specified payment actions under the applicable method and rules.

Recommended usage and sources

Usage: State the payment method, parties, permitted actions, and cancellation terms. A saved credential alone does not establish every required mandate.

Atlas editorial proposal · G240. Source scope matters; this entry is not an ASD vocabulary approval.

manual review

Human assessment of a transaction or account that needs further evaluation.

Recommended usage and sources

Usage: Identify the reviewer decision and its effect. Review approval is separate from issuer authorization and capture.

Atlas editorial proposal · G149. Source scope matters; this entry is not an ASD vocabulary approval.

manual review queue

Set of cases waiting for or undergoing human risk assessment.

Recommended usage and sources

Usage: Name the case population, entry and exit states, priority, and service target. Queue volume is not necessarily fraud volume.

Atlas editorial proposal · G235. Source scope matters; this entry is not an ASD vocabulary approval.

marketplace

Business arrangement that connects buyers and sellers and may perform specified payment functions for those sellers.

Recommended usage and sources

Usage: Distinguish the general business model from the network's registered marketplace classification for the transaction.

Atlas editorial proposal · G056. Source scope matters; this entry is not an ASD vocabulary approval.

MATCH

Mastercard system used for specified merchant-termination and acquiring-risk information.

Recommended usage and sources

Usage: Use the current system and rule terminology. A MATCH result is not a general-purpose proof of criminal fraud.

Atlas editorial proposal · G213. Source scope matters; this entry is not an ASD vocabulary approval.

merchant

Entity accepting payment for the sale of goods or services.

Recommended usage and sources

Usage: Name the seller and its contracted role. Distinguish it from a marketplace operator, payment facilitator, and processor.

Atlas editorial proposal · G052. Source scope matters; this entry is not an ASD vocabulary approval.

merchant account

Merchant-side account or processing configuration used for payment acceptance.

Recommended usage and sources

Usage: Name the provider and account layer. Do not confuse an Adyen merchant account, bank account, MID, and legal entity.

Atlas editorial proposal · G063. Source scope matters; this entry is not an ASD vocabulary approval.

merchant category code (MCC)

Code classifying the merchant's business activity for payment processing.

Recommended usage and sources

Usage: Use the applicable network's current classification and merchant activity. Do not infer it from the company name alone.

Atlas editorial proposal · G065. Source scope matters; this entry is not an ASD vocabulary approval.

merchant descriptor

Merchant-identifying text supplied in transaction and statement data.

Recommended usage and sources

Usage: Use recognizable merchant information and the actual field specification. Keep dynamic and static parts separate.

Atlas editorial proposal · G066. Source scope matters; this entry is not an ASD vocabulary approval.

merchant discount fee

Fee a merchant pays an acquirer for acquiring the merchant's transactions.

Recommended usage and sources

Usage: State what the quoted fee includes and how it is calculated. It is not necessarily identical to interchange alone.

Atlas editorial proposal · G217. Source scope matters; this entry is not an ASD vocabulary approval.

merchant identifier (MID)

Identifier used by an acquirer or provider to identify a merchant in a specified system.

Recommended usage and sources

Usage: Name the system and field. Do not assume a provider merchant-account name equals network DE 42.

Atlas editorial proposal · G064. Source scope matters; this entry is not an ASD vocabulary approval.

merchant monitoring program (MMP)

Mastercard program covering the merchant-monitoring obligations described in the applicable security rules.

Recommended usage and sources

Usage: Use the full network-qualified program title and edition. Do not assume similarly named monitoring programs use the same scope or metric.

Atlas editorial proposal · G210. Source scope matters; this entry is not an ASD vocabulary approval.

merchant of record (MoR)

Entity presented as the seller for the transaction and responsible for the applicable merchant obligations.

Recommended usage and sources

Usage: Use the actual contractual seller and transaction context. A descriptor alone does not settle every legal responsibility.

Atlas editorial proposal · G053. Source scope matters; this entry is not an ASD vocabulary approval.

merchant reference

Merchant-assigned reference used to identify an order or payment request.

Recommended usage and sources

Usage: State its uniqueness and reuse rules. Distinguish it from network and provider transaction identifiers.

Atlas editorial proposal · G074. Source scope matters; this entry is not an ASD vocabulary approval.

merchant-initiated transaction (MIT)

Transaction initiated by a merchant under an agreement without active cardholder participation at that time.

Recommended usage and sources

Usage: Preserve the reason, consent, and required linkage. Recurring payment is one possible MIT type, not the whole category.

Atlas editorial proposal · G095. Source scope matters; this entry is not an ASD vocabulary approval.

multi-factor authentication (MFA)

Authentication requiring more than one distinct factor under the relevant method.

Recommended usage and sources

Usage: Describe factor independence and the authentication context. Do not treat every SMS or challenge flow as MFA automatically.

Atlas editorial proposal · G125. Source scope matters; this entry is not an ASD vocabulary approval.

N

not as described

Dispute basis alleging that goods or services differed from the agreed description or condition.

Recommended usage and sources

Usage: Use the exact condition and supporting facts. Do not automatically classify a quality complaint as third-party fraud.

Atlas editorial proposal · G199. Source scope matters; this entry is not an ASD vocabulary approval.

O

one-time password (OTP)

Password or code intended for one authentication use or a limited validity period.

Recommended usage and sources

Usage: State the channel, expiry, and validation outcome where relevant. An OTP is a mechanism, not evidence that SCA always applies or is satisfied.

Atlas editorial proposal · G126. Source scope matters; this entry is not an ASD vocabulary approval.

out-of-scope transaction

Transaction that does not fall within the stated authentication requirement's scope.

Recommended usage and sources

Usage: State the specific scope test. Do not use out of scope as a synonym for an exemption or frictionless authentication.

Atlas editorial proposal · G120. Source scope matters; this entry is not an ASD vocabulary approval.

overcapture

Capture exceeding the original authorized amount when the provider and network permit it.

Recommended usage and sources

Usage: State the eligible payment type, permitted limit, and provider settings. Do not treat overcapture as universally supported.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Overcapture

Atlas editorial proposal · G250. Source scope matters; this entry is not an ASD vocabulary approval.

P

partial authorization

Approval for less than the originally requested transaction amount.

Recommended usage and sources

Usage: State the requested and approved amounts. Use another permitted means to pay the remainder when applicable.

Atlas editorial proposal · G024. Source scope matters; this entry is not an ASD vocabulary approval.

partial authorization reversal

Reversal that reduces the amount of an existing approved authorization.

Recommended usage and sources

Usage: Distinguish the remaining authorized amount from the amount released; do not substitute partial refund.

Atlas editorial proposal · G027. Source scope matters; this entry is not an ASD vocabulary approval.

partial capture

Capture for less than the currently capturable authorized amount.

Recommended usage and sources

Usage: State whether further captures remain possible and how unused authorization is handled for that provider.

Atlas editorial proposal · G029. Source scope matters; this entry is not an ASD vocabulary approval.

partial refund

Refund for less than the original purchase amount.

Recommended usage and sources

Usage: State the amount and remaining refundable balance. Do not confuse it with partial authorization or partial capture.

Atlas editorial proposal · G039. Source scope matters; this entry is not an ASD vocabulary approval.

pass-through digital wallet

Wallet arrangement that passes payment credential information to support a merchant payment.

Recommended usage and sources

Usage: Use the network's exact wallet definition. Do not assume the wallet holds the customer's funds.

Atlas editorial proposal · G083. Source scope matters; this entry is not an ASD vocabulary approval.

payment account reference (PAR)

Non-financial reference linking activity associated with an underlying payment account.

Recommended usage and sources

Usage: Do not use PAR as an authorizable payment credential or as a replacement for PAN in a payment request.

Atlas editorial proposal · G105. Source scope matters; this entry is not an ASD vocabulary approval.

payment conversion rate

Proportion of the stated payment or checkout population that reaches the defined successful outcome.

Recommended usage and sources

Usage: Name the funnel stage and denominator. Do not automatically substitute issuer approval rate, capture rate, or order conversion.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Payment conversion rate

Atlas editorial proposal · G221. Source scope matters; this entry is not an ASD vocabulary approval.

payment credential

Account-identifying number or credential used to initiate a transaction.

Recommended usage and sources

Usage: Specify PAN, network token, or another credential type. Do not assume every credential is a physical card number.

Atlas editorial proposal · G045. Source scope matters; this entry is not an ASD vocabulary approval.

payment facilitator

Entity contracted or registered with an acquirer to provide acquiring services for sponsored merchants.

Recommended usage and sources

Usage: Use the network-specific role and obligations. Do not treat every PSP, marketplace, or software platform as a payment facilitator.

Atlas editorial proposal · G054. Source scope matters; this entry is not an ASD vocabulary approval.

payment gateway

Service that accepts and routes payment requests between merchant systems and payment-processing services.

Recommended usage and sources

Usage: Describe its interface and routing role. Do not assume it is also the acquirer or merchant of record.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Payment gateway

Atlas editorial proposal · G057. Source scope matters; this entry is not an ASD vocabulary approval.

payment modification

Provider operation that changes an existing payment, such as capture, cancellation, or refund.

Recommended usage and sources

Usage: Use the exact operation and current payment state. An API acknowledgement may precede the final modification outcome.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Payment modifications

Atlas editorial proposal · G069. Source scope matters; this entry is not an ASD vocabulary approval.

payment processor

Service that processes payment messages and connects relevant parties to complete payment operations.

Recommended usage and sources

Usage: Name the processor and its processing role; distinguish software processing from acquiring membership.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. Payment processor

Atlas editorial proposal · G058. Source scope matters; this entry is not an ASD vocabulary approval.

payment retry

New attempt to collect a payment after a prior unsuccessful attempt.

Recommended usage and sources

Usage: Identify the previous outcome, applicable advice, consent, and permitted retry policy. Never prescribe a universal retry count or interval.

Atlas editorial proposal · G230. Source scope matters; this entry is not an ASD vocabulary approval.

payment service provider (PSP)

Provider offering a set of payment acceptance and processing services to merchants.

Recommended usage and sources

Usage: State the actual services and region. PSP does not identify a universal regulatory or card-network role.

Atlas editorial proposal · G059. Source scope matters; this entry is not an ASD vocabulary approval.

payment token

Substitute payment credential used under the applicable tokenization framework.

Recommended usage and sources

Usage: Keep it distinct from PAN, PAR, cryptogram, and provider reference. Do not assume universal portability or usability.

Atlas editorial proposal · G101. Source scope matters; this entry is not an ASD vocabulary approval.

PaymentIntent

Stripe object tracking the attempt to collect a payment through its lifecycle.

Recommended usage and sources

Usage: Preserve the exact object and status names. Do not replace a Stripe status with a generic network stage.

Atlas editorial proposal · G071. Source scope matters; this entry is not an ASD vocabulary approval.

payout

Transfer of available funds to a designated recipient or external account.

Recommended usage and sources

Usage: State payer, recipient, amount, and destination. Distinguish a merchant payout from network settlement.

Atlas editorial proposal · G037. Source scope matters; this entry is not an ASD vocabulary approval.

PCI DSS

Payment Card Industry Data Security Standard.

Recommended usage and sources

Usage: Use the applicable version and scope. Do not describe a payment flow as compliant solely because it uses tokens or a compliant provider.

Atlas editorial proposal · G171. Source scope matters; this entry is not an ASD vocabulary approval.

personal data

Information relating to an identified or identifiable person under the applicable legal definition.

Recommended usage and sources

Usage: State the jurisdiction and processing purpose. Do not assume a single worldwide definition or retention requirement.

Atlas editorial proposal · G174. Source scope matters; this entry is not an ASD vocabulary approval.

phishing

Deceptive communication or site used to obtain information or induce an unsafe action by impersonating a trusted party.

Recommended usage and sources

Usage: Name the channel and impersonated party. Do not label every unsolicited message or suspicious domain as confirmed phishing.

Atlas editorial proposal · G165. Source scope matters; this entry is not an ASD vocabulary approval.

PIN

Personal identification code used in the applicable cardholder-verification or authorization process.

Recommended usage and sources

Usage: Use the network's exact PIN context. Do not use PIN as a generic term for every verification code.

Atlas editorial proposal · G127. Source scope matters; this entry is not an ASD vocabulary approval.

point of sale (POS)

Physical acceptance environment or system used to initiate in-person sales and payments.

Recommended usage and sources

Usage: Specify whether POS means the business location, application, terminal, or network data field.

Atlas editorial proposal · G079. Source scope matters; this entry is not an ASD vocabulary approval.

pre-arbitration

Dispute escalation or response stage before network arbitration when the applicable process permits or requires it.

Recommended usage and sources

Usage: State the network and dispute flow. Do not imply that it is mandatory or available in every case.

Atlas editorial proposal · G181. Source scope matters; this entry is not an ASD vocabulary approval.

pre-dispute alert

Notification intended to allow review or resolution before a formal network dispute progresses.

Recommended usage and sources

Usage: Name the alert service and its rules. Do not assume every alert has identical deadlines, refund requirements, or counting treatment.

Atlas editorial proposal · G193. Source scope matters; this entry is not an ASD vocabulary approval.

preauthorization

Authorization category used when the final amount or completion is not yet certain, subject to network rules.

Recommended usage and sources

Usage: Distinguish Mastercard preauthorization coding from a provider's informal pre-auth label.

Atlas editorial proposal · G019. Source scope matters; this entry is not an ASD vocabulary approval.

prepaid card

Card linked to a previously funded account or stored value.

Recommended usage and sources

Usage: Specify reloadable or non-reloadable when relevant. Prepaid is a funding model, not a synonym for virtual.

Atlas editorial proposal · G088. Source scope matters; this entry is not an ASD vocabulary approval.

presentment

Submission of a transaction clearing record from an acquirer to an issuer.

Recommended usage and sources

Usage: Identify the message system and whether this is first presentment or a later dispute-related submission.

Atlas editorial proposal · G034. Source scope matters; this entry is not an ASD vocabulary approval.

primary account number (PAN)

Account number allocated by an issuer to identify a card account.

Recommended usage and sources

Usage: Use PAN for the issuer account number. Distinguish it from a payment token, PAR, and truncated display value.

Atlas editorial proposal · G046. Source scope matters; this entry is not an ASD vocabulary approval.

proof of delivery

Records offered to show that goods or services were delivered or received as agreed.

Recommended usage and sources

Usage: State what the record actually establishes and who received the item. A delivery scan does not automatically prove cardholder authorization.

Atlas editorial proposal · G185. Source scope matters; this entry is not an ASD vocabulary approval.

proxy

Intermediary through which network traffic is relayed.

Recommended usage and sources

Usage: Describe the observed network arrangement. Proxy use alone does not establish fraudulent intent.

Atlas editorial proposal · G155. Source scope matters; this entry is not an ASD vocabulary approval.

PSP reference

Provider-assigned reference for a payment or related operation.

Recommended usage and sources

Usage: Preserve the exact provider field, such as Adyen pspReference. Do not substitute ARN or merchant reference.

  • Adyen glossary (A1) — Living documentation; retrieved 17–18 November 2026. s.v. PSP reference

Atlas editorial proposal · G073. Source scope matters; this entry is not an ASD vocabulary approval.

Q

questionable merchant audit program (QMAP)

Mastercard program for investigating merchant activity under its defined audit rules.

Recommended usage and sources

Usage: Describe the identified program and finding, rather than calling every high-risk merchant questionable.

Atlas editorial proposal · G211. Source scope matters; this entry is not an ASD vocabulary approval.

R

rapid dispute resolution (RDR)

Visa pre-dispute service supporting automated acceptance of liability for eligible disputes.

Recommended usage and sources

Usage: State the service and configured decision. Acceptance is not the same as winning a contested dispute.

Atlas editorial proposal · G194. Source scope matters; this entry is not an ASD vocabulary approval.

reconciliation

Comparison of transaction, accounting, and funds records to explain differences.

Recommended usage and sources

Usage: Name the records, identifiers, dates, and amounts being compared. Reconciliation itself does not move money.

Atlas editorial proposal · G036. Source scope matters; this entry is not an ASD vocabulary approval.

recurring payment

Series of payments under an agreement for goods or services supplied at regular intervals.

Recommended usage and sources

Usage: State the schedule, amounts, cancellation terms, and network classification. Do not use recurring for every later stored-card payment.

Atlas editorial proposal · G096. Source scope matters; this entry is not an ASD vocabulary approval.

refund

Merchant-initiated return of funds associated with a prior purchase.

Recommended usage and sources

Usage: State the original transaction, refund amount, currency, and processing outcome. Do not equate refund submission with receipt by the customer.

Atlas editorial proposal · G038. Source scope matters; this entry is not an ASD vocabulary approval.

refund authorization

Authorization assessment of a refund transaction.

Recommended usage and sources

Usage: Name the network or provider flow. Refund approval is separate from credit posting and customer availability of funds.

Atlas editorial proposal · G040. Source scope matters; this entry is not an ASD vocabulary approval.

refund rate

Ratio of refunds to a stated purchase or payment population under a defined measurement policy.

Recommended usage and sources

Usage: State whether the ratio uses counts or amounts, transaction or processing dates, and partial-refund treatment.

Atlas editorial proposal · G227. Source scope matters; this entry is not an ASD vocabulary approval.

representment

Industry or provider term for returning a disputed transaction with a response to the chargeback.

Recommended usage and sources

Usage: Prefer the exact network stage, such as Mastercard second presentment or Visa dispute response, in network-specific instructions.

Atlas editorial proposal · G180. Source scope matters; this entry is not an ASD vocabulary approval.

revenue recovery

Activities to collect eligible unpaid revenue, including supported retry and customer-notification processes.

Recommended usage and sources

Usage: State the unpaid amount and permitted actions; do not equate recovered revenue with chargeback wins or guaranteed future payments.

Atlas editorial proposal · G234. Source scope matters; this entry is not an ASD vocabulary approval.

reversal

Operation that negates or corrects a prior message or transaction at a specified processing stage.

Recommended usage and sources

Usage: Always qualify the stage and operation: authorization reversal, clearing reversal, or provider-specific reversal.

Atlas editorial proposal · G041. Source scope matters; this entry is not an ASD vocabulary approval.

risk assessment

Evaluation of available evidence to estimate risk and determine the appropriate treatment.

Recommended usage and sources

Usage: State the scope and evidence. It is not proof of fraud and does not necessarily make the authorization decision.

Atlas editorial proposal · G146. Source scope matters; this entry is not an ASD vocabulary approval.

risk rule

Specified condition and action used to evaluate or treat a payment or account risk.

Recommended usage and sources

Usage: Name the exact condition, action, precedence, and provider. A rule match is not a confirmed fraud label.

Atlas editorial proposal · G148. Source scope matters; this entry is not an ASD vocabulary approval.

risk score

Model or system output expressing an estimated level of risk under a specified scale.

Recommended usage and sources

Usage: Name the provider, model, scale, and decision rule. Scores from different systems are not automatically comparable.

Atlas editorial proposal · G145. Source scope matters; this entry is not an ASD vocabulary approval.

S

SCA exemption

Permitted exception to applying SCA for a transaction that remains within the relevant regulatory scope.

Recommended usage and sources

Usage: Name the exemption and decision-maker. An exemption request can be rejected and is not the same as an out-of-scope transaction.

Atlas editorial proposal · G119. Source scope matters; this entry is not an ASD vocabulary approval.

scheme fee

Fee charged under a card network's pricing framework for specified participation or transaction services.

Recommended usage and sources

Usage: State the network and charge basis. Keep it distinct from interchange and the PSP or acquirer margin.

Atlas editorial proposal · G216. Source scope matters; this entry is not an ASD vocabulary approval.

second presentment

Mastercard acquirer submission responding to a chargeback with the grounds and supporting information for rejecting it.

Recommended usage and sources

Usage: Use the Mastercard stage name. Do not replace Visa dispute response with second presentment without a verified cross-network mapping.

Atlas editorial proposal · G179. Source scope matters; this entry is not an ASD vocabulary approval.

sensitive authentication data

Security information used to authenticate cardholders or authorize transactions under PCI definitions.

Recommended usage and sources

Usage: Use the current PCI category and handling requirements; do not treat every card-data field as belonging to the same category.

Atlas editorial proposal · G169. Source scope matters; this entry is not an ASD vocabulary approval.

SEPA

Single Euro Payments Area framework for specified euro payment schemes.

Recommended usage and sources

Usage: Name the scheme, such as credit transfer or direct debit, and the relevant scheme rules. SEPA is not a single payment product.

Atlas editorial proposal · G244. Source scope matters; this entry is not an ASD vocabulary approval.

settlement

Reporting and transfer of amounts owed as a result of clearing.

Recommended usage and sources

Usage: Identify the settlement participants, currency, and cycle. Merchant funding or payout may be a separate event.

Atlas editorial proposal · G035. Source scope matters; this entry is not an ASD vocabulary approval.

SetupIntent

Stripe object used to prepare payment credentials for future use without collecting a payment itself.

Recommended usage and sources

Usage: Distinguish setup authentication or consent from authorization or capture of a subsequent payment.

Atlas editorial proposal · G072. Source scope matters; this entry is not an ASD vocabulary approval.

single message system

Processing arrangement using one message format for authorization and financial processing as specified by the network.

Recommended usage and sources

Usage: Qualify SMS as Single Message System in payments processing; SMS also means Short Message Service in communications.

Atlas editorial proposal · G252. Source scope matters; this entry is not an ASD vocabulary approval.

social engineering

Manipulation of a person to disclose information, transfer money, or perform another harmful action.

Recommended usage and sources

Usage: Describe the deception and observed result. Distinguish it from the payment network's formal dispute classification.

Atlas editorial proposal · G164. Source scope matters; this entry is not an ASD vocabulary approval.

soft decline

Provider or scheme classification indicating that another action or a later permitted attempt may succeed.

Recommended usage and sources

Usage: Preserve the exact code and required action. Soft does not authorize unlimited retries or bypass required authentication.

Atlas editorial proposal · G231. Source scope matters; this entry is not an ASD vocabulary approval.

split tender

Use of more than one payment method to pay for one purchase.

Recommended usage and sources

Usage: State each amount and method. Do not confuse split tender with splitting a marketplace payout among recipients.

Atlas editorial proposal · G249. Source scope matters; this entry is not an ASD vocabulary approval.

sponsored merchant

Merchant accepting transactions under an arrangement with a payment facilitator.

Recommended usage and sources

Usage: Preserve the network-specific designation; verify whether a provider's sub-merchant label denotes the same role.

Atlas editorial proposal · G055. Source scope matters; this entry is not an ASD vocabulary approval.

spoofing

Falsification of an apparent identity, address, or source to mislead a recipient or system.

Recommended usage and sources

Usage: State what was falsified and the supporting evidence; do not infer spoofing solely from a data mismatch.

Atlas editorial proposal · G166. Source scope matters; this entry is not an ASD vocabulary approval.

staged digital wallet

Wallet arrangement with a funding stage separate from the subsequent merchant-payment stage.

Recommended usage and sources

Usage: Describe both stages and the wallet operator's role; do not treat the funding transaction as the merchant purchase.

Atlas editorial proposal · G084. Source scope matters; this entry is not an ASD vocabulary approval.

stored credential

Payment-account information retained for future transactions under an appropriate agreement or consent.

In practice: Move recurring billing instructions during a payment migration

Recommended usage and sources

Usage: State who stores it, its type, and its permitted future use. Storage does not itself make every payment merchant-initiated.

Atlas editorial proposal · G092. Source scope matters; this entry is not an ASD vocabulary approval.

stored-value wallet

Wallet arrangement using a stored balance for payment.

Recommended usage and sources

Usage: Distinguish the stored balance from a tokenized credential linked directly to a card account.

Atlas editorial proposal · G085. Source scope matters; this entry is not an ASD vocabulary approval.

strong customer authentication (SCA)

Authentication requirement defined in the applicable payment-services regulatory framework.

Recommended usage and sources

Usage: Use Strong, not Secure, in this expansion. State the jurisdiction and applicable rules before describing requirements or exemptions.

Atlas editorial proposal · G118. Source scope matters; this entry is not an ASD vocabulary approval.

subscription

Agreement for continuing access to goods or services, usually with renewal or repeated billing.

Recommended usage and sources

Usage: Distinguish the commercial agreement from the individual payments and their payment-network classifications.

Atlas editorial proposal · G099. Source scope matters; this entry is not an ASD vocabulary approval.

success rate

Proportion reaching a stated successful outcome in a specified population and period.

Recommended usage and sources

Usage: Always name the successful state, counting unit, denominator, and measurement window.

Atlas editorial proposal · G222. Source scope matters; this entry is not an ASD vocabulary approval.

supporting documentation

Records submitted to support a position or required fact in a payment or dispute process.

Recommended usage and sources

Usage: Provide relevant, transaction-linked material for the specified condition and stage. More documents do not necessarily establish a stronger case.

Atlas editorial proposal · G184. Source scope matters; this entry is not an ASD vocabulary approval.

SWIFT

Organization and messaging ecosystem supporting standardized financial communications.

Recommended usage and sources

Usage: Name the message or service used. Do not treat a SWIFT message as identical to settlement or guaranteed fund availability.

Atlas editorial proposal · G246. Source scope matters; this entry is not an ASD vocabulary approval.

System to Avoid Fraud Effectively (SAFE)

Mastercard fraud-reporting system identified in Mastercard security requirements.

Recommended usage and sources

Usage: Use SAFE as a network-qualified system name; do not call Mastercard reporting TC40 or treat a report as a chargeback.

Atlas editorial proposal · G191. Source scope matters; this entry is not an ASD vocabulary approval.

T

TC05

Visa transaction-code reference used for settled transactions in the cited VAMP denominator.

Recommended usage and sources

Usage: Use the program's stated eligible transaction population. Do not substitute authorization attempts or order count.

Atlas editorial proposal · G190. Source scope matters; this entry is not an ASD vocabulary approval.

TC15

Visa transaction-code reference used for disputes in the cited VAMP metric.

Recommended usage and sources

Usage: State the eligible count, exclusions, time period, and data-extract timing. Do not equate it with all customer complaints.

Atlas editorial proposal · G189. Source scope matters; this entry is not an ASD vocabulary approval.

TC40

Visa transaction-code reference associated with issuer-reported fraud information.

Recommended usage and sources

Usage: Distinguish fraud reporting from TC15 disputes. State the reporting extract and program treatment before calculating a ratio.

Atlas editorial proposal · G188. Source scope matters; this entry is not an ASD vocabulary approval.

third-party payment fraud

Unauthorized payment activity using another person's account or payment credentials.

Recommended usage and sources

Usage: Distinguish it from cardholder-authorized purchases and legitimate consumer disputes.

Atlas editorial proposal · G136. Source scope matters; this entry is not an ASD vocabulary approval.

threshold

Boundary used to trigger a stated classification, action, or program outcome.

Recommended usage and sources

Usage: Include the unit, comparison operator, scope, effective date, and complete conditions. Do not transfer thresholds between programs or providers.

Atlas editorial proposal · G228. Source scope matters; this entry is not an ASD vocabulary approval.

token lifecycle management

Management of token activation, suspension, replacement, and other supported lifecycle changes.

Recommended usage and sources

Usage: Name the supported token state and operation. A lifecycle update is not payment approval.

Atlas editorial proposal · G107. Source scope matters; this entry is not an ASD vocabulary approval.

token migration

Transfer or replacement of stored payment-token arrangements between systems.

Recommended usage and sources

Usage: State token type, provider permissions, security controls, and required re-enrollment. Portability must be verified for the specific arrangement.

Atlas editorial proposal · G108. Source scope matters; this entry is not an ASD vocabulary approval.

token requestor

Entity requesting a token for an eligible payment-account credential and use case.

Recommended usage and sources

Usage: Use the assigned requestor identity and token domain where relevant; do not confuse it with the cardholder or issuer.

Atlas editorial proposal · G103. Source scope matters; this entry is not an ASD vocabulary approval.

token service provider (TSP)

Entity that issues and manages tokens for token requestors under the relevant framework.

Recommended usage and sources

Usage: Name the token system. TSP has other meanings outside payment tokenization.

Atlas editorial proposal · G102. Source scope matters; this entry is not an ASD vocabulary approval.

token vault

System or service maintaining token records and the authorized relationship to underlying account data.

Recommended usage and sources

Usage: Distinguish a network token vault from a merchant or PSP vault. State who controls access and lifecycle operations.

Atlas editorial proposal · G104. Source scope matters; this entry is not an ASD vocabulary approval.

tokenization

Replacement of sensitive payment-account data with a substitute value managed under a defined token system.

Recommended usage and sources

Usage: Name the token type and provider. Network payment tokens and provider vault tokens have different scopes and rules.

Atlas editorial proposal · G100. Source scope matters; this entry is not an ASD vocabulary approval.

transaction

Payment-system event involving the use of a credential to make a payment or exchange value.

Recommended usage and sources

Usage: State the transaction type and stage. Avoid using transaction for a request, purchase, dispute, and payout without distinction.

Atlas editorial proposal · G042. Source scope matters; this entry is not an ASD vocabulary approval.

transaction identifier

Identifier used to link a transaction and associated lifecycle events.

Recommended usage and sources

Usage: Name the identifier owner and field. Visa Transaction Identifier, ARN, PSP reference, and merchant reference are different identifiers.

Atlas editorial proposal · G043. Source scope matters; this entry is not an ASD vocabulary approval.

transaction receipt

Electronic or paper record generated for a transaction.

Recommended usage and sources

Usage: Use the receipt as evidence of the recorded event; do not assume it proves final settlement or cardholder authorization.

Atlas editorial proposal · G044. Source scope matters; this entry is not an ASD vocabulary approval.

transaction risk analysis (TRA)

Risk-based assessment used in the applicable framework to support a permitted authentication exemption.

Recommended usage and sources

Usage: State the provider, region, and legal conditions. Do not publish one universal TRA amount or fraud threshold.

Atlas editorial proposal · G121. Source scope matters; this entry is not an ASD vocabulary approval.

two-factor authentication (2FA)

Authentication using two distinct factors from the applicable authentication categories.

Recommended usage and sources

Usage: Name the factors. Two steps or two credentials of the same factor type do not necessarily constitute two factors.

Atlas editorial proposal · G124. Source scope matters; this entry is not an ASD vocabulary approval.

U

unauthorized transaction

Transaction asserted or determined not to have been authorized by the relevant account holder under the applicable process.

Recommended usage and sources

Usage: Separate the customer's allegation from an established finding and the network's required dispute evidence.

Atlas editorial proposal · G197. Source scope matters; this entry is not an ASD vocabulary approval.

unscheduled credential-on-file transaction

Later stored-credential transaction made under an agreement without a fixed recurring schedule.

Recommended usage and sources

Usage: Use the network or provider's exact category; distinguish it from a scheduled recurring installment.

Atlas editorial proposal · G097. Source scope matters; this entry is not an ASD vocabulary approval.

V

VAMP

Visa Acquirer Monitoring Program, which monitors specified fraud, dispute, and enumeration activity.

Recommended usage and sources

Usage: Use the current program guide for the region and date. Do not substitute historical VFMP or VDMP criteria.

Atlas editorial proposal · G202. Source scope matters; this entry is not an ASD vocabulary approval.

VAMP enumeration ratio

Ratio of eligible enumerated authorization transactions to eligible authorization transactions under VAMP.

Recommended usage and sources

Usage: Include approved and declined events as specified. Do not substitute the fraud-and-dispute ratio or ordinary decline rate.

Atlas editorial proposal · G204. Source scope matters; this entry is not an ASD vocabulary approval.

VAMP ratio

Count-based ratio of eligible fraud and disputes to settled transactions under the applicable VAMP rules.

Recommended usage and sources

Usage: Use the stated eligible TC40, TC15, and TC05 populations, extract timing, exclusions, and reporting period. Keep thresholds in versioned rules.

Atlas editorial proposal · G203. Source scope matters; this entry is not an ASD vocabulary approval.

velocity rule

Risk rule evaluating counts or values of activity over a specified interval and matching key.

Recommended usage and sources

Usage: State key, event types, window, reset behavior, and action. Do not count retries as unique customers unless intended.

Atlas editorial proposal · G236. Source scope matters; this entry is not an ASD vocabulary approval.

virtual card

Card credential provided for use without requiring a physical card.

Recommended usage and sources

Usage: Identify the issuer product and controls. Virtual does not imply single-use, prepaid, or exemption from authentication.

Atlas editorial proposal · G089. Source scope matters; this entry is not an ASD vocabulary approval.

virtual private network (VPN)

Network arrangement that carries traffic through an encrypted or controlled tunnel.

Recommended usage and sources

Usage: Treat its presence as contextual evidence, not proof of a shopper's true location or fraud.

Atlas editorial proposal · G156. Source scope matters; this entry is not an ASD vocabulary approval.

Visa Dispute Monitoring Program (VDMP)

Historical Visa program name for dispute monitoring.

Recommended usage and sources

Usage: Preserve it when describing historical periods. Check the current VAMP framework before giving current obligations or calculations.

Atlas editorial proposal · G206. Source scope matters; this entry is not an ASD vocabulary approval.

Visa Fraud Monitoring Program (VFMP)

Historical Visa program name for fraud monitoring.

Recommended usage and sources

Usage: Retain it in historical material and verify the relevant region and effective date; do not present its old thresholds as current VAMP rules.

Atlas editorial proposal · G205. Source scope matters; this entry is not an ASD vocabulary approval.

void

Informal or provider-specific term for canceling a transaction or authorization.

Recommended usage and sources

Usage: Prefer the exact cancellation or reversal operation and name the affected processing stage.

Atlas editorial proposal · G032. Source scope matters; this entry is not an ASD vocabulary approval.

W

webhook

HTTP notification sent by a system to another system when a subscribed event occurs.

Recommended usage and sources

Usage: Validate the event and its identifiers; distinguish receipt of a webhook from successful business processing of the event.

Atlas editorial proposal · G070. Source scope matters; this entry is not an ASD vocabulary approval.

Z

zero-value authorization

Authorization or verification request using a zero amount in a supported card-verification flow.

Recommended usage and sources

Usage: Use the exact network and provider operation. Do not treat it as a completed purchase or an automatic consent record.

Atlas editorial proposal · G239. Source scope matters; this entry is not an ASD vocabulary approval.