Acme Standard Chartered Bank UAE Payments (API)

This describes validations / allowed data formats for Acme payments going through Standard Chartered Bank (SCB) UAE (SCBLAEADXXX) over the SCB Open Banking API. These will be validated by Acme and further validated by the bank. These rules may be stricter than what the bank requires.

Supported types: UAE_IBFT, UAE_FTS, TT, BKTR.

Payment types at a glanceCopy Anchor Link

All times are UAE time (GST, UTC+4).

Processing time and value dateCopy Anchor Link

• Acme sets the payment date to the date the payment is created, in UAE time. You cannot choose a future payment date.
• Acme sends the payment to SCB when it is created.
• If the payment needs approval in Acme, Acme sends it to SCB when it is approved. It keeps the payment date from when it was created.
• SCB debits the sending account on the payment date, unless SCB moves the payment.
• For UAE_FTS, and for BKTR between different currencies, SCB moves a payment it receives after the cut-off, or on a weekend or UAE public holiday, to the next working day.
• SCB also moves a payment with a past payment date to the next possible business date. This applies to a payment approved on a later day than it was created.
• The payment date Acme shows stays the date the payment was created, even when SCB debits the account on a later day.
• For TT, the date the beneficiary is credited depends on the destination country, the beneficiary bank and the currency.
• For TT, SCB can hold a payment until it has accepted any supporting documents it asks for. The payment is debited and processed once SCB accepts them.

Payment limitsCopy Anchor Link

• SCB recommends UAE_IBFT for amounts below AED 50,000.
• SCB recommends UAE_FTS for amounts of AED 50,000 and above.
• Ask your SCB relationship manager about any limit set on your own SCB account.

Common DefinitionsCopy Anchor Link

• SWIFT Character Set:

  • The 26 uppercase Latin letters A-Z
  • The 26 lowercase Latin letters a-z
  • The 10 digits 0-9
  • Forward slash /
  • Hyphen -
  • Question mark ?
  • Colon :
  • Left and right parentheses ( )
  • Full stop .
  • Comma ,
  • Single quote '
  • Plus sign +
  • Space

• customerReference is required for all payment types. It must be unique and must not exceed 16 SWIFT characters.

• paymentDetails is sent to the beneficiary as unstructured remittance information across 2 lines of 70 characters, for a total of 140 SWIFT characters.

• purposeCode is required for all payment types. Provide the UAE Purpose of Payment (POP) code that matches the transaction. See Purpose of Payment (POP) codes.

• receiver.name is required for all payment types and must not exceed 140 characters.

• receiver.address.city and receiver.address.country are required for all payment types, as enforced by Standard Chartered Bank. The line1, line2, state, and postalCode address fields are optional.

• A SWIFT BIC is either 8 or 11 characters: 6 uppercase letters, then 2 alphanumerics, optionally followed by a 3-character branch code. Lengths of 9 or 10 are rejected.

• A UAE IBAN is AE followed by 21 digits, for a total of 23 characters.

• bankChargeBearer defaults to SHARED when omitted. On BKTR it is always SHARED, whatever value is supplied.

• amount is in the currency's smallest unit. For example, AED 12,500.00 is 1250000. See minor units format.

UAE_IBFTCopy Anchor Link

Interbank Funds Transfer. A real-time, low-value local AED transfer to another bank in the UAE.

Cut-off and processing:

• Available 24/7, including weekends and public holidays.
• Processed in real time.
• SCB recommends this type for amounts below AED 50,000.

Example payload, paying AED 12,500.00 to a UAE IBAN. Acme derives the BIC from the IBAN.

{
  "type": "UAE_IBFT",
  "senderAccountId": "intacc_XXXXXXXXXXXXX",
  "senderAccountCurrency": "AED",
  "currency": "AED",
  "amount": 1250000,
  "customerReference": "INV20261014001",
  "paymentDetails": "Invoice 20261014-001",
  "purposeCode": "GDS",
  "receiver": {
    "name": "Example Trading LLC",
    "bankAccountNumber": "AE980260001234567890123",
    "address": {
      "city": "Dubai",
      "country": "AE"
    }
  }
}

UAE_FTSCopy Anchor Link

Funds Transfer System. A same-day high-value AED RTGS transfer.

Cut-off and processing:

• The cut-off is 18:30 UAE time, Monday to Friday.
• A payment SCB receives before the cut-off is processed the same day.
• A payment SCB receives after the cut-off, or on a weekend or public holiday, is processed on the next working day (T+1).
• SCB recommends this type for amounts of AED 50,000 and above.

Example payload, paying AED 250,000.00 to an account number with its BIC.

