AED to INR: How UAE Exchange Houses Settle India Remittances in Real Time

TL;DR

• India is the world's largest recipient of remittances, recording an all-time high inflow of US$135.4 billion in fiscal year 2025 (RBI Annual Report, FY2025) and projected to reach up to US$140 billion in calendar year 2025 (World Bank Migration and Development Brief, April 2025), making the UAE-India corridor one of the highest-volume bilateral remittance flows globally.
• Traditional SWIFT-based AED-to-INR settlement runs T+1 to T+3, with fees and FX spread embedded at multiple correspondent hops. The rate quoted at initiation is rarely the rate applied at settlement.
• Stablecoin-based settlement rails deliver [INR settlement SLA - T+0 OR T+1] AED-to-INR settlement, with the FX rate locked at initiation and on-chain provenance for AML documentation.
• Exchange houses need vIBAN infrastructure, named virtual IBANs per client, to maintain the documented fund trail required for AML compliance on India corridor flows.
• CBB Category 3 licensing is the relevant regulatory standard for stablecoin settlement counterparties used by Bahrain-regulated exchange houses.

Approximately 3.5 million Indian nationals are based in the UAE, the largest national community in the country, and a substantial share of their financial activity flows through the UAE's exchange house network. (UAE Federal Competitiveness and Statistics Centre, 2024; IOM) Exchange houses, not banks, are the primary settlement channel for worker remittances in this corridor, operating on volumes that require institutional-grade settlement infrastructure. The AED-to-INR corridor runs at high frequency and tight margin: treasury and operations teams need settlement speed, FX rate certainty at initiation, and an AML-compliant fund trail that satisfies both CBB and Indian regulatory requirements. Legacy SWIFT infrastructure delivers none of these reliably.

Why the AED-to-INR corridor matters for UAE exchange houses

India has been the world's largest remittance destination for over a decade. Total inbound remittances reached an all-time high of US$135.4 billion in fiscal year 2025, with the World Bank projecting inflows to reach up to US$140 billion in calendar year 2025. (RBI Annual Report, FY2025; World Bank Migration and Development Brief, April 2025) The UAE consistently ranks among the top three source countries for India-bound remittances, alongside the United States and Saudi Arabia. (World Bank RPW; RBI Annual Report on remittances)

The corridor is structurally significant for UAE exchange houses for three reasons. First, the Indian diaspora represents the largest single national community in the UAE - a stable, high-frequency transfer base that anchors corridor volume. Second, India's inbound remittance market is diversifying: neobanks and digital payment platforms are targeting the consumer remittance layer with competitive FX rates and mobile-first interfaces. Exchange houses that cannot match settlement speed and rate transparency face margin compression from both ends. Third, the corridor is operationally demanding, Indian public holidays, Reserve Bank of India (RBI) compliance requirements, and India's extensive domestic banking network create complexity that bilateral banking infrastructure must navigate.

For B2B supplier payments to India - a distinct use case from consumer remittances - see the separate guide: Same-Day Supplier Payments from GCC to India.

How does AED-to-INR settlement work through SWIFT today?

SWIFT-based AED-to-INR settlement follows a multi-hop correspondent chain. Each hop adds processing time, a fee layer, and an FX spread that is not disclosed until settlement occurs. The sequence:

1. Exchange house customer initiates. The exchange house customer deposits AED or submits a transfer instruction at the counter or through a digital channel.
2. Exchange house sends to UAE correspondent bank. The exchange house routes the AED funds to its designated UAE correspondent bank. The correspondent relationship must be maintained with pre-funded nostro balances to avoid delays.
3. Correspondent sends SWIFT MT103 to Indian correspondent. The UAE correspondent transmits a SWIFT MT103 message to its Indian correspondent bank, typically one of the large Indian private banks or a State Bank correspondent.
4. Indian correspondent routes to recipient's local bank. The Indian correspondent processes the SWIFT message and routes INR to the recipient's bank - SBI, HDFC, ICICI, or a regional cooperative bank. This step can involve additional sub-correspondent routing for non-metropolitan recipients.
5. INR credit lands in recipient account. The recipient sees the INR credit. The amount reflects the FX rate applied at the Indian correspondent stage, which was not confirmed to the exchange house or sender at initiation.

