With the redirect/hosted integration method the customer is passed to the Cardsave secure server in order to take the payment. Messages are sent back to the merchant’s website system regarding the status of the transaction.

The redirected/hosted page can be skinned to a degree so the merchants customer does not feel they are being taken to a bogus site to take the payment. 

Developers often opt for this option because they feel more familiar with the integration method, no SSL is required for the server post back method and security on shared servers is less of an issue.

With the option of using no SSL this method incorporates a hash digest with the data sent over the internet to protect the authenticity of the data.

There is no need to use an SSL if using the server post back method and a basic installation of the base language is all that should be required in order to implement this method.

We currently have basic code examples for PHP, Classic PHP and ASP.NET. We are developing more code examples as we speak so please visit our developers downloads section soon for further code examples.

Please note it would be best practice that developers implement the "Server" postback method please read the tab "Server Postback Method" for instruction on how to implement this, it is highly recommended.

	PHP Server Postback Code Example
	PHP Simple Code Example (SSL Recommended)
	Classic ASP Server Postback Code Example
	Classic ASP Simple Code Example (SSL Recommended)
	.NET 3.5 Server Postback Code Example
	.NET 2.0 Simple Code Example (SSL Recommended)

The detailed API and the post URL for the hosted/redirected method is...
 https://mms.cardsaveonlinepayments.com/Pages/PublicPages/PaymentForm.aspx

This URL above in its raw form is the redirected/hosted gateway helper/instruction page which gives instruction on how to construct the http post for the redirected/hosted payment method. This also provides documentation on the returning POST variables. The payment gateway will 'Post' back to the URL specified in the initial server post. You can then read the returning data to determine if the transaction has passed or failed and if so why. The "Status", (now available to you) can then be used to control your action on the website.

Post URL
https://mms.cardsaveonlinepayments.com/Pages/PublicPages/PaymentForm.aspx

Hash Help Tool
https://mms.cardsaveonlinepayments.com/Pages/PublicPages/PaymentFormHelper.aspx?HelperType=PaymentForm

Security updates in various browsers now interrupt the post back to the customer’s browser. It is possible that the merchant’s server is not informed if a payment has been taken by the payment gateway. To combat this we have implemented a server post back method for the result of the transaction directly to the merchant server and not via the customers browser.

The Server Post back process is…

1)   The merchant's website posts to the CardSave hosted payment form with a unique OrderID.

2)   The card details are entered on the hosted payment form and submitted to the payment gateway, a result is returned to the Cardsave hosted payment form.

3)   In the case of “ResultDeliveryMethod=SERVER” the results are posted directly to the merchants server.

4)   The website server (from the URL it was posted to), echo's back a response for the gateway to read so to confirm delivery as we cannot guarantee delivery of the result.
StatusCode=XX&Message=xxxxxx

There should not be ANY other characters in the response (including white space, or any HTML). Here are some valid examples:
StatusCode=0
StatusCode=0&Message=Results received OK
StatusCode=30&Message=Database timeout error
StatusCode=30&Message=Unhandled exception

5)   Once the confirmation message is received by the payment gateway for “ResultDeliveryMethod=SERVER” and “PaymentFormDisplaysResult=false” a further message is posted back to the “callbackURL”. This message includes the CrossReference and OrderID for reconciliation of the response. The customer is then returned to the website.

Further details can be found in the hosted payment form API tab.

The hosted/redirected payment form can be skinned to take a look and feel of the main website. We provide a hosted/redirected payment form skin pack which provides help and template examples for a developer to customise. 

Hosted/Redirected payment form skinning pack

Once the skin is created the developer simply email's ecomm@cardsave.net and Cardsave will implement the skin for the specified merchant.