Sankalp Shakti Demo

Recommendations

Info

When you log in to MySagePay screens you will be asked for a Vendor Name, a Username and a Password. The first time you log in you will need to do so as your system Administrator: In the Vendor Name field, enter your Vendor Name, set during the application process used throughout the development as your unique Sage Pay identifier. In the Username field, enter the Vendor Name again. In the Password field, enter the MySagePay Admin password as supplied to you by Sage Pay when your test account was set up. The administrator can ONLY access the settings Tab. You cannot, whilst logged in as administrator, view your transactions or take MO/TO payments through the online terminal. To use those functions, and to protect the administrator account, you need to create new users for yourself and others by clicking on the ‘Users’ tab then the ‘New User’ button. You will be presented the following screen where you set the log in credentials and account privileges. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 26 of 61
Once you have created a new user, click the Sign Out button and sign back in, this time entering: • Your Vendor name in the Vendor Name field. • The Username of the account you just created in the Username field. • The password for the account you just created in the Password field. You are now logged in using your own account and can view your test transactions and use all additional functions. If you lock yourself out of your own account, you can use the Administrator account to unlock yourself or use the lost password link on the Sign In screen. If you happen to lock out the Administrator account, you will need to contact Sage Pay to unlock it for you. Send an email to unlock@sagepay.com stating the Vendor Name and Merchant Number of the account. If you need reminding of your unique account passwords, send an email to the above and request a password retrieval link, stating the Vendor Name and Merchant Number of the account. Detailed information on using MySagePay can be found here. Play with the system until you are comfortable with it. You cannot inadvertently charge anyone or damage anything whilst on the test server. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 27 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: If you have 3D-Secure set up on you
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

Sankalp Shakti Demo

Create successful ePaper yourself

Delete template?

Save as template?