Has been happening more for ACH, but we just saw one for RTBT / iDEAL
recurring_payment_token: 2a19ab28-36c3-48a4-9b4c-31cadab9606e, order_id: 246470577.2
{"type":"error","code":"bad_request","status":400,"message":"Request failed validation","details":[{"location":"body","pointer":"/payment_method/id","message":"Payment method has not been successfully stored. Current status: failed.","type":"value_error"}]}
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T403769 Gr4vy Chaos Epic | |||
| Open | None | T427341 Gravy recurring payment failure issues | |||
| Resolved | None | T426963 Recurring ideal charges fail with "Payment method has not been successfully stored." |
I just sent 6 IDs with iDEAL failures from the last 3 days to the Gr4vy team on Slack.
Update on the slack convo, last week gravy had us add an ideal specific ipn in the adyen console. I added that but we still got a failure today. I messaged them again with the updated info
I'm worried that all of the iDEAL recurrings that were started between March and when you added the IPN have not been stored at gravy. That's 74 recurring donations with a total of €1313 monthly value. None have been canceled yet. We could either try to get Gr4vy to do some kind of backfill or we could try to update our database to charge them directly via Adyen. That second option might end up with some funny-looking values in a few fields but I think we could do it.
The earliest ones started April 20th and have failure_count=3 so they would be canceled on the next failure. I'll reset the failure count for now.
Gravy fixed the issues on their end and I was able to charge a new recurring sucessfully. Elliott sent ipn data to gravy and they were able to backfill 69 iDEAL payment methods on their end.