Error format

Sample : Error 404

HTTP status codes

Application error codes

Error codes

HUB2 Documentation

HUB2

Integration

Intégration

Documentation

API Reference

Error management

Home

Accueil

A guide to help getting started with HUB2 API integration

Introduction

API Operation

Security

Understand errors

API keys

Failure causes

MSISDN - Blacklist

Authentication

List payments

Object samples

List of available events

Webhooks behavior

Best practices

Samples

Balances

Account Provisioning

Public data

Bank transfer compliance

Un guide pour commencer à intégrer l'API HUB2

Fonctionnement de l'API

Sécurité

Comprendre les erreurs

Clés API

Motifs d'échec

MSISDN - Liste noire

Authentification

Lister les paiements

Exemples d'objets

Liste des évènements disponibles

Comportement des webhooks

Les bonnes pratiques

Échantillons

Soldes

Approvisionnement de compte

Données publiques

Conformité transfert bancaire

Definition of useful terms used in HUB2's payment platform

Glossary

Rate limits

Policies

Glossaire

Ce sont les limites appliquées sur notre API.

Limites de flux

Règles

Gestion des erreurs

Returns the list of countries where Hub2 is available

Get countries

Returns the list of providers available with Hub2

Get providers

Returns a summary of a merchant accounts balances (collection, transfer and transfer irt accounts) .

Check Merchant Balance

Get all webhooks

Create a webhook

Get a webhook

Remove a webhook

Update a webhook

Retrieve number of sms sent between two date

Retrieve number of sms sent

Retrieve a list of sms sent between two date.

Get a list of sms sent

Send Sms

This endpoints is here to provide you an efficient way of retrieving multiple payment intents at the same time.
    Everything is provided in the request's headers to perform a proper pagination on the results.

Retrieve a PaymentIntent collection

This endpoint is the first entry point of the PAY-IN circuit.
    First of all, you must create a payment intent which describes your intention to collect an amount of money in a currency.
    Later on, you will perform payments associated with this payment intent.
    Please do save the fields returned by this endpoint, especially the field 'id' and 'token'.
    That will help you identity the payment intent in our platform whenever you want to retrieve it.

Create a PaymentIntent object

This endpoint allows you to fetch an existing payment intent from our database.
    You must either provide the "id" or the "token" for us to find that payment intent.
    Retrieving using the "token" is the fastest way and is not rate limited, depending on your needs, that's probably the best solution.

Retrieve a PaymentIntent object

This is the endpoint to use whenever you want to attempt a payment on a payment intent.
    It will create a payment object associated with the intent which will contains all the informations about the payment.
    Whenever a payment fails or don't have the appropriate amount to match the intent, other payments can be created on the same intent.

Attempt a payment on a PaymentIntent object

This is the same endpoint but the payment is handled synchronously, it means it will wait for the provider response before returning the status of the payment intent. This endpoint is not the favored way to integrate our api and is not available for all merchants and for all providers.

Synchronously attempt a payment on a payment intent

Some circuit have authentication restrictions which requires an extra step.
    This endpoint is here to allow you to make that extra steps. It happens after a payment has been requested and when that payment moved to the "action_required" state.

Authenticate the current payment

This endpoint allows you to retrieve the fees associated with a payment intent.
    Fees are applied per payment and this endpoints will group all the fees in an array.

Retrieve fees

This endpoint fetch the merchant's preference and return the redirection URL saved in there.
    This is mostly used for the Hub2 modal feature.
    You must provide the payment intent token for that.

Retrieve configured URLs

Return a list of Payments, eventually filtered by criteria.

Retrieve a Payments collection

Retrieve a Provisionings collection

Move funds from merchant's collection account to transfer account

Create a Provisioning

Retrieve a Provisioning from given id

Retrieve a sucessful or failed transfer or payment receipt

Retrieve a Receipt

Retrieve a sucessful or failed transfer or payment receipt as HTML

Retrieve a Receipt as an HTML representation

Execute payment

Retrieve a payment

Return a list of IRT transfers, eventually filtered by criteria.

Retrieve a IRT transfers collection

Create IRT transfer

Return a list of Transfers, eventually filtered by criteria.

Retrieve a Transfer collection

This endpoint allows you to make a transfer (PAY-OUT)

Create Transfer

This endpoint allows you to fetch an existing transfer from our database
    by providing its 'id'

Field name	Description
`status`	The HTTP status
`code`	A business error code internal to hub2 api (see full list below)
`message`	A readable description of the error code
`request_id`	Unique request identifier

Status Code	Status Text	Description
`200`	`OK`	The HTTP request was completed as expected.
`400`	`Bad Request`	The request was unacceptable, often due to a missing required parameter.
`401`	`Unauthorized`	No valid API key provided.
`402`	`Request Failed`	The parameters were valid but the request failed.
`403`	`Forbidden`	The API key doesn’t have permissions to perform the request.
`404`	`Not Found`	The requested resource doesn’t exist.
`409`	`Conflict`	The client’s request is in direct conflict with another action that is already in progress or has been completed
`429`	`Too Many Requests`	Excessive requests have been made to the API in a short amount of time. The request wasn’t accepted to preserve overall api performance
`500`, `502`, `503`, `504`	Server-related errors	Something went wrong on HUB2’s end.

Code	Reason
`account-already-exists`	An account ‘accountType’ in mode (live or sandbox) already exists for the merchant merchantId
`cancellation-already-done`	The transaction id has already been canceled.
`insufficient-funds`	The account does not have enough funds to transfer amount currency.
`invalid-currency`	Invalid currency (currency).
`locked-account`	The account is locked.
`transaction-not-found`	The transaction transactionId for the account accountId is not found.
`currency-not-found`	Currency not found (currency).
`withdrawal-unavailable`	Withdrawals are unavailable on the account accountId. The account may be blocked or does not have sufficient funds.
`missing-funds-reservation`	Insufficient reserved funds.
`merchant-not-found`	The merchant is not found.
`unsupported-command`	Unsupported command.
`no_auth_required`	The transaction id does not require authentication.
`transaction_canceled`	The transaction (payment) has been canceled. No payment can be processed.
`transaction_missing`	The transaction (transfer or payment) is not found.
`transaction_in_progress`	The transaction (transfer or payment) is already in progress.
`transaction_done`	The transaction (transfer or payment) has already been completed.

Documentation

​Error format

​Sample : Error 404

​Error codes

​HTTP status codes

​Application error codes

Error format

Sample : Error 404

Error codes

HTTP status codes

Application error codes