Third-Party Biller Details Query Letter
Please email your your answers to this questionnaire, your full integration document, your testing account information, and your test purchase information to cho@toomuchmedia.com.
Find a PDF copy of this file here: Third Party Biller Details Form
Basic Information
- Company Name:
- Your name:
- Your email:
- Your phone number:
- Your TMMID (you must register for a TMMID at tmmid.com)
- Your NATS version number:
- Name of Developer:
- Developer's phone number:
- Developer's AIM/ICQ:
- Name of Project Manager:
- Project Manager's phone number:
- Project Manager's AIM/ICQ:
- What processing types do you support (for example: CC, Check, Dialer):
- What transaction types do you support (for example: initial, credit, void)?:
Definitions
- transactionid -- a unique identifier for each transaction
- subscriptionid -- a unique identifier for each subscription
- transaction reference id -- for credits, chargebacks, and reversals. The identifier for the original transaction being credited/etc.
- passthrough variable -- a variable we can use to pass custom information, which will be included with initial transactions (for postbacks and/or polling).
- instant upgrade -- an immediate upgrade from trial to full membership status. Force a rebill to occur now, instead of the end of the initial period.
- cross sell -- a sale to a different site, that is made at the time of the initial signup.
- upsell -- a sale to a different site, that is made after the initial signup. Upsells happen without requiring the credit card number.
Join Page
To integrate with NATS as a 3rd party biller, there needs to be a url we redirect surfers to in order to view your join page
What is the url we need to redirect to?
Please list what fields we can send to your join form url, and whether they are required by your system
| Field | Required | Type | Max Length | Description |
Required fields to be sent:
- passthrough variable.
Return URL
After the surfer has filled out your join form, your system needs to redirect the surfer back to our system, whether or not the surfer joined.
How do we set the URL to redirect to?
Please list the fields that will be passed to us on the return url:
| Field | Description |
Required fields:
- passthrough variable
- Indication whether member was approved.
Notification of Initial, Rebill, Credit, and Chargeback Transactions
You need to send information about initial, rebill, credit, and chargeback transactions. NATS can get that information in two formats:
- Your system sends NATS a postback.
- NATS polls your reporting script on a regular basis. (Preferred)
NOTE: Notification of the surfer joining must be sent via postback, but the rest of the transactions can be recorded either through a postback or a reporting script.
- Do you have a postback system?:
- Do you have a reporting script?:
- Are initials reported in either (optional for reporting script. To process initials, we need our passthrough variable)?:
Transaction Notifications Using Postbacks
If you elect to send NATS information about transactions using a postback, please fill in the following table with the fields sent:
| Field | Description |
Fields required by NATS:
- Transaction Type
- Indication whether transaction was approved
- Passthrough variable (if posting initials)
- Transactionid
- Subscriptionid
- Reference Transactionid (required for credits, chargebacks, and reversals)
- Join Option Identifier
- Amount
- Currency (required for multi-currency support)
IP Addresses (for postbacks only)
Please list every IP address that will send information to NATS:
Optionally, please give us a URL where we can download an updated list in a computer readable format of IP addresses that will send information to NATS. To make upgrades to your service easy, we highly recommend you provide this URL.
For example, a url like this:
https://example.com/ip_list.txt
Which contains:
1.2.3.4|1.2.3.5|1.2.3.6|1.2.3.7
URL:
If you are not able to provide us with an updated list of IP addresses, how can nats verify that a post is from your system?
Transaction Notification Using a Poll to a Reporting Script
If you elect to let NATS get information about transactions by accessing a reporting script, please fill in the following information.
What is the URL of the reporting script?
What is the format of the reporting script (csv, xml, SOAP)?
Please list the fields that should be sent to the reporting script:
| Field | Required | Type | Description |
Please fill in the following table with the fields returned for each transaction:
| Field | Description |
Required fields: Fields required by NATS:
- Transaction Type
- Indication whether transaction was approved
- Passthrough variable (if reporting initials)
- Transactionid
- Subscriptionid
- Reference Transactionid (required for credits, chargebacks, and reversals)
- Join Option Identifier (if reporting initials)
- Amount
- Currency (required for multi-currency support)
- Date
Are there any restrictions on the reporting (ie: date range or frequency)?:
Instant Upgrades (Optional)
Does your system support instant upgrades?:
What is the format of the post (ie https post, XML, SOAP, etc)?
Please list what fields we can send to your system for instant upgrades, and whether they are required by your system
| Field | Required | Type | Max Length | Description |
Please list what fields are returned in your response
| Field | Description |
Required fields for the response:
- Instant upgrade approval (yes or no)
Cross Sells and Upsells (Optional)
Do you support cross sells?:
Do you support cross sells across accounts, or only between sites on the same account?
Please list what fields we can send to your join form for cross sell transactions, and whether they are required by your system
| Field | Required | Type | Max Length | Description |
Required fields for the redirect to your form:
- passthrough variable for the cross sell, separate from the passthrough for the main sale. If you support more than one cross sell at a time, there needs to be a separate passthrough variable for each cross sell.
If you support cross sells, you must send a separate post for each cross sell, to the receiver of the cross sell (If Merchant A is cross selling to Merchant B, merchant A needs to receive a post for the main sale, Merchant B needs to receive a post for the cross sale).
Please list what additional fields will be sent for the cross sell in the initial postback:
| Field | Description |
Required fields for the postback (beyond the normal postback fields:
- passthrough variable for the cross sell.
Do you support Upsells?:
Do you support upsells across accounts, or only between sites on the same account?
What url should we send members to in order to purchase upsells?
Please list what fields we can send to your upsell form upsells, and whether they are required by your system
| Field | Required | Type | Max Length | Description |
Required fields for the redirect to your form:
- passthrough variable for the upsell, separate from the passthrough for the main sale. If you support more than one upsell at a time, there needs to be a separate passthrough variable for each upsell.
If you support upsell, you must send a separate post for each upsell, to the receiver of the upsell (If Merchant A is upselling to Merchant B, Merchant B needs to receive a post for the upsell).
Please list what additional fields will be sent for the cross sell in the initial postback:
| Field | Description |
Required fields for the postback (beyond the normal postback fields:
- passthrough variable for the upsell.
Other Special Features
Do you have any special features not addressed by this document?:
If you answered yes, please describe the special features below.
