Sankalp Shakti Demo

Recommendations

Info

9.0 Going Live (Stage 2) Once Sage Pay receives your application your account will be created and details will be sent to the bank for confirmation. The bank will be expected to confirm your merchant details within 3 to 5 working days. Once both the Direct Debit (filled out during application) and the confirmation of your merchant details reach Sage Pay, your account will become Live automatically and you will start to be billed for using our gateway. This does not mean you will immediately be able to use your live account You must ensure you have completed Stage 1 Testing on the Test Server, before you are granted access to your live account. Further information on testing can be found on sagepay.com. NB – Without confirmation from the bank and without a Direct Debit submission, Sage Pay will not be able to set your account live. You will only be charged by Sage Pay when your account has valid Direct Debit details and confirmation of your merchant details from the bank. Once your live account is active, you should point your website transaction registration scripts to the following URL: https://live.sagepay.com/gateway/service/vspform-register.vsp You should then run an end-to-end transaction through your site, ordering something relatively inexpensive from your site and paying using a valid credit or debit card. If you receive an authorisation code, then everything is working correctly. You should then log into MySagePay on the live server https://live.sagepay.com/mysagepay. It is worth noting here that none of the users you set up on the MySagePay system on the test server are migrated across to live. This is because many companies use third party web designers to help design the site and create users for them during testing that they would not necessarily like them to have in a live environment. You will need to recreate any valid users on the live system when you first log in as described in 5.2. Once logged in, locate your test transaction and VOID it so you are not charged. At this stage the process is complete. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 34 of 61
10.0 Congratulations, you are live with Sage Pay Form Well done. Hopefully the process of getting here was as painless and hassle free as possible. You should contact us with any transaction queries that arise or for any help you need with MySagePay. Here are the best ways to reach us and the best department to contact: If you require any information on additional services, email tellmemore@sagepay.com If you have a query regarding a Sage Pay invoice, email finance@sagepay.com If you have a question about a transaction, have issues with your settlement files, are having problems with your payment pages or MySagePay screens, or have a general question about online payments or fraud, email support@sagepay.com with your Sage Pay Vendor Name included in the mail. If you have any suggestions for future enhancements to the system, or additional functionality you’d like to see added, please email feedback@sagepay.com with your comments. We do take all comments on board when designing upgrades, although we may not be able to answer every mail we get. You can call on 0845 111 44 55, for any type of enquiry. Your email address will be added to our group mail list used to alert you to upgrades and other pending events. You can also always check our system availability and current issues on the Sage Pay Monitor page at www.sagepay.com/support/system-monitor. Thanks again for choosing Sage Pay, and we wish you every success in your e-commerce venture. Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 35 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: 8.0 Sage 50 Accounts Software Integ
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

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

Delete template?

Save as template?