fragmented rails
Inside a country, money is easy: a bank app, a wallet, a card. Across a border it becomes a chain of correspondent banks, nostro accounts, and settlement windows. Each hop adds delay, cost, and a place for the quote to change.
RampPay opens the global money layer
Read the manifestoRampPay ........................ A network for money that has to travel
The money layer for a world that already lives across borders.
the problem
Cross-border money still behaves like 1970s banking.
a missing product
RampPay is that missing product: one layer that takes local money in, moves value on a global settlement network, and pays local money out. People and businesses see a balance and a destination — not crypto, not SWIFT, not a stack of forms.
local in
Collect in the currency people already hold.
global settle
Move value once, on a network that does not close at 5pm.
local out
Pay into the account or wallet the recipient actually uses.
the map
Money already works — until it has to leave the country.
Cash, cards, wallets, and bank rails are mature inside a market. Across a border they become a chain of correspondent banks, FX desks, and settlement windows. RampPay sits in the middle as one layer: collect locally, move value globally, pay out locally.
Monday, Sep 28, 2026
16:38:52
Settlement grid
always on
Liquidity, FX, compliance, and last-mile payout — composed as one product, not a pile of intermediaries.
local in
<where money starts>
<local rails>
local out
<where money lands>
<what people actually need>
the network
Every line is a market where local money meets a global rail.
RampPay collects in the currency a market already uses, settles the value once on always-on rails, then pays out in the currency the recipient already uses. Drag the globe to read the corridors in that model: remittance, payroll, trade, and treasury routes across every inhabited region.
- local money markets
- corridor route
- value in flight
Illustrative view of launch corridors, not live settlement volume.
- Lagos, Nigeria to New York, United States — remittance, settled on wire · ACH.
- Accra, Ghana to Toronto, Canada — remittance, settled on wire · ACH.
- Bogotá, Colombia to Miami, United States — remittance, settled on ACH.
- Mexico City, Mexico to Los Angeles, United States — remittance, settled on ACH.
- Mexico City, Mexico to Toronto, Canada — trade, settled on wire.
- Lima, Peru to Madrid, Spain — remittance, settled on SEPA.
- São Paulo, Brazil to Lisbon, Portugal — remittance, settled on SEPA.
- Buenos Aires, Argentina to Madrid, Spain — remittance, settled on SEPA.
- Santiago, Chile to Buenos Aires, Argentina — trade, settled on local rail.
- New York, United States to San Francisco, United States — treasury, settled on ACH.
- Toronto, Canada to New York, United States — treasury, settled on ACH.
- New York, United States to London, United Kingdom — treasury, settled on wire · SEPA.
- Dublin, Ireland to New York, United States — treasury, settled on SEPA · wire.
- Zurich, Switzerland to Frankfurt, Germany — treasury, settled on SEPA.
- Frankfurt, Germany to Warsaw, Poland — payroll, settled on SEPA.
- Warsaw, Poland to Kyiv, Ukraine — payroll, settled on SEPA.
- Amsterdam, Netherlands to Paris, France — payroll, settled on SEPA.
- Amsterdam, Netherlands to Nairobi, Kenya — trade, settled on SEPA.
- Casablanca, Morocco to Madrid, Spain — remittance, settled on SEPA.
- Casablanca, Morocco to London, United Kingdom — remittance, settled on wire.
- Istanbul, Türkiye to Dubai, United Arab Emirates — trade, settled on local rail.
- Cairo, Egypt to Istanbul, Türkiye — remittance, settled on local rail.
- Cairo, Egypt to Riyadh, Saudi Arabia — trade, settled on local rail.
- Johannesburg, South Africa to London, United Kingdom — trade, settled on wire.
- Lagos, Nigeria to Johannesburg, South Africa — trade, settled on local rail.
- Nairobi, Kenya to Dubai, United Arab Emirates — trade, settled on local rail.
- Mumbai, India to Dubai, United Arab Emirates — trade, settled on UPI · local rail.
- Mumbai, India to Nairobi, Kenya — trade, settled on UPI · local rail.
- Delhi, India to Riyadh, Saudi Arabia — remittance, settled on UPI · local rail.
- Karachi, Pakistan to London, United Kingdom — remittance, settled on wire.
- Dhaka, Bangladesh to Riyadh, Saudi Arabia — remittance, settled on local rail.
- Bangkok, Thailand to Singapore, Singapore — trade, settled on local rail.
- Jakarta, Indonesia to Singapore, Singapore — trade, settled on local rail.
- Manila, Philippines to Dubai, United Arab Emirates — payroll, settled on local rail.
- Hong Kong, Hong Kong SAR to Singapore, Singapore — treasury, settled on local rail.
- Shanghai, China to Los Angeles, United States — trade, settled on wire.
- Seoul, South Korea to Tokyo, Japan — trade, settled on local rail.
- Tokyo, Japan to San Francisco, United States — trade, settled on wire.
- Tokyo, Japan to Sydney, Australia — trade, settled on wire.
- Singapore, Singapore to Sydney, Australia — trade, settled on local rail.
- Singapore, Singapore to Dubai, United Arab Emirates — treasury, settled on local rail.
- Perth, Australia to Singapore, Singapore — trade, settled on local rail.
- Sydney, Australia to Auckland, New Zealand — trade, settled on local rail.
- Tel Aviv, Israel to New York, United States — trade, settled on wire.
the gap
Slow and expensive is still the default.
Cross-border money still prices in waiting. Correspondent chains add days. Remittance corridors take a percentage. Cards hide the rest in FX. RampPay is built so time and cost are visible, and both stay small.
RampPay
minutes
$0.50
quoted before send
Bank wire
2–5 days
$32+
plus opaque FX
Remittance
1–3 days
5.2% avg
World Bank avg corridor
Intl cards
auth now
2–4% + FX
settle later, spread hidden
Fee visible at quote
Settled in minutes
Local currency in and out
Fee discovered after
Settled in business days
Nostro / vostro hops
how it holds together
Three jobs. One layer.
Collect
Money enters from the systems people already trust — bank transfer, wallet, or card — in local currency. No new mental model to start a transfer.
Settle
Value moves on always-on rails with a quoted rate and a quoted fee. Compliance, liquidity, and FX sit in the product, not as a scavenger hunt after you send.
Pay out
The other side receives in their local rail — payroll, family, supplier, or merchant account. The infrastructure stays underneath.
RAMPAY.Cost
minutes
Typical time to arrival — not business days.
1 layer
Instead of a chain of correspondent banks.
the crossing
Money leaves home and arrives where it is needed.
who it is for
Anyone whose money has to cross a border.
People
Send support home, pay for travel, or split costs with someone who does not share your banking system.
Operators
Pay freelancers, suppliers, and remote teams without opening a new entity in every country.
Platforms
Add global payouts and collection to a product without rebuilding correspondent banking from scratch.
both sides of a payment
A person pays. A person is paid.
RampPay sits between them. Money goes in through the account, wallet, or card someone already uses, moves once on an always-on network, and arrives in the rail the other person already trusts. No new wallet. No chain of banks in the middle.
Get Early Access
Questions? Answered.
RampPay is a money layer for cross-border value. It collects in local currency, settles on a global network, and pays out in the recipient’s local rail. The settlement machinery stays underneath the product.
Domestic payments already work. Crossing a border still means correspondent banks, opaque FX, and days of waiting. RampPay replaces that chain with one layer so time and cost are quoted up front.
A wire is a message that hops through nostro accounts. A remittance brand is often a fee stack on top of the same hops. RampPay is built as a single product for collection, settlement, and payout — not a new front on the old path.
No. People and businesses interact in local currency. Any on-chain settlement is infrastructure, not a user-facing wallet, seed phrase, or token to manage.
Typical corridors complete in minutes, not business days. Exact timing depends on the local payout rail at the destination.
The quote includes the rate and the fee before send. No surprise deduction after the money is already in flight.
Anyone whose money has to travel: families, operators paying global teams or suppliers, and platforms that need collection and payout without rebuilding correspondent banking.
RampPay works with licensed banking and payout partners, and builds KYC, screening, and auditability into the layer rather than bolting them on later.
Join the waitlist. We are opening corridors in batches and want to hear the route you actually need.