Applications

Everything you build on RDCPASS lives inside an organization — your company, as a tenant of the platform. The organization holds your team, your commercial subscriptions and your billing. Inside it you create applications: one per product or integration, each with its own services, scopes, purposes, keys, webhooks and audit log.

Organizations and applications

Keeping applications separate is data minimization in practice: a loyalty programme that only needs age gating never holds the scopes your account-opening flow requires, and a key leaked from one application cannot reach another application’s data or purposes.

Creating an application

Owners, Administrators and Developers can create applications in the console at console.rdcpass.cd. The wizard takes a few minutes:

Application settings reference

Keys per environment

Sandbox and production are separate systems, and an application holds a separate set of credentials for each. A sandbox key never works in production, and the reverse.

Each environment can hold two active key sets at once so you can rotate without downtime: issue a new set, deploy it, confirm traffic has moved in the request logs, then revoke the old one. Revocation is immediate. The exact use of each credential is described in Authentication.

Editing scopes and purposes

Scopes are chosen per application, from the organization’s subscriptions — see KYC scopes & subscriptions for the full catalogue and the three-layer subscription model.

• Sandbox applications: changes apply immediately.
• Production applications: adding a scope, a purpose or a service creates a change request. A Compliance officer or Administrator submits a justification per scope; RDCPASS reviews it within the standard timeline. Existing scopes keep working throughout — nothing is interrupted while the request is under review.
• Sensitive or Biometric scopes added to a production application trigger enhanced due diligence (DPIA, legal basis, named data-protection officer).
• Removing a scope, purpose or service takes effect immediately and never needs review.
• If the organization cancels a scope subscription, the scope is removed from every application that selected it, and requests for it return 403 scope_not_granted.

Application statuses

An application’s production status follows the due-diligence review. Every change is sent to your webhook as application.production_status_changed.

The full review process, checklists and timelines are described in Going to production.

Audit log

Every change to an application is recorded in its audit log: who made it (by RDCPASS identity and role), when, from which IP address, and the values before and after. Owners, Administrators and Compliance officers can view and export it from the application’s Audit tab, as CSV or JSON. Audit events are retained for five years and cannot be edited or deleted.

{
  "id": "aud_3e91c7b20f",
  "object": "audit_event",
  "action": "application.scopes_change_requested",
  "application_id": "app_5d20e8a1c4",
  "actor": {
    "rdcpass_id": "COD-1908-0521-7730",
    "full_name": "Mbuyi Ilunga Nsimba",
    "role": "compliance_officer"
  },
  "ip_address": "196.223.14.82",
  "changes": {
    "scopes": {
      "before": ["kyc.basic", "kyc.documents.primary"],
      "after": ["kyc.basic", "kyc.documents.primary", "kyc.addresses"]
    }
  },
  "justification": "Proof of residence required by BCC instruction for tier-2 wallets.",
  "created_at": "2026-09-26T08:42:17Z"
}

Next steps