NEOBANKDB
Market: US

Infrastructure glossary / 14 supported markets

A payment name is not a payment path.

ACH, Fedwire, Faster Payments, UPI, NPP, SEPA Instant, Pix and PayShap describe different combinations of rules, messaging, clearing and settlement. PayID, PayNow and CoDi add addressing or initiation rather than a second pool of money. This glossary names the layer before anyone turns a national system into an unsupported provider feature.

32 curated rail records cover 14 supported markets, 7 infrastructure classes and 13 recorded currencies. Each row preserves operator, participation, direction, operating window, clearing, settlement, identifier, limit, source, observation date, evidence state and confidence.

batch clearing system5scoped records
credit transfer scheme4scoped records
instant payment system11scoped records
mobile payment network1scoped records
payment addressing service2scoped records
real time gross settlement7scoped records
retail payment overlay2scoped records

Publication boundary

National infrastructure does not prove product access.

A payment system can exist without a particular bank, fintech, wallet or brokerage being a direct participant. Institutions can connect through sponsors, correspondents, clearing agents or technical service providers. A provider may receive but not send, support personal but not business accounts, impose a lower cutoff or limit, or route the same customer action through a different system.

Speed labels require equal care. “Instant” can describe message exchange, interbank settlement or beneficiary availability. A screening hold, indirect participant, maintenance state, receiving-bank posting process or wrong identifier can add delay. The glossary records the system design and refuses to guarantee a provider-specific execution time.

Market and infrastructure filters

Name the layer before naming the route.

