FIS have changed PAIN.001 <PaymentReturnCode> and <ReturnedPaymentFPID>

[bradydan]

FIS have changed the PAIN.001, without warning (!)

From: Fitzsimons, Michael
Sent: 06 November 2018 20:08
To: Alexander Meynell alexander.meynell@credec.co.uk
Subject: Credec : Urgent XML tag change : FPS Outbound Returns

Following a review of the tag mapping in the FPS Outbound Returns, we have found that we have had to make a minor change to the XML structure of the FPS Outbound Return PAIN.001 message. Specifically - the tags and have been moved from the Supplementary_Data level to the Transaction_Info level. This is in line with how this information is presented to FPS in the 9200 message.

Pls find attached the FPS API Usage Guide, which has been updated with this change. (page 13 contains an example). You will have to ensure that this change is reflected in your messages, as otherwise there is a risk that they will not get passed through to the Scheme. This change is now available in the FPS UAT environment should you wish to conduct any testing.

Key info:

The tags and have been moved from the Supplementary_Data level to the Transaction_Info level

Updated API usage guide is below and on Google team Drive:
UPDATED SPEC NOV 2018 - PaaS FPS API Message Usage Guide.pdf

[judgej]

It is not at all clear from the email, document or document change history what has actually changed here. There has been a change, in the err, data kind of tags stuff...

The document is also a major version beyond anything we have been using, so there are lots of additions and changes in here. v1.3 vs v2.1. v2.0 has added clarifications, additional examples, and I guess stuff we have never seen. One example is the "account switching" response. I guess that's where we are notified the the payment we sent to SCAN1 has been automatically sent to SCAN2 for us, and we need to use that new account from now on. We had that with Starling too. In reality we log it somehow and it becomes an alert to someone to update the records.