Skip to content

GitLab

Stripe
Stripe
Closed
Opened by scardinius@scardinius
Report abuse New issue

Processing charge.failed event is too restrict

When endpoint processes charge.failed it calls Contribution.getsingle. Action getsingle is more restrictive than get because when contribution does not exist then getsingle throw exception.

I have such history of Stripe donations:

  1. customer.created
  2. customer.updated
  3. payment_method.attached
  4. customer.source.created
  5. charge.failed

On 5. step there is no contribution in CiviCRM yet. This is a single donation, not subscription.

My idea is such:

  • use Contribution.get with trxn_id = chargeId
  • when contribution exists, update status to Failed
  • when contribution does not exists, create it with Failed status
Edited by scardinius

The one place for your designs

To enable design management, you'll need to meet the requirements. If you need help, reach out to our support team for assistance.