This topic lists the known issues with our Payments API.
Lloyds/Halifax/Bank of Scotland - Payment Consent Journey - Error during journey - 2019-05-22
When the payer is redirected to the bank payment consent journey, they may occasionally encounter an error after submitting their username, preventing them from authenticating and authorising the payment. An example of the error is displayed below:
This is a bank issue; Lloyds Banking Group is investigating.
If the user encounters this error, a workaround is for the user to open an incognito or private browsing window, or to delete all their relevant bank cookies; however we note that this is impractical for any non-technical users.
Barclays - Payments API - Payments do not transition to executed - 2019-05-22
When a Barclays payment is authorised and submitted, the payment is executed, but the Barclays API does not provide confirmation that the payment has been executed due to an error.
This means that the TrueLayer single-immediate-payments resource status attribute stays in the submitted state. Despite this, the payment should have been successfully executed.
Until Barclays fixes this issue, we recommend that the beneficiary bank account is verified directly for the deposit by matching the reference value provided in the original POST API call to single-immediate-payments against the transaction record in the beneficiary bank account statement, especially for any payments covering higher risk products.
Barclays is investigating this issue but has not yet provided a fix date.