Sankalp Shakti Demo

Recommendations

Info

VendorData No 200 chars Use this field to pass any data you wish to be displayed against the transaction in MySagePay. ReferrerID No 40 char This can be used to send the unique reference for the Partner that referred the Vendor to Sage Pay. Language No 2 chars ISO 639-2 Examples: EN, DE and FR The language the customer sees the payment pages in is determined by the code sent here. If this is not supplied then the language default of the shopper’s browser will be used. If the language is not supported then the language supported in the templates will be used. Currently supported languages in the Default templates are: French, German, Spanish, Portuguese, Dutch and English. Website No 100 chars Reference to the website this transaction came from. This field is useful if transactions can originate from more than one website. Supplying this information will enable reporting to be performed by website. FIRecipientAcctNumber No 10 chars This should either be the first 6 and the last 4 characters of the primary recipient PAN (no spaces). Where the primary recipient account is not a card this will contain up to 10 characters of the account number (alphanumeric), unless the account number is less than 10 characters long in which case the account number will be present in its entirety. This field is only required for UK merchants who have a merchant category code of 6012 (Financial Institutions) FIRecipientSurname No 20 chars This is the surname of the primary recipient. No special characters such as apostrophes or hyphens are permitted. This field is only required for UK merchants who have a merchant category code of 6012 (Financial Institutions) Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 44 of 61
FIRecipientPostcode No This is the postcode of the primary recipient. This field is only required for UK merchants who have a merchant category code of 6012 (Financial Institutions) FIRecipientDoB No This is the date of birth of the primary recipient in the format YYYYMMDD This field is only required for UK merchants who have a merchant category code of 6012 (Financial Institutions) Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 45 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: Apply3DSecure No Flag 0 (default) 1
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?