Sankalp Shakti Demo

Recommendations

Info

11.0 Character Sets and Encoding All transactions are simple synchronous HTTPS POSTs sent from a script on your servers to the Sage Pay gateway, with the same script reading the Response component of that POST to determine success or failure. These POSTs can be sent using any HTTPS compatible objects (such as cURL in PHP, HttpWebRequest in .NET and Apache HttpComponents in Java). The data should be sent as URL Encoded Name=Value pairs separated with & characters and sent to the Sage Pay Server URL with a Service name set to the message type in question. The following sections detail the contents of the POSTs and responses, between your server and ours. The format and size of each field is given, along with accepted values and characters. The legend below explains the symbols: Letters (A-Z and a-z) Caret Plus Numbers Square brackets Parentheses Accented characters Asterisk Semi-colon Ampersand Apostrophe (single quote) Pipe At sign Slash and Backslash Exclamation Mark Colon Hyphen Space Comma Underscore Tilde Curly brackets Full stop / Period Equals Quotes Dollar Valid 2-letter US States Hash Question Mark Date in the format YYYY-MM-DD ISO 639-2 (2-letter language codes) ISO 3166-1 (2-letter country codes) ISO 4217 (3-letter currency codes) Valid Base64 characters (A-Z,a-z,0-9,+ and /) New line (Carriage Return and Line Feed) RFC 1738 compliant HTTP(S) URL All non-compliant characters, including spaces should be URL encoded True or False RFC 5321/5322 (see also RFC 3696) compliant email addresses Valid HTML with no active content. Script will be filtered. Includes all valid letters, numbers, punctuation and accented characters Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 36 of 61
Appendix A: Transaction Registration A1. Form Fields The final confirmation page on your website should contain an HTML FORM with the Action set to the Sage Pay Form submission URL and the following 4 hidden fields as part of that Form. Request format Name Mandatory Format Max Length Allowed Values Description VPSProtocol Yes 4 chars 3.00 This is the version of the protocol you are integrating with. Default or incorrect value is taken to be 3.00. TxType Yes 15 chars PAYMENT The value should be in UPPERCASE. DEFERRED AUTHENTICATE Vendor Yes 15 chars Used to authenticate your site. This should contain the Sage Pay Vendor Name supplied by Sage Pay when your account was created. Crypt Yes 40 chars Your site builds the Crypt field in real time for each order. The contents of the field are described below. All other transaction information is encrypted then encoded. See below. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 37 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: 10.0 Congratulations, you are live
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

Sankalp Shakti Demo

Create successful ePaper yourself

Delete template?

Save as template?