Skip to main content

​
Introduction

This feature is dedicated to merchant aggregators and allows collection through bank transfers.

​
Life cycle

The diagram below shows the process.
  1. The aggregator declares the business of each aggregated merchant (KYB).
  2. The aggregator declares each transaction with its reference.
  3. The merchant sends the bank transfer with the same reference.
  4. On receipt of the transfer, HUB2 checks the data and validates or rejects the transaction.
  5. Once the transaction is validated, the aggregator is notified through the transaction.deposit webhook event.

​
Compliance

​
Declare the merchants’ business

Before anything else, the aggregator must declare information about its merchants. Several endpoints are available to manage the aggregated merchants.
See these endpoints in the API reference.
To keep a full history, deleted data are kept by HUB2 for compliance reasons. The same applies when merchant information is edited: previous data are kept.

​
Declare a transaction

Whenever a merchant sends a bank transfer to HUB2 with a reference, the aggregator must also call the HUB2 API to declare this transaction.
See this endpoint in the API reference.
All the following fields are required:
  • name: the name of the aggregated merchant the transaction belongs to
  • reference: the reference entered in the bank transfer
  • amount and currency: the amount and currency of the bank transfer
  • iban: the IBAN of the destination account
The process is not synchronous: the aggregator can call the HUB2 API before or after the bank transfer occurs.

​
Validation by HUB2

Whenever a bank transfer reaches the HUB2 accounts, HUB2 performs the following checks:
  • Using the reference of the bank transfer, HUB2 looks up the declared transaction with this reference
  • HUB2 checks the transaction information, such as amount and currency
  • Once the checks pass, HUB2 credits the aggregator’s account on the HUB2 platform with a deposit
The aggregator is then notified through the transaction.deposit webhook event, which contains the reference.