VETenrol allows credit card payments to be accepted as part of the registration only via third party providers.
After choosing to pay via credit card, the user will be transferred to our secure server where they enter their card details, which are securely sent to and processed by the third party payment gateway.
VETenrol integrates with the following providers:
- BPoint (provider's website: bpoint.com.au)
- eWay (provider's website: eway.com.au)
- PayPal (provider's website: paypal.com/au)
- Stripe (provider's website: stripe.com/au)
- SecurePay (provider's website: securepay.com.au)
Please Note: The VETtrak Online Invoice Payment feature introduced with 21.1 only supports selected providers/integrations/payment gateways.
If you already have an account with one of the above providers, please supply us with the applicable credentials issued by the provider.
DO NOT email your credentials to us! Instead, let our support team know you want to send your merchant information for VETenrol and you will receive a link to our secure service (provided by sendsafely.com) in order to supply the details securely.
There are no additional costs to set up VETenrol with provider services that are already integrated, but if you intend to sign up please ensure you have selected the product supported by VETenrol. Please see below for further details regarding each integration.
BPoint (new integration supporting VETtrak Online Payments)
Users wanting to sign up will need to choose a BPoint Package that includes the API.
To integrate, we need the credentials for BPoint: Merchant ID, Username and Password.
Instructions from Bpoint for credentials for use with the API:
- Login to the Merchant Back Office
- Navigate to Admin >> User Management
- Click on Add New User
- Enter the User Name and Email Address
- Select the User Permission 'API'
- Enter your (Administrator/Manager(T1) user's) password
- Click on Create User
The Eway Customer ID, a number starting with 1 or 2, is the "Merchant ID" required by VETenrol for set up.
Use the following guide (provided by Eway) to help identify where to find your Eway Customer ID:
Do not provide us with your Eway password for this integration. Note this integration does not support VETtrak Online Payments.
Please note for the Eway sign up process - we do not use any of their shopping carts, VETenrol has a custom solution using Eway's API.
Eway - Rapid API (new integration supporting VETtrak Online Payments)
We require the API Key and Password. The following instructions from Eway explain the process.
Please request a SendSafely link (if one has not already been provided) in order to pass on the credentials to us.
Visit our dedicated instruction article here: PayPal (payment gateway)
Please be advised our original SecurePay integration was done a number of years ago and uses their Secure XML API, which has since been superseded by SecurePay's RESTful API. Their older API is still available, meaning this integration continues to work, but customers may find the API Transaction Password is not filled out in their Merchant Portal and need to request it from SecurePay Support. This integration does not support VETtrak Online Payments.
SecurePay RESTful API (new integration supporting VETtrak Online Payments)
We require a Merchant ID, username and password for the SecurePay API. Please note these are NOT your login credentials for SecurePay.
As per https://www.securepay.com.au/resources/faqs:
What is the difference between my login credentials and my API credentials?
The login credentials are used to log in to the SecurePay Merchant Login. They consist of a 3 character Merchant ID (MID), a username and a password. The API credentials are used to identify your SecurePay account when sending payment requests from your website to our payment server. Your API credentials will include a 7 character Merchant ID and an API/Transaction Password.
We need the Publishable Key and Secret Key, which can be found via the Stripe dashboard by choosing Developers > API Keys from the menu.
Instructions/information is available from Stripe: https://stripe.com/docs/keys