Knowledge Base Inzant Support Articles Inzant Website / CMS Payment Gateways

            Configuring SecurePay as a Payment Gateway

            To start with you will need a SecurePay Online Payments account - this is 100% required so get this process started before you need the site up and running as it could take a while for SecurePay to approve your application. Please also consider whom the payment gateway should apply to (i.e. public visitors, account customers or both) and whether or not freight calculations should be implemented on the website at the same time.

            Step 1 - Login to your SecurePay Account

            When your "SecurePay Online Payments" account is successfully created you will receive a welcome email from SecurePay, which should contain pretty much everything you need to get the payment gateway up and running. The first thing you need to do is login to the merchant portal with the details provided in the welcome email. After logging in the first time you will be prompted to set a permanent password.

            Step 2 - Complete your Merchant Services "Compliance Form"

            Before the site can be used you will need to complete the merchant services compliance form. Until this is completed it will show on your landing page after logging in with a large red box around it. To complete the compliance form scroll down to read through all the requirements to fulfil with suggestions from Inzant where applicable.

            • I / We own the domain name for the website on this application.
            This is a pretty straightforward one, all you need to do is own the domain the site is hosted on. Provided you own the domain (the domain the site will be hosted on once live) you can check this one off.
            • The website displays the business/company name along with the ABN/ARBN clearly shown on the Home page or Contact Us page
            If your site doesn't already have the ABN or ARBN listed on the home or contact us page then ensure to include it. An easy way to include it on both (and all other) pages at once it to include it the "Copyright Text" section of the footer widget.
            • The website clearly shows the business/company landline phone number (not IP phone, nor mobile phone)  *Must be physical (eg. 038641xxxx) or registered (eg. 1300/1800) landline number.
            If your site doesn't already have the business contact landline phone number listed on the contact us page (or other pages) then please include it now. A simple way to include it is on the telephone section of the "Contact Details" widget. 
            • The website clearly shows the products and/or services offered, including accurate description/display of the price & currency offered. Filler text of service descriptions not accepted. Unless applying for a multi-currency service, all prices must be denoted in AUD.
            Inzant should always list a product with the name & price in any potential order screen, however there is potential for configuration issues to cause names not to appear. Always ensure that "Use Product Name" is checked in Inzant unless you have gone to the trouble of creating website friendly product names in the "Website Name" field. Your Terms & condition's should probably also state that pricing on the site is in AUD.
            • The website clearly displays the refund and returns policy (regardless of products or services being offered). This details how a cardholder can dispute a payment, refund options and any imposed return limitations.
            If your site doesn't already have a refunds and returns policy page then you'll need to create one. A good place to provide a link for this page would be in the footer widget in the Copyright Section Link 1/2 Name/URL fields. These are displayed on all pages. If both fields are already used then providing a link to your refund / returns policy within your Terms & Conditions page, or even incorporating this policy into your terms and conditions would also suffice.
            • The website clearly displays our complete Delivery Instructions and Timeframes. Showing the time it takes after a cardholder makes a payment to when they receive the goods/service.
            If your website doesn't already display this information within your FAQ's, Shipping policy or Terms and Conditions then you'll need to add it in. A dedicated page or any of the aforementioned areas would be an ideal spot for this information.
            • Website clearly shows the complete Privacy Policy with accurate description of how your cardholder information gathered, will be secured and protected. This must include your measures in place to secure cardholder account data.
            If your website doesnt already have a privacy policy then please look into creating one and linking it from the footer widget (copyright section 1/2 name/url fields are ideal for this). Its important to note that you'll be using SecurePay's "SecureFrame" option, which intentionally doesn't allow the Inzant website to capture, store or transfer any sensitive customer information (card details), so your privacy policy should include reference to this.
            • The Website clearly indicates that the business / company are an Australian Business.
            If your website doesn't already do this please include within your terms and conditions (or anywhere else within the site you'd like).
            • The complete payment process is accessible on the website for assessment. You may assess a complete customer experience from selecting the product/service to entering credit card details, or final payment button.
            To check this box you'll need to provide your website URL in the "Website or Test Environment URL" form element, as well as provide active username and password details should someone at SecurePay login and review the website. It's important for you to set this up on a customer who wont be automatically voided in Inzant after a day or so, if you need to set this "test" customer up in your ERP then please do so (you can use this customer for your own testing if you need to in the future).
            • I am aware of my obligations to comply with the PCI Data Security Standard. If you use an API (Application Programming Interface) this means your application will store, process and/or transmit card numbers, and Payment Card Industry Data Security Standards (PCI DSS) apply. If requested by Australia Post, you will need to provide proof of compliance with the relevant PCI mandates in the form of a PCI Certificate of Compliance. If you use an external hosting or processing service provider you will also need to provide their Certificate. Please refer to for payment data security guidelines.
            Inzant has built this payment gateway to cut out as much of the "Red tape" surrounding PCI compliance as possible, however please visit the PCI security standards website and make sure you are across your responsibilities.

            After submitting the form you should be able to commence testing transactions on your website.

            Step 3 - Configure the SecurePay settings in Inzant

            Login to the Inzant CMS, then navigate to the "Merchant Settings" page. Here you will need to check the "SecurePay" option to be on, and complete the below form. You will need to use the Welcome to SecurePay email you received earlier to populate some of this form.
            • Use Live Account : ON 
              • This setting refers to using a live account versus a test account. To keep the account in test mode leave this OFF, only turn on when you are ready to go live.
            • Merchant ID: This was provided in the welcome to SecurePay email. It is under the section called "Live Integration", and its labelled "Transaction Merchant ID". This is your live merchant Id.
            • Merchant URL:
            • Merchant Password: This was provided in the welcome to SecurePay email. It is under the section called "Live Integration", and its labelled "Live Transaction Password". This is your live password.
            • Test Merchant ID: ABC0001
            • Test Merchant URL:
            • Test Merchant Password: abc123
            • Currency : AUD 
              • Note this changes depending on what you want the currency to be, however the above covers Australian transactions. 
            • Declined Payment Message: This message will display when a payment is declined by the SecurePay Payment gateway (and the user returns to the Checkout Payment page). 
              • Suggested Message: "Your payment via SecurePay was declined, please try again." 
            • Cancelled Payment Message: This message will display when the user returns to the Checkout Payment page after cancelling the payment.
              • Suggested Message: "Your payment via SecurePay was cancelled." 

            Step 4 - Configure Checkout Payment Widget

            Now you will need to configure the "Checkout Payment" widget. This will involve navigating the "Pages" page in the CMS, then creating a "Preview" version of the "Checkout Payment" page. 

            Once the Preview version is open navigate to the "Content" section of the page and open the "Checkout Payment" widget configuration. 
            Now select "SecurePay" from the Payment Gateway dropdown. Make sure to configure this for only Public, only Account customers or both depending on your requirements. Once complete, click "Save & Publish" in the top right of the screen. 

            Important Notes;
            • As always, if your page configuration for this widget is blank, then you can configure this via the widget section ("Widgets">"Checkout Payment") instead of creating a new version of the page (saving you a bit of time).
            • If you wish to continue to provide alternate non payment checkout methods to your users (i.e. phone based payment for public users, or Account checkout for account customers) then please leave these checkout methods ON.

            Step 5 - Create a Logo file for the Payment Gateway Page

            You'll need to upload a logo file named in a specific way to load onto the payment gateway screen. This provides you the opportunity to create a custom logo file containing a mix of your logo and the "SecurePay" logo. Upload this file using the "File Library" section of the website CMS.

            File Requirements
            • It needs to be 190px (width) x 60px (height). 
            • It needs to be in PNG format 
            • the file needs to be named "logo" (i.e. resulting in a file being uploaded into Inzant called "logo.png") 
            Example Logo file;

            Step 6 - Test SecurePay Order Placement

            One great thing about the SecurePay interface is that it allows you to have the gateway in "Test" mode, and you can place some test transactions to validate you are happy with how its working. You can see below a list of the test details you can use to validate the setup of your SecurePay payment gateway.

            Once you are happy with the gateway in Test mode, the next step is to push the gateway live and place a test order, please be mindful however that this will require a real payment via SecurePay to ensure everything is working as expected. Some things to be mindful of; 
            • Make sure the user experience throughout the checkout process in SecurePay is as expected. 
            • Make sure the cart successfully converts to an order in Inzant. 
            • Make sure the order contains the receipt information in Inzant. 
            • Make sure you can see the information regarding the payment in your SecurePay account interface. 
            Important Note; not all ERP integrations Inzant offers will push freight/surcharge/payment receipt information through to the ERP when a sales order is transferred, please contact Inzant to determine what level of integration is available with your ERP/accounts package.

            Once your happy with the user experience and everything is pushed live then you're all set, the configuration process is complete. Your SecurePay account will by default be linked to the bank account you provided as part of the account creation process with SecurePay, so if this needs to change at any time you will need to get in touch with SecurePay to discuss.

            Help us to make this article better
            0 0