Sankalp Shakti Demo
hcvdshcvdhscvghds hcvdshcvdhscvghds
Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 8 of 61
3.0 Form Integration in Detail Step 1: The customer orders from your site A payment begins with the customer ordering goods or services from your website. This process can be as simple as selecting an item from a drop down list, or can involve a large shopping basket containing multiple items with discounts and delivery charges. Your interaction with your customer is entirely up to you and Form integration requires you to collect only a few compulsory pieces of information, which are detailed in the latter part of this guide. It is generally a good idea to identify the customer by name, email address, delivery and billing address and telephone number. It is also helpful to have your server record the IP Address from which the user is accessing your system. You should store these details in your session alongside details of the customer’s basket contents or other ordered goods. You do not need to collect payment data, all your site needs to do is calculate the total cost of the order in whatever currency your site operates and present the user with a confirmation page, containing the transaction detail in an encrypted hidden field (see Step 2). If you wish to apply a surcharge to a particular payment method/currency then this will be applied and shown on the subsequent payment pages. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 9 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 5 and 6: Sage Pay Form Integration and Proto
- Page 7: 2.0 Overview of Form Integration Th
- Page 11 and 12: The Sage Pay system begins by valid
- 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 19 and 20: Sage Pay Form Integration and Proto
- Page 21 and 22: 5.0 Testing on the Test Server (Sta
- Page 23 and 24: Sage Pay Form Integration and Proto
- 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
Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 8 of 61