Versions Compared

Key

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

...

#

Step

Rules & Guidelines

COP-1

Single Instant Payment Consent

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Single-Instant-Payment-Consent , step 1.1 except for:

  • Payee Identification details

TPPs MUST:

1.1 Enable Payee Identification using one of the following options:

  • 1.1.1 IBAN: In this case the information required for the payee is:

    • IBAN of the Payee

    • Name of the Payee (First/Last Name or Business Name)

  • 1.1.

    1 TPPs MUST identify the holding entity by decoding the IBAN and MUST NOT ask Users to provide it or select from a list.

    1.1.2 Account Number (Domestic): In this case the information required for the payee is:

    • Account Number of the Payee. This is the 12 or 14 digits domestic account number of the payee with their LFI.

    • Name of the Payee (First/Last Name or Business Name)

    • The Payee account holding entity. TPPs MUST enable Users to identify the holding entity using its trading name which is familiar to Users. The trading name MUST correspond to a valid IBAN Bank Code.

1.2 Ensure that the format and the validation rules of the Payee Identification details are correct, when Users manually enter the Payee Identification details. If incorrect, TPPs MUST request Users to review and re-enter the information.

COP-2

Discovery

TPPs MUST:

2.1 Have the ability to send a request to the OFP in order to discover the LFI entity of the Payee that will be used to confirm the payee using the COP service. The request MUST include the following information:

  • IBAN of the Payee

OFP MUST:

2.2 Resolve the request received by the TPP and respond back to the TPP with the information of how to access the COP service on the LFI entity that holds the Payee Account.

COP-3

COP Service

TPPs MUST:

3.1 Request the OFP to perform Confirmation of Payee for the Payee Identification provided by the User for the payment Consent. This may be required when:

3.2 Provide the necessary information to the OFP to perform the Confirmation of Payee service. This informaiton include:

  • Payee Identification details (as specified in 1.1 above)

OFP MUST:

3.3 Make a Customer Data Request to the Payee’s LFI, using the Proxy API endpoint and specifying the Payee Account in IBAN or domestic account number format. The data permissions the the OFP request include the following:

  • Account Name (including First Name and Surname or Business Name)

3.4 Receive the Customer Data from the Data Request Response of the API endpoint.

3.5 Compare the Account Name information received by the Payee’s LFI with the Payee Identificaiton details included in the Confirmation of Payee Request. The outcome will be as follows:

  • Exact Match - Confirmed

  • No Match - The comparison of the Account Name (First Name & Surname or Business Name) with the Payee Name in the Confirmation of Payee Request is NOT an exact match.

3.6 Provide to the TPP the appropriate information depending on the outcome of the Confirmation of Payee service as follows:

  • 3.6.1 - If Confirmation of Payee outcome is Exact Match, then provide a positive response (Yes)

  • 3.6.2 - If Confirmation of Payee outcome is No Match, then provide to the TPP a negative response (No)

COP-4

User Payee Name Confirmation

TPPs MUST:

4.1 Display to Users the outcome of the Confirmation of Payee service next to the Account Name information received by the Payee’s LFI.

4.2 Request Users to either abort the payment journey or start the payment information process again to provide new Payee Identifications details, if the outcome of the Confirmaiton of Payee service is negative. Move to step COP-1.

COP No Return of Data/Error Only

OFP MUST:

4.3 Inform the TPPs that the Payee Name cannot be verified due to error in the Confirmation of Payee service. the OFP MUST provide the appropriate error message for the failure.

TPPs MUST:

4.4 Inform the User that the Payee Name cannot be verified by the Confirmation of Payee service.

4.5 Inform the User about the risk of proceeding with making the payment without confirming the Payee and advise that the payment journey should either be aborted or start the payment information process again to provide new Payee Identifications details. Move to step COP-1.

COP-5

Single Instant Payment Consent

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Single-Instant-Payment-Consent , step1 1.2 to 1.6

COP-6

Consent Staging

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Consent-Staging

COP-7

Hand-off to LFI

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Hand-off-to-LFI

COP-8

Authentication

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Authentication

COP-9

Confirmation/ Authorization

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Confirmation%2F-Authorization

COP-10

Payment Initiation

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Payment-Initiation

COP-11

Payment Status Update

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Payment-Status-Update

COP-12

Hand-off back to the TPP

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Hand-off-back-to-the-TPP

COP-13

Confirmation to User

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Confirmation-to-User

COP-14

Payment Notifications

As per https://openfinanceuae.atlassian.net/wiki/spaces/standardsv1draft4/pages/98337961/Single+Instant+Payment#Payment-Notifications

...