Gateway tokens v4

From TMMwiki
Jump to: navigation, search
NATS 4
    Biller Instructions
NATS4 Biller List
2000Charge
2000Charge Gateway
A1Payments
Aebill
Allopass
Aconti
AltoBilling
Argus
Authorize.net
BoaCompra
Bill1st Gateway
BillAPay Gateway
Billing Revolution
Billing United
Bit-Pay
C2Bill
CardFlex
CCBill
CCBill Flexform
CCBill Web900
CashSend
Centili
Centrobill
Clearcard
Clearcard IDV
Click and Buy
CommerceGate
CurePay
DHD
DHDGateway
DIMOCO
EGatePay
ElectraCash
eMerchantPay Gateway
eMPPay.com
Epoch
Escalion
EuroBill
Ezic, Inc.
EPGBill.com
Focal Payments
FXBilling
FXBilling Native
Gateway tokens
Gigadat
Global Access
GlobalCharge
Global DPS
GoCoin
Greta 11 (G11Bill)
GTBill
GTBill GATEWAY
GXBill
ICN Ltd.
Itelebill
Jettis International
Jettis International Gateway
LocalBilling
MerlinBill
NETbilling
NETbilling Native
NetCash
NetMobile
Netpay International
NoCreditCard
OrbitalPay
Password By Phone
Pay4
Pay900
Payment Network
Paygarden
PayPal
Paysite Cash
Payspace
Payspace Gateway
Plug'n Pay
Probiller
RocketGate
RocketGate Native
RSBilling
RSBilling Native
SafeCharge
SafeCharge Native
Secure Billing Worldwide
Secure Billing Worldwide Gateway
Secure Trading
SegPay
SegPay Gateway
SOFORTdauerauftrag
Sonic Bill
StandardBill
TrustCharge
Telecom
UKash
Vendo Services
Vendo
Verotel Pro
Voxtel
VXSBill
WebBilling
BoaCompra
Wispay
WTS
WTSeu
Zombaio
Shopping Cart Sales
Switching From Epoch to Epoch EU

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;
$config['NETBILLING_NONRECURRING_USERNAME'] = 1;

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