Index
Order Types
Responding to Your Customers
Custom Messaging
Securing Your Web Pages
Testing Your Web Pages
Broadcast Email
Secure Secondary Posting
Setting Up
Implementing
Reporting
Automatic Retry
Troubleshooting
 
Additional Processing
Netcentives
Tags
FAQs

Secure Secondary Posting

Send a copy of your incoming transaction's data to another site of your choice. Using SSL (Secure Socket Layer) encryption to protect your customer's information, ITPS 2.0 offers support for real-time secondary posting to multiple sites, with automatic retry and on-line reporting to track your posts. The Secure Secondary Posting feature is driven by a protected database configuration, so information about your secondary destination remains private. The Secure Secondary Posting feature supports transmission via both "GET" and "POST" methods, as well as multiple destinations.

 

Setting up a Destination for Secure Secondary Posting

 

In order to set up a destination to receive copies of your incoming transactions, you will need to call your account team to request a Secure Secondary Posting implementation. The destination needs to be able to process a standard URL encoded string, and it needs to reside on a secure web server that supports SSL. You will also need to have a SAF-T (Secure Automated File Transfer) account to transfer any failed transmissions. The SAF-T account must have the encryption option activated -- no transaction data will be transferred unencrypted. You may use the same SAF-T account for more than one Secure Secondary Posting destination. You will need the following information to initiate a Secure secondary Post implementation:

Publication Description The four character ItemCode used to uniquely identify the publication submitting transactions
Destination URL A CGI or program that is able to accept secure http requests and process URL encoded strings.
Transmission Method Either "GET" or "POST"
PGP Key The encryption key to be used to encrypt file transfers in the event that a transmissin to your secondary destination fails repeatedly

As part of the implementation process, a SAF-T (Secure Automated File Transfer) account will be created for you if you do not already have an existing account. You will receive the following information back from your account team when the implementation is complete:

Destination Identification Number (DIN) The number that the system will use to uniquely identify your secondary destination. You will use this number on your web page, enabling you to keep all the other information about your secondary destination private.
SAF-T Configuration Identification Number (SCIN) The number that uniquely identifies your SAF-T account
SAF-T account user ID and password If a new SAF-T account is created.

Please allow two weeks for the configuration and testing of your Secure Secondary Post destination.