{
  "type": "UAE_FTS",
  "senderAccountId": "intacc_XXXXXXXXXXXXX",
  "senderAccountCurrency": "AED",
  "currency": "AED",
  "amount": 25000000,
  "customerReference": "PO20261014002",
  "paymentDetails": "Purchase order 20261014-002",
  "purposeCode": "GDI",
  "bankChargeBearer": "SHARED",
  "receiver": {
    "name": "Example Supplies FZE",
    "bank": "EBILAEADXXX",
    "bankAccountNumber": "1012345678901",
    "address": {
      "line1": "Office 101, Example Tower",
      "city": "Dubai",
      "country": "AE"
    }
  }
}

TTCopy Anchor Link

Telegraphic Transfer. A cross-border SWIFT transfer.

Cut-off and processing:

• The cut-off is 20:30 UAE time, every day of the week, on the payment date.
• Each payment currency also has its own cut-off, which can be earlier.
• The beneficiary is usually credited within 1 to 3 days, depending on the currency, the destination country and the beneficiary bank.
• SCB can ask for supporting documents. The payment is processed once SCB accepts them.

Example payload, paying USD 10,000.00 from a USD account to a bank in the United States.

{
  "type": "TT",
  "senderAccountId": "intacc_XXXXXXXXXXXXX",
  "senderAccountCurrency": "USD",
  "currency": "USD",
  "amount": 1000000,
  "customerReference": "TT20261014003",
  "paymentDetails": "Services October 2026",
  "purposeCode": "ITS",
  "bankChargeBearer": "SHARED",
  "receiver": {
    "name": "Example Software Inc",
    "bank": "CHASUS33XXX",
    "bankAccountNumber": "123456789",
    "address": {
      "line1": "100 Example Street",
      "city": "New York",
      "state": "NY",
      "postalCode": "10001",
      "country": "US"
    }
  }
}

BKTRCopy Anchor Link

Book Transfer. An intra-SCB transfer between two accounts at SCB UAE (SCBLAEADXXX).

Cut-off and processing:

• A transfer in the same currency is available 24/7 and processed the same day.
• A transfer between different currencies has a cut-off of 18:00 UAE time.

Example payload, paying AED 5,000.00 to another SCB UAE account.

{
  "type": "BKTR",
  "senderAccountId": "intacc_XXXXXXXXXXXXX",
  "senderAccountCurrency": "AED",
  "currency": "AED",
  "amount": 500000,
  "customerReference": "BT20261014004",
  "paymentDetails": "Rent October 2026",
  "purposeCode": "RNT",
  "receiver": {
    "name": "Example Properties LLC",
    "bankAccountNumber": "AE360440001234567890123",
    "address": {
      "city": "Abu Dhabi",
      "country": "AE"
    }
  }
}

Purpose of Payment (POP) codesCopy Anchor Link

SCB UAE also calls these FTS codes.

• A POP code is required on every outgoing payment from the UAE, for every payment type. This is a UAE regulatory requirement.
• SCB rejects a payment without one.
• Send the code in purposeCode. It is the 3-letter code from the table below.
• Use the Originator POP code that describes why you are making the payment.
• UAE_IBFT accepts only the codes marked Y in the IBFT column.
• For UAE_FTS, TT and BKTR, use any code from the table.
• The descriptions follow SCB's list, with capitals and typos tidied.
• Acme checks only that purposeCode is present. SCB validates the code itself.

Bank referencesCopy Anchor Link

bankReference is SCB's clearing reference, clearingSystemReference. SCB usually sends it when it reports the payment as processed. bankReferences lists every id SCB sent, keyed by SCB's field name.

Other keys in bankReferences:

• From SCB's answer to the request: paymentIdentifier, internalTrackingId, clientReferenceId (your customerReference, echoed back).
• From SCB's status updates, when sent: endToEndId, clientIdentifier, instructionIdentifier, paymentContainerId, originalTransactionId, groupId.

Good to know:

• UAE_IBFT: SCB doesn't send a clearingSystemReference, so bankReference stays null. bankReferences still has the other ids.
• If SCB completes the payment immediately, bankReference can stay null until a later SCB update brings it. No webhook is sent for that update, so fetch the payment to see it.
• A rejected payment keeps the ids SCB sent before rejecting it.

A completed TT payment returns:

{
  "bankReference": "6OT2610051234567",
  "bankReferences": {
    "clearingSystemReference": "6OT2610051234567",
    "paymentIdentifier": "2610051234567890",
    "internalTrackingId": "3f2b8c1e-7d4a-4e9b-9c6f-1a2b3c4d5e6f",
    "clientReferenceId": "ET12345678-USD-0",
    "endToEndId": "E2E2610051234",
    "clientIdentifier": "CLI2610051234",
    "instructionIdentifier": "INS2610051234",
    "paymentContainerId": "PC2610051234",
    "originalTransactionId": "OT2610051234",
    "groupId": "GRP2610051234"
  }
}