Type
Bank TransferBNPLCardDirect DebitOfflineVoucherWallet
The primary product or funding model. Bank Transfer covers account-to-account methods, while Offline covers methods completed outside a native digital payment flow.
Taxonomy
Taxonomy
Entity types
Payment Methods
Customer- or merchant-facing ways to initiate or receive a payment.
Channel
OnlineIn-Person
Where the payment experience is available. A method may support more than one channel.
Use Case
PayinP2PPayout
The payment purpose: collecting funds, transferring between people or disbursing funds.
Initiation
PayeePayer
Who starts the payment. Payee is the merchant- or recipient-initiated model formerly called Pull; Payer is the customer-initiated model formerly called Push.
Markets
Countries and explicitly modelled geographic payment markets.
Region
US&CLatAmEMEAAPAC
The four regional groups used across Atlas market filters and comparisons.
Market scope
CountryTerritoryExplicit payment market
Geographies remain canonical market records instead of being embedded as free text on other entities.
Population access
Banked populationUnbanked population
The overview filter distinguishes markets above and below 50% formal financial-account access.
PSPs
Providers that connect merchants to acceptance, processing and payout capabilities.
Provider role
PSPProcessorGatewayAcquirerOrchestrator
Provider roles describe the payment services an organization offers without merging the provider with the methods or rails it supports.
Graph connections
Payment MethodsMarketsLicencesStandards
Coverage, implementations, permissions and security claims remain explicit relationships.
Currencies
Fiat currencies represented by their canonical ISO 4217 identity.
Canonical identity
ISO 4217 alpha codeISO 4217 numeric codeMinor units
Currencies are first-class records with standardized identifiers rather than repeated text labels.
Graph connections
MarketsPayment MethodsPricingSettlement
Currency use is represented through relationships to the relevant market, product or payment flow.
Schemes
Governed rules, rights and obligations for a payment proposition.
Type
CardCredit TransferDirect DebitAlternative
Scheme type describes the governed payment proposition independently from the technical system beneath it.
Graph connections
Payment MethodsSystemsOperatorsMarkets
Participation, operation and reach are modelled as separate sourced relationships.
Systems
Infrastructure that routes, processes, clears or settles payment instructions.
Type
RetailLarge-valueCard
System type classifies the infrastructure used to route, process, clear or settle payment instructions.
Graph connections
SchemesOperatorsMarketsStandards
Technical infrastructure stays distinct from the scheme rules and customer-facing methods that use it.
Operators
Organizations that operate a payment method, scheme or system.
Operating role
Payment MethodSchemeSystem
An operator remains its own organization record and connects to each product or infrastructure layer it operates.
Graph connections
MarketsStandardsRegulatorsBanks
Reach, conformance and oversight remain source-linked relationships.
Regulators
Authorities responsible for payment-market supervision and oversight.
Jurisdiction
NationalRegionalInternational
Regulators are classified by the jurisdictional scope of their mandate.
Graph connections
RegulationsRegulated entitiesPayment infrastructureMarkets
Authorities stay separate from the instruments they publish and the entities they supervise.
Economics
Fees, rates and pricing parameters with explicit scope and effective periods.
Record type
Fee capRate schedulePricing ruleEconomic parameter
Economics records keep the amount or rate separate from its fee layer, product scope and legal basis.
Graph connections
MarketsPayment MethodsSchemesRegulations
Applicability, jurisdiction and effective periods remain explicit and source-linked.
Compliance
Requirements, controls and reference records used to manage compliance.
Category
Customer Due DiligenceConsumer ProtectionSanctions & ScreeningAML & MonitoringOperational ResilienceData & SecurityRegulation & LicensingPricing & InterchangeFraud & Reimbursement
Compliance records are grouped by the primary control, legal or operational domain they address.
Banks
Banking institutions participating in payment markets and infrastructure.
Bank boundary
Canonical bankIssuerAcquirerParticipant
A bank stays one canonical bank record while its roles in products, schemes and systems are expressed through relationships.
Graph connections
CardsMarketsSystemsIdentifiers
Products, reach, infrastructure participation and assigned identifiers remain independently traceable.
Standards
Technical, security and operating standards used across payment systems.
Category
Schemes & RailsAcceptance & InterfacesSecurity & AuthenticationIdentifiers & DataMessaging & DataAPIs & Open Banking
Standards are grouped by the primary interoperability, acceptance, security, data or implementation domain they define.
Cards
Individual consumer and business card products.
Card type
DebitCreditChargePrepaid
Card type describes how the product is funded or repaid; product-specific variants remain distinct records.
Audience
ConsumerBusinessCommercial
Audience distinguishes personal and organizational propositions without merging separately marketed products.
Form factor
PhysicalVirtualHybrid
Form factor records how the card credential is issued and used.
Identifiers
Canonical payment and institution identifiers, including BIN, BIC, BSC and MCC.
Family
BINBICBSCMCC
Each identifier family keeps its own format, authority, scope and lookup behavior.
BIN
BIN
Bank Identification Number / Issuer Identification Number ranges used for payment cards.
BIC
BIC
Business Identifier Codes used to identify financial institutions.
BSC
BSC
Bank and branch sort codes used in domestic clearing contexts.
MCC
MCC
Merchant Category Codes used to classify merchant activity.