Automatic payments (AutoPay)

AutoPay provides organizations the ability to support automatic renewal of membership fees or recurring donations. AutoPay uses a tokenization engine (DataVault) to process credit card and bank account information for recurring payments while maintaining PCI compliance.

The following are required in order to use AutoPay:

Key features and benefits of AutoPay

  • Offering members or donors the choice of easy, automated payments.
  • Maximizing member and donor retention with automated renewals.
  • Enabling staff to discontinue automatic payments for members or donors at any time.
  • Using settings in the Staff site to set automatic payment options as off, opt-in, opt-out, always on or required.
  • Differentiating between automatic and non-automatic renewals so your members are billed accurately.
  • Staff manually adding members to the automatic membership renewal program.
  • Staff previewing membership fees or donations to be collected, and submit for collection.
  • Securely storing credit card details in a PCI-compliant manner.

AutoPay setup status messages

Staff users can review status messages that provide more information about the status of the AutoPay configuration and setup. For more information, see AutoPay setup status messages.

Configure the Staff site for AutoPay

You must initially configure the Staff site for automatic membership renewals and recurring donations. See Automatic membership renewals and Recurring donations for more information.

Using AutoPay in iMIS

The following are the basic steps to using AutoPay in iMIS:

  1. Generate invoices.
    • Generate invoices for recurring donations:
      • If paid by credit card, the first payment is processed immediately.
      • If paid by direct debit, the first payment generates a pledge invoice that must be sent to the tokenization engine.
    • Generate invoices for membership renewals:
      • If paid by credit card, the first payment is processed immediately.
      • If paid by direct debit, the first payment generates an accrual dues invoice that must be sent to the tokenization engine.
  2. Submit invoices to the tokenization engine.
  3. Process invoices. This is the step you take to gather all invoices that have a due date on or before the date you enter.
  4. Update iMIS to retrieve payments that have been processed. iMIS calls to the tokenization engine to retrieve all processed transactions.
  5. Review submitted renewal payments.