We no longer get these files and so not have code to handle any other recurring signup or cancel data from the audit files - does that matter? If not the only thing we need to do before we can delete audit from tools is move the download protocol over
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Eileenmcnaughton | T405404 Handle Gravy Paypal Chargebacks and Refunds from the resolution center | |||
| Open | Eileenmcnaughton | T415003 PAYPal - we no longer receive SAR files - ie recurring notifications |
Event Timeline
Comment Actions
I think we have been relying on these to create the initial donor and contribution_recur rows for recurring donations not recorded via IPNs or messages from the front end. Does the new PHP audit code handle creating those for new recurring donations just from the TRR files?
Comment Actions
@Ejegg I was gonna get the audit code processing the SAR files & then I looked and there were none incoming
Comment Actions
@Eileenmcnaughton when was the date we last got them? gravy was reporting something going on with the paypal ftp so it could be related to that if they stopped over the weekend?
Comment Actions
Well, once we migrate all the tokens over from the EC (and older) paypal-scheduled-recurring integrations, there won't be anything to record from SAR files anyway, so it's probably fine to move ahead without them.
Comment Actions
@Ejegg should we decline this task, add it to chaos holding pen for documentation, or just wait until we're in the midst of (or completed) token migration before making a call on this?
Comment Actions
After speaking with @Ejegg and the team, it sounds like we're still determining the feasibility of migrating the Paypal tokens to Gravy. Once we know for sure we'll be able to make a decision about this task.