Difference between revisions of "ConnectBillling"
From TMM Wiki
Jump to navigationJump to search| (5 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
{{NATS4 Manual}} | {{NATS4 Manual}} | ||
| − | == Setting Up at ConnectBilling | + | == Setting Up at ConnectBilling == |
Before you can begin configuring ConnectBilling as a biller in NATS, you must first register an account through ConnectBilling themselves. You can find out more about this process at their website: https://www.connectbilling.com/ | Before you can begin configuring ConnectBilling as a biller in NATS, you must first register an account through ConnectBilling themselves. You can find out more about this process at their website: https://www.connectbilling.com/ | ||
| Line 41: | Line 41: | ||
When you have finished filling out the required fields, click Save Changes. | When you have finished filling out the required fields, click Save Changes. | ||
| + | == Additional information == | ||
| + | ConectBilling support 3DS for both the hosted form and the gateway integrations. If you are using the gateway integration, you have an option to auto fail all transactions that require 3DS by disabling the ALLOW_CBILLING_TO_INITIATE_3DS config setting.<br /> | ||
| + | |||
| + | In order to send values needed for the device fingerprinting for 3DS for the gateway integration, you will need to use the [[NATS4_Extra_Biller_Fields|nextra]] feature and add the following to your join or the gateway_join template. | ||
| + | <pre> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_java_enabled]" value="<values goes here>"> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_language]" value="<values goes here>"> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_color_depth]" value="<values goes here>"> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_screen_height]" value="<values goes here>"> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_screen_width]" value="<values goes here>"> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_tz]" value="<values goes here>"> | ||
| + | <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_challenge_window_size]" value="<values goes here>"> | ||
| + | </pre> | ||
[[Category:NATS4 Biller Instructions]] | [[Category:NATS4 Biller Instructions]] | ||
Latest revision as of 11:44, 17 August 2021
NATS 4
|
|---|
Setting Up at ConnectBilling
Before you can begin configuring ConnectBilling as a biller in NATS, you must first register an account through ConnectBilling themselves. You can find out more about this process at their website: https://www.connectbilling.com/
While signing up for ConnectBilling, make sure that you take down the information provided by them, including your Transaction Key, Product Code
Setting Up ConnectBilling in NATS
Billers Admin
If you wish to set up ConnectBilling to process transactions in NATS4, go to the Billers Admin. In the Billers Admin, scroll down to the "Setup New Biller" drop-down menu, select ConnectBilling, and click "Add New Option."
When prompted, enter your ConnectBilling Transaction Key. If you were not provided with the required information, please contact ConnectBilling.
Sites Admin
To continue setting up ConnectBilling in NATS4, go to the Sites Admin. On the main page, create a new tour or edit an already existing one, then scroll down to the "Biller Details" section. Enter the Product Code and choose if you want to set ConnectBilling to Use Hosted Forms or uncheck to Use Gateway Join Forms-- this is an optional setting. Under Join option section, Enter Option Code for each join options.
Additionally, you must add rules in order for this join option to be displayed on your join page. You can do so by using the "Rules" action icon, marked with purple arrows. For more information on Rules in NATS4, please see our NATS4 Rules wiki article.
Upsells Admin
ConnectBilling also supports cross sale transactions in NATS4. To begin configuring NATS to accept these transactions, go to the Upsells Admin. For more information on Cross Sales in NATS, please see our NATS4 Configuring Cross Sells wiki article.
Incoming Cross Sales
To set up incoming cross sales to process transactions through ConnectBilling, go to the Upsells Admin and click the "Incoming Cross Sells" tab at the top of the page. Select ConnectBilling from the "Biller" drop-down menu, select the site and the program that you want to associate with this cross sale option, then click Add New Option.
When prompted, enter the title and fees/lengths of your join options. Under "Biller Info," enter your ConnectBilling option code, initial cost, initial days, recurring cost and recurring days. Click save changes when you have filled out the required fields, and your cross sale should now be configured in NATS.
Outgoing Cross Sales
In the Upsells Admin, begin by configuring an Outgoing Cross Sale (if applicable). To do so, scroll down to the "Biller" drop-down menu and choose ConnectBilling from your list of options.
On the next page, you will be prompted for a variety of information. Fill out the title, description, and disclaimer for your cross sale option, and choose if you want cross sales enabled for all join options. Next, fill in your Transaction Key, Product Code, Option Code, Processor and the length and cost of your initial/recurring memberships, your Ref Code, and site Domain.
When you have finished filling out the required fields, click Save Changes.
Additional information
ConectBilling support 3DS for both the hosted form and the gateway integrations. If you are using the gateway integration, you have an option to auto fail all transactions that require 3DS by disabling the ALLOW_CBILLING_TO_INITIATE_3DS config setting.
In order to send values needed for the device fingerprinting for 3DS for the gateway integration, you will need to use the nextra feature and add the following to your join or the gateway_join template.
<input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_java_enabled]" value="<values goes here>"> <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_language]" value="<values goes here>"> <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_color_depth]" value="<values goes here>"> <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_screen_height]" value="<values goes here>"> <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_screen_width]" value="<values goes here>"> <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_browser_tz]" value="<values goes here>"> <input type="hidden" name="nextra[CBILLING][subscription][bill_to][3ds_challenge_window_size]" value="<values goes here>">
