| jgleeson | |
| Sep 19 2024, 3:41 PM |
| F57617191: image.png | |
| Oct 15 2024, 4:36 PM |
| F57617199: image.png | |
| Oct 15 2024, 4:36 PM |
Gravy requires us to add payment method scheme settings for 3DSecure with Adyen. Adyen has advised that we can get this info from the Adyen console by generating a 'Account Configuration Report'.
Moved this table from Jack's comment for visibility and editability:
Test coverage: (Links to transactions embedded)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T364501 Gravy Integration | |||
| Resolved | jgleeson | T375214 Set up production Gravy Adyen 3DSecure Scheme config |
I've asked Philip @ Gravy to confirm the field mappings between the Gravy console and the adyen report here
I've activated and configured the 3D secure payment scheme details for the following payment methods:
I was unable to find details for:
When setting up the 3D Secure payment scheme configuration in the Gravy console, I noticed that Adyen had sent us payment scheme data for some payment methods broken down by country. For example, Amex has 22 different payment scheme configurations split across each of the 22 currencies that we can take payment with Amex via Adyen. However, Gravy does not currently support multi-currency 3D Secure via the console, and we are limited to adding one country/currency per payment method.
Philip mentioned that we can work around this by adding the individual configurations as a separate API Connection for each supported currency.
Review Info:
Using the data in this spreadsheet, I've enabled 3D Secure for the following Gravy Connections:
Note:
Due to AMEX requiring currency-specific 3D Secure for each country, we take payment in, I've added Gravy routing config to detect if AMEX is used in one of the configured countries and route it to the specific connection ahead of the main US Adyen Connection. That configuration is here
@KHancock99 ran into two declines with her mastercard https://wikimedia.gr4vy.app/merchants/default/transactions/622e712f-9192-42de-af3e-262f9b3fbaca/overview
It does look like it handled the 3DS part okay? and is erroring on the address. We are only collecting state/province for AU so maybe that?
"errorDescription": "Format of one or more elements is invalid according to the specification.", "errorDetail": "billAddrCity,billAddrLine1,billAddrPostCode", "errorMessageType": "AReq", "messageType": "Erro",
Huh, maybe we should update the config to collect this for now and chat with Gravy about relaxing it, since we don’t actually need to collect it. I know we’re already handling addresses differently for Gravy—like, with PayPal Gravy payments, we have to collect the address upfront, but with our own direct integration, we just pull it from the response info.
Thanks for reviewing all that and also updating the spreadsheet with the right MC info.
Last night, we had a one-hour test covering 6ENC countries with 3D Secure enabled. Unfortunately, we started seeing failures early into the test for most (not all) transactions coming from Ireland. The errors were related to missing billing address details, and as the forms did not require the donor to enter a billing address, it made sense.
Some did get through, so we should do some analysis to see why. Let's also update the country settings to require these fields for Gravy.
It looks like Gravy's 3D Secure service (NDI or something like that) requires billing address details for most countries. This is different to what Adyen requires, so we've also made @evelyn aware of his change in case it impacts conversion rates.