The Hosted Payment Forms module essentially has two ways of handling transaction responses. Online Receipt pages, and Transparent Redirect.
For merchants that do not have a full-service back-end application, or do not require direct feedback, the online receipt pages provide the easiest solution for providing customers with confirmation receipts and decline notifications.
The receipt page is displayed whenever a transaction is successful, or approved. It will utilize the same logo as the hosted payment form, and will echo the confirmation text as defined on the HPF edit admin page.
Receipts will display the following data from the transaction:
- Payment Amount or amounts in the case of split transactions
- Payment Date
- Payment Method is the type & last 4 digits of card or account
- Payment Status is set to approved for Cards, Pending for ACH. Billing name Custom field(s)
A button is included to allow customers to print their receipt.
The decline pages are terminal. They do not provide a means to re-try the transaction. Customers will be presented with a generic message telling them the payment was declined, plus: Payment date Response Code. A numeric code. * Response Message. This is the decline notice reflected back from the processor.
It is possible for the Merchant to specify the various URL’s for “Response Handling” outside of the form setup, if desired. Doing so could lessen the number of forms needed for a Merchant, but it needs to be handled in a secure fashion, so care and expertise needs to be used.
In the URL that is used to render the Hosted Payment Form, you can control the back-end behavior by adding even more elements to the URL string. The possible values are explained in the table below. Note that none of them can be sent directly (plain text) and must be included in a hash for security reasons. They do not however need to be specified in a hash_key since they are already required to be hashed. For more on HASH and its use, refer to the appendix in this document.
|success_url||string||optional||Used for a non-default (merchant "hosted") successful transaction receipt. Must be a valid URL that will be called if transaction is successful. It needs to be specified inside the hash, but does NOT need to be included in the hash_key.|
|decline_url||string||optional||Used for a non-default (merchant "hosted") NOT successful transaction receipt. Must be a valid URL that will be called if transaction is declined. It needs to be specified inside the hash, but does NOT need to be included in the hash_key.|
|cancel_url||string||optional||Must be a valid URL that will be called if user presses Cancel button on HPF. It needs to be specified inside the hash, but does NOT need to be included in the hash_key.|
|timeout_redirect||string||optional||Must be a valid URL that will be used if the HPF times out on the user. It needs to be specified inside the hash, but does NOT need to be included in the hash_key.|
|postback_url||string||optional||Must be a valid URL to receive POSTback data.|
Updated about 1 year ago