Sankalp Shakti Demo

Recommendations

Info

└ Yes Check in date for hotel. └ Yes Check out date for hotel. └ Yes 3 chars Number of people in the hotel booking. └ No 10 chars Folio reference number for hotel. └ No Y N Flag to indicate whether a guest has confirmed their reservation Y= Confirmed Reservation N = Unconfirmed Reservation └ Yes 15 chars Daily room rate for the hotel. └ Yes 20 chars Name of guest └ No Used to provide cruise information for settlement. There can be only one cruise element. └ Yes Start date for cruise. └ Yes End date for cruise. └ No Used to provide car rental information for settlement. There can be only one car rental element. └ Yes Check in date for car rental. └ Yes Check out date for car rental. └ No Used to provide tour operator information for settlement. There can be only one tour operator element. └ Yes Check in date for tour operator. └ Yes Check out date for tour operator. └ No Used to provide airline information for settlement. There can be only one airline element └ Yes 11 chars The airline ticket number └ Yes 3 chars IATA airline code └ Yes 8 chars IATA agent code └ Yes 26 chars Agency name └ No 6 chars Flight number └ Yes Can be 0, 1, true or false. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 52 of 61
└ Yes 29 chars Name of passenger └ Yes 3 chars IATA airport code └ Yes Contains other elements detailing the segment At least one segment element must be supplied under the airline element, but can supply up to 4 segments. └ Yes 3 chars IATA carrier code └ Yes 3 chars Class of service └ Yes Can be 0,1, true or false to indicate a stopover └ Yes Departure date of the segment. └ Yes 3 chars IATA airport code of destination └ No 6 chars Fare basis code └ No 20 chars Airline customer code └ No 15 chars Airline Invoice Number └ No 15 chars Diners customer reference Can include up to 5 elements View example Basket XML snippets on sagepay.com Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 53 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 and 10: 3.0 Form Integration in Detail Step
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 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: └ No 14 chars Amount of tax on de
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

Sankalp Shakti Demo

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?