32 of 32 rail recordsPage 1 of 4 · 10 records per page
  1. au-becsBECS

    Australia / batch clearing system

    Bulk Electronic Clearing System

    Industry has communicated a target to retire BECS in favour of modern infrastructure, subject to review. Current support and transition timing must be rechecked.

    scheduled batchAUDcredit transferdebit transfer
    Market
    Australia
    Operator
    Australian Payments Network under RBA oversight
    Operating model
    operator scheme
    Verification
    verified current scope with transition
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Direct-entry files follow participant business-day and exchange schedules rather than continuous instant processing.

    Participant boundary: Participating financial institutions exchange bulk direct-entry files; customers access payroll and debit services through their providers.

    Clearing: BECS clears bulk direct credits such as salaries and recurring direct debits in files.

    Settlement: Net obligations settle through Australian settlement arrangements after clearing exchanges.

    Identifiers: BSB and account number identify accounts; direct debit also requires an authority and sponsor processes.

    Limit basis: Rules and participants determine file and transaction constraints; providers set product and customer limits.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-RBA-BECS

    Open official rail source
  2. au-nppNPP

    Australia / instant payment system

    New Payments Platform

    NPP infrastructure does not prove every Australian provider, account, direction or NPP service is supported or instantly credited.

    near real timeAUDcredit transferperson to personperson to business
    Market
    Australia
    Operator
    Australian Payments Plus; Reserve Bank of Australia operates the Fast Settlement Service
    Operating model
    participant network
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Designed for near-real-time 24/7 operation, subject to participant service, fraud and maintenance controls.

    Participant boundary: Financial institutions connect directly or through access arrangements; customers use enabled accounts and services from participating providers.

    Clearing: The NPP routes data-rich retail payment messages between participating institutions.

    Settlement: The RBA Fast Settlement Service settles NPP obligations individually in central-bank funds.

    Identifiers: BSB and account number or enabled PayID can address an NPP payment; PayID is a separate addressing service.

    Limit basis: NPP services and participants set transaction, security, customer and product limits.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-RBA-NPP

    Open official rail source
  3. au-payidPayID

    Australia / payment addressing service

    PayID Addressing Service

    PayID is an addressing layer, not a rail, account or guarantee of immediate completion. Institution support and displayed recipient name must be checked.

    near real timeAUDcredit transferperson to personperson to business
    Market
    Australia
    Operator
    Australian Payments Plus
    Operating model
    overlay on underlying rail
    Verification
    verified current overlay
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Address lookup is available through participating online banking services when the linked account and NPP service are available.

    Participant boundary: A customer registers a supported identifier with a participating financial institution and links it to an eligible account.

    Clearing: PayID resolves an identifier to account-routing information; it does not itself clear funds.

    Settlement: The resulting payment uses an NPP service and settles through NPP/Fast Settlement Service arrangements.

    Identifiers: Supported mobile number, email, ABN or organisation identifier can be linked depending on provider rules.

    Limit basis: PayID has no independent payment cap; the NPP service and financial institution set limits and security holds.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-APPLUS-PAYID

    Open official rail source
  4. br-pixPix

    Brazil / instant payment system

    Pix Instant Payment System

    Pix participation does not prove every institution offers every key, request, QR, limit, fee or direction to every customer.

    instant secondsBRLcredit transferperson to personperson to businessrequest to pay
    Market
    Brazil
    Operator
    Banco Central do Brasil
    Operating model
    central bank system
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Designed for continuous instant operation through participating institutions, subject to security, fraud and maintenance controls.

    Participant boundary: Direct and indirect participants serve eligible transactional accounts; BCB publishes the participant list and participation class.

    Clearing: The Pix infrastructure routes and validates instant payment instructions, keys and supported initiation flows.

    Settlement: Interbank Pix obligations settle in central-bank money through the BCB instant-payment settlement infrastructure.

    Identifiers: Pix key, QR code and account details can identify eligible recipients depending on the flow and participant.

    Limit basis: BCB rules and participants apply transaction, time-of-day, device and risk limits; no one customer cap applies globally.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-BCB-BR-PIX

    Open official rail source
  5. ca-acssACSS

    Canada / batch clearing system

    Automated Clearing Settlement System

    ACSS is infrastructure for several item types, not a consumer product. It does not prove every provider supports EFT, cheque, debit or a specific posting time.

    scheduled batchCADUSDcredit transferdebit transfer
    Market
    Canada
    Operator
    Payments Canada
    Operating model
    operator scheme
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Retail batch exchanges and settlement follow Payments Canada business-day schedules; institution cutoffs differ.

    Participant boundary: Eligible Payments Canada members exchange paper and electronic items directly or through clearing agents; customers access through providers.

    Clearing: ACSS and USBE calculate multilateral net positions for eligible retail payment items.

    Settlement: Net obligations settle in central-bank money through Bank of Canada accounts after clearing.

    Identifiers: Canadian institution, transit and account details identify common EFT items; item-specific rules apply.

    Limit basis: System and payment-stream rules govern item values; providers set customer, risk, hold and product limits.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-PAYMENTS-CA-ACSS

    Open official rail source
  6. ca-interac-e-transferInterac e-Transfer

    Canada / retail payment overlay

    Interac e-Transfer

    Interac e-Transfer is a service overlay, not a bank account or direct central-bank rail; provider participation and receipt method must be verified.

    near real timeCADcredit transferperson to personrequest to pay
    Market
    Canada
    Operator
    Interac Corp.
    Operating model
    participant network
    Verification
    verified current overlay
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Generally available through participating online and mobile banking channels, subject to institution maintenance and review.

    Participant boundary: Both parties generally need eligible Canadian accounts at participating financial institutions for the standard flow.

    Clearing: Interac carries notification, addressing and transfer instructions between participating institutions.

    Settlement: Underlying account debit, clearing and settlement occur through participating financial institutions and Canadian payment infrastructure.

    Identifiers: Email or mobile number can notify or address a recipient; Autodeposit and security-question flows differ.

    Limit basis: Each financial institution sets customer limits, fees, holds and risk controls.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-INTERAC-ETRANSFER

    Open official rail source
  7. ca-lynxLynx

    Canada / real time gross settlement

    Lynx High-Value Payment System

    A Canadian wire label may involve Lynx and correspondents. The rail record does not establish provider pricing, cutoff, route or beneficiary timing.

    real timeCADhigh value creditcredit transfer
    Market
    Canada
    Operator
    Payments Canada
    Operating model
    operator scheme
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Operates on Canadian business days under the Lynx system schedule; providers can set earlier customer wire cutoffs.

    Participant boundary: Eligible financial institutions participate directly; other institutions and customers can access through correspondents or providers.

    Clearing: High-value payment instructions are validated and processed individually.

    Settlement: Final settlement occurs in real time through participant settlement accounts at the Bank of Canada.

    Identifiers: Institution and account or correspondent details are used; customer wire fields and intermediaries vary.

    Limit basis: The system is designed for high-value payments; provider, compliance, liquidity and customer limits are separate.

    Message standard: Not established in the approved public record.

    Source IDs: SRC-PAYMENTS-CA-LYNX

    Open official rail source
  8. fr-sepa-credit-transferSCT

    France / credit transfer scheme

    SEPA Credit Transfer Scheme

    SCT is a pan-European scheme rather than a France-only rail. Domestic infrastructure and provider support must be established separately.

    same day or deferredEURcredit transfer
    Market
    France
    Operator
    European Payments Council
    Operating model
    operator scheme
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Scheme execution follows EU law, EPC rules and participant processing calendars; French provider cutoffs affect execution.

    Participant boundary: Participating French and EEA PSPs adhere directly or through reachability arrangements; account location alone does not prove product support.

    Clearing: The EPC rulebook defines standardized euro credit-transfer messages; French payments can clear through CORE(FR) or other mechanisms.

    Settlement: Settlement occurs through the clearing and settlement mechanism selected by participants, not through the EPC itself.

    Identifiers: IBAN identifies the destination; additional bank, beneficiary and purpose fields depend on the provider and payment.

    Limit basis: Regulation and scheme rules govern execution while providers can apply lawful product, compliance and channel limits.

    Message standard: ISO 20022 SEPA credit-transfer messages

    Source IDs: SRC-EPC-SEPA-CREDIT-TRANSFER, SRC-BDF-PAYMENT-SYSTEMS

    Open official rail source
  9. fr-sepa-instant-credit-transferSCT Inst

    France / credit transfer scheme

    SEPA Instant Credit Transfer Scheme

    The under-ten-second target is not a guarantee for every account, screened transaction, outage or provider channel.

    instant secondsEURcredit transferperson to personperson to business
    Market
    France
    Operator
    European Payments Council; Banque de France oversight context
    Operating model
    operator scheme
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Designed for 24/7 execution with funds available within seconds; Banque de France describes an under-ten-second target.

    Participant boundary: Reachable participating PSPs implement the scheme; French accounts can use different clearing infrastructures and provider controls.

    Clearing: The rulebook standardizes instant euro credit transfers; French instant messages clear through eligible European mechanisms.

    Settlement: Settlement uses compatible clearing and settlement mechanisms; scheme messaging and settlement infrastructure are separate.

    Identifiers: IBAN identifies the destination; beneficiary verification and fraud controls are separate from the rail.

    Limit basis: Institutions can apply customer-specific controls and maximums within current legal and scheme requirements.

    Message standard: ISO 20022 SCT Inst messages

    Source IDs: SRC-EPC-SEPA-INSTANT, SRC-BDF-SEPA-INSTANT, SRC-BDF-PAYMENT-SYSTEMS

    Open official rail source
  10. de-sepa-credit-transferSCT

    Germany / credit transfer scheme

    SEPA Credit Transfer Scheme

    SCT is a rulebook and reachability scheme, not one central rail. Provider support, direction, cutoff, fee and settlement path require separate evidence.

    same day or deferredEURcredit transfer
    Market
    Germany
    Operator
    European Payments Council
    Operating model
    operator scheme
    Verification
    verified current scope
    Observed
    2026-07-12
    Confidence
    high
    Review participation, clearing and settlement

    Operating window: Scheme execution follows EU law, EPC rules and participant processing calendars; provider cutoffs affect execution.

    Participant boundary: Participating payment service providers adhere directly or through reachable arrangements; a German IBAN alone does not prove a product feature.

    Clearing: The EPC rulebook defines standardized euro credit-transfer messages and obligations; clearing occurs in separate clearing mechanisms.

    Settlement: Settlement occurs through selected clearing and settlement mechanisms, not through the EPC itself.

    Identifiers: IBAN identifies the payment account; BIC and other fields can apply in specific institutional or cross-border contexts.

    Limit basis: Regulation and scheme rules govern execution while providers can apply product, compliance and channel limits.

    Message standard: ISO 20022 SEPA credit-transfer messages

    Source IDs: SRC-EPC-SEPA-CREDIT-TRANSFER

    Open official rail source

