Payment setup for PSPs who provide their own FX

Cases where the Source PSP can provide their own FX

Some Source PSPs may be able to act as an FX Provider to themselves. This is possible where the Source PSP holds an account with a Destination Settlement Access Provider, so that funds can be paid from that account to the Destination PSP.

Specifically, a PSP can act as FXP for a specific payment if:

• For this specific payment, the Source PSP holds the Destination Currency in an account at a member of the Destination IPS

• The institution that provides this account is registered as a Settlement Access Provider with Nexus and is able to participate in the payment processing flow (eg receiving and reviewing the pacs.008 from Nexus and then re-submitting it to the Destination IPS) - see Settlement Access Provision.

• The Source PSP has informed Nexus that it owns that account at the Destination SAP and has authority to issue payment instructions against that account

These conditions apply in three scenarios:

• The Source PSP holds an account at the Destination SAP, which is a different entity, (Scenario 10 below) OR

• The Source PSP is also a member of the Destination IPS, and so also acts as Destination SAP to itself. However, the Recipient is a customer of another PSP (so the Destination PSP is a separate entity from the Source PSP) (Scenario 11 below), OR

• The Source PSP and Destination PSP are actually the same entity (in different countries), and that entity is a member of both local IPS. (Scenario 12 below).

(Note: in the last two scenarios, the Source PSP may be able to bypass Nexus and make the payment directly from their own account in the Destination Country. However this requires building internal systems that perform much the same function as Nexus, so may not be the preferred option for many financial institutions.)

Process when the Source PSP acts as FXP

When the Source PSP wishes to act as FXP to itself:

• The Source PSP does not need to request a quote from Nexus, and does not need to include a quote ID in the pacs.008 payment instruction.

• The Source PSP can define any exchange rate they want. (The exchange rate specified will be used to calculate how much will be debited from the Source PSP’s account at the Destination SAP.)

• The Source PSP MUST ensure that the Sender still has certainty over what will be credited to the Recipient by following the process below.

Preparing the pacs.008 payment instruction

• The Source PSP will prepare a pacs.008 payment instruction which defines the exchange rate set by the Source PSP. There will be no Nexus FX Quote Id, since the Source PSP is not using a third-party FXP.

  • The Source PSP can define any exchange rate in the pacs.008 payment message. Before the payment is forwarded to the Destination Country, Nexus will apply this exchange rate to the Interbank Settlement Amount (in the Source Currency) to get the Interbank Settlement Amount in the Destination Currency.

• The Source PSP must call the GET /fees-and-amounts/ API to establish the amount that will be credited to the Creditor Account at this exchange rate. (Normally the GET /quotes API would calculate these values automatically, but it is not being called in this case.)

• The Source PSP must define the Intermediary Agents in the pacs.008 as follows:

  • Interbank Settlement Amount: set to the sourceSapAmount from the response from the GET /fees-and-amounts/ API

  • Intermediary Agent 1 = The Source PSP themselves

  • Intermediary Agent 1 Account = The Source PSP's internal account number that they use for recording Nexus payments

  • Intermediary Agent 2 = The Destination SAP at which the Source PSP holds an account

  • Intermediary Agent 2 Account = The Source PSP’s account at the Destination SAP

  • Charges Type = “SLEV”

  • Charges Amount = the Charges Amount response from the GET /creditor-agent-fee/ API