VETenrol allows credit card payments to be accepted as part of the registration only via third party providers.
Should the user choose to pay via credit card, the user will be transferred to a secure server where they enter their card details which are then securely sent to and processed by the third party.
VETenrol integrates with the following providers:
Please Note: The VETtrak Invoice Payment feature introduced with 21.1 only supports Stripe and PayPal at this time. It is expected support for additional payment gateways will be included in future updates.
Stripe (stripe.com/au) is our recommended provider as they are easy to implement, follow best practices when it comes to security and are often the cheapest option for our clients too.
If you already have an account with one of the above providers, please provide us with the Merchant ID and Password (where applicable) that the provider has issued to you.
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 for setting VETenrol to use the services that are already integrated, but if you intend to sign up please confirm with us that you have selected the product supported by VETenrol.
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
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.
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.
Visit our dedicated instruction article here:
Please be advised our 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 the 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.
There is no integration using SecurePay's RESTful API at this time.
RELATED: Payment Preferences (General Settings) - where the merchant account details will be displayed once your integration is complete.