Layer boundaries

System, scheme, message and money are different objects.

The glossary classes are discovery aids; each row’s official operating boundary controls.

01

Payment system

A payment system supplies common rules and infrastructure for participants to exchange payment instructions and discharge obligations. Fedwire, Lynx and UAEFTS combine instruction processing with real-time gross settlement. Retail instant systems can use different clearing and settlement designs.

02

Scheme or rulebook

A scheme defines message, participant and processing obligations without necessarily operating the settlement account. SEPA Credit Transfer and SEPA Instant are European Payment Council rulebooks used with compatible clearing and settlement mechanisms. The EPC does not itself become every participant’s settlement system.

03

Clearing

Clearing validates, routes, matches and can calculate what participants owe. ACH, Bacs, ACSS and BECS process batches or files and settle resulting positions later. Real-time customer notification does not transform a deferred-net clearing arrangement into gross settlement.

04

Settlement

Settlement discharges the obligation between participants, often across central-bank accounts. Gross systems settle transfers individually; net systems settle calculated positions. Customer account credit, interbank settlement and legal finality are related but must not be presented as one timestamp.

05

Messaging standard

ISO 20022 or a scheme-specific file format defines how payment data is structured. A standard does not move money by itself. Two systems can use ISO 20022 while differing in participants, settlement asset, operating window, recall rules and customer experience.

