SinglePoint International Payments: 180+ Countries, Three Rails

SinglePoint cross-border payments run through three carefully chosen rails — SWIFT MT103 for general international coverage, NACHA IAT for cross-border ACH to Canada, and Directo a Mexico for USD-to-MXN settlement via Banco de México. One authenticated SinglePoint sign-in covers 180+ countries through U.S. Bank's correspondent network.

Every SinglePoint international payment is screened against FinCEN BSA/AML requirements and OFAC sanctions lists. IBAN structure validates at initiation. BEN/SHA/OUR charge codes set per wire. The SinglePoint audit trail holds every cross-border event for 7 years.

Initiate a Cross-Border Payment Speak With the FX Desk

SinglePoint international payments dashboard showing SWIFT, IAT and Directo a Mexico rails with beneficiary routing

SWIFT Correspondent Network

SWIFT MT103 customer credit transfers reach beneficiary banks in 180+ countries via U.S. Bank's correspondent network. U.S. Bank BIC is USBKUS44IMT. Settlement at the beneficiary bank takes 1-2 business days in major corridors, longer in remote destinations. SinglePoint composes MT103 and MT202COV cover payments, BEN/SHA/OUR charge codes, ordering customer name, address and purpose.

USD-to-USD IAT for Canada

IAT (International ACH Transaction) is the NACHA SEC code purpose-built for cross-border ACH. SinglePoint originates IAT entries to Canada using U.S. Bank's correspondent relationship. Settlement posts to the Canadian RDFI in 1-3 business days at a fraction of SWIFT cost — the preferred rail for recurring Canadian vendor and payroll payments.

Directo a Mexico

Directo a Mexico is a corridor operated jointly by the Federal Reserve and Banco de México. SinglePoint originates USD; the Banco de México side delivers Mexican pesos to the beneficiary via CLABE. Cost is materially below a standalone SWIFT wire to Mexico — ideal for recurring vendor disbursement, cross-border payroll and franchise fee collection between U.S. and Mexican entities.

Multicurrency Settlement

SinglePoint supports settlement in USD, EUR, GBP, CAD, MXN, JPY, CHF, AUD and additional currencies by corridor. For beneficiaries requiring local currency, SinglePoint rate-locks via the FX desk at institutional spreads before the wire releases — locking FX exposure on initiation, not post-settlement.

Compliance Notes

BEN/SHA/OUR charge codes select per wire at initiation.
IBAN validation for European Economic Area, UK, UAE, Saudi Arabia and other IBAN jurisdictions.
CLABE validation (18-digit Clave Bancaria Estandarizada) for Mexican beneficiaries.
Sanctions screening: OFAC SDN, consolidated Treasury sanctions and UN lists on every payment.
Travel Rule data carried in SWIFT MT103 and NACHA IAT addenda.
Beneficial owner capture for CIP/CDD alignment with FinCEN expectations.

Region	Settlement Days	Currencies	Network	SinglePoint Workflow
Canada	1-3	USD, CAD	NACHA IAT or SWIFT	IAT batch upload or MT103
Mexico	1-2	USD, MXN	Directo a Mexico or SWIFT	CLABE capture on initiation
European Economic Area	1-2	EUR, USD, GBP	SWIFT MT103	IBAN structure validation
United Kingdom	1-2	GBP, USD, EUR	SWIFT MT103	IBAN validation + sort code
Asia-Pacific	1-3	USD, JPY, AUD, SGD, HKD	SWIFT MT103	Local account validation
Latin America (ex-Mexico)	1-4	USD, BRL, CLP, COP	SWIFT MT103	Local ID capture where required

Beneficiary Bank Charges (BEN / SHA / OUR)

SWIFT charge codes assign who pays correspondent and beneficiary-bank fees. BEN — beneficiary pays all. SHA — shared; originator pays sending fee, beneficiary absorbs the rest. OUR — originator pays all, beneficiary receives full principal. Commercial clients default to OUR for invoice settlement where the supplier expects the full invoice amount to clear. SinglePoint surfaces the code inline so Accounts Payable can align invoice terms with instruction payment.

