Currency Guides

EGP should not be presented as a generic collection currency unless the customer's generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the beneficiary route and local bank requirements before creating a payout.
• Settlement expectation: Depends on the payout partner, beneficiary bank, and required compliance checks.
• Operational note: Do not share collection instructions for EGP unless Product confirms collection support for the account.

ETB should be treated as a payout route, not a holdable collection currency.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the supported payout route and beneficiary-bank details before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present ETB as a holdable wallet or local collection account unless Product confirms that capability.

GHS has payout support but should not be described as having collection support by default.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and receiving-bank processing.
• Operational note: Do not present GHS as collectable unless Product confirms collection support for the customer's account.

KES supports local collections and payouts across instant wallet, instant bank, and high-value bank rails.

• Capability: Local collection and payout support, subject to account approval.
• Validation: Bank and branch codes are mandatory for KES bank beneficiaries.
• Operational note: Do not use the previous 14:00 GMT same-day bank settlement guidance. Amounts above 1M KES settle T+1 after the 13:00 GMT cutoff and require supporting documents.

MAD should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the beneficiary route and local bank requirements before creating a payout.
• Settlement expectation: Depends on the payout partner and receiving-bank processing.
• Operational note: Do not share MAD collection instructions unless Product confirms collection support for the account.

NGN supports local collections and payouts across instant, standard, and high-value Nigerian bank rails.

• Capability: Local collection and payout support, subject to account approval.
• Account format: NGN bank accounts are exactly 10 digits.
• Transaction limit: Bank payments may be subject to a 2.5bn NGN per-transaction limit, with higher limits reviewed case by case.
• Operational note: Do not assume a default issuing route for sub-accounts. Confirm the current rail on the generated wallet details before sharing sender instructions.

RWF availability is route-dependent and should be confirmed from the generated wallet or beneficiary details before funds are sent.

• Capability: Collection, hold, and payout support may vary by account, corridor, and approval status.
• Typical rails: Local bank-transfer routes may be available where enabled for the account.
• Settlement expectation: Depends on the approved route, receiving bank, and local processing timelines.
• Operational note: Use the issued account or beneficiary instructions to confirm supported identifiers, rail, and settlement expectations before initiating a transaction.

ZAR requires additional regulatory review and should not be treated as a standard collection route for every use case.

• Capability: Collection capability may be subject to review or pending regulatory approval depending on the customer flow. Some flows require evidence of a South African licence or a related approved use case.
• Typical rails: Local ZAR routing can involve SAMOS/RTGS, especially for Non-Resident Rand (NRR) account structures. NRR flows may be RTGS-only.
• Settlement expectation: Typically 1 working day where approved, subject to the account type and regulatory checks.
• Compliance requirement: ZAR inflows require a declared Balance of Payments (BoP) code for SARB reporting.
• Operational note: Confirm NRR account requirements, Exchange Control treatment, review status, and any C2B limits or pending approvals before sharing ZAR funding instructions.

TZS supports local payment routes across instant and high-value rails.

• Capability: Local collection and payout support, subject to account approval.
• Collection SLA: Same day with a 15:00 UK cutoff, based on the Atlas Collections PDF.
• Payout SLA: Instant via TIPS up to 20M TZS; amounts above 20M TZS use TISS where available or another approved high-value route.
• Operational note: Confirm whether the transfer should use TIPS, TISS, or EFT before sharing sender or beneficiary instructions.

TND should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the beneficiary route and local bank requirements before creating a payout.
• Settlement expectation: Depends on the payout partner and receiving-bank processing.
• Operational note: Do not present TND as a holdable collection wallet unless Product confirms that capability.

UGX collections use a pooled allocation model.

• Capability: Collection and payout support, subject to route approval.
• Collection model: Bank details are issued in Verto's name, not your company's name.
• Collection SLA: Pooled allocation with T+1 settlement.
• Payout SLA: Same day with a 13:00 UK cutoff.
• Typical rails: Standard domestic EFT and RTGS-style bank transfers, with sender-bank routing determined by transaction value and urgency.
• Operational note: Confirm corridor eligibility and sender instructions before going live, and use the issued funding details to validate the exact bank and account identifiers.

ZMW should be treated as a non-holdable payout route unless generated funding details confirm collection support.

• Capability: Non-holdable payout support, subject to route approval.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present ZMW as a holdable wallet or collection currency unless Product confirms that capability.

