​
Introduction

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

​
Life cycle

Here’s a schema of the process.
  1. Merchant must declare the business of the sub-merchant
  2. Then they must declare each transaction using their reference
  3. The bank transfer must occur with the same reference
  4. An Hub2 agent will check the data upon reception of the transfer and validate or reject the transaction
  5. Once validated, merchant will be notified with a webhook on event transaction.deposit

​
Compliance

​
Declare merchants business

First of all, before anything else, the aggregator must declare information about their merchants. Multiple endpoints are available to manage the aggregated merchants.
Please check these endpoints in the API reference.
In order to keep track of a full history, please keep in mind that deleted data are kept in HUB2 database for compliance reasons. That’s also the case when editing a merchant information, previous data are kept.

​
Declare transaction

Whenever a merchant will send a bank transfer to HUB2 with the reference, the aggregator must also call HUB2 API to declare information about this transaction.
Please check these endpoints in the API reference.
  • The transaction field merchantName is here to know for which merchant this transaction is accountable
  • The field reference is the one typed in the bank transfer
  • The IBAN of the destination account must be provided here
This is not a synchronous process, the aggregator can call the HUB2 API before of after the bank transfer occurs, it does not matter here.

​
Internal process

Whenever a bank transfer gets on the HUB2 accounts, cash management and control teams will perform checks:
  • Using the reference in the bank transfer, they will seek the declared transaction associated with this reference
  • Once found, they will perform checks on the information such as amount and currency
  • Once validated, they will perform a deposit on the aggregator’s account on HUB2 platform
From there, the aggregator can be notified using the webhook event transaction.deposit which will contains the reference.