Sankalp Shakti Demo

Step 2: Your server builds a Confirmation Page
Your server-side script will build an order confirmation page, displaying the full details of the purchase
to the customer, including their billing and delivery addresses, basket contents, total order value and
contact details.
This script will also place an HTML FORM on that page with the action set to the Sage Pay Form
registration page. That form will also contain four hidden fields:
VPSProtocol – which lets our system know the version of our messages you are using (the current
version is 3.00).
TxType – this lets us know which transaction type you wish to perform. In most cases this will be
PAYMENT.
VendorName – your unique identifier, assigned to you by Sage Pay during sign up.
Crypt – a field containing encrypted and encoded details of the transaction. This prevents the
customer from being able to tamper with the contents of the order before they are submitted to us.
See Appendix A1.1 for details on how to construct the Crypt field.
The contents of the crypt field are built by your script and include, amongst other things:
A unique reference to this transaction that you generate (VendorTxCode).
Total transaction value and currency.
The URLs of the order Success and Failure pages.
Customer email address for confirmation emails.
Your email address for notification emails.
Billing and Delivery addresses.
Basket contents and a description of goods.
See Appendix A1.3 for the full protocol which lists all the fields you can send if you wish, and those
which are compulsory for all transactions.
The integration kits we provide contain scripts in a variety of languages that illustrate how you
compose and send this message from your server to ours. These can be downloaded from
sagepay.com.
When the customer clicks the ‘Pay Now’ button on the form, the hidden fields are POSTed to Sage
Pay and customer’s browser is redirected to our hosted payment pages.
Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 10 of 61