Token Sites

From TMM Wiki
Jump to navigationJump to search
NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
Sites Admin
The Sites Admin
Sites
Site Setup
Site Templates
Tour Setup
Join Options
No Cost Registration
Special Pricing Options
Join Option Rules
Post URL Usage
Post URLs in NATS4
Approval/Upgrade/Denial Variables
Approval/Upgrade/Denial Template Variables
Mobile Tours
Token Sites
ID Numbers
Site Partner
Site User Management
Example Postbacks for Site User Management
Configure Redirects
Split A-B Testing
Username Checking
Form Validation
Post-Biller Templates
Send Information To Special Biller
Join Option Box vs Button
Qualified Join Page Hits
Allowed languages
Customize Join Form
Package Plus
Token Plus
Signup Plus
Type-In Traffic
Coupon Codes
Setting Rules
Site Groups
Options Simulator
ATVOD Verification Process

What is a Token Site?

  • A token site gives you the ability to have surfers purchase tokens as options instead of a period of time for membership.
  • You then have the ability to send that surfer back to the form to purchase additional tokens under that same username.
  • NATS will keep track of the total number of tokens that a surfer has purchased.
  • You can then post to NATS to deduct the tokens from a member when they are used in your system.

Posting to Signup

  • You have the ability to send the surfer through the NATS pre-join form without them needing to see that form.
  • The only required data is the token option and cascade.
Simply redirect the surfer to the join page with these variables:
&signup[optionid]=<TOKENOPTION>&cascade=<CACADEID>
  • You can optionally add all of the other fields to be submit like username, password, and e-mail address.

You can utilize this option to send members that have already purchased back to the join form and use their same username.

  • The post to reuse a username MUST contain the original username and the matching e-mail or matching token_hash.
  • When a member is created in NATS, they are assigned a token_hash that is passed in all of the NATS postbacks.
&signup[username]=<USERNAME>&signup[email]=<EMAIL>
or
&signup[username]=<USERNAME>&signup[token_hash]=<TOKENHASH>

Deducting Tokens