Difference between revisions of "Gigadat"
| Line 16: | Line 16: | ||
Record this information, as you will need it to set up GigaDat in [[NATS]]. | Record this information, as you will need it to set up GigaDat in [[NATS]]. | ||
| − | You will need to | + | You will need to setup campaigns at GigaDat Admin |
| − | - Under each campaign, you will need to | + | - Under each campaign, you will need to setup the follow url: |
| + | |||
1. Listener: http://linkdomain/signup/process_gigadat.php | 1. Listener: http://linkdomain/signup/process_gigadat.php | ||
| − | |||
2. Success Uri: http://linkdomain/signup/returnurl_gigadat.php?ok=1 | 2. Success Uri: http://linkdomain/signup/returnurl_gigadat.php?ok=1 | ||
| − | |||
3. Failure Uri: http://linkdomain/signup/returnurl_gigadat.php | 3. Failure Uri: http://linkdomain/signup/returnurl_gigadat.php | ||
| Line 27: | Line 26: | ||
| − | '''Note: This [[Ct#Biller|biller]] only | + | '''Note: This [[Ct#Biller|biller]] only support onetime transaction.''' |
| − | |||
'''Note: This biller does not support [[Ct#Rebills|rebills]] | '''Note: This biller does not support [[Ct#Rebills|rebills]] | ||
Revision as of 10:58, 7 April 2017
Setting up at GigaDat
If you wish to become a merchant and accept GigaDat as a payment processor, go to http://gigadatsolutions.com.
GigaDat will provide you with the following information for each site that you set up with them:
- Username
- Access Token
- Security Token
- Campaigns id
Record this information, as you will need it to set up GigaDat in NATS.
You will need to setup campaigns at GigaDat Admin - Under each campaign, you will need to setup the follow url:
1. Listener: http://linkdomain/signup/process_gigadat.php 2. Success Uri: http://linkdomain/signup/returnurl_gigadat.php?ok=1 3. Failure Uri: http://linkdomain/signup/returnurl_gigadat.php
Replace linkdomain with your linkdomain.
Note: This biller only support onetime transaction.
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. You can enter the "Campaign" informatoin for the site/tour
After selecting a language, scroll down to the section labeled "Add New Join Option" and add the join option you wish to use. In the "Biller Codes" section, locate the fields that start with "BOA". Here you will see an option to enter "Override Campaign" for the join option, it will override the site setting "Campaign".
After you have enter the Campaign or Override Campaign, save your join option details. GigaDat will now be configured for use as a biller in NATS.
Additional Setup
You will want to setup a display for Gagidat member to view the sale information on both approve/denial page, and below is an example of the approve template:
{if $prev_billerid==0}
<br>
<br>
<table width="100%">
{assign var="gigadat" value="|"|explode:$member.custom4}
<tr><td align="left">
<font size=3 face="Arial">
Interac Transaction ID: {$gigadat[2]} [Successful]<br><br>
This receipt is to be kept for your own refernce.<br><br>
Tranasaction Status: [Successful]<br>
Transaction ID: {$gigadat[2]} <br>
Customer ID: {$member.username} <br>
Date of transaction: {$member.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 anyquestions or require customer service at any time, please contact customer service
</font>
</td></tr>
</table>
{/if}
You will need to replace billerid to be the id of Gagidat biller id and replace the "custom4" if you have config setting "STORED_GIGADAT_CUSTOM_FIELD" to different custom field. (by default, all return data from Gagidat will store on custom4 field)
Below is the list of templates that you would need to modify: cascade.tpl page_approval.tpl page_approval_mobile.tpl page_denial.tpl page_denial_mobile.tpl
