SecurePay

SecurePay is based in Australia and available to Asia-Pacific customers. AutoPay is required for all SecurePay transactions. The SecurePay gateway can be used for:

• Credit card:
  • single donation, membership, or product
  • recurring donation
  • recurring membership
• Direct debit:
  • recurring donation

Note: Staff users only can make direct debit recurring donations through SecurePay. Staff users must make the donation On Behalf Of the donor.

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

1. Ensure you have set up card authorization in iMIS.
Click for details
Enter gateway information through the Advanced Accounting Console. You can also set up multiple gateways in the Advanced Accounting Console. Do the following to set up a gateway authorization account:
1. In Advanced Accounting Console, go to Finance > Options > Configure accounting options > Credit Card Auth.
2. Click New and select a gateway from the Gateway drop-down list.

Note: Once you save a card authorization account, you cannot change the Gateway field.

3. Specify the authorization type: Manual Authorization (direct debits), Immediate Authorization (credit cards), or Deferred Authorization.
4. Enter an Account Code. This value displays in the Select a Value window that is displayed when you use the lookup icon on the CC Auth Account field on the Cash accounts (Finance > Options > Set up tables > Cash accounts) setup page. This value cannot be changed once the record is saved.

Note: When entering gateway information for iATS or SecurePay, you must use a pre-defined Account Code. For iATS, enter IATS. For SecurePay, enter SECUREPAY. These codes must match the entry in the web.config file. Read more information about modifying the web.config file for a gateway Account Code.

Note: Once you save a card authorization account, you cannot change the Account Code field.

5. Enter an Account description, which will appear under the CC Auth Account field on the Set up cash accounts window.
6. Enter a meaningful description for the authorization account in the Account description field. This information displays as read-only data on the CC Auth Account field on the Cash accounts setup page.
7. Enter a Host URL. You will receive the Host URL from your gateway provider when you register.

   You can use test Host URLs while testing your gateway to verify setup. This ensures a real financial transaction is not mistakenly processed during the testing. Some common live and test Host URLs include:

   • Payflow Pro:
     • Host URL (Test) -- pilot-payflowpro.paypal.com
     • Host URL (Live) -- payflowpro.paypal.com
   • iATS:
     • North America (Test) -- www.iatspayments.com
   • SecurePay:
     • Credit card transactions:
       • Host URL (Test) -- https://test.securepay.com.au/xmlapi/payment
       • Host URL (Live) -- https://api.securepay.com.au/xmlapi/payment
     • Direct debit transactions:
       • Host URL (Test) -- http://test.securepay.com.au/xmlapi/directentry
       • Host URL (Live) -- https://api.securepay.com.au/xmlapi/directentry
   • Moneris:
     • Host URL (Test) -- esqa.moneris.com
     • Host URL (Live) -- www3.moneris.com
   • TNSPay (Test) -- secure.na.tnspayments.com

   Note: For the most up-to-date live and test Host URL information, contact your gateway provider or refer to your gateway provider documentation.

8. (Moneris only) In the Vendor field, enter the Store ID you were provided by Moneris.
9. Enter a UserName (this is the user name supplied by the gateway).
10. Enter the Password you were given by the gateway provider during the sign-up process. Verify your password.

For Moneris gateways, enter the API token (password) you were provided by Moneris.

11. Click Save.
12. Recycle the AsiSchedulerPool:
    1. Open the IIS administrative utility. Go to Start > Administrative Tools > Internet Information Services (IIS) Manager.
    2. In the left navigation panel, go to Sites > Default Web Site. Select to view the Default Web Site Content by Content View.
    3. Select the Asi.Scheduler_ [your instance] application for the instance you installed.
    4. Do one of the following:
       • Right-click and select Manage Application > Browse. An ASP.Net page will open.
       • In the Actions pane, select Browse. An ASP.Net page will open.
    5. Close the browser. The Asi.Scheduler_ [your instance] service is now enabled.
2. Register with the SecurePay card authorization gateway.
Click for details

You must set up an account with SecurePay for your card authorization gateway. Set up your account by going to the SecurePay website at https://www.securepay.com.au/.

Note: Make a note of your user login and password. You will need it to configure iMIS. ASI Technical Support does not have access to this information.

3. Verify your registration setup.
4. Apply for a merchant bank account at a financial institution.
Click for details

Note: SecurePay offers merchant account services. Contact SecurePay for more information.

You must apply for a merchant bank account. The merchant bank is where all the credit card transactions are verified. You can find a list of financial institutions using the authorization gateway website. However, before contacting a merchant bank, check with your bank to see if it is compatible with the authorization gateway.

Every organization accepting online credit card transactions must have a merchant account with an acquiring financial institution.

The acquiring financial institution deposits the daily credit card sales into the merchant’s account after deducting applicable fees. Some acquiring financial institutions perform merchant services in-house; others outsource these functions to a third-party processor. These services may include billing, customer service, reporting, authorization, and settlement services for merchants. A third-party processor is a company that provides credit card services to merchants on behalf of acquiring financial institutions.

5. Submit and review test transactions.
6. The acquiring financial institution approves the application and notifies the authorization gateway.
7. Switch from test mode to live mode.
8. Complete the online compliance form for SecurePay.
9. The default currency code must be specified in order for iMIS to pass the correct currency values to iATS. See Quick setup for more information.