This chapter explains the initial call carried out by the commercial server to initialize the process of payment. This call is normally on the initiative of the future purchaser clicking on a link "PAYMENT" on the commercial server, after having created and having validated its basket of purchase.
|
1/ Pre-necessary
|
The test phase can be carried out only with this pre-necessary:
- to have opened an account webmaster (cf heading "Inscription", "Webmaster")
|
2/ Made your first test of payment
|
Click here to open the test form.
This page simulates HTTP request made by your application. As soon as your account is activated, you can use this form to do to ensure a test of payment and you that your account is correctly configured.
Fill manually with your own data: your NumSite, your Password (not crypted), a single reference (OrderID), an amount multiplied by 100 (Amount), the ISO code of the currency.
Leave the empty optional fields for the moment (see chapter 3 for more details)
Click on "Go!"
You should receive like answer, an input page (specific according to the type of selected payment) allowing to finalize the transaction.
You can consult your new payment in the module of administration of H2EPAYMENT.
If it is not already done:
==> Go on the backoffice H2EPAYMENT: http://www.h2epayment.com/backoffice
==> you Identify (enter your NumSite and your password).
Then :
==> Click on "Payments" in the menu of left.
==> Enter your criteria of selection and visualize your payments.
The transaction owes apparaitre with an amount to 0.00 EUR , the request having been stopped before being sent to the bank (phase of test).
|
3/ Integration in your application
|
You can now call directly via a FORM method POST the URL:
|
| https://www.h2epayment.com/test/ecom_menu.php |
|
to directly start the process of payment since your application.
Make a test of payment with the same data and consult this payment in the module of administration of H2EPAYMENT, as described in chapter 3/.
|
4/ To simulate a payment refused in test
|
In the environment of Test, the answers of the purchasers are simulated. You can simulate the various possible answers (accepted, refused, dubious) by modifying the amount of the transaction:
- From 0 to 9.000: all the requests for authorization are accepted in test (Amount = 0 => 900000)
- Above 9000: all the transactions are refused (Amount > 900000)
|
5/ Resolution of the basic problems
|
Problems can occur owing to the fact that the data which we receive from your application do not correspond to the parameters that you defined by configuring your account, or we receive erroneous parameters.
The most current errors:
" Site not operational. ":
You ensure that your account is active. Check the number of your site.
" not accepted Currency? "(the currency is not accepted?):
The currency must be that which you chose for your catalogue.
" decimal Amount not accepted. ":
The amount of the order must be multiplied by 100. For the BEF, the decimals are not authorized, therefore the last 2 figures of the field "Amount" must be "00".
" the call must be made in protected mode (https). ":
Check that the URL of the action of your request starts with https
" This transaction was already treated. ":
We check that a payment is not treated 2 times, ensure you that each payment has a single reference number (orderID). You can see which reference numbers were already used when you consult your payments on the site of administration of H2EPAYMENT.
|
6/ How to pass from an account of test to an account of production
|
It is enough to send an email to us on webmaster@h2epayment.com to make us this request.
Your account will be activated as soon as all the administrative and contractual tasks are finished.
In your requests:
replace the URL:
|
| https://www.h2epayment.com/test/ecom_menu.php |
|
by
|
| https://www.h2epayment.com/prod/ecom_menu.php |
|
You are ready to box payments.
ATTENTION with the passages of parameters, Password of your site must be sent to us crypted in MD5, to avoid an interception in uncrypted (see heading "Installation", "modules of encoding")
|
