Please note, this ticket has been created to give visibility to the OB group regarding this issue, which has separately been raised in the RBS service desk under RSD-813.
On the 27/11/2019 we noticed that since 25/11/2019, customers have been unable to complete the payment authorisation for Open Banking payments with RBS group. Upon making a test payment we discovered that when selecting the account to use for the payment, the user is presented with an error message of ’Error validating payment [Invalid Payment Reference]', and cannot complete the authorisation.
RBS clarified in RSD-813 that they no longer accept remittance information reference values with ':' characters in it, we use a format of 'pisp:<PAYMENT_ID>' for the reference value, which is why our payments cannot be authorised.
To ensure customers can make payments again as soon as possible, we have started working on changes on our end to remove the unsupported characters from the reference, as we do not believe the change will be reverted on RBS's end.
As I mentioned in the TWG ALL call earlier today, some feedback on the way this change has been handled:
we received no prior notice, that I am aware of, that this change was going to be made
it does not seem to be documented anywhere the specific characters that RBS accepts or does not accept for the reference value
it's not clear why this change has been made, I assume it's to be in line with RBS's online banking, but that's a guess
if RBS knows that the payment cannot be authorised, then it would be better if the payment setup attempt is rejected at the API level, instead of allowing the payment to be setup and allowing the customer to login, only to show them an error at the end of the process
Customers are presented with an error message ’Error validating payment [Invalid Payment Reference]' when selecting the account to use for the payment.
Customers are unable to authorise payments.