06

Addressing or overlay

PayID maps an Australian identifier to an eligible account before an NPP payment. PayNow maps Singapore proxies before a FAST transfer. CoDi creates a collection message that initiates SPEI. The alias or QR layer does not create a second settlement rail.

07

Provider feature

The customer-facing button is the final layer and needs its own evidence. A provider decides eligible accounts, direction, amount, fee, cutoff, review, fields and error recovery within applicable system rules. Country infrastructure cannot fill those facts.

Speed and finality

“Fast” is a stack of clocks.

A user sees one status, while the payment can pass through validation, clearing, settlement and beneficiary posting. The directory therefore classifies design speed but retains operating and participation boundaries beside it.

Submission clock

The provider can hold an instruction before sending it for balance, fraud, sanctions, beneficiary, device or approval checks. A system’s open window is not the provider’s customer cutoff.

Clearing clock

Batches wait for an exchange or settlement window. Instant systems validate individual messages continuously. Near-real-time overlays can still rely on a participant or underlying rail that introduces its own state.

Settlement clock

Gross systems settle each instruction; net systems calculate and settle positions. Settlement finality between institutions does not automatically answer when a recipient can withdraw or reverse a customer credit.

Availability clock

The receiving provider posts funds to the customer under its own account, compliance and value-date rules. “Within seconds” remains a design target, not a universal service-level guarantee.

Identifiers

An alias can find an account without becoming the account.

Recipient identifiers, account identifiers and routing identifiers play different roles.

Account and routing data

IBAN, CLABE, BSB plus account number, sort code plus account number, IFSC plus account number and US routing plus account number identify institution and account structures. Required fields, checksum, account type and purpose remain market- and provider-specific.

