Sankalp Shakti Demo

Appendix B: Transaction Completion
For Sage Pay Form transactions, Sage Pay cannot guarantee to return the customer to your website. If the customer closes their browser mid-way through a transaction,
or if something goes wrong at any redirect stages, it will be up to you to check the status of the transactions on the MySagePay reporting screens.
In normal circumstances, however, where the customer does not close their browser and there are no redirection problems, Sage Pay Form will return them to your site,
either to the SuccessURL (in the event the transaction was successful), or the FailureURL (in all other circumstances).
The system will append to the SuccessURL or FailureURL a field called Crypt, in the manner:
[ResponseURL]?crypt=[encrypted_information]
Or if the URL already has your own fields attached, it will be appended thus:
[ResponseURL]?vendor1=test&vendor2=test2&crypt=[encrypted_information]
The SuccessURL and FailureURL fields should point to scripts on your server that extract the information in the crypt field and use it to update your database (if you
have one) and/or format an appropriate response page for the customer. This is not compulsory, however, and you may choose to simply direct customers to a static
HTML page that ignores the contents of the crypt field. In such cases, you will need to manually check the MySagePay report pages to determine if a transaction
succeeded or failed. In fact, we recommend you always check the MySagePay pages before sending any goods just to confirm the status of each transaction.
The Crypt field contains the plain text shown overleaf. For details of the Encryption used see Appendix A1.1
Remember to remove the ‘@’ sign before decrypting.
Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 55 of 61