Identification events

We have four events for identifications, just as we have described in Webhooks Section

Identification pending

Every time a user submit the data to do the identification and this data is received in our platform, the identification process starts and we inform with the next payload

{
  "data": {
    "event": "identification_pending",
    "attributes": {
      "identification_id": Identification.uuid,
      "status": "pending",
      "timestamp": 1665491887
    }
  }
}

Identification verified

If the outcome of the identification is successful, this webhook event will inform you that the account is ready to start operations in our platform.

{
  "data": {
    "event": "identification_verified",
    "attributes": {
      "identification_id": Identification.uuid,
      "status": "verified",
      "timestamp": 1665491887
    }
  }
}

Identification rejected

If the user identity is not accepted to operate in our platform, the identification will be rejected without allowing any retrials.

{
  "error": {
    "event": "identification_failed",
   	"attributes": {
      "identification_uuid": Identification.uuid,
      "message": "Identification failed",
      "status": "verified",
      "timestamp": 1665491887
    }
  }
}

Identification retry

In case the identification results in fail because of errors or missing information in received data, the client will received the communication with the next information

{
  "data": {
    "event": "identification_retry",
    "attributes": {
      "user_uuid": "559ec6c7-2e2b-46b0-811e-79ec180f3465",
      "identification_id": Identification.uuid,
      "status": "retry",
      "timestamp": 1665491887
    }
  }
}

Account events

We have one event for accounts, just as we have described in Webhooks Section

Account created

This information is communicated by webhook every time an account is created in our platform

{
   data: {
          event: 'account_created',
          attributes: {
            referral: XBCD2
            timestamp: 1665491887,
            account_uuid: "989eg9c7-3h8a-9d0a-987a-02ka192a8012"
      }
    }
  }

Fiat payment events

We have three events for fiat payments just as we have described in Webhooks Section

Fiat payment received

This information is communicated by webhook every time a payment is received in our platform

{
  "data": {
    "event": "fiat_payment_received",
    "attributes": {
        "fiat_payment_uuid": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
        "bank_account_id": "559ec6c7-2e2b-46b0-811e-79ec180f3465",
        "account_id": "559ec6c7-2e2b-46b0-811e-79ec180f3465",
        "iban": "ES3500818245944561890645",
        "recipient": "Recipient name",
        "description": "Description",
        "amount": 106.15,
        "currency": "EUR",
     		"status": "confirmed",
        "identification_uuid": Identification.uuid,
        "timestamp": 1665491887
    }
  }
}

Payment sent (event: sent)

This information is communicated by webhook every time a payment is sent in our platform

{
  "data": {
    "event": "fiat_payment_sent",
    "attributes": {
      "fiat_payment_uuid": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
      "bank_account_id": "559ec6c7-2e2b-46b0-811e-79ec180f3465",
      "account_id": "559ec6c7-2e2b-46b0-811e-79ec180f3465",
      "iban": "ES3500818245944561890645",
      "recipient": "Recipient name",
      "description": "Description",
      "amount": 106.15,
      "currency": "EUR",
      "status": "confirmed",
      "identification_uuid": Identification.uuid,
      "timestamp": 1665491887
    }
  }
}

Payment failed (event: failed)

This information is communicated by webhook if for any reason the transaction process has not been finished.

{
  "error": {
    "event": "fiat_payment_failed",
   	"attributes": {
      "fiat_payment_uuid": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
      "message": "Insufficient balance"
    }
  }
}

Blockchain payment events

We have three events for blokchain payments just as we have described in Webhooks Section

Payment received (event: received)

This information is communicated by webhook every time a payment is received in our platform

{
  "data": {
    "event": "blockchain_payment_received",
   	"attributes": {
    	"tx_hash": "6146ccf6a66d994f7c363db875e31ca35581450a4bf6d3be6cc9ac79233a69d0"
      "blockchain_payment_uuid": "691ab628-157f-4beb-8a2f-d17dfb323f3b",
      "blockchain_wallet_id": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
      "account_id": "f86bba92-ac98-4094-be92-aaa36e577857",
      "amount": 106.15,
      "currency": "USDT",
      "status": "confirmed",
      "timestamp": 1665491887
    }
  }
}

Payment enqueued (event: enqueued)

This information is communicated by webhook if for any reason the transaction has been enqueued.

{
  "data": {
    "event": "blockchain_payment_enqueued",
   	"attributes": {
      "blockchain_payment_uuid": "691ab628-157f-4beb-8a2f-d17dfb323f3b",
      "blockchain_wallet_id": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
      "account_id": "f86bba92-ac98-4094-be92-aaa36e577857",
      "amount": 106.15,
      "currency": "USDT",
      "status": "enqueued",
      "timestamp": 1665491887
    }
  }
}

Payment sent (event: sent)

This information is communicated by webhook every time a payment is sent in our platform

{
  "data": {
    "event": "blockchain_payment_sent",
   	"attributes": {
    	"transaction_id": "6146ccf6a66d994f7c363db875e31ca35581450a4bf6d3be6cc9ac79233a69d0"
      "blockchain_payment_uuid": "691ab628-157f-4beb-8a2f-d17dfb323f3b",
      "blockchain_wallet_id": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
      "account_id": "f86bba92-ac98-4094-be92-aaa36e577857",
      "amount": 106.15,
      "currency": "USDT",
      "status": "pending",
      "timestamp": 1665491887
    }
  }
}

Payment failed (event: failed)

This information is communicated by webhook if for any reason the transaction process has not been finished.

{
  "error": {
    "event": "blockchain_payment_failed",
   	"attributes": {
      "blockchain_payment_uuid": "989eg9c7-3h8a-9d0a-987a-02ka192a8012",
      "message": "Insufficient balance"
    }
  }
}