Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following table summarizes the various available combinations, the naming conventions used and the scope of the IP Payments:

Domestic Same Currency

Foreign Different Currency

Same Country

Domestic Payment (supported by SIP)

FX-Payment (not in scope)

Different Country

International Payment (in scope)

International-FX Payment (in scope)

...

Panel
panelIconId068fdde3-c1f6-4759-9967-8a80e7ba7356
panelIcon:rock:
panelIconText:rock:
bgColor#DEEBFF

TPPs MUST:

4.2.1 Either allow Users to manually enter the payment currency or pre-populate it for the Users, depending on the use case.

  • 4.2.1.1 Have the option to select which currencies that they want to support for their use cases. TPPs SHOULD check with the LFIs participating in the UAE Open Finance ecosystem which currencies they support in order to provide better customer experience and reduce payment initiation rejections.

4.2.2 Either allow Users to manually enter the payment amount or pre-populate it for the Users. This is dependent on the use case.

  • 4.2.2.1 Allow Users to enter the payment amount either in the currency of their selected payment account or in the currency selected for the payment order. This is dependent on the use case and whether users are allowed to enter the payment amount manually or not.

(warning) Note: The payment amount in the currency specified before any FX conversion will be the actual consented amount for the IP/FXP payment Consent. This is because the FX rate provided by the FX Quote Rate Request cannot be guaranteed that will not change before the User provides authorization of the payment Consent at the LFI.

4.2.3 Ensure that Users clearly understand the currency of the payment amount. This would be as follows:

  • foreign currency for Domestic- FX Payments, Domestic-foreign Payments, International-FX Payments and International Payments

  • local currency for International Payments in local currency

4.2.4 Ensure and validate that the payment amount MUST be specified with max 2 decimal digits, if required.

4.2.5 Ensure that the maximum allowable amount is equal to https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft2/pages/52528887/Limits+and+Constants#Max-Inter-bank-IP%2FFXP-Payment-Amountfor any payments to payee accounts managed by a different account holding entity than the User’s LFI.

  • 4.2.5.1 NOT apply any maximum amount limit for Domestic- FX or Domestic-Foreign payments to payee accounts managed by the same LFI as the User’s LFI (i.e. Intra-bank payments). TPP MUST be able to identify the account holding LFI from the payee identification details.

4.2.6 Display a message to Users informing them that the payment amount cannot exceed the https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft2/pages/52528887/Limits+and+Constants#Max-Inter-bank-IP%2FFXP-Payment-Amount value for all Inter-bank payments.

...

Panel
panelIconId5b2e39a5-8ce4-448d-936b-b645409e332b
panelIcon:bank:
panelIconText:bank:
bgColor#FFFAE6

LFIs MUST:

4.6.1 Provide a message to the User that the displayed FX rate is indicative and that the actual rate that will be used for the Future Dated IP /FXP Payment or each of their Fixed Recurring IP payments will be the spot rate on the date of each of the payment initiation, if the FX Rate was Indicative type.

4.6.2 Provide to the User the details of the forward FX rate agreement (e.g. future contract) and request User to consent to the T&Cs of the agreement, if required, before payment Consent authorization, if the FX was Forward type. LFIs MUST also display to the User the date that the Forward FX rate is valid.