Third-Party Biller Details Query Letter

Integration Document and Testing Information

Please email your your answers to this questionnaire, your full integration document, your testing account information, and your test purchase information to rob@toomuchmedia.com.

Basic Information

• Company name:

• Your name:

• Your email:

• Your phone number:

• What processing types do you support (for example: CC, Check, Dialer):

• How does your system identify members?:

• Do you show all price points on your join form (yes/no):

• What transaction types do you support (for example: initial, credit, void)?:

Join Page Fields

We need a list of fields NATS should send to your join page. For each field, please list whether it's required or optional.

• What field should we use to send you the site identifier?:

• What field should we use to send you the option selected by the consumer?:

• What field should we use to send you the consumer's username?:

• What field should we use to send you the consumer's password?:

• What field should we use to send you the passthrough variable?:

Note: we must send you the passthrough variable because you must return it to us later. Note: the passthrough variable must support up to 255 case-sensitive characters.

Postback Script

You need to send NATS a postback when the consumer joins. We support two postback options:

1. Your postback script sends us all information about the transaction.
2. Your postback script sends us enough information to make the consumer active.

Please tell us which option you will implement:

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:

1. Your system sends NATS a postback.
2. NATS polls your reporting script on a regular basis. (Preferred)

Please tell us whether you will provide a postback, reporting script, or both:

Transaction Notifications Using Postbacks

If you elect to send NATS information about transactions using a postback, please answer the following questions:

• What fields are contained in the postback?:

• How can NATS identify approved transactions?:

• Which field contains our passthrough variable?:

• Which field identifies the price option?:

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 answer the following questions:

• What fields must NATS send to your reporting script?:

• What fields are contained in your response?:

• How can NATS identify initial, rebill, credit, and chargeback transactions?:

• How can NATS identify approved transactions vs failed transactions?

• Which field contains the required subscription identifier?:

• Which field contains the required transaction identifier?:

• Which field contains the required original transaction identifier for credits and chargebacks?

• Is the passthrough variable available on your report?:

Notification of Expirations

You need to tell NATS either when a member has expired or when a member will expire. NATS can get that information in two formats:

1. Your system sends NATS a postback.
2. NATS polls your reporting script on a regular basis. (Preferred)

Please tell us whether you will provide a postback, reporting script, or both:

Expiration Notifications Using Postbacks

If you elect to send NATS information about expirations using a postback, please answer the following questions:

• What fields are contained in the postback?:

• What field contains the unique subscription I.D.?:

• Is the expiration immediate:?

• If the expiration isn't immediate, which field contains the expiration date?:

Expiration Notification Using a Poll to a Reporting Script

If you elect to let NATS get information about expirations by accessing a reporting script, please answer the following questions:

• What fields must NATS send to your reporting script?:

• What fields are contained in your response?:

• What field contains the unique subscription I.D.?:

• Is the expiration immediate:? {BL}}

• If the expiration isn't immediate, which field contains the expiration date?:

Return URL

Not applicable to dialer billers

Your system must send the consumer to a NATS return URL after both approvals and denials.

• Does the program owner need to set the return URL in your system?:

• Can NATS send the return URL in its join form query (preferred)?:

• What fields does your return URL send?:

• Which field contains the required passthrough field?:

• How do we identify an approved transaction?:

IP Addresses

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:

URL:

Instant Upgrades (Optional)

Does your system support instant upgrades?:

If your system does support instant upgrades, it must send a postback to NATS. Please answer the following questions about the instant upgrade postback:

• What fields are contained in the postback?:

• How can NATS identify approved transactions?:

Cross Sells and Upsells (Optional)

Does your system support cross sells?:

Does your system support upsells?:

If you system supports cross sells, upsells, or both, please answer the following questions:

• What fields should NATS send to you?:

• What field should NATS use to send the passthrough variable?:

Your system must return the cross sell status to the NATS process script.

• What fields will you send to the process script?:

• Which field contains the NATS passthrough variable?:

Check Billers (Optional)

• How do we identify transaction authorizations?:

• How do we identify transaction settlements?:

Other Special Features

Do you have any special features not addressed by this document?:

If you answered yes, please describe the special features below.