Payflow Pro

Payflow Pro is based in the United States and is available to customers in North America and Asia-Pacific. The Payflow Pro gateway can be used for:

  • Credit card (North America and Asia-Pacific):
    • single donation, membership, or product
    • recurring membership
    • recurring donation

Note: For more information about the payment gateway appropriate to your locale, contact ASI or your AiSP.

Note: The Payflow Pro gateway is incompatible with Commonwealth Bank of Australia for transactions through an iMIS website. It is recommended that you use TNSPay or SecurePay instead.

You do not need to have an AutoPay license key in order to use an ASI-hosted tokenization engine (DataVault) to make non-recurring payments; however, you must configure the DataVault service address (from the Staff site, go to Settings > Finance > DataVault settings) to enable iMIS to communicate with the tokenization engine. AutoPay is required for all recurring Payflow Pro transactions.

The ASI-hosted tokenization engine (DataVault) is only required for Payflow Pro for the following:

  • Recurring transactions
  • Conducting credit card transactions with Gift Entry.

Note: Payflow Pro authorizes credit card transactions up to $9,999.00.

Before you go live with card authorization, you must complete the following implementation steps and checks. You will need a merchant account with Payflow Pro. As a developer, you will also need a test account with test card numbers. Make sure your test account credentials work properly.

  1. Apply for a merchant bank account at a financial institution.
  2. Register with the Payflow Pro card authorization gateway.
  3. Verify your registration setup. This will be a notification from Payflow Pro.
  4. Add your gateway in iMIS.
  5. Associate an authorization account with a credit/debit card cash account code.
  6. The default currency code must be specified in order for iMIS to pass the correct currency values to the gateway. See Default currency code used by RiSE components for more information.
  7. Submit and review test transactions.
  8. The acquiring financial institution approves the application and notifies the authorization gateway.
  9. Switch from test mode to live mode.

This process generally takes two-to-four weeks to complete.