Cross-Border Payments: How They Work, Costs, Timelines, and Tracking
TL;DR - Summary
- What is a cross-border payment? - Any transaction where the sender and receiver are in different countries. The money moves through international networks like SWIFT and correspondent banks before your Indian AD bank converts it and credits your account.
- What are the common methods? - Bank wires over SWIFT, card or checkout payments, local collection accounts (virtual accounts), and marketplace payouts. Each differs in speed, cost, trackability, and compliance effort.
- Why do you receive less than invoiced? - Intermediary banks deduct fees as the payment passes through, and banks convert at a marked-up rate instead of the mid-market rate. Asking buyers to send under the OUR fee instruction protects your margins.
- How long does it take? - SWIFT wires commonly take up to five business days. Delays come from compliance checks, incorrect beneficiary details, long intermediary chains, and weekend or holiday cut-offs.
- What compliance applies in India? - A clean documentation trail: invoice, contract or SOW, remitter details, and a FIRA, FIRC, or eFIRC per payment. Goods exporters also need shipping documents and an eBRC where applicable.
What are cross-border payments?
A cross-border payment is any transaction where the sender and receiver are in different countries.
So your client is the sender, and you’re the receiver, but before the money hits your Indian bank account, it may move through international payment networks (often SWIFT + correspondent banks), and then get processed by your Indian AD bank.
A good cross-border payments setup prioritises:
- Cash flow: faster settlement and fewer “idle days”
- Compliance: clean documentation trail (invoice/SOW, purpose, FIRA/FIRC as applicable)
- Predictability: clarity on fees, FX rate, and where the payment is
How does cross-border payments work?
Cross-border payments work by moving money from your client's bank in one country to your bank in another through a network of authorised banks, with the funds converted into your local currency before they are credited. The payment is initiated by the sender, may pass through one or more intermediary banks if there is no direct relationship between the two banks, and is finally credited to your account by your Indian AD bank after compliance checks.
Here is how each step works.
Step 1: Sender initiates the payment
Your client instructs their bank to send money using your beneficiary details (name, account number/IBAN where relevant, and SWIFT/BIC for wires). For a SWIFT wire, the transfer is typically communicated using SWIFT customer credit transfer messaging like mt103 (or ISO 20022 equivalents).
Step 2: Intermediary/correspondent banks may get involved
If the sender’s bank doesn’t have a direct relationship with your bank, the payment may hop through one or more correspondent banks. Each intermediary may apply its own fees and processing timelines.
Step 3: Indian AD bank credits you after checks
Once the funds reach India, your bank may run compliance checks (KYC/AML/sanctions screening + purpose/payment context). If all is clean, funds are converted (if needed) and credited to your account
What are the common cross-border payment methods?
There are four common cross-border payment methods: bank wires over SWIFT, card or checkout payments, local collection accounts (also called virtual accounts), and marketplace payouts. Each differs in speed, cost, trackability, and how much compliance work it leaves you with. Here is how they compare.
1) Bank Wire (SWIFT)
Reliable for larger b2b payments — but often:
- slower
- harder to track as a receiver
- prone to unpredictable deductions
2) Card / Checkout
Great for SaaS/e-commerce and online checkout flows, but fees can be higher (gateway + cross-border + chargeback exposure + FX spread).
3) Local Collection Accounts (Virtual Accounts)
You get local bank details abroad (like US ACH rails). Often faster and more predictable than SWIFT, depending on provider/currency/country.
4) Marketplace Payouts
Amazon/other platforms pay out on their own cycles; reconciliation and export documentation become the bigger pain.
What are cross-border payments used for?
Cross-border payments power much of how money moves around the world, connecting people and businesses across different countries for everyday and large-scale needs alike. Some of the most common use cases include:
Global trade: Companies that buy or sell across borders rely on these payments to settle invoices with overseas suppliers and collect money from international customers.
Sending money home: Many people working abroad use cross-border payments to support family and friends back home, a lifeline for households and local economies in many developing nations.
Overseas investments: Investors use them to buy foreign assets such as shares, bonds, or property, and to bring back the returns those investments generate.
Travel spending: When people travel internationally, these payments let them book flights, settle hotel bills, and pay for tours and experiences in another currency.
Giving across borders: Individuals and organisations use cross-border payments to fund charities and nonprofits operating in other countries, backing causes worldwide.
What are the fees in cross-border payments?
Where costs typically show up
- FX rate (spread/markup) Banks often don’t convert at the mid-market rate you see on Google — they apply a spread. The exact % varies by bank, corridor, and amount.
- Sender bank fee The sender’s bank usually charges an outgoing wire fee (varies widely by bank/type of account).
- Intermediary bank deductions On SWIFT wires, correspondent banks can deduct fees en route — which is why you sometimes receive a “short payment”.
- Receiving/handling + compliance friction Your receiving bank may charge inward remittance/handling fees, and documentation follow-ups can add operational cost.
Fee instruction matters: OUR vs SHA vs BEN
On SWIFT wires, the sender can choose who bears charges:
- OUR: sender pays all fees (recipient should get full amount)
- SHA: fees shared (recipient may receive less)
- BEN: recipient pays all fees (fees deducted from amount sent)
This is a big lever for exporters: if you’re receiving wires, push large buyers toward OUR to protect your margins.
How long do cross-border payments take?
There isn’t one universal timeline — it depends on rail, corridor, cut-off times, intermediary chain, and compliance checks.
Typical timelines by method (practical view)
- SWIFT wire: commonly up to ~5 business days; can be faster on some routes, or slower if held for checks.
- Cards: settlement depends on gateway + acquiring setup; can be 1–5 business days.
- Local rails/virtual accounts: often faster than SWIFT in many corridors, but still depends on provider/currency/banking cut-offs.
- Marketplace payouts: depends on platform payout cycles and withdrawal method.
Why “2 days” becomes “7 days”
- Compliance checks/manual review (KYC/AML/sanctions)
- Incorrect beneficiary details (name mismatch, wrong account/SWIFT)
- Long intermediary chain
- Weekend/holiday cut-offs
- Missing context (invoice/SOW/purpose clarification requested)
What are cross-border payment challenges and how to fix them?
Receiving cross-border payments is difficult because the money passes through multiple banks that each deduct fees, gets converted at marked-up exchange rates, and carries compliance paperwork like purpose codes and FIRCs that must be completed for every transaction. For an Indian exporter collecting from overseas clients, the friction usually shows up in a few predictable places:
Money gets lost in transit: A payment from your US or EU client rarely travels in a straight line. It often passes through one or more intermediary banks, and each can take a cut along the way. The result is that a $5,000 invoice can land as significantly less, with little clarity on where the deductions happened.
Forex markups eat into earnings: Most banks convert your dollars or euros at a rate marked up over the real mid-market rate. This spread is rarely shown as a line item, so it quietly reduces what you receive on every single payment.
Compliance paperwork piles up: Every inward payment needs the correct purpose code, FEMA-compliant documentation, and a FIRC or FIRA for your GST refunds and tax filing. Banks often issue these only after repeated follow-ups, which holds up your compliance.
Tracking is hard: Once your client hits send, visibility drops. You often cannot tell whether the payment is sitting at an intermediary bank or clearing compliance checks at your Indian bank, which makes reconciling receivables a guessing game.
Time zones slow things down: When your client's bank operates 10 or more hours behind India, a query raised on their end can mean waiting a full day for a response, stretching out an already slow settlement.
How to Track Cross-Border Payments
Tracking a cross-border payment relies on SWIFT's tracking layer called SWIFT gpi. For gpi-enabled flows, every payment carries a UETR (Unique End-to-End Transaction Reference), which works like a parcel tracking number that follows the payment from sender to receiver.
There is one important catch. Even when gpi exists, you as the receiver usually cannot see the tracking yourself unless your bank provides a tracker or portal, or your bank shares updates when you give them the UETR or MT103 details. Some banks do offer trackers built around the UETR, so it is worth asking yours directly.
There is also SWIFT Go, designed for low-value cross-border payments in consumer and SME use cases. It supports transfers up to $10,000 equivalent, but only works if both banks involved offer it. For most exporter wires, it is not the default option.
What to ask for to trace a payment?
If you need to trace a payment, ask your client for these details first:
UETR (Unique End-to-End Transaction Reference), the sender bank name and SWIFT/BIC, the value or transfer date, the amount and currency, and the beneficiary name and account number exactly as sent.
If they cannot find the UETR, ask for a copy of the MT103 or the SWIFT payment confirmation, which often contains the UETR in gpi flows.
What are compliance requirements for cross-border payments in India?
Documents exporters typically need
- Invoice (must match amount/currency and payment narrative)
- Contract / SOW (especially for service exports)
- Remitter details (who paid, why, relationship)
- FIRA/FIRC/eFIRC (depending on bank/process and what you need it for)
- Shipping docs (goods exports: BL/AWB, shipping bill, etc.)
- eBRC (where applicable: DGFT/export benefit workflows / certain export compliance needs)
How to choose a cross-border payment provider
- What rates do you offer? Give priority to banks or platforms that openly mention mid-market rates, like Skydo and Wise. If they use terms like “best rates” or “best in the market rates,” chances are there will be a hidden markup at the time of currency conversion. Always check your FIRA to compare the rate offered to you with the exchange rate on that day.
- What’s the settlement timeline by country? Settlement speed impacts your working capital. The quicker the money settles, the easier it is to maintain liquidity
- Can I track payments end-to-end? End-to-end visibility means you always know where your money is, which a huge advantage to plan your other business activities
- What compliance docs do you provide and how fast? Non-compliance keeps payment stuck. A partner that automates paperwork as soon as funds must get brownie points.
- What’s the dispute/chargeback exposure (if cards)? Clear documentation about chargebacks keeps you safe from unwarranted risks and protects your revenue
- Support turnaround time? A slow response freezes your cash flow for days. A reliable support team, preferably based in India is essential to resolve compliance bottlenecks
Receiving cross-border payments in India with Skydo
Skydo is built for Indian exporters and freelancers who want a receiving setup that’s predictable: clear fees, clear FX, and clear payment status.
1) Real-time visibility (receiver-side)
Instead of chasing MT103s, Skydo positions dashboard tracking (initiated → in transit → credited) so the receiver can monitor progress directly.
2) Transparent fees + live FX positioning
Skydo positions flat fees (instead of % pricing) and no fx markup / live FX — so exporters can estimate net INR more reliably before the payment lands.
3) Compliance trail
Skydo positions instant FIRA availability per payment from the dashboard, reducing bank follow-ups.
4) Latest RBI PA-CB authorisation (trust layer)
Skydo received final RBI authorisation to operate as a Payment Aggregator – Cross Border (PA-CB) in January 2026.
Bottom line: The best setup isn’t just “receive money.” It’s: receive + track + stay compliant — without guessing what happened in between.
1. What is the difference between a cross-border payment and a domestic payment?
A cross-border payment is any transaction where the sender and receiver are in different countries. Unlike a domestic payment that settles within one country, it moves through international payment networks, often SWIFT and correspondent banks, gets converted into your local currency, and is then processed by your Indian AD bank after compliance checks.
2. Why did I receive less money than my client sent?
3. What does OUR, SHA, and BEN mean on a SWIFT wire?
4. Why does a payment that should take 2 days end up taking 7?
5. Can I track a cross-border payment as the receiver?
6. What documents do I need to stay compliant when receiving export payments in India?
