Request for Information

Overview of the RFI process

In Nexus, the Source PSP, Destination PSP, and Settlement Account Providers (SAPs) must screen the Sender and Recipient against the sanctions lists applicable in their jurisdiction to check that neither party is on the sanctions list.

One challenge is that sanctions screening systems generate high numbers of “false positives” ie alerts where the Sender or Recipient is not actually the person (or company) on the sanctions list.

When this happens, further information on the Sender or Recipient can help to establish if an alert represents a true match against the sanctions list or a false positive. Alerts may be resolved automatically by software (which would normally take seconds) or passed to a member of staff for manual review (which could take hours).

To support this process, Nexus will provide a Request for Information (RFI) service that allows any PSP or SAP to request further information from either the Source or Destination PSP, in the hope that the additional information will be sufficient to eliminate false matches without manual intervention.

Information shared through a Request for Information

The Request for Information would be used to request the standard information about the Sender or Recipient that is commonly used in sanctions screening, specifically:

  • Name

  • Address (if not already provided)

  • Date and place of birth

  • National identity number or another unique identifier

A PSP can choose whether or not to share this information. (A PSP can also opt out of responding to RFIs entirely, if it does not have the technical capacity to do so, although this will be detrimental for their own customers.)

When RFI is used in Nexus

An RFI can be issued at two points during the setting up and processing of a Nexus:

  1. By Nexus, during the POST /creditorrequests/ process:

When a Source PSP makes a call to the POST /creditorrequests/ API operation, Nexus will use the RFI process to contact the Recipient’s bank and ask for further, verified information about the Recipient, so that the Source PSP does not have to ask the Sender to enter this information (which the Sender may not know or may enter incorrectly). This step will only be done when the Destination PSP has earlier informed Nexus that it supports the RFI process.

  1. By a PSP or SAP during payment processing:

  • The Destination PSP could send an RFI to the Source PSP, requesting further information on the Sender

  • A Settlement Account Provider could send an RFI to the Source PSP and/or Destination PSP, requesting further information on the Sender and Recipient accordingly.

  • (Since Nexus would already attempt an RFI to the Destination PSP during the POST /creditorrequests/ process, there is no need for the Source PSP to call the RFI API directly.)

ISO 20022 Messages used in RFI

There are three ISO 20022 messages involved in the Request for Information process:

  • First, the “requestor” (the PSP or SAP asking for further information about another PSP’s customer) sends a camt.026 “UnableToApply” message. This message acts as the information request. (The “UnableToApply” message name represents that the payment cannot be processed without further information).

  • The “requestee” (the PSP that is receiving the request for further information about their customer) should first reply with camt.029 “ResolutionOfInvestigation”, with one of two status codes:

    • “NINF”: ie no further information is available” or

    • “INFO” ie Further information to follow

  • If further information is available, the requestee will send a “camt.028 AdditionalPaymentInformation” message with the request information.

Last updated