Setting up at Gigadat (INTERAC Online Transactions)
If you wish to become a merchant and accept Gigadat as a payment processor, go to the Gigadat website.
For more information on this payment processor visit the Gigadat Product Documentation
Sales / Contract Gigadat:
Contact: Sebastien Maraine
Phone: +1-844-349-1700
Email:smaraine@gigadatsolutions.com
Support / On-boarding Gigadat:
Contact: Cliff Nywening
Phone: +1-403-259-7581
Email:cnywening@gigadatsolutions.com
Gigadat will provide you with the following information for each site that you set up with them:
https://interac.express-connect.com
You will be given the following
- Username
- Password
- Access Token
- Security Token
Within the portal you will need to upload your logo under User profile:
Update the password
Campaigns id (found under campaign when created)
You will have access to the interac logo’s that can be used on your website within the Interac portal under “Logos”
Record this information, as you will need it to set up Gigadat in NATS.
You will need to set up campaigns at Gigadat Admin
- Under each campaign, you will need to set up the following url's, replacing linkdomain with your linkdomain:
You will need to complete the Merchant Checklist that will be supplied by Gigadat after a contract has been signed.
Note: This biller only supports onetime transactions.
Note: This biller does not support rebills
Setting up Gigadat in NATS
Billers Admin
To begin setting up Gigadat in NATS4, go to the Billers Admin. Scroll down to the "Setup New Biller" drop-down menu, select Gigadat, and click "Add".
Note: If you don't see Gigadat, put in a support ticket, as you may need an updated version of NATS.
Fill in the required information when prompted, and click Save. If you were not provided with the requested information, please contact Gigadat.
Sites Admin
Next, go to the Sites Admin, create or edit a tour, and scroll down to the "Biller Details" section. Locate the fields that start with "Gigadat". Here you will see an option to enter "Campaign" information for the site/tour. Hit "Save Changes" after filling in the "Campaign".
Scroll down to the section labeled "Add New Join Option" and add the join option you wish to use.
If you have a join option that needs to use "Campaign" info that differs from what you have set for the site/tour, please do the following. Hit "Edit Global Option Details" under the Actions for the specific join option. In the "Biller Codes" section, locate the fields that start with "Gigadat". Here you will see an option to enter "Override Campaign" for the join option. This option will override the "Campaign" setting for the site/tour. Hit "Save" after filling in the "Override Campaign"
Gigadat will now be configured for use as a biller in NATS.
Additional Setup
You will want to set up a display for Gigadat members to view the sale information on the approval/denial/cascade pages. Here is an example of the approval template:
{if $prev_billerid == $config.GIGADAT_BILLER_ID}
<br><br>
<table width="100%">
{assign var=custom_field value="custom"|cat:$config.STORED_GIGADAT_CUSTOM_FIELD}
{assign var="gigadat" value="|"|explode:$data[$custom_field]}
<tr><td align="left">
<font size=3 face="Arial">
Interac Transaction ID: {$gigadat[2]} [Incomplete/Unsuccessful]<br><br>
This receipt is to be kept for your own reference.<br><br>
Transaction Status: [Incomplete/Unsuccessful]<br>
Transaction ID: {$gigadat[2]} <br>
Customer ID: {$data.username} <br>
Date of transaction: {$data.stamp|date_format} <br>
Amount: {$gigadat[3]|string_format:"%.2f"} <br>
Issuer Name: {$gigadat[1]} <br>
Issuer Confirmation: {$gigadat[0]}<br>
<br><br>
If you have any questions or require customer service at any time, please contact customer service
</font>
</td></tr>
</table>
{/if}
You will need to set the GIGADAT_BILLER_ID (default: -1) and the STORED_GIGADAT_CUSTOM_FIELD (default 4 -> custom4 field) congfig settings on the config admin -> billers page
Below is the list of site templates that you would might need to modify:
- cascade
- cascade_mobile
- page_approval
- page_approval_mobile
- page_denial
- page_denial_mobile.tpl