Timeline: Under normal conditions, T+1 to T+3 business days. During Indian public holidays, Diwali, Republic Day, year-end banking closures, or during peak transfer periods, timelines can extend to T+3 to T+5 and beyond.

Cost structure: Each correspondent hop adds a processing fee. FX spread is applied at the point of conversion, typically at the Indian correspondent, and the margin between the rate quoted at initiation and the rate applied at settlement can be material on high-volume days. Exchange houses absorb this spread risk when they quote a fixed rate to customers.

Operating constraint: SWIFT processes during banking hours on business days only. There is no 24/7 settlement capability. Exchange house operations that run evening or weekend shifts cannot initiate SWIFT flows outside banking windows.

Liquidity tie-up: Pre-funding nostro accounts at each correspondent represents idle capital with zero yield, a structural inefficiency that compounds at scale.

What do UAE exchange houses need from an AED-to-INR settlement platform?

Seven requirements define a fit-for-purpose institutional settlement platform for this corridor:

1. Live AED local rails - not SWIFT-routed coverage. "AED support" on a settlement platform does not mean live local rails. The distinction matters: SWIFT-routed AED flows pass through the same correspondent chain and inherit the same delays. Local AED rail access eliminates the first-hop correspondent entirely.
2. [INR settlement SLA - T+0 OR T+1] INR credit at destination. The platform must specify a written settlement SLA, same-business-day credit or clear T+1 commitment. Vague "near-real-time" language is not an SLA. Exchange house treasury teams run liquidity positions against specific settlement windows.
3. FX rate locked at initiation. The exchange house must receive a confirmed rate before committing the transaction, not a reference rate that adjusts to market at settlement. Rate certainty at initiation is the operational baseline for a business quoting AED-to-INR rates to customers.
4. Named vIBAN per client. A virtual IBAN assigned per exchange house client creates the documented fund trail required by AML frameworks. Pooled receiving accounts, where multiple clients' funds arrive into a single account, create reconciliation gaps and AML documentation risks. Named vIBANs confirm sender identity at the point of AED receipt, before conversion and cross-border transfer.
5. CBB-compliant counterparty. Bahrain-regulated exchange houses require settlement counterparties that operate within the CBB's regulatory framework. This is not a commercial preference, it is a compliance requirement. Confirm permissible counterparty classifications with your CBB compliance liaison before onboarding.
6. Institutional KYB/AML onboarding. Exchange houses cannot onboard through retail KYC flows. The onboarding process must support business-level KYB, institutional AML documentation, and compliance liaison access. Consumer-oriented onboarding is structurally incompatible with exchange house compliance requirements.
7. Exchange houses as primary ICP - not a vertical among many. Product development, corridor SLA commitments, and compliance support must reflect exchange house operational requirements. A platform that serves exchange houses as one segment among consumer senders, SMEs, and corporates will not prioritise the infrastructure depth or compliance support that institutional AED-to-INR operations require.

How does stablecoin-based settlement work for the AED-to-INR corridor?

Stablecoin rails remove the correspondent chain from the AED side and replace it with a direct local rail receipt, an on-chain transfer, and an India-side banking partner for INR delivery. The sequence:

