Page MenuHomePhabricator

Recurring Token Migration - Adyen
Open, Needs TriagePublic

Description

We would like to move our existing Adyen recurring over to Gravy in order to manage all recurrings from Gravy.

Since Gravy currently possess the Adyen credentials that was used in creating the tokens, we should confirm with them if they're happy to charge the existing tokens on our behalf first.

Event Timeline

This Searchkit shows we currently have over 400K recurrings through Adyen and the breakdown according to payment method. I've began the conversation on Slack about having Gravy charge our existing tokens on our behalf.

Gravy confirmed they would be able to use the existing tokens for CC, Sepa, and ACH Adyen recurrings. However, for Apple Pay and Google Pay, they would initialise new methods on their end like we did for the Stripe Apple/Google pay tokens.

The next step would be to run a test import for each Adyen Payment method on Gravy before committing to do the full imports.

Given the different approach for each payment method in the import, this task would be an epic to oversee the Adyen token migration.

I've created and sent recurring records on my card to test out Card/Apple/Google token migration. I've also created subtasks to enable the tracking of each payment method import.

Gravy sent the test tokens imported from the Adyen tokens, we are currently in the process of ingesting those for testing.

In the meantime, we sent over the remaining active recurring tokens to Adyen for export to Gravy. The stats of this export are below:

Credit Card278712
ACH1625
Check1
Sepa6780
Ideal39900