Table of Contents
OneClick Overview
Feature Explained
...
For increased security you may also pass two additional fields with your OneClick request.
x_fp_hash | Similar to the MD5 hashing feature returned by the gateway response, the x_fp_hash is build by creating a MD5 hash with the following fields: login ID
| This is the timestamp (unix UTC) of the request. This will be the same timestamp value that was included in the x_fp_hash. |
...
| ||||||
x_fp_timestamp | This is the timestamp (unix) of the request. Must be in UTC timezone. This will be the same timestamp value that was included in the x_fp_hash. | |||||
x_fp_sequence | Custom sequence value designated by the merchant. Also used in the creation and validation of the x_fp_hash. | |||||
x_fp_expiry | (optional) Custom expiration time defined by the merchant, in minutes. If x_fp_expiry is given, the value must also be included in the string portion of the x_fp_hash generation.
|
Passing Customer Contact Information
...
<HTML> <HEAD> <TITLE>Example OneClick HTML page</TITLE> </HEAD> <BODY> <form action="https://secure.gotoBilling.com/gateway/transact.php" method="POST"> <input type="hidden" name="x_show_form" value="PAYMENT_FORM"> <!-- Replace this value with your valid Merchant ID --> <input type="hidden" name="x_login" value="234568"> <!-- Enter pre-set amount, or leave blank to allow customer to enter an amount --> <input type="hidden" name="x_amount" value="1.00"> <!-- Enter a description for the payment --> <input type="hidden" name="x_description" value="My Order"> <!-- Receipt page the response will be redirectredirected to, un-comment to use --> <!-- <input type="hidden" name="x_relay_url" value="http://www.mydomain.com/thankyou.html"> --> <input type="submit" value="Accept Order"> </form> </BODY> </HTML>
...