Our upstream 3D Secure provider has notified us of an incident between 04:00am - 04:20 which has now been resolved.
We have been notified by our upstream supplier that a seperate issue is now intermittently affecting transaction processing and we are seeing intermittent issues with 3DS2 authentication, which is resulting in a high number of 'Authentication attempted' responses being received by our upstream supplier.
Encoded will still attempt to process 3DS2 transactions that have received an 'Authentication attempted' response, however you may see an increase in declined rates whilst this issue is ongoing, as card issuers may be less likely to authorise a transaction that has not had a successful 3DS2 authentication performed. If you have implemented your own integrations with our APIs, please ensure that you continue to send transaction challenge responses to the API that receive a "transStatus" of "A", as this will ensure that the transaction is still attempted, maximising the chance of authorisation of the transaction.
Our upstream 3DS supplier is currently investigate what is causing the increase and this page will be updated with further information once available.