Hi @MDemosWMF - I'll book in time to discuss to flesh this phab out even more!

(Note from team: could use service to surface list of DAFs)

Thanks @AKanji-WMF ! They also offered to have their technical folks join a meeting with our team to answer any questions. I can loop them in once that is on the calendar.

@EMartin flagged this would need to be in place by the end of October.

Adding additional detail here on the request at hand. In order to move DAF acceptance from Overflow to Chariot, we will now need to display Chariot's DAFPay button on our donation form along with other payment methods (when the Online team elects to trial this payment mechanism). In our form, a donor will chose the amount to be donated and if they choose DAFPay as the payment instrument, we will need to call the Chariot API and send the nominated amount to the Chariot platform to complete the transaction on the Chariot platform. All financial reporting will be manual and transaction information will be loaded into Civi by the DP team vs pursuing any automated daily output file. @XenoRyet @AKanji-WMF

Major Gifts would like to have this enabled for peak season this year, which means by the end of OCT. @Pcoombe for awareness.

@MDemosWMF do you have information about the workflow, etc? I'm guessing given this extra prominence we'll start to see tickets and questions, or should we just send them to @RLewis as we currently do with DAF?

@RLewis let me know if that's alright with you and you can always pass any tickets my way if needed!

@AKanji-WMF Hi Anil, will this be possible to add before the end of the month? I have concluded that FRTech WOULD need to enable this button, i.e., make the API call /transmit the donation amount to Chariot so Peter can enable it. No importing audit files, etc.

@MDemosWMF and @krobinson - I think for now send them my way but maybe we can reassess if volume gets to much for me. I think its mainly a case of civi clean up (merging records, linking DAFs, snoozing).

@EMartin is the idea that this will always be a separate direct integration, or will we eventually be looking to do this via Gr4vy?

DAF payments are always one-time, not recurring, correct? Are they ever reversed?

Will require at least

• new gateway skeleton (smashpig config, smashpig payment processor and api classes, DonationInterface gateway class & config, Civi gateway config)
• implementing at least 3 API calls in SmashPig-level API and calling them in DonationInterface class
• new production and sandbox credentials
• new IPN listener endpoint for their webhooks (https://docs.givechariot.com/api/webhooks)
• new queue runner and job logic for processing webhooks

Seems like a pretty big stretch to be ready for end of Oct

So we'd need to call the createGrant API from payments-wiki after the donor completes the DAFPay flow in the modal, which will give us a lot of info we need to save to Civi to correlate with the completed payment

https://docs.givechariot.com/api/grants/create
That'll give us the donor info plus a bunch of other IDs
We'll probably need to save trackingID, externalGrantID, and fundID

Looks like they CAN be cancelled before disbursement, but not refunded after:
https://docs.givechariot.com/guides/dafpay/integrating-dafpay/transactions#cancellations--refunds

@Ejegg Hi Elliott, this will always be outside of Gr4vy. Chariot is an alternate platform for handling offline donations such as DAFs. We don't intend to include in the Gr4vy flow. I hear you on being more work than we thought. @CaitVirtue @RLewis I am copying you in for awareness on this. The DafPay button via Chariot will be more work than we can get done in time for month end for busy season now that FRTech have made an assessment. Letting you know as I know there was hope we could fit this in for busy season, but it doesn't look feasible unfortunately. cc mdemos.

{F66750759}Thanks for the quick assessment @Ejegg!

We are pursuing a componentized call approach to see if Peter/Online can enable this in the Ways to Give page and ultimately the banners for 6ENC testing ( per the agreement with MGFE and Online). In the coming months we should look at a proper implementation of this payment type. I am making inquiries with Gr4vy per the API spec at the top of this task and will advise further their response.

We are going with the componentized approach. If we decide to do the full integration to the API, we are making inquiries with Gr4vy.

Noting that regardless on what we do with the front end we should look into what information we can retrieve from the Chariot api to help with donation tracking & possibly prevent imports - in the first instance this is a case of retrieving api credentials and exploring