February 9, 2026 — Reap Compliance API v1.0.2

This release adds PENDING webhook notifications for identity verification and improves support for single-line name documents.

Breaking Changes

Action Required: Update your webhook handlers before enabling PENDING webhooks.

• PENDING Webhook Notifications
  • Webhooks are now sent when identity verification requirements are submitted and marked as PENDING.
  • Previously, only APPROVED and REJECTED statuses triggered webhooks.
  • Impact: Clients must update webhook handlers to process PENDING status.
  • Rollout: Disabled by default. Contact support to enable for your business.

Required client update:

switch (data.status) {
  case 'APPROVED':
    // Handle approved
    break;
  case 'PENDING':    // ← NEW: Add this case
    // Handle pending - application received
    break;
  case 'REJECTED':
    // Handle rejected
    break;
  default:
    // Ignore unknown statuses (recommended)
    break;
}

KYC

• Generate Signed Identity Payload (GET /entity/{entityId}/signed-payload)
  • lastName now accepts empty strings for identity documents with single-line names (e.g., mononyms).
  • firstName remains required and cannot be empty.

Notifications

• Webhook Payloads
  • Added eventId field (UUID) for webhook event deduplication.

Notes

• The eventId field addition is non-breaking; existing integrations can ignore it.
• The lastName empty string support is non-breaking; field is still required but accepts "".
• PENDING webhooks require opt-in activation via support.