Why choose Sage Pay Server?
When you are looking to implement the Sage Pay integration on to your site you will need to choose which method of the integration you will use.
The Server method offers you enough control and security of the transactional process to enable effective management on the platform without the need to host the card capture process directly.
Server offers you:
- Increased security of using the Sage Pay hosted pages to capture card details.
- Effective communication management: with more than one post being made to Sage Pay the vendor will be able to monitor the entire transactional process and control the transaction up to the point of accepting the payment when the transaction has completed.
- Custom Payment Pages: Vendors can develop the standard Sage Pay payment pages to look and feel like their own without hosting the payment pages on their own site.
- Inframe: Vendors can embed the Sage Pay payment pages into their own site, Sage Pay will still host the card capture pages securely however the vendor can customise the Inframe to fit with their own pages and give shoppers the impression and peace of mind that they are not moving to another platform for the details to be captured.
- Processing remote actions: Unlike the Form solution Server allows vendors the option to perform Refunds, Voids, Authorises, and Releases of transactions remotely without having to log into the Sage Pay administration panel (My Sage Pay).
- Remote Terminal: As Server allows vendors greater control over transactions that are processed through the system Sage Pay can allow vendors to process both e-commerce (online) and MOTO (telephone) transactions through the Server protocol without having to access the administration panel.
How does Server work?
When a transaction is processed through the Sage Pay systems using the Server method of integration the you are required to submit a transaction registration post to our systems. An acknowledgement of this is then sent to your site from Sage Pay including the next page (nexturl) where the shopper will be re-directed too.
Once the shopper has been transferred to this page (or the iframe has been loaded within your site) the shopper will then enter the card details into the secure Sage Pay payment page. Sage Pay will then check the details are correct and submit this through for authorisation from the Merchant (vendors) and Card Issuing (shoppers) bank.
After this authorisation has been given Sage Pay will provide you with the status (OK, Rejected, Invalid) in a Notification post of the transaction and a signature string (MD5 hash value). You will then compare the signature provided by Sage Pay to the string you have created to ensure no tampering has taken place.
It is at this point you has the option to accept or reject the transaction and this is done by providing us with a response (to the notification post) and an instruction for re-direction. Sage Pay will then navigate the shopper back to the page specified by you in order to complete the transactional cycle.
Below is a full breakdown of the Server transactional process on the Sage Pay platform:
How do I start?
Once you have decided that the Server integration is for you Sage Pay have a number of documents and tools available to help with your integration. We offer our vendors, partners, and developers integration kits for each method of integration, custom template files to allow for customisation of the payment pages, and protocol and integration guidelines that outline the integration, posts, and requirements of the fields that are submitted through to Sage Pay.
What does it look like?
It all depends how you complete your integration when using the Server method of integration. Before you start your development the first choice is to decide between the Inframe solution and the standard payment pages. You can then choose between the customised version of these pages or the standard.
What’s the difference between standard and Inframe?
Aside from the Inframe being embedded into the vendors pages (website) the Inframe also involves less steps to complete the transactional process.
The standard Server method of integration includes a Card Selection, Card Details, and Confirmation page that the shopper must progress through before the transaction is completed. The Inframe simply has a card details page where the shopper will enter the card details to be used for the transaction.
Both the Inframe and the standard Server payment pages process will increase by 1 page each if the 3d Secure Fraud prevention tool is activated within the account.