Page MenuHomePhabricator

Transactions at Authenticating in Gr4vy and not visible at Adyen?
Closed, ResolvedPublic

Description

As mentioned in Slack, the donor in Zendesk ticket #1863282 / CID 20091462 wrote in on 04/12 noting "Trying to donate, not working." In Gr4vy searching by their email address there are two attempts via Visa card that are still at "Authenticating". However, there seems to be no trace of these attempts at Adyen searching by their email or the Reconciliation IDs from Gr4vy.

Donor in #1863640 / CID 41507551 is a second example. They have 4 SEK attempts via Visa that are all still at Authenticating in Gr4vy and none of the attempts appear to be visible at Adyen by email or reconciliation id.

I'm not sure if these transactions still being at Authenticating (I'm not sure how long transactions stay at this status or if they should have moved to a failed status?) or there being no trace of the transactions at Adyen when searching by email or Reconciliation ID may be concerning so wanted to flag.

Additionally, not sure if this is related, but noticing that for both of the examples neither of them also have the the connection id that we usually see in Gr4vy that @MBeat33 flagged here.

Event Timeline

Sharing one more transaction, from Adri, that matches this parameter:

  1. Gravy Transaction ID 2c003eb3-f937-4ac4-9cb6-021f12ef9c1a;

Status Authenticating since March 27th, not visible at Adyen
Ticket https://wikimedia.zendesk.com/agent/tickets/1858592

  1. Gravy Transaction ID 63282b06-ed9f-44f2-a625-63024c4c92d8

Status Authenticating 3D since April 11th, not visible at Adyen
Ticket https://wikimedia.zendesk.com/agent/tickets/1864685

Just adding three more examples of transactions at authenticating in Gr4vy and not findable in Adyen by email or reconciliation id:

Ticket #CIDTransaction dateGr4vy transaction #
18651675073710804/14/20263c01c939-89ec-4bf1-a9d7-5eb3e7d7b5e6
18651552577642604/15/202626c6219f-4e82-44ab-ba34-a9fd5019db37 & d85ff081-7d2e-48e3-bd83-346b6a95df3c
18651653161407104/15/20261199cd9e-5089-4175-b9ff-077cc566aa80

This is because Gravy assigns a transaction ID earlier in the process than Adyen does.

For example

  1. We make a createPayment call to gravy, and gravy makes a call to Adyen.
  2. Adyen detects that the payment needs a redirect for donor auth (either to a wallet site or for 3ds)
  3. Adyen assigns some transient session ID that we/gravy can use to look up results of that redirect, and returns the redirect URL to Gravy
  4. Gravy assigns a durable transaction ID as soon as they get the result back from Adyen (where the result is not a simple validation failures).

If the donor does not complete the action and get back to Adyen's site, we end up with the state you see here - still at 'authenticating' in Gravy, and nowhere to be found at Adyen.

  1. If the donor DOES complete the action and make it back to Adyen's site, Adyen then assigns a transaction ID and indicates whether the auth was successful.

Gotcha. Thank you for sharing this context, @Ejegg! So it sounds like donations being in Gr4vy but not Adyen is expected as they just didn't get far enough in the process for the attempt to also be visible in Adyen.

I'm guessing in terms of a donor response then if a transaction is stuck at "authenticating" in Gr4vy we should go with our messaging that speaks to authentication of > "The error code given by our payment processing system suggests that your bank did not authorize the transaction, which could be due to an invalid security code. Sending a confirmation code by SMS is required by some banks. Please retry your donation or contact your bank so they can help you."?

XenoRyet set Final Story Points to 2.