NATS4 Post-Biller Templates

From TMMwiki
Jump to: navigation, search
NATS 4
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
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
ATVOD Verification Process
Billers Admin
The Billers Admin
Biller
Biller Fees
NATS Cascades
Add Cascade
Cascade Weight
Autocascade
Hidden Cascades
Geo-Targeting Cascades
Post-Biller Templates
HTTPS Gateways
Timed Cascade Rules
Upgrade Plus
Token Plus
Gateway One Step Join
Extra Biller Fields
Send Information To Special Biller
Setting Rules
Cross Sell Supported Billers
Upsell Supported Billers
Packageplus Supported Billers
Tokenplus Supported Billers

When a surfer's transactions on a site are approved, denied, or upgraded, they are typically sent to an external URL. However instead of sending members to an external URL after their transaction is processed, NATS can instead send them to a custom internal URL using post-biller templates.

Customizing a Post-Biller Template

This template's layout is customizable through the use of Smarty.

To edit the templates go to the Sites Admin, edit or create a tour, click the Templates tab, and find the following templates: page_approval, page_denial, page_upgrade_approval, and page_upgrade_denial.

Click the customize template icon, and edit your template with the text you want to display after the surfer has completed their transaction or has been denied.

When editing the template, you can use the $site, $member, and $option Smarty arrays in order to create a custom template for members to be redirected to after their transaction has been completed. For example, the default page_approval template can say something along the lines of:


You joined site {$site.name} with the following information:
<br><br>
Username: {$member.username}
<br>
Password: {$member.password}


This displays a short message to the surfer, as well as informing them of their Username and Password through an automated script if their transaction has been approved. This function allows clients flexibility if they want to keep surfers on their internal URLs after a transaction has occurred.