Wallet Webhooks

Attention!

QI Tech webhooks should not be mapped in a restrictive way. Additional fields may be included in webhook payloads returned by our APIs.

Webhook Resending

You can check and resend webhooks by following the detailed instructions in the documentation: Webhook Resending.

Introduction

After creating a wallet (wallet) within our system, webhooks will be sent with the following statuses:

Enumerator	Translation	Description
active	active	Active wallet available for use
rejected	rejected	Wallet rejected in KYC analysis

Information

The timeout for our webhook response is 10 seconds.

Examples

---

Opening confirmation

Webhook Body

{
	"webhook_type": "baas.invoice.wallet",
	"webhook_datetime": "2024-08-13T21:35:55.679Z",
	"data": {
		"wallet_key": "fd86d9b1-2a5e-4e03-9a59-a043c7632c97",
		"owner_person_key": "ecf87b4b-fa6e-49c0-a7f0-f2cad6b42d79",
		"wallet_status": "active"
	}
}

Webhook Fields

Field	Type	Description	Characters
wallet_key	string	Unique wallet identification key in uuid v4 format	36
owner_person_key	string	Unique identification key of the wallet owner in uuid v4 format	36
wallet_status	string	Wallet status	wallet_status Enumerators

wallet_status Enumerators

Enumerator	Description
active	Active wallet available for use
rejected	Wallet rejected in KYC analysis