All three methods are designed to handle Payment Page transaction results.
Receipt Link: Displays a standard receipt to the customer. These are the simplest of the three methods: the Exact Pay Gateway does not automatically send the transaction results back to the merchant server, and displaying a customized receipt is not an option. This method is most ideal for merchants doing a small number of transactions per day and are content using logging in to Gateway Admin to reconcile data later.
Additionally, there are 4 Receipt Link methods to choose from:
- LINK: user must click a link to return to the merchant's storefront after completing their purchase
- GET: similar to the LINK method plus the transaction details are returned to the merchant in the form of a query string URL
- POST: similar to the LINK method plus the transaction details are returned to the merchant server as a form post
- REDI: similar to the POST method except the user is automatically returned to the merchant's storefront without having to click a link
Relay Response: A more complex model but also the one that offers the most control. Here the merchant receives transaction results directly from the Gateway and then responds back to drive the results displayed to the customer. Transaction results sent by the Gateway can be used to automatically update databases, inventory, and empty online shopping carts. HTML code the merchant sends back to Exact customizes the look and feel of the receipt page.
Silent Post: A mashup of the above methods, the Gateway sends the transaction results to the merchant and displays a standard receipt page to the customer. So, the merchant has the benefit of receiving transaction data in real time but does not have to worry about sending Exact a 'handshake' back. This method is very similar to Receipt Link POST—except that the user is not required to click a link in order to call the method.