Gateway tokens v4

From Tmmwiki

Jump to: navigation, search
NATS 4
  Biller Instructions
NATS4 Biller List
2000Charge
Aebill
Authorize.net
CCBill
CCBill Web900
Clearcard
CommerceGate
CurePay
DHD
DHDGateway
Epoch
Gateway tokens
Global Access
Itelebill
GlobalCharge
Greta 11 (G11Bill)
GXBill
ICN Ltd.
Jettis International
LocalBilling
NETbilling
NETbilling Native
NetCash
Netpay International
OrbitalPay
Pay900
Payment Network
Plug'n_Pay
PayPal
RocketGate
SafeCharge
SegPay
Switching From Epoch to Epoch EU
WebBilling
WTS
WTSeu
Zombaio

Contents

Origination and Version History

As of version 4.0.74.1, Nats supports the gateway token setup (currently only supported for Netbilling) . This article describes how to setup this feature and how it works.

Setting up in NATS

Gateway Join Page

In order to use the gateway token system with Netbilling, you will need to modify your gateway join page. Login to your Nats admin and go to the Sites Admin. Locate the site you want to use tokens with and "Edit Site Templates". Find gateway_join and edit to make the following changes:


  1. The gateway_join template must be wrapped in <HTML></HTML> (and must also have <head></head> and <body></body> sections
  2. The sign-up form must have a name parameter
  3. Smarty code must check for the surfer's customer identification code (when passed memberid and billerid)
  4. If the Smarty code doesn't find the identification code, it must have the surfer fill in their billing information
  5. If the Smarty code does find the identification code, it should use that code and automatically submit the form using Javascript

For example:

{* 1. The gateway_join template must be wrapped in <HTML></HTML> 
      (and must also have <head></head> and <body></body> sections *}
<html>
<head></head>
<body>


{* 2. The sign-up form must have a name field *}
<form action="signup.php" method="POST" name="purchase_netbilling_token">


{* 3. Smarty code must check for the surfer's customer identification code
 * 4. If the Smarty code doesn't find the identification code, it must have the surfer 
      fill in their billing information *}

{nats_get_gateway_token memberid=$smarty.request.memberid billerid=$billerid}

{if !$gateway_token}
    <input type="hidden" name="nextra[NETBILLING][cisp_storage]" value="1">
    ....


{* 5. If the Smarty code does find the identification code, it should use that code 
      and automatically submit the form using Javascript *}
{else}
    <input type="hidden" name="signup[cc]" value="CS:{$gateway_token}">
    </form>

    <script language="JavaScript">
        document.purchase_netbilling_token.submit();
    </script>
{/if}
</body>
</html>

Renaming Members

This feature works when REUSE_MATCHING_USERNAME is enabled (Configuration admin -> Surfers tab). However since usernames are unique at Netbilling, you need to enable the following configuration variable in your includes/config.php file

$config['NETBILLING_RENAME_USERNAME'] = 1; 

This will attempt to rename away the current username at Netbilling so a new subscription can be created for this member.

products