Bills operations flow
This is the bill payment describing the APIs in the following section. For steps are necessary : The bill initiation, The bill payment by the user and the bill verification

Bill initiation

This step is implemented in the merchant application. The user will then have a form to put his email, phone number or iHela ID. The application will then send it with all the payment information and a bill will be created in the user's account in iHela. The user will automatically see it in all of our client applications and can pay it before the expiration time.
The bill can be created in a partner bank, according to the banks list provided in our APIs. The merchant application will then send the bank slug on bill initiation. If there is no bank slug given, the bill is created directly in iHela.
The expiration is set to 1 week in iHela by default. But this value can change according to the merchant who created the bill or the bank where the bill have been sent. For example, if the bill is sent to a mobile bank, it can expire in 5 or 10 minutes as mobile banks bills expire after a short time.

Bill payment

After initiation, the user visits our applications to see the unpaid bills and then pay them. If the redirect url is mentioned in the bill, the user is redirected to the merchant application.

Bill verification

Direct verification

The merchant application can directly verify the bill status calling the bill validation Endpoint to see the bill status. The status can be "Paid", "Error", "Pending" or "Expired". This can be configured in a cron job that verifies after a time or on the payment detail page in the merchant application.

Callback configuration

A callback endpoint can be configured to receive the bill payment confirmation after the user payment. The merchant application then must provide an url following the given instructions.
Last modified 2mo ago