Payflow Pro is based in the United States and available to US and Canadian customers.
The Payflow Pro gateway can be used for:
- Credit card (Canada and United States):
- Direct debit (United States):
Note: Payflow Pro authorizes credit card transactions up to $9,999.00.
Before you go live with card authorization, you must complete these 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.
- Ensure you have set up card authorization in iMIS.
- In Advanced Accounting Console, go to Finance > Options > Configure accounting options > Credit Card Auth.
- Click New and select a gateway from the Gateway drop-down list.
- Specify the authorization type: Manual Authorization (direct debits), Immediate Authorization (credit cards), or Deferred Authorization.
- 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.
- Enter an Account description, which will appear under the CC Auth Account field on the Set up cash accounts window.
- 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.
- 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
- North America (Test) -- www.iatspayments.com
- 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
- Credit card transactions:
- 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.
- Payflow Pro:
- (Moneris only) In the Vendor field, enter the Store ID you were provided by Moneris.
- Enter a UserName (this is the user name supplied by the gateway).
- Enter the Password you were given by the gateway provider during the sign-up process. Verify your password.
- Click Save.
- Recycle the AsiSchedulerPool:
- Open the IIS administrative utility. Go to Start > Administrative Tools > Internet Information Services (IIS) Manager.
- In the left navigation panel, go to Sites > Default Web Site. Select to view the Default Web Site Content by Content View.
- Select the Asi.Scheduler_ [your instance] application for the instance you installed.
- 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.
- Close the browser. The Asi.Scheduler_ [your instance] service is now enabled.
- Register with the Payflow Pro card authorization gateway.
- Verify your registration setup.
- Apply for a merchant bank account at a financial institution.
- Submit and review test transactions.
- The acquiring financial institution approves the application and notifies the authorization gateway.
- Switch from test mode to live mode.
- The default currency code must be specified in order for iMIS to pass the correct currency values to Payflow Pro. See Quick setup for more information.
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:
Note: Once you save a card authorization account, you cannot change the Gateway field.
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.
For Moneris gateways, enter the API token (password) you were provided by Moneris.
Make a note of your user login and password. You will need it to configure iMIS and to view reports on the PayPal website. ASI Technical Support does not have access to this 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.
This process generally takes 2 to 4 weeks to complete.
PayPal transaction entries are generated with a captured status. You can edit or delete payment transactions if the changes are made on the same day. If the transaction has already been charged to the credit card, an error will be reported.
iMIS assumes that authorizations are captured every night, so the changes are only allowed if performed on the same system date as the authorization. However, the system date might not be the same as the batch date or the transaction date.
Note: Deferred payments have not been authorized and can be edited without restriction.