XAF is live for pooled collections and local payouts, with virtual-account expansion planned.

• Capability: Holdable, collectable through pooled collection where enabled, and payable through local payout routes.
• Typical rails: Pooled collection and local payout rails.
• Settlement expectation: T+1 to T+2 for local payouts.
• Operational note: BDA integration work is planned for Q2 2026. Confirm whether the customer has pooled collection access or future virtual-account access before sharing XAF instructions.

XOF is live for pooled collections and local payouts.

• Capability: Holdable, live for pooled collections, and live for local payouts.
• Typical rails: Pooled collection and local payout rails.
• Settlement expectation: T+1 for pooled collections where enabled; T+1 to T+2 for local payouts.
• Operational note: BDA integration work is planned for Q2 2026. Confirm the exact issued details before sharing XOF collection instructions.

AED should not be presented as a live holdable currency.

• Capability: Not currently holdable. AED collections are auto-converted, typically to USD, where supported.
• Coming soon: AED virtual account capability is listed as Coming Soon. The Zand AED VA Integration and AED Held Funds System are in Discovery for Q2 2026.
• Planned SLA: Instant for amounts below 50k AED and T+1 for amounts above 50k AED, once the coming-soon capability is live.
• Operational note: Do not describe Aani, UAEFTS, dedicated AED virtual accounts, or AED held balances as live for a customer unless Product confirms the capability is enabled for that account.

BHD requires route confirmation before being presented as collectable or holdable.

• Capability: Confirm collection, hold, and payout status on the generated account or beneficiary details.
• Typical rails: Route-dependent.
• Settlement expectation: Depends on the approved route and banking partner.
• Operational note: Do not rely on generic collection copy for BHD; verify the exact corridor capability before sharing customer instructions.

BDT should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present BDT as a holdable wallet or collection currency unless Product confirms that capability.

CNY and CNH are different currencies for operational and regulatory purposes.

• Capability: Verto's documented China payout capability is CNH (offshore Yuan), not onshore CNY collection.
• Typical rails: CNH/CNY payout routing may use CIPS where enabled. Do not describe onshore CNY CNAPS or IBPS collection support unless Product and Compliance explicitly confirm the route.
• Flow restrictions: B2B flows only. C2X and B2C flows are not supported, and payments from FATF Grey List countries are not allowed.
• Roadmap note: Yeepay integration targets CNH and potentially HKD.
• Operational note: Confirm whether the customer needs onshore CNY or offshore CNH before quoting capability, pricing, or settlement.

HKD collections typically route through Hong Kong's domestic bank-transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: FPS for instant eligible transfers and standard domestic bank transfer rails for regular account funding.
• Settlement expectation: Instant on FPS-supported flows, with same-day settlement common for standard domestic transfers submitted within banking windows.
• Operational note: Use the funding details generated for your wallet to confirm the bank code, branch code, and account number format required for the issued account.

IDR should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present IDR as a holdable wallet or collection currency unless Product confirms that capability.

ILS collections usually rely on Israel's domestic bank clearing framework where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Masav for routine domestic clearing and Zahav for high-value or urgent bank transfers.
• Settlement expectation: Standard domestic collections generally follow banking-day cycles, while urgent high-value transfers can settle faster through the appropriate bank rail.
• Operational note: Use the funding details generated for your wallet to confirm the bank code, branch code, and account number the sender should use.

INR should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present INR as a holdable wallet or collection currency unless Product confirms that capability.

JPY collections commonly route through Japan's domestic bank-transfer network where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Zengin System for domestic bank transfers, with standard bank-transfer processing determined by the sending institution.
• Settlement expectation: Same day on standard domestic banking cycles, with posting speed dependent on bank processing windows and cutoff times.
• Operational note: Use the funding details generated for your wallet to confirm the bank code, branch code, and account format required for the transfer.

KRW should be treated as a non-holdable payout route unless generated funding details confirm collection support.

• Capability: Non-holdable payout support, subject to route approval.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present KRW as a holdable wallet or collection currency unless Product confirms that capability.

KWD requires route confirmation before being presented as collectable or holdable.

• Capability: Confirm collection, hold, and payout status on the generated account or beneficiary details.
• Typical rails: Route-dependent.
• Settlement expectation: Depends on the approved route and banking partner.
• Operational note: Do not rely on generic collection copy for KWD; verify the exact corridor capability before sharing customer instructions.

