Skip to content

Supported KYC callbacks#

XGateway will send the KYC callbacks for the following KYC status changes:

  • CREATED KYC user is created via POST /customer/{id}/bank-transfer/user
  • KYC_NEEDED KYC process required
  • PENDING_KYC_DATA Awaiting KYC data
  • KYC_PENDING KYC is in progress
  • SOFT_KYC_FAILED Non-critical KYC failure
  • HARD_KYC_FAILED Critical KYC failure
  • FULL_USER KYC completed successfully

In addition to KYC status changes, a callback is sent when the customer's entity (applicant) status changes. These are delivered via the same KYC callback and are reflected in the entityStatus field:

  • BLOCKED Transactions for the customer are suspended (e.g. fraud suspicion, compliance reasons)
  • MISSING_TERMS_AND_CONDITIONS_SIGNED Customer requires a Terms & Conditions patch
  • UNBLOCKED Customer is active again

The entityStatus field is independent from the KYC status. A customer may be FULL_USER on KYC while BLOCKED on entity status. When entityStatus is BLOCKED or MISSING_TERMS_AND_CONDITIONS_SIGNED, stop accepting deposits/withdrawals for the customer.

It is advised to subscribe and use those callbacks. This will simplify the integration and reduce response time from our side.

Callback format and usage could be tracked on the KYC Callbacks page