Purchasing Tokens Through Netbilling

From TMM Wiki
Revision as of 18:03, 19 February 2009 by Boris (talk | contribs) (→‎Explanation)
Jump to navigationJump to search
NATS 3
  Biller Instructions
NATS3 Biller List
123Bill
365Billing
2000Charge
Aconti Payment Service
Allopass
Ampay
Argus
Authorize.net
Bill1st Gateway
Billing Line
BoaCompra
Card Gate Plus
CCBill
CCBill Direct Pay
CCBill Web900
Centrobill
ChargeMeLater
ClearCard
ClearCard IDV
Commerce Gate
CurePay
DHD Media
E-Pay Company
Edelweiss Card
EGatePay
ElectraCash
EMerchantPay (Interconsult)
EnterCharge
Epoch
EProcessingNetwork
EuroBill
EPGBill.com
FABILLING
Global Access
GTBill
GXBill
HeidelPay
HeidelPay Gateway
iBill
ICN Ltd.
Infinity Payment
Interconsult
Jettis
Jettis Gateway
Jettis International
Linkpoint
LocalBilling
Merchant Partners Gateway
Merchant Partners Membership
Merchant Solutions
MyVirtualCard
Netbilling
Netbilling Native
NetCash
Netpay International
NoCreditCard
Oakbill
Optimized Payment System
Password by Phone
Pay4
Paygea
Payment Network
Paysite Cash
PhoneAccess
Plug'n Pay
PPPCard
Probiller
Protx
Pure Vanilla
RocketGate
RocketGate Native
RSBilling
SafeCharge
Secure Billing World
SegPay
Sonic Bill
StandardBill
Streamate
Symmetrex
TrustCash
TrustCharge
txtNation
Ukash
Universal Processing
Verotel Pro
VXSBill
WebBilling
WebPay
WTS
WTSeu
YNOT Processing
Zombaio
Netbilling v3 Upgrade Instructions
Purchasing Tokens Through Netbilling
Streamate Biller versus Third-Party
Switching From Epoch to Epoch EU
Epoch Member Approval Plus
Multiple Biller Accounts

NATS lets surfers purchase tokens through NetBilling. The surfer only needs to enter their payment information once to purchase an unlimited number of tokens.

Explanation

In Sites Admin, on the Site Templates, the _ex_gateway_join_token template contains an example for purchasing tokens through Netbilling. This example records the surfer's customer identification code the first time they purchase a token and automatically sends the customer identification code back to Netbilling on subsequent visits. To do this, five changes must be made to the gateway_join template:

  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
  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}

{if !$gateway_token}
    <input type="hidden" name="nextra[NETBILLING][cisp_storage]" value="1">
    <input type="hidden" name="signup[set_gateway_token]" 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>

Please note: the example above is not complete; please see the _ex_gateway_join_token template for a complete example.

Instructions

Go to Sites Admin, add and setup a new site, and edit its site templates. Use the description above to modify your gateway_join template or replace the gateway_join template contents with the _ex_gateway_join_token template contents.