Page MenuHomePhabricator

record failed payments
Open, HighPublic2 Story Points

Description

Ahh awesome, thanks for the update, @Ejegg! I want to bump this additional
question:

I'm curious what information we're recording about these folks--is there a
sql table I can peek at? Looking at the contact record Michael cited above,
here's some additional info I'd like to see:

Donor name -- I'd think if we got their email, we got the name?
Opt-in date
Attempted amount -- could we retain this info? It would be really helpful in future targeting.
Thanks again for the quick response :)

Event Timeline

DStrine triaged this task as High priority.Apr 30 2019, 7:56 PM
DStrine created this task.
Restricted Application removed a project: Patch-For-Review. · View Herald TranscriptApr 30 2019, 7:56 PM

I think this is a duplicate of this task? https://phabricator
.wikimedia.org/T220645

@CCogdill_WMF ah right, this ticket the 'where and how' that @Eileenmcnaughton and I decided would make sense for recording the attempts. So we would add a contribution with all the usual fields to the civicrm_contribution table (this would also link us to the contribution_tracking stats like medium, campaign, etc), but it would have status 'Failed' so it wouldn't get counted towards totals.

Ejegg added a comment.May 1 2019, 9:21 PM

I think for starters, we would only record failed payments for people with opt-in=1.

Cool, that all sounds great! Is there any chance we can also satisfy this
ask in T220645?

  1. *Create separate export file for IBM*: The best way for us to set up the double opt-in program on the IBM side is to have it import into IBM as a separate file (and therefore be in a separate database from the rest of our email list). Can we keep these out of the main file and add them to a new one?

If not, let me know and I will poke around in IBM and follow up with
Trilogy to see if there's another way.

@CCogdill_WMF I would open that as a new task or subtask to make sure it doesn't get missed