Difference between revisions of "NATS4 Netbilling"

From TMM Wiki
Jump to navigationJump to search
 
(22 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{NATS4 Manual
+
{{NATS5 Manual
| show_billers_section = true
+
|show_billers_section = true
 
}}
 
}}
 +
{{NATS4 Manual}}
  
 
{{Test Billers Disclaimer}}
 
{{Test Billers Disclaimer}}
  
''Note: these instructions describe using Netbilling as a [[ct#Gateway|gateway]].  If you want to use Netbilling as a regular biller, please see the [[Netbilling Native]] article.''
+
''Note: these instructions describe using Netbilling as a [[ct#Gateway|gateway]].  If you want to use Netbilling as a regular biller, please see the [[NATS4 Netbilling Native]] article.''
 
<!--
 
<!--
 
Netbilling: the keywords are [per site] at:
 
Netbilling: the keywords are [per site] at:
Setup > Site Tools > Site Tags > press 'config' next to the desired sitetag
+
Site Tools > Site Tags > press 'config' next to the desired sitetag
On this page look for "Scriptable Reporting Interface" > "Access Keywords"
+
On this page look for "Data Retrieval Interface" > "Access Keywords"
 
and then:
 
and then:
 
"Control CGI advanced options" > "Access keyword"
 
"Control CGI advanced options" > "Access keyword"
 
--
 
--
so &#65279;Scriptable Reporting Interface is for the reporting keyword, and the &#65279;Control CGI advanced options is for the access keyword?
+
so &#65279;Data Retrieval Interface is for the reporting keyword, and the &#65279;Control CGI advanced options is for the access keyword?
 
--
 
--
 
correct, and to clarify
 
correct, and to clarify
Line 25: Line 26:
 
''Please note: Netbilling uses the term Access Keyword to describe two different settings.  To distinguish the two different settings, I've placed my own terms in brackets after the Netbilling terms.''
 
''Please note: Netbilling uses the term Access Keyword to describe two different settings.  To distinguish the two different settings, I've placed my own terms in brackets after the Netbilling terms.''
  
To process transactions, in the Netbilling administration panel under "Setup" -> "Access Security", check the box next to "Enable Native Direct Mode v.3 (SAS) Channel" and enter your server's IP address in the box labeled "Specify Trusted Static IP Addresses allowed to originate Direct Mode transactions".  Transactions will not process through Netbilling if you don't do this.
+
To process transactions, in the Netbilling administration panel under "Account Setup" -> "Account Management" -> "Access Security", check the box next to "Enable Native Direct Mode v.3 (SAS) Channel" and enter your server's IP address in the box labeled "Specify Trusted Static IP Addresses allowed to originate Direct Mode transactions".  '''Transactions will not process through Netbilling if you don't do this.'''
  
Reporting keyword: You will need to add a reporting keyword for each site in Netbilling.  You can do this by going to "Setup" -> "Sitetags" -> "config" for each site -> under the section "Scriptable Reporting Interface", there is a box for "Access keywords" [Reporting Keyword].  You need to enter a keyword here to be added later in the NATS admin.  You need to do this for each of your sites.  Also, under "Setup" -> "Access Security" -> "Scriptable Reporting Interface", you need to check the box next to "Enable Scriptable Reporting Interface v1.x" and add your server's IP address to the "Reporting Client IP Addresses section".  You need to do this to track rebills, refunds, chargebacks, etc.
+
Reporting keyword: You will need to add a reporting keyword for each site in Netbilling.  You can do this by going to "Site Tools" -> "Site Tags" -> "config" for each site -> under the section "Data Retrieval Interface", there is a box for "Access keywords" [Reporting Keyword].  You need to enter a keyword here to be added later in the NATS admin.  You need to do this for each of your sites.  Also, under "Account Setup" -> "Account Management" -> "Access Security" -> "Data Retrieval Interface", you need to check the box next to "Enable Data Retrieval Interface v1.x" and add your server's IP address to the "Reporting Client IP Addresses section".  You need to do this to track rebills, refunds, chargebacks, etc.
  
 
== Set up Netbilling in NATS ==
 
== Set up Netbilling in NATS ==
Line 39: Line 40:
 
'''Note:''' If you don't see Netbilling as a [[Ct#Biller|biller]] in [[NATS4]], [http://clients.toomuchmedia.com put in a support ticket], as you may need an updated version of [[NATS]].  
 
'''Note:''' If you don't see Netbilling as a [[Ct#Biller|biller]] in [[NATS4]], [http://clients.toomuchmedia.com put in a support ticket], as you may need an updated version of [[NATS]].  
  
When prompted, fill in the 12-digit Netbilling Account Number that you received from Netbilling under the "Account Info" section. You can optionally enter your dynamic IP code as well. if you were not provided with this information, please contact your [[Ct#Biller|biller]] to receive it.
+
When prompted, fill in the 12-digit Netbilling Account Number that you received from Netbilling under the "Account Info" section. You can optionally enter your dynamic IP code as well. If you were not provided with this information, please contact your [[Ct#Biller|biller]] to receive it.
  
 
=== Sites Admin ===
 
=== Sites Admin ===
  
Next, go to the [[NATS4 Sites Admin|Sites Admin]], create or edit a [[Ct#Tour|tour]], and scroll down to the "Biller Details" section. Enter your Netbilling Site Tag and Access Keyword [Reporting Keyword] here. You can find both of these by logging into Netbilling, going to Setup, Site Tools, and Site Tags -- the site tag is on the main browse sites screen; the access keyword [Reporting Keyword] is
+
Next, go to the [[NATS4 Sites Admin|Sites Admin]], create or edit a [[Ct#Tour|tour]], and scroll down to the "Biller Details" section. Enter your Netbilling Site Tag and Access Keyword [Reporting Keyword] here. You can find both of these by logging into Netbilling, going to Setup, Site Tools, and Site Tags -- the site tag can be found in the "Site tag" column on the main Site Tags screen, or under "Basic Information" on the edit site screen; the access keyword [Reporting Keyword] is under the Scriptable Reporting Interface link. You may also enter an Access Keyword [Control Keyword] for [[ct#Cross Sell|cross-sells]] and instant upgrades (see below). This can be found in Netbilling's admin. Just go to "Site Tools" -> "Site Tags", then click "config" on the site you want to set this up for. Your Access Keyword will be under the "Control CGI advanced options" section on the next page.
under the Scriptable Reporting Interface link. You may also enter an
 
Access Keyword [Control Keyword] for [[ct#Cross Sell|cross-sells]] and instant upgrades
 
(see below).
 
  
 
Once you have done this, scroll down to the section labeled "Join Options for this Tour" and click the "Edit Option Details for this tour" icon that corresponds to the [[Ct#Join Option|join option]] you wish to use. In the "Biller Codes" section on the next page, locate the "NETBILLING" options. All of these options are optional -- simply fill out the provided fields if you wish to use these features.
 
Once you have done this, scroll down to the section labeled "Join Options for this Tour" and click the "Edit Option Details for this tour" icon that corresponds to the [[Ct#Join Option|join option]] you wish to use. In the "Biller Codes" section on the next page, locate the "NETBILLING" options. All of these options are optional -- simply fill out the provided fields if you wish to use these features.
 +
 +
<b>NOTE: If you are using a $0 trial option, you will need to set the NETBILLING_POLL_BACKDAYS in the configuration admin under the billing section to a number of days equal to 1 more than your longest trial length.  This is to ensure that the conversions are properly captured from NetBilling's system.</b>
  
 
Once you have completed these steps, save your [[Ct#Join Option|join option]] details. Netbilling will now be configured for basic use as a [[Ct#Biller|biller]] in [[NATS]].
 
Once you have completed these steps, save your [[Ct#Join Option|join option]] details. Netbilling will now be configured for basic use as a [[Ct#Biller|biller]] in [[NATS]].
Line 55: Line 55:
 
Currently NATS only supports NetBilling Gateway cross sells between NATS clients.
 
Currently NATS only supports NetBilling Gateway cross sells between NATS clients.
  
In Netbilling, under "Setup" -> "Credit Cards" -> "Step 6", you need to check the box to "Enable PCI Repeat Billing".  If you are going to be up-selling or cross-selling to your own Netbilling account, you do not need to enter any account numbers into the text box in Step 6.  If you are going to be up-selling or cross-selling to different Netbilling accounts, you need to enter those Netbilling account numbers into the text box.
+
In Netbilling, under "Account Setup" -> "Account Management" -> "Credit Cards" -> "Step 6", you need to check the box to "Enable PCI Repeat Billing".  If you are going to be up-selling or cross-selling to your own Netbilling account, you do not need to enter any account numbers into the text box in Step 6.  If you are going to be up-selling or cross-selling to different Netbilling accounts, you need to enter those Netbilling account numbers into the text box.
  
 
=== Outgoing Cross Sells ===
 
=== Outgoing Cross Sells ===
Line 75: Line 75:
 
* {$xsell.details.disclaimer}
 
* {$xsell.details.disclaimer}
  
You will also have to contact your partners and have them change the ip
+
You will also have to contact your partners and have them change the IP
 
for you in their XSELL_NETBILLING_SECURE_IPS configuration variable. This can
 
for you in their XSELL_NETBILLING_SECURE_IPS configuration variable. This can
be found in either their config.php or their config_override.php
+
be found in either their config.php or their config_override.php
 +
 
 +
'''In addition, you will need to have the sending IPs added to NetBilling's allowed IP list. '''<br>
 +
If you do this, you DO NOT need to fill in "Dynamic IP Code" for the outgoing cross sell.  If you setup a cross sell verification code with them instead, then place this code in the field "Dynamic IP Code". 
 +
 
 +
If the company who is sending you the cross sell does not have NATS, you can not use this method. Please view our [[NATS4 Process Gateway Cross Sales Outside NATS|NATS4 Process Gateway Cross Sales Outside NATS]] wiki.
  
 
=== Incoming Cross Sells ===
 
=== Incoming Cross Sells ===
Line 100: Line 105:
  
 
=== Extra Biller Options ===
 
=== Extra Biller Options ===
Netbilling has the following [[Extra Biller Fields]] available:
+
Netbilling has the following [[NATS4 Extra Biller Fields|Extra Biller Fields]] available:
  
 
* processor
 
* processor
Line 113: Line 118:
 
{if !$available_data.username}
 
{if !$available_data.username}
 
<TR><TD class="join_name">Username:</TD><TD class="join_value"><input class="join_input" type="text"
 
<TR><TD class="join_name">Username:</TD><TD class="join_value"><input class="join_input" type="text"
name="signup[username:1:6:16:::username_check]" value="{$vars.username}"><span class="join_error">{if $errors.username}<br>{$errors.username}</span>{/if}</TD></TR>
+
name="signup[username:1:6:16:::username_check]" value="{$mdata.username}"><span class="join_error">{if $errors.username}<br>{$errors.username}</span>{/if}</TD></TR>
 
{/if}
 
{/if}
 
{if !$available_data.password}
 
{if !$available_data.password}
 
<TR><TD class="join_name">Password:</tD><TD class="join_value"><input class="join_input" type="text"
 
<TR><TD class="join_name">Password:</tD><TD class="join_value"><input class="join_input" type="text"
name="signup[password:1:6:16:::password_check]" value="{$vars.password}"><span class="join_error">{if $errors.password}<br>{$errors.password}</span>{/if}</TD></TR>
+
name="signup[password:1:6:16:::password_check]" value="{$mdata.password}"><span class="join_error">{if $errors.password}<br>{$errors.password}</span>{/if}</TD></TR>
 
{/if}
 
{/if}
 
</pre>
 
</pre>
Line 125: Line 130:
  
 
If the Upsell is going to another NetBilling account, then the sender will need to enter a space-separated list of accounts that are authorized to use this feature under Authorized accounts in Step 6 of the Credit Card setup page.
 
If the Upsell is going to another NetBilling account, then the sender will need to enter a space-separated list of accounts that are authorized to use this feature under Authorized accounts in Step 6 of the Credit Card setup page.
 +
 +
== Package Plus ==
 +
The NetBilling Package Plus integration will be available after NATS4.1.4.1. If you would like to use the NetBilling Package Plus feature prior to this release, please send us a ticket. For more information on Package Plus, visit the [[NATS4 Package Plus|Package Plus]] wiki.
 +
 +
== Netbilling Configurations ==
 +
 +
Netbilling For '''non-recurring''' transactions, by default Netbilling is '''not''' sent the username (and no NetBilling subscription is created).  This means the transaction does not make a new member for '''non-recurring''' transactions.  There are two ways you can change this:
 +
 +
*''NETBILLING_NONRECURRING_USERNAME'' forces NATS to send the username to Netbilling, appending the transaction date to the username.  This makes sure all usernames remain unique in Netbilling.
 +
 +
*''NETBILLING_NONRECURRING_USERNAME_NODATE'' forces NATS to send the original, unmodified username to Netbilling for non-recurring signups.
 +
 +
Turn these on using:
 +
$config['NETBILLING_NONRECURRING_USERNAME_NODATE'] = 1;
 +
$config['NETBILLING_NONRECURRING_USERNAME'] = 1;
 +
 +
'''Note:'''
 +
 +
To use these configs, make sure REUSE_MATCHING_USERNAME config is on.  This can be done in the Configuration Admin --> Surfers --> Signup Form.
 +
Also turn on
 +
$config['NETBILLING_RENAME_USERNAME'] = 1;
  
 
== See Also ==
 
== See Also ==
 
* [[Post-Biller Templates]] -- editing the Return URL pages
 
* [[Post-Biller Templates]] -- editing the Return URL pages
 
* [[Netbilling v3 Upgrade Instructions]] -- upgrading Netbilling from version two to version three
 
* [[Netbilling v3 Upgrade Instructions]] -- upgrading Netbilling from version two to version three
* [[Purchasing Tokens Through Netbilling]] -- NATS lets surfers purchase tokens through NetBilling. The surfer only needs to enter their payment information once to purchase an unlimited number of tokens.
+
* [[Gateway tokens v4]] -- NATS lets surfers purchase tokens through NetBilling. The surfer only needs to enter their payment information once to purchase an unlimited number of tokens.
 +
 
 +
[[Category:NATS4 Biller Instructions]]

Latest revision as of 13:07, 20 February 2020

NATS 5
    Biller Instructions
NATS Biller List
2000Charge
2000Charge Gateway
2KCHARGE
A1Payments
Aebill
Aconti
Allopass
AltoBilling
Argus
Authorize.net
Bill1st Gateway
BillAPay Gateway
Billing Revolution
Billing United
Bit-Pay
BoaCompra
Braintree Payments
C2Bill
CardFlex
CCBill
CCBill Flexform
CCBill Web900
CashSend
CashtoCode
Centili
Centrobill
Clearcard
Clearcard IDV
Click and Buy
CoinGate
CoinPayments
CommerceGate
CurePay
DHD
DHDGateway
DIMOCO
EGatePay
ElectraCash
eMerchantPay Gateway
eMPPay.com
Epoch
Escalion
EuroBill
EPGBill.com
Ezic, Inc.
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
MobiusPay
MerlinBill
NETbilling
NETbilling Native
NetCash
NetMobile
Netpay International
NoCreditCard
OrbitalPay
Password By Phone
Pay4
Pay900
Payment Network
Paygarden
Paygea
PayPal
Paysite Cash
Payspace
Payspace Gateway
Plug'n Pay
Prime Orange
Probiller
PumaPay
Rocketfuel
RocketGate
RocketGate Native
RSBilling
RSBilling Native
SafeCharge
SafeCharge Native
Secure Billing Worldwide
Secure Billing Worldwide Gateway
Secure Trading
SecurionPay
SegPay
SegPay Gateway
SOFORTdauerauftrag
Sonic Bill
StandardBill
TrustCharge
Telecom
UKash
Vendo Services
Vendo
Verotel Pro
Voxtel
VXSBill
WebBilling
Wispay
WTS
WTSeu
Zombaio
Shopping Cart Sales
Switching From Epoch to Epoch EU
Members Section
Members Management
Adding a Member
View Member Details
Restricted Values
OpenID Connect
Mod Auth OpenIDC
    Adtool
GET /adtool/admin
GET /adtool/adtools
GET /adtool/adtool
GET /adtool/adtool-rules
GET /adtool/adtool-rule
GET /adtool/categories
GET /adtool/field-options
GET /adtool/field-types
GET /adtool/groups
GET /adtool/search
GET /adtool/templates
GET /adtool/types
GET /adtool/type
POST /adtool/adtool
POST /adtool/adtool-rule
POST /adtool/category
POST /adtool/field
POST /adtool/field-option
POST /adtool/group
POST /adtool/import
POST /adtool/type
PATCH /adtool/adtool
PATCH /adtool/adtool-group
PATCH /adtool/adtool-rule
PATCH /adtool/category
PATCH /adtool/field
PATCH /adtool/field-option
PATCH /adtool/group
PATCH /adtool/move
PATCH /adtool/restore-adtool
PATCH /adtool/restore-category
PATCH /adtool/restore-field
PATCH /adtool/restore-field-option
PATCH /adtool/restore-type
PATCH /adtool/type
DELETE /adtool/adtool
DELETE /adtool/adtool-rule
DELETE /adtool/category
DELETE /adtool/field
DELETE /adtool/field-option
DELETE /adtool/group
DELETE /adtool/type
    Affiliate
DELETE /affiliate/account-rep
DELETE /affiliate/account-type
DELETE /affiliate/affiliate
DELETE /affiliate/doc
DELETE /affiliate/group
DELETE /affiliate/permissions
GET /affiliate/account-changes
GET /affiliate/account-types
GET /affiliate/admin-settings
GET /affiliate/campaigns
GET /affiliate/current
GET /affiliate/current-permissions
GET /affiliate/docs
GET /affiliate/doc
GET /affiliate/groups
GET /affiliate/group
GET /affiliate/hits
GET /affiliate/link-styles
GET /affiliate/loginids
GET /affiliate/loginlog
GET /affiliate/manual-payout
GET /affiliate/news-sections
GET /affiliate/notes
GET /affiliate/notices
GET /affiliate/override
GET /affiliate/payout
GET /affiliate/payment-periods
GET /affiliate/payvia-types
GET /affiliate/payvia-type
GET /affiliate/permissions
GET /affiliate/programcampaigns
GET /affiliate/referrer
GET /affiliate/referring-urls
GET /affiliate/reps
GET /affiliate/rest-methods
GET /affiliate/search
GET /affiliate/search-limited
GET /affiliate/settings
GET /affiliate/skins
GET /affiliate/soap-functions
GET /affiliate/status
PATCH /affiliate/adminsettings
PATCH /affiliate/account-change
PATCH /affiliate/account-type
PATCH /affiliate/account-type-permissions
PATCH /affiliate/admin-setting
PATCH /affiliate/affiliate-account-type
PATCH /affiliate/affiliate-group
PATCH /affiliate/allsettings
PATCH /affiliate/account-rep
PATCH /affiliate/avatar
PATCH /affiliate/customs
PATCH /affiliate/defaults
PATCH /affiliate/details
PATCH /affiliate/override
PATCH /affiliate/password
PATCH /affiliate/payment-period
PATCH /affiliate/payvia
PATCH /affiliate/payvia-info
PATCH /affiliate/permissions
PATCH /affiliate/referrer
PATCH /affiliate/reset-api
PATCH /affiliate/reset-rss
PATCH /affiliate/reset-tos
PATCH /affiliate/rest-permissions
PATCH /affiliate/restore
PATCH /affiliate/restore-account-type
PATCH /affiliate/settings
PATCH /affiliate/soap-permissions
PATCH /affiliate/status
POST /affiliate/account-type
POST /affiliate/add
POST /affiliate/doc
POST /affiliate/group
POST /affiliate/invoice
POST /affiliate/manual-sale
POST /affiliate/note
    Biller
GET /biller/available
GET /biller/partner-available
GET /biller/billerdata
GET /biller/cascades
GET /biller/cascades-available
GET /biller/cascade-count
GET /biller/cascade-history
GET /biller/cascade-rules
GET /biller/cascade-rule
GET /biller/cascade-step-count
GET /biller/cascade-steps
GET /biller/cascade-detail
GET /biller/cascade-list
GET /biller/count
GET /biller/detail
GET /biller/fees
GET /biller/partner-fees
GET /biller/last_poll
GET /biller/partner-last-poll
GET /biller/list
GET /biller/partner-detail
GET /biller/partner-list
GET /biller/partner-shortnames
GET /biller/process_types
GET /biller/partner-process-types
GET /biller/shortnames
GET /biller/transaction_types
GET /biller/partner-transaction-types
GET /biller/taxes
POST /biller/add
POST /biller/cascade
POST /biller/cascade-rule
POST /biller/cascade-step
POST /biller/partner
PATCH /biller/cascade
PATCH /biller/cascade-rule
PATCH /biller/cascade-step
PATCH /biller/cascade-steps-reorder
PATCH /biller/fee
PATCH /biller/partner-fee
PATCH /biller/restore
PATCH /biller/restore-cascade
PATCH /biller/restore-partner
PATCH /biller/setting
PATCH /biller/partner-setting
PATCH /biller/tax
DELETE /biller/biller
DELETE /biller/cascade
DELETE /biller/cascade-rule
DELETE /biller/cascade-step
DELETE /biller/fee
DELETE /biller/partner-fee
DELETE /biller/partner
DELETE /biller/tax
    Codes
GET /codes/affiliate-codes
GET /codes/decode
GET /codes/linkcodes
GET /codes/strack
    Config
DELETE /config/setting
GET /config/section
GET /config/sections
PATCH /config/affiliate_default
PATCH /config/section
    Include
DELETE /include/include
DELETE /include/step
GET /include/include
GET /include/includes
GET /include/templates
PATCH /include/include
PATCH /include/restore
PATCH /include/step
POST /include/include
POST /include/step
    Mailing
DELETE /mailing/mailing
DELETE /mailing/mailing-rule
DELETE /mailing/queue
GET /mailing/mailing
GET /mailing/mailings
GET /mailing/mailing-rules
GET /mailing/mailing-rule
GET /mailing/queue
GET /mailing/removelist
PATCH /mailing/mailing
PATCH /mailing/mailing-rule
PATCH /mailing/removelist
PATCH /mailing/removelist-queue
PATCH /mailing/resend-queue
PATCH /mailing/restore-queue
PATCH /mailing/send-mailing
PATCH /mailing/send-test-mailing
POST /mailing/mailing
POST /mailing/mailing-rule
POST /mailing/removelist
    Maintenance
DELETE /maintenance/log
DELETE /maintenance/cache
GET /maintenance/admin-actions
GET /maintenance/log
GET /maintenance/logs
GET /maintenance/nats
GET /maintenance/report
GET /maintenance/report-progress
GET /maintenance/reports
GET /maintenance/server
GET /maintenance/table
GET /maintenance/tables
GET /maintenance/table-clean-count
GET /maintenance/table-clean-progress
PATCH /maintenance/log
PATCH /maintenance/report
PATCH /maintenance/table
    Member
GET /member/available_flags
GET /member/encryptusername
GET /member/authstring
GET /member/details
GET /member/flags
GET /member/loginlog
GET /member/matching
GET /member/notes
GET /member/notices
GET /member/restricted-values
GET /member/search
GET /member/suggestedcanceloffers
GET /member/surfer-actions
PATCH /member/details
PATCH /member/expiration
PATCH /member/expiremanual
PATCH /member/resend-transaction-email
PATCH /member/resend-transaction-postback
PATCH /member/restricted-value
PATCH /member/forget
PATCH /member/lock
PATCH /member/unlock
POST /member/flag
POST /member/login
POST /member/note
POST /member/restricted-value
DELETE /member/flag
DELETE /member/restricted-value
    Message
DELETE /message/message
DELETE /message/permanent
GET /message/count
GET /message/messages
GET /message/view
PATCH /message/read
PATCH /message/unread
PATCH /message/undelete
POST /message/message
    News
DELETE /news/entry
DELETE /news/section
GET /news/entry
GET /news/news
GET /news/sections
PATCH /news/entry
POST /news/entry
POST /news/section
    Notification
DELETE /notification/notification
DELETE /notification/permanent
GET /notification/count
GET /notification/notifications
GET /notification/view
PATCH /notification/read
PATCH /notification/unread
PATCH /notification/undelete
    Option
GET /option/options
GET /option/rule
PATCH /option/rule
PATCH /option/text
POST /option/rule
    Payment
DELETE /payment/invoice
DELETE /payment/payout-period
DELETE /payment/payvia-field
DELETE /payment/payvia-field-mc
DELETE /payment/payvia-rule
GET /payment/dump-format
GET /payment/dump-formats
GET /payment/invoices
GET /payment/payments
GET /payment/payment-dumps
GET /payment/payment-dump
GET /payment/payment-search
GET /payment/payvia
GET /payment/payvias
GET /payment/payvia-fields
GET /payment/payvia-field-mcs
GET /payment/payout-period
GET /payment/payout-periods
GET /payment/payvia-rules
GET /payment/payvia-rule
GET /payment/payviarule
PATCH /payment/copy-dump-format
PATCH /payment/default-payout-period
PATCH /payment/dump-format
PATCH /payment/duplicate-payvia
PATCH /payment/invoice
PATCH /payment/payment
PATCH /payment/payment-paid
PATCH /payment/payment-store
PATCH /payment/payment-unstore
PATCH /payment/payments
PATCH /payment/payments-unstore
PATCH /payment/payout-period
PATCH /payment/payout-period-affiliates
PATCH /payment/payvia
PATCH /payment/payvia-field
PATCH /payment/payvia-fields-reorder
PATCH /payment/payvia-field-mc
PATCH /payment/payvia-field-mcs-reorder
PATCH /payment/payvia-rule
PATCH /payment/payviarule
PATCH /payment/restore-payout-period
PATCH /payment/restore-payvia-field
PATCH /payment/restore-payvia-field-mc
POST /payment/check-dump
POST /payment/dump-format
POST /payment/import-dump
POST /payment/invoice
POST /payment/payout-period
POST /payment/payvia
POST /payment/payvia-field
POST /payment/payvia-field-mc
POST /payment/payvia-rule
    Program
DELETE /program/program
DELETE /program/payout-change
DELETE /program/payout-change-tier
GET /program/additional-payout-change-targets
GET /program/affiliate-available
GET /program/detail
GET /program/list
GET /program/options
GET /program/payout-changes
GET /program/redirect-available
GET /program/sites
GET /program/tours
GET /program/types
PATCH /program/default_payout
PATCH /program/details
PATCH /program/disable_affiliate
PATCH /program/disable_tour
PATCH /program/enable_affiliate
PATCH /program/enable_site
PATCH /program/enable_tour
PATCH /program/move-payout-change
PATCH /program/payout-change
PATCH /program/payout-change-tier
POST /program/new
POST /program/payout-change
POST /program/payout-change-tier
    Report
GET /report/affiliate-ratios
GET /report/hits
GET /report/hit-totals
GET /report/profitloss
GET /report/profit-loss
GET /report/fields
GET /report/focus
GET /report/focuses
GET /report/groups
GET /report/perspective
GET /report/perspectives
GET /report/report
GET /report/subscription
GET /report/surfer
GET /report/surferaction
GET /report/transactionpayouts
GET /report/transactions
GET /report/transaction
GET /report/report-widget
GET /report/widgets
GET /report/widget
GET /report/widget-info
GET /report/views
POST /report/focus
POST /report/group
POST /report/perspective
PATCH /report/focus
PATCH /report/focus-enabled
PATCH /report/focus-default
PATCH /report/focuses-reorder
PATCH /report/perspective
PATCH /report/perspective-group
PATCH /report/report-widget
PATCH /report/widget
DELETE /report/focus
    Reward
DELETE /reward/category
DELETE /reward/purchase
DELETE /reward/point
DELETE /reward/reward
GET /reward/categories
GET /reward/points
GET /reward/purchases
GET /reward/rewards
PATCH /reward/move-point
PATCH /reward/point
PATCH /reward/reward
PATCH /reward/ship-purchase
PATCH /reward/unship-purchase
POST /reward/category
POST /reward/point
POST /reward/reward
    Service
GET /service/check-functions
GET /service/condition
GET /service/countries
GET /service/country
GET /service/datetime
GET /service/languages
GET /service/periods
GET /service/ping
GET /service/project
GET /service/rule-condition-data
GET /service/rule-info
GET /service/stats-breakdowns
GET /service/timezone
GET /service/timestamp
POST /service/sendemail
    Site
GET /site/base-templates
GET /site/billers
GET /site/cookies
GET /site/coupon
GET /site/coupons
GET /site/coupon-revisions
GET /site/email-settings
GET /site/groups
GET /site/option
GET /site/options
GET /site/options-available
GET /site/option-fields
GET /site/option-rules
GET /site/option-rule
GET /site/option-type
GET /site/option-types
GET /site/programs
GET /site/redirect
GET /site/redirects
GET /site/redirect-rules
GET /site/redirect-rule
GET /site/site-list
GET /site/site
GET /site/site-notices
GET /site/site-partner
GET /site/site-partners
GET /site/site-type
GET /site/sites
GET /site/template
GET /site/templates
GET /site/template-sections
GET /site/template-sites
GET /site/tour
GET /site/tours
GET /site/tour-emails
GET /site/tour-notices
POST /site/coupon
POST /site/group
POST /site/option
POST /site/option-rule
POST /site/redirect
POST /site/redirect-rule
POST /site/site-partner
POST /site/site-tour
POST /site/copy-template
POST /site/tour
PATCH /site/cookie
PATCH /site/coupon
PATCH /site/duplicate-option
PATCH /site/email-settings
PATCH /site/group
PATCH /site/move
PATCH /site/option
PATCH /site/option-rule
PATCH /site/redirect
PATCH /site/redirect-rule
PATCH /site/reset-coupon
PATCH /site/restore-group
PATCH /site/restore-option
PATCH /site/restore-redirect
PATCH /site/restore-site
PATCH /site/restore-site-partner
PATCH /site/restore-tour
PATCH /site/site
PATCH /site/site-partner
PATCH /site/template
PATCH /site/tour
DELETE /site/cookie
DELETE /site/group
DELETE /site/option
DELETE /site/option-rule
DELETE /site/site
DELETE /site/site-partner
DELETE /site/redirect
DELETE /site/redirect-rule
DELETE /site/template
DELETE /site/tour
DELETE /site/tour-field
    Skin
DELETE /skin/skin
DELETE /skin/template
GET /skin/colors
GET /skin/export
GET /skin/skins
GET /skin/sections
GET /skin/templates
GET /skin/template
PATCH /skin/colors
PATCH /skin/flush
PATCH /skin/skin
PATCH /skin/template
POST /skin/copy-template
POST /skin/import
POST /skin/skin
POST /skin/template
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

Please don't test your biller setup with NATS4 Netbilling's test account—it won't work correctly.

Note: these instructions describe using Netbilling as a gateway. If you want to use Netbilling as a regular biller, please see the NATS4 Netbilling Native article.

Set up on Netbilling's Website

Register an account on Netbilling's website.

Please note: Netbilling uses the term Access Keyword to describe two different settings. To distinguish the two different settings, I've placed my own terms in brackets after the Netbilling terms.

To process transactions, in the Netbilling administration panel under "Account Setup" -> "Account Management" -> "Access Security", check the box next to "Enable Native Direct Mode v.3 (SAS) Channel" and enter your server's IP address in the box labeled "Specify Trusted Static IP Addresses allowed to originate Direct Mode transactions". Transactions will not process through Netbilling if you don't do this.

Reporting keyword: You will need to add a reporting keyword for each site in Netbilling. You can do this by going to "Site Tools" -> "Site Tags" -> "config" for each site -> under the section "Data Retrieval Interface", there is a box for "Access keywords" [Reporting Keyword]. You need to enter a keyword here to be added later in the NATS admin. You need to do this for each of your sites. Also, under "Account Setup" -> "Account Management" -> "Access Security" -> "Data Retrieval Interface", you need to check the box next to "Enable Data Retrieval Interface v1.x" and add your server's IP address to the "Reporting Client IP Addresses section". You need to do this to track rebills, refunds, chargebacks, etc.

Set up Netbilling in NATS

Note: You must have PHP's mcrypt installed in order to set up Netbilling. Please see the PHP documentation.

Billers Admin

To begin setting up Netbilling as a biller in NATS, go to the Billers Admin. Scroll down to the "Biller" drop-down menu, select Netbilling, and click "Add."

Note: If you don't see Netbilling as a biller in NATS4, put in a support ticket, as you may need an updated version of NATS.

When prompted, fill in the 12-digit Netbilling Account Number that you received from Netbilling under the "Account Info" section. You can optionally enter your dynamic IP code as well. If you were not provided with this information, please contact your biller to receive it.

Sites Admin

Next, go to the Sites Admin, create or edit a tour, and scroll down to the "Biller Details" section. Enter your Netbilling Site Tag and Access Keyword [Reporting Keyword] here. You can find both of these by logging into Netbilling, going to Setup, Site Tools, and Site Tags -- the site tag can be found in the "Site tag" column on the main Site Tags screen, or under "Basic Information" on the edit site screen; the access keyword [Reporting Keyword] is under the Scriptable Reporting Interface link. You may also enter an Access Keyword [Control Keyword] for cross-sells and instant upgrades (see below). This can be found in Netbilling's admin. Just go to "Site Tools" -> "Site Tags", then click "config" on the site you want to set this up for. Your Access Keyword will be under the "Control CGI advanced options" section on the next page.

Once you have done this, scroll down to the section labeled "Join Options for this Tour" and click the "Edit Option Details for this tour" icon that corresponds to the join option you wish to use. In the "Biller Codes" section on the next page, locate the "NETBILLING" options. All of these options are optional -- simply fill out the provided fields if you wish to use these features.

NOTE: If you are using a $0 trial option, you will need to set the NETBILLING_POLL_BACKDAYS in the configuration admin under the billing section to a number of days equal to 1 more than your longest trial length. This is to ensure that the conversions are properly captured from NetBilling's system.

Once you have completed these steps, save your join option details. Netbilling will now be configured for basic use as a biller in NATS.

Netbilling Cross-Sells

Currently NATS only supports NetBilling Gateway cross sells between NATS clients.

In Netbilling, under "Account Setup" -> "Account Management" -> "Credit Cards" -> "Step 6", you need to check the box to "Enable PCI Repeat Billing". If you are going to be up-selling or cross-selling to your own Netbilling account, you do not need to enter any account numbers into the text box in Step 6. If you are going to be up-selling or cross-selling to different Netbilling accounts, you need to enter those Netbilling account numbers into the text box.

Outgoing Cross Sells

Account, Site Tag, Pass Code, Initial Days, Initial Dollars, Recurring Days, Recurring Dollars, Ref Code and Integrity Key are provided by the person you are sending cross sells to. The domain is the base domain of their NATS install. So if their NATS is at http://www.democash.com then http://www.democash.com is the domain you need to enter. Only set domain if the cross sell goes to another affiliate program. Domain should not be set if the cross sell is for another site in your program.

NATS will automatically display a checkbox accompanied by the description entered in the Upsells and CrossSells Admin. If you enter a disclaimer in the Upsells and CrossSells Admin then you can also access that via {$xsell.details.disclaimer}.

The main xsell tags available for use in this section are:

  • {$xsell.details.name}
  • {$xsell.details.description}
  • {$xsell.details.disclaimer}

You will also have to contact your partners and have them change the IP for you in their XSELL_NETBILLING_SECURE_IPS configuration variable. This can be found in either their config.php or their config_override.php.

In addition, you will need to have the sending IPs added to NetBilling's allowed IP list.
If you do this, you DO NOT need to fill in "Dynamic IP Code" for the outgoing cross sell. If you setup a cross sell verification code with them instead, then place this code in the field "Dynamic IP Code".

If the company who is sending you the cross sell does not have NATS, you can not use this method. Please view our NATS4 Process Gateway Cross Sales Outside NATS wiki.

Incoming Cross Sells

To set up an incoming cross sell, go to the Upsells and Cross Sells Admin and click on the Incoming Cross Sells tab. Select NETbilling from the Biller drop down menu, then select what site and program this cross sell relates to. Click Add New Option once you have selected those.

On the next page, you can select your site/program again. Under details, you will have to fill out the title of your cross sale. Initial Days, Initial Dollars, Recurring Days, and Recurring Dollars are the initial and recurring period and amounts for this option. Under Biller Info, you can also enter an Auth Amount, which is only necessary with a $0 initial join. You can also choose to disable AVS and disable Fraud Checking. Set up your discount upgrade price in Netbilling's system and add it to the Discount Upgrade Price field. When you are done configuring your cross sell, click Add New Option.

For affiliates to send you cross sells (or you to send cross sells to yourself), you'll need to add the IPs to XSELL_NETBILLING_SECURE_IPS configuration variable.

Upgrade Subscription

To set up an Upgrade subscription you need to use the following link in your limited members area for user upgrades:

  • http://<linkdomain>/signup/upgradeplus.php?site=<siteid>&username=<username>

Where <linkdomain> is the linkdomain for the site, <siteid> is the siteid for the site in NATS, and <username> is the username for the user that is trying to upgrade (To get the Username via PHP you would use <?=$_SERVER['REMOTE_USER']?>)

You will also need to add this line to your configuration file to turn on the trials with netbilling; $config['NETBILLING_UPGRADES'] = 1;

Extra Biller Options

Netbilling has the following Extra Biller Fields available:

  • processor

Using Netbilling as a HTTPS Gateway

Please see the the HTTPS Gateways article.

Auto Cascading to Netbilling

When you autocascade, your member does not get a chance to specify their username on the normal prejoin form. As a result, you must present this input on the gateway_join template.

{if !$available_data.username}
<TR><TD class="join_name">Username:</TD><TD class="join_value"><input class="join_input" type="text"
name="signup[username:1:6:16:::username_check]" value="{$mdata.username}"><span class="join_error">{if $errors.username}<br>{$errors.username}</span>{/if}</TD></TR>
{/if}
{if !$available_data.password}
<TR><TD class="join_name">Password:</tD><TD class="join_value"><input class="join_input" type="text"
name="signup[password:1:6:16:::password_check]" value="{$mdata.password}"><span class="join_error">{if $errors.password}<br>{$errors.password}</span>{/if}</TD></TR>
{/if}

Upsells

In the Configuration Admin, under the Billers section, you will need up add the IP of the system sending the upsell to the XSELL_NETBILLING_SECURE_IPS. Even your own IP will need to be added if you are sending this upsell to yourself.

If the Upsell is going to another NetBilling account, then the sender will need to enter a space-separated list of accounts that are authorized to use this feature under Authorized accounts in Step 6 of the Credit Card setup page.

Package Plus

The NetBilling Package Plus integration will be available after NATS4.1.4.1. If you would like to use the NetBilling Package Plus feature prior to this release, please send us a ticket. For more information on Package Plus, visit the Package Plus wiki.

Netbilling Configurations

Netbilling For non-recurring transactions, by default Netbilling is not sent the username (and no NetBilling subscription is created). This means the transaction does not make a new member for non-recurring transactions. There are two ways you can change this:

  • NETBILLING_NONRECURRING_USERNAME forces NATS to send the username to Netbilling, appending the transaction date to the username. This makes sure all usernames remain unique in Netbilling.
  • NETBILLING_NONRECURRING_USERNAME_NODATE forces NATS to send the original, unmodified username to Netbilling for non-recurring signups.

Turn these on using:

$config['NETBILLING_NONRECURRING_USERNAME_NODATE'] = 1;
$config['NETBILLING_NONRECURRING_USERNAME'] = 1;

Note:

To use these configs, make sure REUSE_MATCHING_USERNAME config is on. This can be done in the Configuration Admin --> Surfers --> Signup Form. Also turn on

$config['NETBILLING_RENAME_USERNAME'] = 1;

See Also