SinglePoint International Payments: SWIFT, IAT and FedGlobal Cross-Border to 180+ Countries

SinglePoint cross-border payments cover three distinct rails. SWIFT MT103 customer credit transfers reach beneficiaries in 180+ countries via U.S. Bank correspondent banking (BIC USBKUS44IMT). USD-to-USD International ACH Transactions (IAT) handle structured cross-border ACH to Canada and Mexico. FedGlobal Directo a Mexico delivers peso payments to Mexican receiving banks in one banking day.

Every SinglePoint cross-border payment is screened against OFAC SDN, EU consolidated sanctions and UN Security Council lists in real time. IBAN validation, BEN/SHA/OUR charge handling and full IAT addenda structure are built into the SinglePoint workflow. For regulatory detail, review OCC BSA guidance.

SinglePoint Login Contact Cross-Border Desk

SinglePoint international payment screen with SWIFT BIC, IBAN, correspondent bank chain and sanctions screening panel

SWIFT Correspondent Network

U.S. Bank uses BIC USBKUS44IMT to move MT103 customer credit transfers and MT202 cover payments across a correspondent network reaching 180+ countries. SinglePoint constructs the correspondent chain automatically, supports BEN/SHA/OUR charge codes and issues a SWIFT gpi UETR for end-to-end tracking.

International ACH Transactions (IAT)

IAT is the NACHA SEC code for cross-border ACH with seven mandatory addenda records carrying OFAC-required originator, beneficiary, FX and correspondent detail. SinglePoint auto-populates the IAT structure from the beneficiary library for cross-border ACH to Canada and Mexico with 2 to 4 banking day settlement.

Region	Settlement Days	Currencies	Network	SinglePoint Workflow	Charge Code
Canada	1-2 days	USD, CAD	IAT via FedGlobal	Cross-border ACH with IAT addenda	SHA / OUR
Mexico	1 day	USD, MXN	FedGlobal Directo a Mexico	IAT with MXN conversion at Banxico FIX	OUR
Eurozone	1-2 days	EUR, USD	SWIFT MT103 / SEPA via correspondent	IBAN validation + OFAC screen	BEN / SHA / OUR
United Kingdom	1 day	GBP, USD, EUR	SWIFT MT103	Sort code + account or IBAN	BEN / SHA / OUR
Asia Pacific	1-2 days	JPY, CNY, AUD, SGD, HKD	SWIFT MT103 / CNAPS for CNY	Correspondent chain + regulatory memo	BEN / SHA / OUR
Latin America (ex-MX)	2-3 days	USD, BRL, CLP, COP, ARS	SWIFT MT103 correspondent	Tax ID + purpose code capture	SHA / OUR

IBAN and SWIFT BIC Validation

SinglePoint validates every IBAN on entry using the ISO 13616 checksum and country-specific length rules. SWIFT BIC entries are matched against the SWIFTRef directory for routing viability. Invalid IBANs are blocked before wire release so repairs cannot happen at the correspondent and accrue NOS fees.

The beneficiary library stores validated IBANs and SWIFT BICs with country code, bank identifier and account number. Re-use across wires, IAT and FedGlobal Directo a Mexico is automatic inside SinglePoint.

SinglePoint IBAN validation panel showing ISO 13616 checksum pass and SWIFT BIC directory lookup

SinglePoint sanctions screening hit panel with OFAC SDN, EU consolidated and UN Security Council list matches queued for compliance review

OFAC, EU and UN Sanctions Screening

Every SinglePoint cross-border payment is screened against the OFAC Specially Designated Nationals list, the OFAC Consolidated Sanctions list, the EU consolidated sanctions list, the UN Security Council sanctions list and U.S. Bank internal watchlists before release. Potential matches pause the payment and route to the U.S. Bank BSA/AML Compliance desk.

Hits are resolved with manual research inside the SinglePoint compliance workflow. Cleared payments release normally; confirmed matches are rejected, reported on SAR/CTR filings and retained for the 7-year audit window.

Compliance Notes

Every cross-border payment through SinglePoint is screened against OFAC SDN, Consolidated Sanctions, EU and UN lists.
IAT entries carry seven mandatory addenda records per NACHA to support OFAC screening at every correspondent hop.
CTR filings above USD 10,000 aggregate across SinglePoint international payments per FinCEN 31 CFR 1020.
Beneficial ownership captured under FinCEN CDD final rule for all new SinglePoint commercial relationships.
Cross-Border Electronic Reporting System (CBERS) feeds originate inside SinglePoint for $10,000+ cross-border flows.

BEN / SHA / OUR Charges

SinglePoint supports all three SWIFT charge codes. OUR is the default for commercial wires so the beneficiary receives full value. SHA splits charges. BEN deducts all charges from the beneficiary amount.

FX Rate Lock

Lock an FX rate at the point of SinglePoint wire entry across 140+ currency pairs. The locked rate binds correspondent settlement so beneficiary receives the contracted amount.

FedGlobal Directo a Mexico

SinglePoint routes MXN payments through the FedGlobal Directo a Mexico service with Banxico FIX conversion, 1-day settlement and the beneficiary's CLABE as the routing element.

Wire Transfers

SWIFT MT103 international wires share the same SinglePoint workflow as Fedwire domestic, with IBAN validation, charge codes and UETR tracking added for cross-border.

ACH Payments

Domestic ACH origination runs alongside IAT for U.S. leg settlement. SinglePoint batches can mix domestic and IAT entries when the NACHA file format is correct.

Foreign Exchange

Lock an FX rate at SinglePoint wire entry across 140+ currency pairs without ticketing a trader. Spot and forward contracts both available.

Vendor Payments

Pay international suppliers inside SinglePoint with PO matching, 3-way match and remittance detail delivered through SWIFT gpi UETR tracking.

Treasury Management

Multi-currency notional pooling and cross-border ZBA are available to SinglePoint clients with qualifying cross-border flow and entity structure.

Transaction Reporting

Filter cross-border payments by country, currency, UETR, IMAD/OMAD, charge code and compliance status inside SinglePoint.

How many countries can SinglePoint reach?

SinglePoint reaches 180+ countries through U.S. Bank's SWIFT correspondent banking network (BIC USBKUS44IMT). MT103 and MT202 instructions settle in 1 to 2 business days. IAT settles in 2 to 4 banking days and FedGlobal Directo a Mexico posts in 1 banking day.

What is an IAT entry in SinglePoint?

IAT is the NACHA SEC code for International ACH Transactions where one leg touches a non-U.S. financial institution. Every SinglePoint IAT entry carries seven mandatory addenda records with OFAC-required originator, beneficiary, FX and correspondent detail.

What are BEN, SHA and OUR charge codes?

BEN: beneficiary pays all charges. SHA: charges shared. OUR: originator pays all charges so beneficiary receives full value. SinglePoint defaults to OUR for commercial wires so counterparties receive the contracted amount.

Does SinglePoint validate IBANs?

Yes. SinglePoint validates every IBAN on entry using the ISO 13616 checksum and country-specific format rules. Invalid IBANs are blocked before wire release. The beneficiary library stores validated IBANs with country code, bank identifier and account number.

How does SinglePoint screen cross-border payments?

Every SinglePoint cross-border payment is screened against OFAC SDN, OFAC Consolidated Sanctions, EU consolidated, UN Security Council and U.S. Bank internal watchlists. Matches route to the U.S. Bank BSA/AML Compliance desk for clearance or rejection under FinCEN rules.

SinglePoint International Payments: SWIFT, IAT and FedGlobal Cross-Border to 180+ Countries

Three Cross-Border Rails Inside SinglePoint