Step 1: Retrieving the SLD for the Destination IPS

The Source Bank ask the Source Gateway for the Destination IPS's Service Level Description
As a first step in the payment process, the Sender must select the Destination country for the payment (1). The Source Bank will then call the Source Gateway’s SLD API (2), to retrieve the SLD for the Destination IPS.
The Source Gateway will load the SLD for the Destination IPS and return this to the Source Bank.
This step is necessary so that the Source Bank’s app knows which information to ask the Sender for and can set up the screens accordingly. For example, the app needs to know what account formats or aliases are accepted and the maximum payment size that can be sent to that country.
As described above, a synchronized SLD is stored locally by the Source Gateway. Because the functionality in an IPS is rarely changed, SLDs are rarely updated. For this reason, it is more efficient for the Source Gateway to store a copy of the Destination IPS’s SLD than to ask the Destination Gateway for the SLD on a payment-by-payment basis. The SLD synchronization process described earlier ensures that all the local copies of SLD are up to date.

Message Flow

Triggered by GetSLD API call.
The Source Bank asks the Source Gateway for the Destination IPS's SLD.