MYR should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present MYR as a holdable wallet or collection currency unless Product confirms that capability.

OMR requires route confirmation before being presented as collectable or holdable.

• Capability: Confirm collection, hold, and payout status on the generated account or beneficiary details.
• Typical rails: Route-dependent.
• Settlement expectation: Depends on the approved route and banking partner.
• Operational note: Do not rely on generic collection copy for OMR; verify the exact corridor capability before sharing customer instructions.

PKR should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present PKR as a holdable wallet or collection currency unless Product confirms that capability.

PHP should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present PHP as a holdable wallet or collection currency unless Product confirms that capability.

QAR requires route confirmation before being presented as collectable or holdable.

• Capability: Confirm collection, hold, and payout status on the generated account or beneficiary details.
• Typical rails: Route-dependent.
• Settlement expectation: Depends on the approved route and banking partner.
• Operational note: Do not rely on generic collection copy for QAR; verify the exact corridor capability before sharing customer instructions.

SAR collections typically rely on Saudi Arabia's domestic bank-transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: SARIE for domestic bank transfers, including instant-enabled flows where available through participating banks.
• Settlement expectation: Domestic transfers are commonly same day, with faster posting available on supported instant bank flows.
• Operational note: Use the funding details generated for your wallet to confirm the exact local or international bank identifiers available for the issued account.

SGD should not be presented as a live virtual-account collection currency by default.

• Capability: Payout-only with mandatory inline FX. SGD is non-holdable in current capability documentation.
• Typical rails: FAST may be available for approved local payouts.
• Settlement expectation: In minutes where the approved FAST payout route is available; otherwise depends on the receiving-bank route.
• Operational note: Do not promise FAST, PayNow, or dedicated Singapore virtual-account details unless Product confirms collection capability is enabled for the customer.

LKR should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present LKR as a holdable wallet or collection currency unless Product confirms that capability.

THB should be treated as a payout route unless generated funding details confirm collection support.

• Capability: Payout-only with mandatory inline FX, based on the current Atlas capability audit.
• Typical rails: Confirm the payout route and beneficiary-bank requirements before creating a transaction.
• Settlement expectation: Depends on the payout route and local bank processing.
• Operational note: Do not present THB as a holdable wallet or collection currency unless Product confirms that capability.

GBP uses UK domestic rails where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Format requirements: GBP local accounts use an 8-digit account number and a 6-digit sort code.
• Operational note: Account-name lookups via the get_account_name API are supported where the route allows it.

BGN should not be presented as a generic collection currency without route confirmation.

• Capability: Confirm collection, hold, and payout status before sharing customer instructions.
• Typical rails: Route-dependent.
• Settlement expectation: Depends on the approved route and banking partner.
• Operational note: Replace this with specific rail guidance once Product confirms the live BGN capability set.

CHF is referenced as a holdable currency.

• Capability: Holdable; confirm collection and payout support on generated account or beneficiary details.
• Typical rails: Route-dependent.
• Settlement expectation: Depends on the approved route and banking partner.
• Operational note: Confirm the exact account identifiers and sender instructions before sharing CHF payment details.

CZK collections generally use the Czech domestic clearing network where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: CERTIS for domestic clearing and CERTIS Instant Payment for eligible instant transfers between participating banks.
• Settlement expectation: Instant on supported real-time flows, otherwise same banking day or next banking cycle.
• Operational note: Use the funding details generated for your wallet to confirm the domestic bank identifiers the sender should reference.

DKK collections typically route through Denmark's domestic bank-transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Straksclearing for instant eligible transfers and domestic bank clearing for standard account-to-account collections.
• Settlement expectation: Instant between participating banks on supported flows, otherwise same banking day or next banking cycle.
• Operational note: Use the funding details generated for your wallet to confirm the exact account identifiers and any bank-specific sender requirements.

EUR supports SEPA-based collections and payouts where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Format requirements: EUR collections require a valid IBAN.
• Transaction limit: EUR payments may be subject to a 10M EUR per-transaction limit and a 12:00 UK cutoff, depending on the route.
• Account models: EUR collections can use different account models and eligibility criteria depending on the approved route.
• Operational note: Do not assume the IBAN jurisdiction is always LT or FR; it can vary by banking partner and account model.

