Notes on Renewals

Unsolicited Identified Renewals allow customers to submit renewals on existing accounts from a web page. The renewals are unsolicited because the piece of media that motivated the customer to go to the web page and submit the renewal will not be apparent when the transaction is formatted and processed. You will need to supply source code/key code on the web page to mark these renewals as unsolicited.

The expected sequence of interface with the customer is that the customer will first submit an Inquiry. The return page from the Inquiry will post the matchcode (for identified customers) as a hidden html tag on the response page. The customer will then have the option to choose a button that will take them to a Renewal page. The Renewal page will be prepopulated with the customer's account information. It will contain fields that specify the term and amount of the renewal. A default renewal offer is available that offers the customer the same term and amount of the last non-donor order on their mainfile record. The transactions will be subject to order hygiene (matchcode check digit, credit card check digit, and an optional on-line credit card authorization). Successful transactions will be inserted into the ITPS database, where they will be extracted once per day and formatted for processing to the subscriber mainfile.

The following fields are required for a Renewal transaction:

HTML Tags

• ItemCode (4 character pub description)
• Matchcode (Value will be supplied by Inquiry via double bar substitution)
• Term (term@amount)
• SourceCode (1 byte)
• KeyCode (3 bytes)

There are two options for using the Unsolicited Renewal feature: the first requires the use of custom html pages; the second utilizes system-generated default response pages.

Using Custom Replies

To use custom reply pages, you will need to construct a custom reply page that is identified in the iResponse tag on your Inquiry web page. That form will have an OrderType of "Reply Only", and an iResponse tag that returns the actual web form to take the Renewal information.
Example:
<input type=hidden name="iResponse" value="Inquiry_Response">

The custom reply page (Inquiry_Response) will use double bar substitution to pass the matchcode and other double bar substituted information as hidden tags within the form associated with the "Renewal" button on the iResponse page.

Example (not a complete form):
<form action="http://www.neodata.com/ITPS2.cgi" method=post>
<input type=hidden name=ordertype value="Reply Only">
<input type=hidden name=matchcode value="||matchcode||">
<input type=hidden name=iResponse value="SolicitRenewal">
<input type=submit value="Renew My Subscription">

You may use double bar substitution to prepopulate the Renewal form, using any of the standard tags available from the Inquiry page. Any field that is used for prepopulation must be passed in only the "Reply Only" page, however. The Renewal form will have an ordertype of "Renewal".

Using Default Replies

To use the system-generated default pages, you need only include a "DoRenewal" html tag on your Inquiry page, plus the required for the Renwal transaction. ITPS will scan for this option tag, and add the appropriate html to the default response page for successful lookups.

Example (not a complete form):
<form action="http://www.neodata.com/ITPS2.cgi" method=post>
<input type=hidden name=ordertype value="Inquiry">
<input type=hidden name=DoRenewal value="On">
<input type=hidden name=SourceCode value="X">
<input type=hidden name=KeyCode value="XXX">
<input type=submit value="Account Lookup">