We would like to move our existing Adyen recurring over to Gravy in order to manage all recurrings from Gravy.
This phab tracks the migration of the SEPA tokens to Gravy for them to be able to charge on our behalf.
Description
Description
Details
Details
Related Changes in Gerrit:
Customize query in gerrit
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T364501 Gravy Integration | |||
| Open | None | T394996 Recurring token migration from all PSPs to Gr4vy | |||
| Open | Damilare | T418619 Recurring Token Migration - Adyen | |||
| Open | Damilare | T418761 Recurring Token Migration - Adyen SEPA |
Event Timeline
Comment Actions
A total of 6780 active Adyen SEPA tokens have been sent to Adyen for export to Gravy. Awaiting feedback from Adyen and Gravy.
Comment Actions
Gravy reached out with some issues before they could go ahead with the imports.
Firstly, some Ideal transactions were included in the SEPA token exports from Adyen, so Gravy reached out to verify if these tokens should be imported as SEPA tokens or Ideal. Adyen's response suggest the tokens should be imported as SEPA. Here was Adyen's response:
On the SEPA + Ideal question,
Ideal recurring transactions would get processed through SEPA, via a SEPA mandate.
So in the case of the Ideal tokens, you may indeed import these as SEPA instead of Ideal.
About 2 SEPA transactions were blocked because the export did not make it out with ownername values. I asked Adyen if anything could be done about it and here was their response:
The ownerName field looks to be required for Sepa token imports,
You may attempt the import to see if the exclusion of the ownerName parameter can be successful.
In the event of a failure, you may add a generic name to these and see if it works well for you.
Looking at our records, it seems we have contacts with names attached to this recurring tokens as such I've asked Gravy if we could provide these names (if it is absolutely necessary) in order to unblock the imports. Here's a SearchKit containing the affected SEPA tokens
Comment Actions
We decided to move ahead with the imports but we are currently blocked as it appears the tokens were not properly configured on Gravy before they were shared. Bug phab: T438431
Comment Actions
Change #1344370 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[wikimedia/fundraising/SmashPig@master] Add Provider for Gravy Adyen direct paybybank connection for ACH/SEPA transactions
Comment Actions
Change #1344755 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):
[mediawiki/extensions/DonationInterface@master] Add fields for payments through Gravy paybybank connector. While we currently do not have use for this connector on the frontend, this patch was useful in testing the connector on sandbox since it'd be used for the token migration.