AED virtual IBANs for platform flows
Run AED collections and payouts through named accounts. Clear via IPP, FTS, and SWIFT from one integration.

What you run in AED
AED collections
Receive AED into named accounts for each merchant, client, or user.

AED payouts
Send AED payouts with traceability and clean status updates.

Account-level segregation
Separate client money from operating funds with clear controls.

Ledger-ready reconciliation
Match every movement to the right account and reference.

Rails supported
IPP
For instant UAE AED transfers
FTS
For high-value UAE AED transfers
SWIFT
For cross-border AED routing
How it fits into your account structure
Operational accounts
Run treasury and prefunding for each program.

Client master accounts
Hold safeguarded client money with clear oversight.

Named customer accounts
Attribute funds to each end customer and keep balances segregated.

Escrow structures
Support conditional settlement for defined platform flows.

Integration and controls

Single API surface
Issue accounts, move funds, and pull reporting through one integration.
Sandbox and rollout
Test end-to-end flows before go-live, then launch in phases.
Permissions and audit trails
Control access by role and keep a full record for finance and ops.
Enter new markets with speed and certainty

FAQs
Yes. AED accounts support UAE routing formats and account-level attribution.
Yes. Issue named AED IBANs at scale, aligned to your program structure.
Yes. IPP and FTS support UAE domestic AED clearing, with SWIFT for cross-border routing.
Use account-level attribution plus references and webhook updates.
Yes. Add currencies as your program expands.




