Sankalp Shakti Demo

Recommendations

Info

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
The Sage Pay system begins by validating the Crypt field contents. It first checks to ensure all the required fields are present, and that their format is correct. If any are not present or contain the wrong type of data, a validation error is sent to your failure page if possible, or displayed on screen. This normally only happens in the development stage so your customers are unlikely to encounter this page. If all fields are present and correct, the information in those fields is then validated. The VendorName is checked against our database and the Currency of the transaction is validated against those accepted by your merchant accounts. The VendorTxCode is checked to ensure it has not been used before, the Basket/BasketXML contents are validated to ensure they have been sent in the correct format and the Amount field is validated. Flag fields are checked… every field, in fact, is checked to ensure you have passed appropriate values. If everything in the POST checks out, the transaction is registered with the Form system and a new transaction code is generated that is unique across ALL merchants using the Sage Pay gateway. This code, the VPSTxId (or Transaction ID), is our unique reference to the transaction, and is sent back to you at the transaction completion stage. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 11 of 61
Page 1 and 2: Sage Pay Form Integration and Proto
Page 3 and 4: A1.3 Request Crypt Fields 39 A1.4 S
Page 7 and 8: 2.0 Overview of Form Integration Th
Page 9: 3.0 Form Integration in Detail Step
Page 13 and 14: Step 4: Sage Pay checks for 3D-Secu
Page 15 and 16: Step 6: Issuing bank returns the cu
Page 17 and 18: as a failed transaction in MySagePa
Page 21 and 22: 5.0 Testing on the Test Server (Sta
Page 25 and 26: If you have 3D-Secure set up on you
Page 27 and 28: Once you have created a new user, c
Page 29 and 30: 6.0 Additional Transaction Types Sa
Page 31 and 32: To charge the customer when you are
Page 33 and 34: 8.0 Sage 50 Accounts Software Integ
Page 35 and 36: 10.0 Congratulations, you are live
Page 37 and 38: Appendix A: Transaction Registratio
Page 39 and 40: A1.3 Request Crypt Fields Name Mand
Page 41 and 42: BillingAddress2 No 100 chars Billin
Page 43 and 44: Apply3DSecure No Flag 0 (default) 1
Page 45 and 46: FIRecipientPostcode No This is the
Page 47 and 48: A1.5 Basket The shopping basket con
Page 49 and 50: └ XML container element There can
Page 51 and 52: └ No 14 chars Amount of tax on de
Page 53 and 54: └ Yes 29 chars Name of passenger
Page 55 and 56: Appendix B: Transaction Completion
Page 57 and 58: REGISTERED = 3D-Secure checks faile
Page 59 and 60: 3DSecureStatus Yes 50 chars OK NOTC
Page 61:
12.0 URLs The table below shows the
show all

Sankalp Shakti Demo

Create successful ePaper yourself

Delete template?

Save as template?