One Payment Business May Need Several Rails
A payment company may collect through ACH, receive a U.S. wire through Fedwire, settle internationally through SWIFT and deliver funds through a local domestic rail in the beneficiary country.
These are different networks with different operating rules, timing, settlement models and compliance requirements.
We help qualified financial institutions source infrastructure that connects the rails required by their transaction model.
Common Rails
ACH
ACH is widely used for U.S. electronic bank payments.
Typical use cases include:
- Customer collections
- Vendor payments
- Payroll
- Recurring payments
- Business-to-business transfers
Availability for debits, credits and third-party payment activity depends on the bank and program.
Fedwire
Fedwire is used for U.S. domestic wire transfers, particularly where speed, finality or transaction size makes a wire more appropriate than ACH.
SWIFT
SWIFT supports international bank messaging and cross-border payment instructions across a broad banking network.
The actual movement of funds depends on correspondent relationships and the banks participating in the transaction.
SEPA
SEPA supports euro payments within participating European markets.
Depending on the provider, SEPA Credit Transfer and other local euro payment functionality may be available.
Local Payment Rails
Many markets have domestic clearing or instant-payment systems.
For cross-border payment companies, local delivery can be materially more efficient than sending an international wire directly to every beneficiary.
Example Architecture
CUSTOMER COLLECTION
│
├── ACH
├── FEDWIRE
├── SWIFT
└── SEPA / LOCAL RAIL
│
▼
BANKING / PAYMENT INFRASTRUCTURE
│
├── Account Layer
├── Compliance Controls
├── FX
└── Routing
│
▼
OUTBOUND PAYMENT
│
├── FEDWIRE
├── SWIFT
├── ACH
├── SEPA
└── LOCAL PAYOUT
│
▼
BENEFICIARY
Choosing the Correct Rail
The correct payment rail depends on:
- Currency
- Country
- Transaction size
- Urgency
- Beneficiary type
- Payment purpose
- Cost sensitivity
- Reversibility
- Regulatory requirements
- Counterparty preference
A well-designed infrastructure stack does not force every transaction through the same route. It allows the institution to use the appropriate rail for the transaction.
Cross-Border Payouts
The international payment may not remain an international wire from start to finish.
A common model is:
- Funds are collected in the originating country.
- Treasury or settlement funds are transferred to a provider.
- FX is performed if required.
- The payout is delivered through a domestic rail in the destination country.
This can improve speed and beneficiary experience, but the structure must be reviewed from both a regulatory and compliance perspective.
What We Review
We typically require:
- Originating country
- Destination country
- Currency pair
- Payment purpose
- Monthly volume
- Average transaction size
- Maximum transaction size
- Customer type
- Beneficiary type
- Required settlement speed
- Licensing status
- Whether prefunding is acceptable
Request an Assessment
Send us the corridors and rails you need. We can then determine whether a direct bank, payment institution, correspondent, aggregator or other infrastructure model is appropriate.