1. Exchange house initiates AED payment. The exchange house sends AED to the settlement provider's local UAE banking relationship, via UAE local rails, not SWIFT.
2. Settlement provider receives AED via local UAE banking rails. No UAE correspondent hop. The AED lands at the provider's local account without passing through the SWIFT correspondent network.
3. AED converted to USDT or USDC at rate confirmed at initiation. The FX rate is locked and disclosed to the exchange house before the transaction is committed. No post-settlement rate adjustment.
4. Stablecoin transferred on-chain to the provider's India-side settlement partner. On-chain transfer provides full end-to-end provenance, every step in the fund flow is recorded on the blockchain ledger and available for AML documentation.
5. India-side partner converts to INR and routes to recipient's local bank account. The India-side partner handles INR delivery via India's domestic banking infrastructure. The recipient receives a standard INR credit, the stablecoin does not touch the Indian banking system directly.
6. INR credit lands - [INR settlement SLA - T+0 OR T+1]. Settlement completes within the confirmed SLA window. The operation runs 24/7, Indian public holidays do not create processing delays on the stablecoin transfer leg.

Rate transparency: Rate is locked at Step 3, confirmed to the exchange house before commitment. The exchange house can quote customers with certainty.

AML documentation: On-chain provenance provides a complete fund trail from AED receipt to INR credit. The named vIBAN at Step 2 confirms sender identity at the point of AED receipt.

Operating hours: Not constrained by banking hours. AED-to-INR flows can be initiated and settled through weekends and Indian public holidays.

How ARP Digital settles AED-to-INR for exchange houses

ARP Digital provides* cross-border corridor settlement via live local AED rails for exchange house and PSP counterparties. FLOW Send is ARP's corridor settlement product - the infrastructure that removes the SWIFT correspondent hop from the AED side and delivers INR at [INR SETTLEMENT SLA — T+0 OR T+1] via ARP's India-side banking partner.

Settlement infrastructure: FLOW Send* receives AED via ARP's local banking relationships, converts at a rate confirmed at initiation, and routes on-chain to the India-side partner for INR delivery. Each exchange house client is assigned a named vIBAN, creating a documented fund trail from AED receipt to INR credit.

Institutional onboarding: Onboarding follows a business KYB and AML framework designed for exchange houses and PSPs. Compliance liaison access is available throughout the onboarding process.

Explore ARP Digital's exchange house settlement infrastructure →

Speak with our settlement team →

(*) Payment Services are provided in partnership with Veripay Investments Corp., having its registered office at 234 – 5780 Victoria Drive, Vancouver, British Columbia, V5P 3W7, Canada, a Money Services Business licensed and regulated by the Financial Transactions and Reports Analysis Centre of Canada (FINTRAC) under MSB Registration No. C100001146, and operating under applicable Canadian anti-money laundering and financial services legislation.

Frequently Asked Questions

How long does AED-to-INR settlement take through SWIFT?

T+1 to T+3 business days under normal conditions. During Indian public holidays or high-volume periods, Diwali, Republic Day, year-end banking closures, timelines can extend to T+5 or beyond. Each correspondent hop in the chain adds processing time: UAE correspondent, SWIFT network, Indian correspondent, and recipient's local bank each represent a potential delay point.

What is vIBAN and why do exchange houses need it for the AED-to-INR corridor?

A virtual IBAN (vIBAN) is a named virtual account number issued per client or per payment flow. For exchange house compliance teams, named vIBANs create the documented fund trail required by AML frameworks, the named account confirms the identity of the funds source at the point of AED receipt, before stablecoin conversion and cross-border transfer. Pooled accounts do not provide the same per-client documentation.

What is the difference between T+0 and real-time settlement for exchange house corridor flows?

T+0 means same-business-day settlement, INR credit lands on the same calendar day the AED payment is initiated. Real-time means instant or near-instant credit regardless of time of day. For exchange house treasury planning, T+0 is the operational baseline: it enables same-day liquidity management and reduces working capital tied up in in-flight transactions. Confirm the exact SLA with the settlement platform before relying on it for treasury forecasting.

Does India restrict incoming remittances settled via stablecoin?

Remittances to Indian bank accounts must arrive as INR, stablecoin is converted to INR before the final credit. The recipient receives a standard INR bank transfer; the stablecoin settlement mechanism does not touch the Indian banking system directly. The stablecoin operates as the cross-border transfer layer between the UAE-side origination and the India-side INR delivery partner. Exchange houses should confirm current RBI guidelines with their legal counsel before go-live.