Gateway Biller Details Query Letter

From TMM Wiki
Revision as of 12:29, 30 April 2010 by TMMJoe (talk | contribs)
Jump to navigationJump to search

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


Basic Information


  • Company Name:


  • Your name:


  • Your email:


  • Your phone number:


  • Your TMMID (you must register for a TMMID at tmmid.com)


  • 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):


  • How does your system identify members?:


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


Required Fields and 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.

Gateway Communication

Field                      Required              Description                                                                                    
     
     
     
     
     
     
     
     
     
     
     
     
     


  • What fields must NATS send to process an initial transaction?:


  • Which field should NATS use for our passthrough variable?:


  • In your response, how do we identify approved transactions?:


  • In your response, which field contains the transactionid?:


  • In your response, which field contains the subscriptionid?:


  • In your response, which field contains the amount?:


  • In your response, which field contains the currency (required for multi-currency support)?:


Notification of Initial, Rebill, Credit, and Chargeback Transactions

You need to send information about 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)


  • Do you have a postback system?:


  • Do you have a reporting script?:


  • Are initials reported in either (optional. 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 answer the following questions:


  • What fields are contained in the postback?:


  • What types of transactions will be posted (example: rebill, return/credit, cancel, expire)?:


  • How should NATS identify the transaction type?:


  • How can NATS identify approved transactions?:


  • Which field contains our passthrough variable (if posting initials)?:


  • Which field contains the transactionid?:


  • Which field contains the subscriptionid?:


  • Which field contains the amount?:


  • Which field contains the 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.


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


  • What fields are contained in the response?:


  • What types of transactions will be reported (example: rebill, return/credit, cancel, expire)?:


  • How should NATS identify the transaction type?:


  • How can NATS identify approved transactions?:


  • Which field contains our passthrough variable (if reporting initials)?:


  • Which field contains the transactionid?:


  • Which field contains the subscriptionid?:


  • Which field contains the amount?:


  • Which field contains the currency (required for multi-currency support)?:


  • Are they any restrictions on the reporting (ie: date range or frequency)?:


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?:


Gateway Communication

  • What fields must NATS send to your transaction form?:


  • Which field should NATS use to send the price?:


  • In your response, how do we identify approved transactions?:


  • In your response, which field contains the transaction identifier?:


  • In your response, which field contains the subscription identifier?:


Other Special Features

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

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




Retrieved from "https://tmmwiki.com/index.php?title=Gateway_Biller_Details_Query_Letter&oldid=9187"