HUF collections commonly use Hungary's domestic instant-transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: AFR (Azonnali Fizetési Rendszer) for instant domestic transfers, with standard domestic bank transfer processing for non-instant cases.
• Settlement expectation: Near real-time on eligible AFR flows, otherwise same banking day based on bank cutoffs.
• Operational note: Use the funding details generated for your wallet to confirm the exact domestic account identifiers and sender formatting requirements.

NOK collections generally use Norway's domestic bank-transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: NICS for domestic clearing and Straksbetaling for supported instant bank transfers.
• Settlement expectation: Instant on eligible real-time flows, otherwise same banking day or next banking cycle.
• Operational note: Use the funding details generated for your wallet to confirm the exact account number and any sender-bank formatting requirements.

PLN collections commonly use Poland's domestic clearing system where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Elixir for standard domestic clearing and Express Elixir for eligible instant transfers.
• Settlement expectation: Instant on supported Express Elixir flows, otherwise same banking day based on clearing sessions.
• Operational note: Use the funding details generated for your wallet to confirm the account identifiers and sender instructions for the issued account.

RON collections generally route through Romania's domestic account-to-account transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Standard domestic clearing and Instant Payments on supported bank connections.
• Settlement expectation: Instant between participating banks where supported, otherwise same banking day or next clearing cycle.
• Operational note: Use the funding details generated for your wallet to confirm the exact IBAN or local bank details the sender should use.

SEK collections generally use Sweden's domestic bank-transfer ecosystem where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Standard domestic clearing through Swedish bank-transfer rails, with instant settlement supported across participating-bank real-time infrastructure.
• Settlement expectation: Same day for standard bank transfers, with real-time posting on eligible instant flows.
• Operational note: Use the funding details generated for your wallet to confirm the clearing code and account-number format required by the sender's bank.

TRY collections commonly use Turkey's domestic account-to-account transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: FAST for instant transfers and domestic EFT rails for standard bank-funded collections.
• Settlement expectation: Real-time on supported FAST payments, otherwise same banking day on standard EFT processing.
• Operational note: Use the funding details generated for your wallet to confirm the exact IBAN and bank identifiers the sender should use.

BRL is supported for payouts only.

• Capability: Payout-only with mandatory inline FX.
• Typical rails: Confirm the beneficiary route and required bank details before creating a payout.
• Settlement expectation: Depends on the payout route and receiving-bank processing.
• Operational note: Do not present BRL as a holdable or collectable wallet currency unless Product confirms that capability is enabled.

CAD collections generally use Canada's domestic electronic funds network where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: EFT for standard domestic collections and domestic or international wire rails for time-sensitive transfers.
• Settlement expectation: EFT collections usually settle on standard banking cycles, while wires are typically same day once released by the sending bank.
• Operational note: Use the funding details generated for your wallet to confirm the exact account, transit, and institution identifiers available for the issued account.

MXN collections typically use Mexico's domestic real-time bank-transfer infrastructure where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: SPEI for domestic account-to-account transfers.
• Settlement expectation: Real-time or near real-time on supported SPEI flows.
• Operational note: Use the funding details generated for your wallet to confirm the exact CLABE or other domestic bank identifiers required for sender instructions.

USD supports local and international collection routes where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Routing numbers: US virtual accounts include a 9-digit routing number, also known as an ABA code.
• Operational note: Domestic wires can use different routing numbers than ACH; verify the generated wallet details before sharing instructions.

AUD is holdable and collectable where the current banking partner supports the route.

• Capability: Holdable and collectable; confirm payout support on the generated beneficiary route.
• Typical rails: New Payments Platform (NPP) and BECS where enabled by the current banking partner.
• Settlement expectation: NPP can support real-time settlement where available; BECS typically settles on a T+1 cycle.
• Format requirements: Australian local accounts use a 6-digit BSB (Bank State Branch) and an account number.
• Operational note: Verify NPP availability against the generated wallet details before promising real-time inbound settlement.

NZD collections typically route through New Zealand's domestic bank-transfer network where enabled.

• Capability: Confirm collection, hold, and payout status on the generated account details.
• Typical rails: Standard domestic account-to-account bank transfers, with settlement speed driven by the sending bank's processing windows.
• Settlement expectation: Usually same banking day for routine local transfers submitted within bank cutoffs.
• Operational note: Use the funding details generated for your wallet to confirm the exact account number format and any required bank or branch references.