Why Corridor Costs Vary So Much Between GCC Markets

The same AED-to-INR payment can cost materially more or less depending on which account it lands in, what it is worth, and which rail carries it. The same is true for AED-to-PHP and for payments into Europe. Understanding which routes exist within a corridor, and what determines which one a payment takes, is the prerequisite for managing what it costs. For the full cost stack and the mix risk concept, see What a GCC Cross-Border Payment Actually Costs.

Why isn't a corridor a single price?

The pillar established that corridor cost is the weighted average of the routes payments take, and that a quoted rate is a forecast of that mix rather than a commitment. This article addresses the question beneath it: why do the routes differ at all?

The answer is not market conditions. It is that a corridor name describes a currency pair, and a currency pair is not a payment infrastructure. Between AED and INR there are two principal non-resident account types, two domestic settlement rails with different value thresholds, and more than one way to source the rate, each of which affects the path a payment takes and what it costs.

Naming the corridor does not determine the route. Four structural drivers do.

What actually determines which rail a payment takes?

Destination account type

India is the clearest case in any GCC corridor, and it is entirely explainable from public regulation.

Indian bank accounts held by non-residents come in two principal types. An NRE account - Non-Resident External - holds funds from foreign earnings. The balance is denominated in rupees but is freely repatriable: principal and interest can be transferred abroad without restriction, and interest is exempt from Indian income tax. An NRO account - Non-Resident Ordinary - holds income earned in India, such as rent, dividends or domestic salary. Repatriation from an NRO account is capped at USD 1 million per financial year and requires tax documentation from the account holder (RBI Master Direction on Non-Resident Accounts).

These are not variants of the same instrument. They sit on different regulatory tracks, with different compliance requirements at the receiving bank and different operational coverage among the payment partners serving the corridor.

For a payment provider the distinction matters immediately, because partner coverage of NRE and NRO accounts is not identical across every route, and the routing decision depends on knowing which type the recipient holds.

The difficulty is that senders frequently do not know the distinction, or supply account details at initiation that are incomplete. When a payment is submitted with details that do not match the rail attempted, it is rejected at the destination bank and retried on the alternative rail, which may use different partner coverage and different economics.

This is the normal operational consequence of a corridor where the routing decision depends on information the sender cannot always supply reliably.

Value thresholds and rail eligibility

Different rails within a corridor operate under different conditions, and the choice between them is often not voluntary. A transaction value can place a payment on one rail rather than another, with different cost implications on each.

The Philippines makes this concrete. A PHP payment of 49,000 can route via Instapay, instant, 24/7. A payment of 51,000 exceeds the Instapay ceiling and must route via Pesonet, which clears in batches on weekdays. Two payments on the same corridor, separated by PHP 2,000, take different rails with different timing.

India works the same way in reverse. IMPS carries transactions up to ₹5 lakh and settles instantly at any hour. RTGS is the high-value rail, with a regulatory minimum of ₹2 lakh rather than a maximum, payments below that threshold cannot use it at all.

Cost follows rail. Rail follows value.

Rate sourcing

Not every corridor prices the same way. Some providers source rates from the partner that will execute the payment — a live, executable rate reflecting what that partner will actually transact at. Others source from market data feeds, which give a reference price reflecting where the market is, and which may not be achievable with any specific counterparty at that moment.

The distinction is consequential. A provider pricing from partner-supplied rates is quoting what that partner will do. A provider pricing from a market reference is quoting where the market is, not the same thing as where the payment will settle. Where execution rate and reference rate diverge, the gap lands in the effective cost.

Rate freshness

Rates have a shelf life. A rate fetched from a live source is current to the moment of fetch; served a minute later without refreshing, the underlying market may have moved. On liquid, high-volume corridors brief rate age is inconsequential. On corridors where the source updates periodically, a stale rate creates a gap between the price shown at initiation and the rate at which the payment settles.

A pricing system that refreshes from live sources before quoting and before executing closes that gap. The alternative, falling back to a reference rate the system cannot actually transact at, produces quotes that do not reflect executable economics.

How does destination infrastructure change the cost?

The table below sets out the principal domestic settlement rails in three destination markets, with the operating characteristics and limits published by the relevant authorities.

Sources: Reserve Bank of India and NPCI for IMPS and RTGS characteristics; Bangko Sentral ng Pilipinas for Instapay and Pesonet; European Payments Council for SEPA schemes. Corridor availability through ARP is documented at docs.platform.arpdigital.io/fees-and-processing. Scheme limits are set by the relevant authority and individual banks may apply lower ceilings; a provider may also apply its own transaction limits, which are separate from scheme rules. Confirm current parameters before operational planning.

The practical weight of this table sits in the thresholds rather than the timings. Since December 2020 both IMPS and RTGS operate around the clock, so the old assumption that a large Indian payment must wait for banking hours no longer holds. What does still bind is value: a payment above the IMPS ceiling of ₹5 lakh has to use RTGS, and a payment below the RTGS floor of ₹2 lakh cannot. Between those two thresholds a provider has a genuine choice of rail, and whether it prices both identically is a question worth asking before committing volume.

For the mechanics of the AED-to-INR corridor specifically, see AED to INR: How UAE Exchange Houses Settle India Remittances in Real Time. For how transfer costs accumulate across a correspondent chain, see SWIFT Transfer Costs for GCC Businesses.

Why do providers reserve the right to reprice?

Most corridor agreements include a repricing provision allowing the provider to adjust pricing on notice where sourcing conditions change materially. This is standard market practice, and it is worth understanding rather than dismissing.

A provider's cost to serve a corridor reflects what its routes cost at a point in time. If a partner supplying the rate changes its own pricing, or a route becomes unavailable, the provider's input cost changes. A repricing clause allows that to be passed through with notice, which is preferable to the alternatives of absorbing it silently or routing to a worse path without disclosure.

The useful question is not whether a provider has such a clause. Most do. The useful questions are what triggers it, how much notice is given, and whether the provider will show the sourcing conditions that justified the change. A provider willing to evidence that on request is making a qualitatively different offer from one treating pricing mechanics as proprietary.

What should a business actually do about it?

Five steps, in order of impact.

Ask which rails serve your corridor, and what determines the choice between them. Any provider operating a corridor seriously can answer without hesitation.

Ask how rates are sourced, from live partner rates or from a market reference feed. If from a feed, ask what happens when the feed rate and the executable rate diverge.

Supply complete recipient account data at initiation. In the India corridor, establishing whether the account is NRE or NRO before submission prevents rejection and retry. It is the one step the sender controls that most directly affects routing.

Ask for corridor-level reporting showing the rail each payment took and the effective settling rate. Without it, corridor cost is structurally unauditable.

Understand your own payment profile. The value distribution of your payments determines which rails you use and how often. A business sending many payments below ₹5 lakh into India has a different cost profile from one sending above it, even on the same quoted rate.

FLOW Send provides cross-border settlement on AED and BHD corridors, with corridor parameters documented at docs.platform.arpdigital.io.