Individual onboarding is asynchronous. After an application is submitted or upgraded, 1Money sends webhook events as KYC2 or EDD review progresses.

Use webhooks as your primary status signal, and reconcile missed or out-of-order events with Get Individual Application. Generic delivery headers, signature verification, retry behavior, and receiver best practices are documented in Webhooks.

Event Catalog

Event	Fires when	Important payload state	Next action
`kyc.submitted`	`POST /submit` is accepted and KYC2 review starts.	`kyc_status=PROCESSING`	Wait for the next webhook or poll the application.
`kyc.action_required`	KYC2 needs replacement ID or selfie documents.	`kyc_status=ACTION_REQUIRED`, `edd_status=NOT_REQUIRED`	Upload requested `ID_FRONT`, `ID_BACK`, or `SELFIE` documents, then call `POST /submit` again.
`kyc.under_review`	KYC2 is in manual review.	`kyc_status=UNDER_REVIEW`	Wait.
`kyc.approved`	KYC2 is approved and Tier2 is reached.	`kyc_status=APPROVED`, `tier=TIER2`	Use the account or optionally start Tier3/EDD.
`kyc.rejected`	KYC2 is rejected.	`kyc_status=REJECTED`	Terminal KYC2 state.
`kyc.upgrade_started`	`POST /upgrade` is accepted and EDD review starts.	`kyc_status=APPROVED`, `edd_status=PENDING`	Wait for the next EDD webhook.
`kyc.upgrade_action_required`	EDD needs additional information or POA, or KYC2 risk requires EDD before access.	`edd_status=REQUIRED`	Patch `due_diligence`, upload `POA` if requested, then call `POST /upgrade`.
`kyc.upgrade_under_review`	Tier3/EDD is in manual review.	`edd_status=PENDING`	Wait. Tier2 access is retained when KYC2 is already approved.
`kyc.upgrade_approved`	Tier3/EDD is approved.	`edd_status=APPROVED`, `tier=TIER3`	Terminal Tier3 state.
`kyc.upgrade_rejected`	Tier3/EDD is rejected.	`edd_status=REJECTED`, `tier=TIER2`	Terminal EDD state. Tier2 access is retained.

Payload Envelope

All individual onboarding events use the same top-level envelope:

{
  "event_name": "kyc.approved",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:approved:state"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "APPROVED",
    "edd_status": "NOT_REQUIRED",
    "tier": "TIER2"
  }
}

Field	Meaning
`event_name`	One of the `kyc.*` event names in the catalog above.
`resource.type`	Always `kyc_applicant` for individual onboarding webhooks.
`resource.id`	The individual application's `customer_id`.
`resource.idempotency_key`	Opaque platform deduplication key. Do not parse its format.
`data.customer_id`	Same customer/application ID as `resource.id`.
`data.submit_cycle`	Submit attempt counter. It increments on each accepted `POST /submit` and `POST /upgrade`.
`data.kyc_status`	Current KYC2 status after the transition.
`data.edd_status`	Current EDD/Tier3 status after the transition.
`data.tier`	Approved tier when applicable. It is `null` while no tier has been resolved for that transition.
`data.action_required`	Present only when partner action is required. Omitted otherwise.
`data.client_idempotency_key`	Echo of the `Idempotency-Key` header from the originating `POST /submit` or `POST /upgrade`, when provided. Omitted otherwise.

resource.idempotency_key is not the same thing as data.client_idempotency_key. Use resource.idempotency_key for receiver-side deduplication. Use data.client_idempotency_key only to correlate the webhook back to a partner request.

Status Values

kyc_status tracks the KYC2 lifecycle:

Status	Meaning
`DRAFT`	Application created but not submitted.
`PROCESSING`	KYC2 verification is running asynchronously.
`ACTION_REQUIRED`	Partner action is required.
`UNDER_REVIEW`	Manual review is in progress.
`APPROVED`	Tier2 is approved.
`REJECTED`	KYC2 is rejected.

edd_status tracks the Tier3/EDD lifecycle:

Status	Meaning
`NOT_REQUIRED`	EDD is not currently in scope.
`REQUIRED`	EDD data and POA are required before upgrade.
`PENDING`	EDD review is running asynchronously.
`APPROVED`	Tier3 is approved.
`REJECTED`	EDD is rejected.

Action Required Routing

There are two action-required paths:

Event	Meaning	Partner action
`kyc.action_required` with `edd_status=NOT_REQUIRED`	KYC2 document recovery.	Upload requested `ID_FRONT`, `ID_BACK`, or `SELFIE` documents, then call `POST /submit`.
`kyc.upgrade_action_required` with `edd_status=REQUIRED`	EDD/Tier3 recovery or KYC2 risk requiring EDD before access.	Patch `due_diligence`, upload `POA` if requested, then call `POST /upgrade`.

