Difference between revisions of "Gateway tokens v4"
From TMM Wiki
Jump to navigationJump to search (Created page with '== 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 set…') |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{NATS5 Manual | ||
| + | |show_billers_section = true | ||
| + | }} | ||
| + | {{NATS4 Manual}} | ||
| + | |||
== Origination and Version History == | == Origination and Version History == | ||
| Line 59: | Line 64: | ||
<pre> | <pre> | ||
| − | $config['NETBILLING_RENAME_USERNAME'] = 1; | + | $config['NETBILLING_RENAME_USERNAME'] = 1; |
| + | $config['NETBILLING_NONRECURRING_USERNAME'] = 1; | ||
</pre> | </pre> | ||
This will attempt to rename away the current username at Netbilling so a new subscription can be created for this member. | This will attempt to rename away the current username at Netbilling so a new subscription can be created for this member. | ||
| + | |||
| + | [[Category:NATS4 Biller Instructions]] | ||
Latest revision as of 13:05, 20 February 2020
NATS 4
|
|---|
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:
- The gateway_join template must be wrapped in <HTML></HTML> (and must also have <head></head> and <body></body> sections
- The sign-up form must have a name parameter
- Smarty code must check for the surfer's customer identification code (when passed memberid and billerid)
- If the Smarty code doesn't find the identification code, it must have the surfer fill in their billing information
- 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.
