> ## Documentation Index
> Fetch the complete documentation index at: https://public-openfx.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# AED payout integration guide
> Pay a UAE bank account in AED: register the IBAN, then meet the purpose, funding, memo, and limit rules.
Pay a UAE bank account in UAE dirhams (AED).
For the general flow, see [Payout lifecycle](/v3/payouts). The quote, confirm, and webhook steps are the same as for EUR, and so is the fee model. [Supported payout currencies](/v3/payouts#supported-payout-currencies) compares every payout currency side by side.
## Before you start
* Your organization must be enabled for AED. Until it is, a request in it fails with `403` PAYOUT\_CURRENCY\_NOT\_ENABLED.
* The recipient's account needs the UAE-dirham receiving capability, ACTIVE before you pay. [Capabilities](/v3/capabilities#the-capability-catalog) lists the id, and [Be paid in UAE dirhams](/v3/capabilities#be-paid-in-uae-dirhams) lists the identity the recipient owes.
* AED has no sending capability. Don't send a `sender` on a quote or payout, or it fails with `422` SENDER\_NOT\_SUPPORTED.
* Every `POST` needs an `Idempotency-Key` header. See [Idempotency](/v3/idempotency#payments-endpoints).
## Register the bank account and create the payout
A UAE bank account is identified by its IBAN and paid over AE\_LOCAL. The recipient owes a name and an address with `line1` and `country`, in any country, and no identity document. See [Be paid in UAE dirhams](/v3/capabilities#be-paid-in-uae-dirhams).
Register the account with `routingFamily` AE\_LOCAL and the UAE IBAN as `accountNumber`. The IBAN carries the bank, so you send no BIC, bank code, or account type. No name check runs, so `verifications[]` stays empty. The `accountHolderName` can be at most 75 bytes. [Be paid in UAE dirhams](/v3/capabilities#be-paid-in-uae-dirhams) lists the characters it can use.
```bash cURL theme={"theme":{"light":"poimandres","dark":"poimandres"}}
curl -X POST https://api.openfx.com/v3/payments/payout-addresses \
-H "Authorization: Bearer $OPENFX_JWT" \
-H "X-Request-Signature: $OPENFX_SIGNATURE" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"payoutAddressType": "BANK_ACCOUNT",
"accountId": "acc_BMY3UenpGBn8ZQ8hio4BgE",
"bankAccount": { "routingFamily": "AE_LOCAL", "accountNumber": "AE070331234567890123456" }
}'
```
Three rules apply only to AED:
* **Every payout needs a `purpose`.** Send one of GOODS\_AND\_SERVICES, INVESTMENTS, PAYROLL, or TREASURY\_MANAGEMENT. OTHER is refused. A missing or refused value fails with `400` PURPOSE\_INVALID. A quote carries no `purpose`, so send it when you create the payout.
* **You fund it from a stablecoin or AED balance.** The financial account must hold USDC, USDT, EURC, or AED. Any other send currency fails with `422` QUOTE\_SEND\_CURRENCY\_UNAVAILABLE.
* **Per-payout limits apply.** A `receiveAmount` outside them is refused when the payout is priced, with `422` AMOUNT\_OUT\_OF\_RANGE. `error.details` carries the exact bound.
```bash cURL theme={"theme":{"light":"poimandres","dark":"poimandres"}}
curl -X POST https://api.openfx.com/v3/payments/payouts \
-H "Authorization: Bearer $OPENFX_JWT" \
-H "X-Request-Signature: $OPENFX_SIGNATURE" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"type": "INLINE",
"financialAccountId": "finacc_AmKC5dMVXUbiAW8VzKBfqz",
"receiver": { "payoutAddressId": "pytadd_PbDQ126YUAbkNrNX6XbGL" },
"receiveAmount": "5000.00",
"receiveCurrency": "AED",
"purpose": "GOODS_AND_SERVICES",
"receiverMemo": "Invoice 4012"
}'
```
The payout starts in REQUIRES\_CONFIRMATION. [Confirm it](/v3/payouts#send-the-payout) as you would any payout.
## Memos
On AE\_LOCAL, a `receiverMemo` is at most 100 letters, digits, and spaces. A memo that is too long or holds any other character fails with `400` RECEIVER\_MEMO\_INVALID. OpenFX never truncates it.
## Track settlement
On an AE\_LOCAL payout, `settlementTraceId.status` reads UNSUPPORTED. [Trace a payout with the receiving bank](/v3/payouts#trace-a-payout-with-the-receiving-bank) lists the key for every rail.
## Common mistakes
* **Naming a `sender`.** AED has no sending capability. Remove `sender` from the quote and the payout.
* **Leaving out `purpose`, or sending OTHER.** Both fail with `400` PURPOSE\_INVALID. Pick the closest of the other four values.
* **Funding the payout from another currency.** Fund it from USDC, USDT, EURC, or AED.
## What's next
The general payout flow.
The receiving capability and identity each currency needs.
Paying euro accounts over SEPA or SWIFT.
Paying Mexican bank accounts over SPEI.
Paying Colombian bank accounts and Bre-B keys.
Every payout and address event.