Documentation
Documentation

Understanding the payment workflow between iMIS, Pay Central, and payment gateways

Review the following information to understand the payment workflow between iMIS, Pay Central, and the gateway.

🚧

Warning

Neither iMIS nor Pay Central store payment details such as credit card numbers. Instead, a unique token is used that represents the payment data.

One-time payments

The following outlines the payment flow for one-time payments:

  1. A user submits a cart with payment details.
  2. The payment details are sent to Pay Central.
  3. The payment details are sent to the payment gateway.
  4. Pay Central receives a payment status message. This status is documented in Pay Central.
  5. iMIS receives a payment status message. If the payment was successful, the payment is settled in iMIS.
  6. The user receives a payment successful message in the cart.
📘

Note

Direct debit payments do not follow steps 5 and 6. A direct debit payment does not settle at checkout, and can take several business days to reach a Completed or Failed status. The payment remains in the AwaitingReconciliation state until the Retrieve processed payments from Pay Central scheduled task updates the final payment status. See Using the 'Retrieve processed payments from Pay Central' scheduled task for more information.

Recurring payments (AutoPay)

The following outlines the payment flow for recurring payments:

  1. A user enrolls in recurring memberships or recurring donations.
📘

Note

Staff users may also enroll public users in memberships or donations.

  1. The payment details are sent to Pay Central.
  2. The payment details are sent to the payment gateway.
  3. Pay Central receives a payment status message. This status is documented in Pay Central.
  4. iMIS receives a payment status message. If the payment was successful, the membership is renewed, or the donation is processed.

Updated about 1 month ago

Did this page help you?