POST
/
compliance
/
transaction

Headers

ApiKey
string
required

Your api key. To create a key, please get into our dashboard. If you don't have access to it, please reach the Support team.

MerchantId
string
required

Your merchant ID. This information is available in our dashboard. If you don't have access to it, please reach the Support team.

Environment
enum<string>
required

Allow you to choose between the sandbox mode to perform some tests or the live mode for real world transactions.

Available options:
live,
sandbox

Body

application/json
merchantId
string
required

The id identifying the merchant

name
string
required

The name of the aggregated merchant

reference
string
required

Reference of the transaction

amount
number
required

Amount of the transaction

currency
string
required

Currency in which the transaction has been done

bankAccountId
string
required

ID of the bank account on which funds will be transferred

Response

200 - application/json
id
number
required

The id identifying the transaction

kyb
object
required

The kyb related to the transaction

reference
string
required

Reference of the transaction. Should be unique for a given merchantId

amount
number
required

Amount of the transaction

currency
string
required

Currency in which the transaction has been done

createdAt
string
required

Datetime in UTC timezone at which this object was created. Follows the Datetime ISO.

status
enum<string>
required

Enum indicating the status of the kyb transaction

Available options:
created,
pending,
rejected,
validated
bankAccountId
string
required

ID of the bank account on which funds have been transferred

rejectionReason
string

The reason why a kyb transaction has been rejected by Hub2 teams (i.e, the deposit hasn't been done)