When data.action_required.items is non-empty, each item identifies a document or field that needs replacement. When items is empty, the next action is usually missing EDD fields; the latest 400 edd_data_incomplete response identifies which fields are missing.

Examples

All examples below use the same customer_id for readability.

`kyc.submitted`

POST /submit was accepted and asynchronous KYC2 review started.

{
  "event_name": "kyc.submitted",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:submitted:state"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "PROCESSING",
    "edd_status": "NOT_REQUIRED",
    "tier": null,
    "client_idempotency_key": "partner-submit-001"
  }
}

`kyc.action_required`

KYC2 requested replacement ID/Selfie documents. Upload the requested document types, then call POST /submit again.

{
  "event_name": "kyc.action_required",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:action_required:id_selfie"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "ACTION_REQUIRED",
    "edd_status": "NOT_REQUIRED",
    "tier": null,
    "action_required": {
      "items": [
        {
          "type": "document",
          "doc": "ID_FRONT",
          "reason": "blurry"
        },
        {
          "type": "document",
          "doc": "SELFIE",
          "reason": "face_not_visible"
        }
      ]
    }
  }
}

`kyc.under_review`

KYC2 moved to manual review.

{
  "event_name": "kyc.under_review",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:under_review:state"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "UNDER_REVIEW",
    "edd_status": "NOT_REQUIRED",
    "tier": null
  }
}

`kyc.approved`

KYC2 is approved and the customer has Tier2 access.

{
  "event_name": "kyc.approved",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:approved:state"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "APPROVED",
    "edd_status": "NOT_REQUIRED",
    "tier": "TIER2"
  }
}

`kyc.rejected`

KYC2 was rejected. This is a terminal KYC2 outcome.

{
  "event_name": "kyc.rejected",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:rejected:state"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "REJECTED",
    "edd_status": "NOT_REQUIRED",
    "tier": null
  }
}

`kyc.upgrade_started`

POST /upgrade was accepted and EDD review started.

{
  "event_name": "kyc.upgrade_started",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c2:upgrade_started:edd"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 2,
    "kyc_status": "APPROVED",
    "edd_status": "PENDING",
    "tier": "TIER2",
    "client_idempotency_key": "partner-upgrade-001"
  }
}

`kyc.upgrade_action_required`

EDD/Tier3 needs partner action. If items is empty, provide missing due_diligence fields. If items lists POA, upload a replacement POA. Then call POST /upgrade.

{
  "event_name": "kyc.upgrade_action_required",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c2:upgrade_action_required:poa"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 2,
    "kyc_status": "APPROVED",
    "edd_status": "REQUIRED",
    "tier": "TIER2",
    "action_required": {
      "items": [
        {
          "type": "document",
          "doc": "POA",
          "reason": "address_mismatch"
        }
      ]
    }
  }
}

KYC2 can also require EDD before Tier2 access. In that case the event is still kyc.upgrade_action_required, but kyc_status is ACTION_REQUIRED:

{
  "event_name": "kyc.upgrade_action_required",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c1:upgrade_action_required:kyc2_high_requires_edd"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 1,
    "kyc_status": "ACTION_REQUIRED",
    "edd_status": "REQUIRED",
    "tier": null,
    "action_required": {
      "items": []
    }
  }
}

`kyc.upgrade_under_review`

Tier3/EDD moved to manual review.

{
  "event_name": "kyc.upgrade_under_review",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c2:upgrade_under_review:edd"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 2,
    "kyc_status": "APPROVED",
    "edd_status": "PENDING",
    "tier": null
  }
}

`kyc.upgrade_approved`

Tier3/EDD was approved.

{
  "event_name": "kyc.upgrade_approved",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c2:upgrade_approved:edd"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 2,
    "kyc_status": "APPROVED",
    "edd_status": "APPROVED",
    "tier": "TIER3"
  }
}

`kyc.upgrade_rejected`

Tier3/EDD was rejected. The customer keeps Tier2 access when kyc_status=APPROVED and tier=TIER2.

{
  "event_name": "kyc.upgrade_rejected",
  "resource": {
    "type": "kyc_applicant",
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "idempotency_key": "kyc:550e8400-e29b-41d4-a716-446655440000:c2:upgrade_rejected:edd"
  },
  "data": {
    "customer_id": "550e8400-e29b-41d4-a716-446655440000",
    "submit_cycle": 2,
    "kyc_status": "APPROVED",
    "edd_status": "REJECTED",
    "tier": "TIER2"
  }
}

Deduplication and Ordering

Webhook delivery is at least once and may arrive out of order. Use this receiver-side dedup tuple:

(event_name, resource.id, resource.idempotency_key)

Do not deduplicate only by (event_name, resource.id): the same customer can legitimately receive the same event name across different submit cycles or EDD attempts.

Use data.submit_cycle and the latest state from Get Individual Application to reconcile event ordering.