Update Custom payment gateway to work with 3DS v2.0
Budget: £750 – £1,500 GBP
We use a very basic custom built web based payment gateway that connects to Braintree to allow our customers to make payments to us for invoices. We recently received notification that it needs to compatible with 3DS v2.0 which we are told it is not. We need someone to either upgrade the current code/system or give us alternative option to replace it that does not involve third party costs per CC transaction. The payment webpage operates on a few different servers, all running LAMP stack.
This is the requirements from the recent Braintree email:
The Second Payment Services Directive or PSD2 as implemented in European and UK law requires all in-scope merchants to enable 3D Secure (3DS) in their checkout to ensure they can continue to process card payments.
Strong Customer Authentication (SCA) was enforced in Europe from 31 December 2020, with enforcement in the UK starting from 01 June 2021. All UK transactions will be fully subject to SCA from 14 March 2022.
We have previously requested you to comply with this requirement.
Since 01 June 2021 card issuers may require 3DS 2.0 on card transactions to allow them to authenticate their cardholders and without this you may start seeing payments decline.
If you already are processing transactions using 3D Secure, no further action is needed. If you are not, please review next steps below.
What do I need to do to ensure there is no disruption?
1. Confirm that you are using the latest version of the Braintree SDKs where possible.
a. If you’re not sure, check in with your developer to see if your SDK is on the most recent version, which can be found by looking at the SDK’s respective changelog: iOS, Android, Web
b. If you are using a third-party shopping cart provider, please reach out to them directly for steps to meet PSD2 SCA requirements.
2. Review the 3DS 2 Adoption Guide and ensure you are collecting and passing the data points needed to qualify for a 3DS 2 authentication
3. Validate 3DS 2 readiness by sending at least one test transaction for each payment method available in the checkout flow.
a. You can verify this by checking the presence of three_d_secure_info in transaction response payloads, and/or checking for a “3D Secure Information” section in a transaction in the Control Panel.
--------------------------------
Attached is a copy of a screenshot of the basic web payment page we operate.. To give an idea of what we have in place.
We will require the system to be fully tested and done in a highly secure coding manner due to the sensitive nature of the task.
This is the requirements from the recent Braintree email:
The Second Payment Services Directive or PSD2 as implemented in European and UK law requires all in-scope merchants to enable 3D Secure (3DS) in their checkout to ensure they can continue to process card payments.
Strong Customer Authentication (SCA) was enforced in Europe from 31 December 2020, with enforcement in the UK starting from 01 June 2021. All UK transactions will be fully subject to SCA from 14 March 2022.
We have previously requested you to comply with this requirement.
Since 01 June 2021 card issuers may require 3DS 2.0 on card transactions to allow them to authenticate their cardholders and without this you may start seeing payments decline.
If you already are processing transactions using 3D Secure, no further action is needed. If you are not, please review next steps below.
What do I need to do to ensure there is no disruption?
1. Confirm that you are using the latest version of the Braintree SDKs where possible.
a. If you’re not sure, check in with your developer to see if your SDK is on the most recent version, which can be found by looking at the SDK’s respective changelog: iOS, Android, Web
b. If you are using a third-party shopping cart provider, please reach out to them directly for steps to meet PSD2 SCA requirements.
2. Review the 3DS 2 Adoption Guide and ensure you are collecting and passing the data points needed to qualify for a 3DS 2 authentication
3. Validate 3DS 2 readiness by sending at least one test transaction for each payment method available in the checkout flow.
a. You can verify this by checking the presence of three_d_secure_info in transaction response payloads, and/or checking for a “3D Secure Information” section in a transaction in the Control Panel.
--------------------------------
Attached is a copy of a screenshot of the basic web payment page we operate.. To give an idea of what we have in place.
We will require the system to be fully tested and done in a highly secure coding manner due to the sensitive nature of the task.