Payment Workflows for CiviCRM¶

Recurring payment workflow (PayPal)¶

1. POST request from user to CiviCRM (User submits form) CiviCRM creates a pending contribution and recurring contribution record.
   1. POST request from CiviCRM to PayPal (Civi asks PayPal to authorize card). PayPal responds with success or failure. CiviCRM responds to user's POST request with a thank-you page (or a PayPal error) A few minutes later...
2. POST request from PayPal to CiviCRM (informing Civi that recurring contribution was created on PayPal's side)
3. POST request from PayPal to CiviCRM (informing Civi that contribution was successfully charged).

Recurring payment with interdiction (PayPal)¶

1. POST request from user to CiviCRM (User submits form) CiviCRM creates a pending contribution and recurring contribution record.
   1. POST request from CiviCRM to PayPal (Civi asks PayPal to authorize card). PayPal responds with success or failure. CiviCRM responds to user's POST request with a thank-you page (or a PayPal error) A few minutes later...
2. POST request from PayPal to webhook.site (informing Civi that recurring contribution was created on PayPal's side) 3a. POST request (curl, using webhook.site request) to Civi.
3. POST request from PayPal to CiviCRM (informing Civi that contribution was successfully charged).

One-time payment (PayPal, Auth.net)¶

1. POST request from user to CiviCRM (User submits form) CiviCRM creates a pending contribution and recurring contribution record.
   1. POST request from CiviCRM to PayPal (Civi asks PayPal to authorize card). PayPal responds with success or failure. CiviCRM responds to user's POST request with a thank-you page (or a PayPal error)

One-time payment (Stripe)¶

• POST request from user to Stripe (user submits form). Stripe responds in JavaScript with success/failure. (aka "pre-authorization")
• POST request from user to CiviCRM (triggered by the return of Stripe's request, and including the result of Stripe's request). Civi responds with thank-you page or an error.