For SEPA payments within the European Economic Area, the default is SHA per the EU Payment Services Directive. SinglePoint sets SHA automatically for SEPA-eligible EUR payments to align with the directive.

SinglePoint SWIFT charge code selection screen with BEN, SHA and OUR options

SinglePoint IBAN validation and CLABE capture for European and Mexican beneficiaries

IBAN, CLABE and Local Validation

IBAN validation checks structure and Mod-97 check digit per ISO 13616 on initiation. Invalid IBAN blocks release before the file transmits to SWIFT — saving repair fees downstream. For Mexican beneficiaries, SinglePoint validates the 18-digit CLABE. For UK-only payments, the 6-digit sort code and 8-digit account pair validates. Country-specific national clearing codes (BSB for Australia, BLZ for Germany, Transit for Canada) validate on the relevant corridor.

Each field surfaces with inline help so the operator knows what the beneficiary has specified on their invoice or remittance advice.

Sanctions Screening and Returned Payments

Every SinglePoint international payment flows through OFAC SDN, consolidated Treasury sanctions, UN lists and U.S. Bank's internal watchlists before release. Hits route to the Financial Intelligence Unit for Level-1 review. Common-name collisions resolve in hours; true matches block and cancel. The originator sees clear status — clean, under review, blocked — with no ambiguity.

Payments returned by the beneficiary bank (closed account, name mismatch, missing Travel Rule data) flow into the SinglePoint exceptions queue. Originators repair and resubmit or request a full recall back to the originating account. For SWIFT investigations, SinglePoint raises MT195/199 inquiries against the beneficiary bank and tracks the case inside the portal.

SinglePoint OFAC sanctions screening and international exception queue with Level-1 review status

Wire Transfers

Domestic Fedwire and SWIFT outbound wires with dual-control and OFAC screening.

ACH Payments

Domestic NACHA ACH origination across CCD, PPD, CTX, WEB and TEL codes.

Foreign Exchange

Real-time rate-lock across 140+ currency pairs with forward contracts and hedging.

Vendor Payments

AP automation that blends ACH, wires and cross-border payments per vendor preference.

Payroll

ACH PPD/CCD for U.S. payroll with IAT options for cross-border Canadian employees.

Treasury Management

Sweeps, ZBA and positive pay on multicurrency accounts inside SinglePoint.

Transaction Reporting

Reconcile cross-border wires against GL with BAI2, MT940 and custom exports.

Business Checking

The funding account for every SWIFT wire, IAT entry and Directo a Mexico payment.

Which networks does SinglePoint use for international payments?

SinglePoint uses SWIFT MT103 for general international, NACHA IAT for Canada and Directo a Mexico for USD-to-MXN. U.S. Bank BIC is USBKUS44IMT.

What are BEN, SHA and OUR charge codes?

BEN = beneficiary pays all; SHA = shared; OUR = originator pays all. SinglePoint sets the code per wire; commercial default is OUR for invoice settlement.

Does SinglePoint validate IBAN numbers?

Yes. SinglePoint validates IBAN structure and Mod-97 check digit at initiation. Invalid IBANs block before SWIFT submission. CLABE and local account formats validate for Mexico and other non-IBAN corridors.

How does SinglePoint handle cross-border ACH to Canada?

SinglePoint originates NACHA IAT entries to Canada with Travel Rule addenda. Settlement at the Canadian RDFI takes 1-3 business days at a fraction of SWIFT cost.

How does Directo a Mexico work?

Directo a Mexico is a Federal Reserve / Banco de México corridor. SinglePoint originates USD; Banco de México delivers pesos to the beneficiary's CLABE. Cost is materially below a standalone SWIFT wire to Mexico.

Activate SinglePoint International Payments

Whether you pay 10 suppliers in 3 countries or 500 suppliers in 40 countries, a U.S. Bank Commercial Banking advisor can configure SinglePoint cross-border entitlements, currencies and rail preferences for your business.

Contact a Relationship Manager