Acme logoAcme docs
GuidesAPI referenceChangelog
Bank payment rules

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.

Common Definitions

  • 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 code that matches the transaction.

  • 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.

ISO 20022 migration: SCB address requirements

  • SCB is migrating to the ISO 20022 message standards. The beneficiary address requirements on this page are part of this migration. Refer to ISO 20022 at Standard Chartered for an overview.
  • Under the SCB Payment API guide, the beneficiary address.city (town name) and address.country are mandatory for all payment types. Acme validates this on every payment.

Supported sender account currencies

  • SCB UAE requires a currency prefix on the debit account number, so the sending account currency must be one Acme holds a prefix for.
  • The supported currencies are AED, USD, GBP, EUR, CHF, AUD, SGD, CAD, HKD, JPY, NOK, NZD, SEK, and ZAR.
  • A payment from an account in any other currency is rejected. Contact Acme if you need one added.

UAE_IBFT

Interbank Funds Transfer. A local AED transfer to another bank in the UAE.

  • currency must be AED.
  • Provide either a UAE IBAN in receiver.bankAccountNumber, or an account number of at most 16 digits together with a receiver.bank BIC.
  • When a UAE IBAN is provided without receiver.bank, Acme derives the beneficiary BIC from the IBAN routing code. If that routing code is not recognised the payment is rejected, and receiver.bank must be supplied explicitly.
fieldpattern / charsetmax lengthmandatory/optional
currencyAED3M
customerReferenceSWIFT16M
paymentDetailsSWIFT140O
purposeCodeUAE Purpose of Payment codeM
bankChargeBearerSENDER or RECEIVER or SHAREDO
receiver.nameFree text140M
receiver.bankSWIFT BIC8–11M for the account-number form
receiver.bankAccountNumberUAE IBAN, or at most 16 digitsM
receiver.address.citySWIFT35M
receiver.address.countryISO 3166-1 alpha-22M

UAE_FTS

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

  • currency must be AED.
  • Provide either a UAE IBAN in receiver.bankAccountNumber, or an account number of at most 16 digits together with a receiver.bank BIC.
  • When a UAE IBAN is provided without receiver.bank, Acme derives the beneficiary BIC from the IBAN routing code. If that routing code is not recognised the payment is rejected, and receiver.bank must be supplied explicitly.
fieldpattern / charsetmax lengthmandatory/optional
currencyAED3M
customerReferenceSWIFT16M
paymentDetailsSWIFT140O
purposeCodeUAE Purpose of Payment codeM
bankChargeBearerSENDER or RECEIVER or SHAREDO
receiver.nameFree text140M
receiver.bankSWIFT BIC8–11M for the account-number form
receiver.bankAccountNumberUAE IBAN, or at most 16 digitsM
receiver.address.citySWIFT35M
receiver.address.countryISO 3166-1 alpha-22M

TT

Telegraphic Transfer. A cross-border SWIFT transfer.

receiver.bank (SWIFT BIC) is required.

fieldpattern / charsetmax lengthmandatory/optional
currencyISO 4217 currency code3M
customerReferenceSWIFT16M
paymentDetailsSWIFT140O
purposeCodeUAE Purpose of Payment codeM
bankChargeBearerSENDER or RECEIVER or SHAREDO
receiver.nameFree text140M
receiver.bankSWIFT BIC8–11M
receiver.bankAccountNumberFree textM
receiver.address.citySWIFT35M
receiver.address.countryISO 3166-1 alpha-22M

BKTR

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

  • receiver.bank must not be provided. SCB routes the payment to itself.
  • bankChargeBearer is always SHARED on this payment type.
fieldpattern / charsetmax lengthmandatory/optional
currencyISO 4217 currency code3M
customerReferenceSWIFT16M
paymentDetailsSWIFT140O
purposeCodeUAE Purpose of Payment codeM
receiver.nameFree text140M
receiver.bankAccountNumberUAE IBAN, or at most 16 digitsM
receiver.address.citySWIFT35M
receiver.address.countryISO 3166-1 alpha-22M

Acme Standard Chartered Bank Hong Kong Payments (API)

Previous Page

Acme UOB Singapore Payments

Next Page

On this page

Common DefinitionsUAE_IBFTUAE_FTSTTBKTR