Proxy or alias

Mobile numbers, email addresses, UPI IDs, Pix keys and PayID aliases resolve through a directory controlled by a participant or scheme. Registration, portability, recipient display and supported alias types require exact evidence.

QR and request messages

A QR code can encode a fixed recipient, dynamic invoice or payment request. Scanning does not itself transfer funds. The payer still authorizes an underlying credit transfer and the receiving institution still applies its posting rules.

Name checking

Confirmation of Payee and other beneficiary-verification services reduce some misdirection risk but are separate from clearing and settlement. A name match is not a guarantee that the intended person controls the account or that a transfer is recoverable.

Direction and use

Push, pull and request-to-pay cannot be merged.

The same infrastructure family can contain different authorization and return models.

Push credit

The payer instructs the transfer.

FPS, SPEI, Pix, UPI and most wire flows move after the payer or its bank initiates a credit. A completed push payment can be difficult to cancel; fraud reimbursement and mistaken payment recovery are separate policy questions.

Pull debit

The payee relies on authority.

ACH debits, Bacs Direct Debit and BECS direct debits require authorization or a mandate. Returns, indemnities and dispute windows differ from a push transfer and cannot be inferred from the system’s credit capability.

Request-to-pay

A message asks; it does not move funds.

A request or collection instruction invites the payer to approve an underlying transfer. CoDi, UPI and selected instant systems support forms of request or collection, but provider interfaces, merchant access and customer controls can differ.

Route verification

Six checks before publishing a provider payment path.

The glossary identifies possible infrastructure; route evidence must complete the chain.

  1. 01

    Fix the legal entities and market.

    Identify the sending and receiving entities, customer types and account locations. A global brand can use different participants and rails by market.

  2. 02

    Name the product action and direction.

    Distinguish deposit, withdrawal, bank transfer, card funding, direct debit, wallet payment, request-to-pay and internal ledger movement. Similar buttons can create different claims.

  3. 03

    Verify direct or indirect access.

    Check the operator’s participant list and provider documentation. A sponsor, correspondent or partner can change cutoffs, identifiers, fees, returns and operational responsibility.

  4. 04

    Attach the identifier and message layer.

    Record the exact account, routing, alias or QR data and whether a separate name-checking or request service is used. Never substitute a message standard for a rail.

  5. 05

    Separate clearing, settlement and posting.

    State what the official system proves at each stage. Keep provider review, batch exchange, interbank finality and beneficiary availability as distinct timestamps.

  6. 06

    Capture limits, exceptions and date.

    Record provider and system limits separately, plus operating windows, maintenance, sanctions, fraud controls, return rules, observation date, verification state and confidence.

Operational states

Unknown infrastructure remains unknown.

The interface fails closed when market, source or participation evidence is missing.

Loading

Filter changes announce a loading state before replacing the scoped record set. No temporary route or speed answer is shown.

Empty

A zero-result combination offers a reset without substituting a similar scheme, overlay, market or provider feature.

Stale

Observation dates remain visible. Participant lists, limits, hours, message migrations and transition plans require decision-time review.

Error

Duplicate IDs, unknown markets, missing operators, malformed classifications or unknown sources block the glossary.

Unavailable

A missing message standard or provider path is stated as not established instead of being completed from model knowledge.

Overlap

One customer action can use an alias, scheme, clearing system, settlement system and provider ledger. The records keep each layer visible.

Evidence ledger

Infrastructure is a starting point, never the provider verdict.

Every record links to an official central bank, operator, regulator, scheme or standards source and retains the approved source IDs separately from rendered copy. Canonical validation checks the market, operator, class, currency, evidence date and confidence before publication.

The glossary is educational research, not a promise that a provider participates, that a transfer will complete, or that the rail is suitable for a particular payment. Live participant registers, provider terms and transaction-time review control. A crawler or model cannot publish a route directly.

Inspect source recordsMap the authoritiesCompare protection mechanismsRead the methodology