Created Provision

At this step, provisioning the user is finalized when you notice the sub_status = PENDING_PROCESS_USER_ONBOARDING . At this stage, the user is required to perform actions to finalize the onboarding. And company can use the next onboarding API to send the KYC data to bunq for validation.

Endpoint:

GET /v1/partner-user-provision/{provision_id}

Response - Active Provision:

{
    "Response": [
        {
            "PartnerUserProvision": {
                "id": 123,
                "created": "2025-08-13 14:45:18.621550",
                "updated": "2025-08-13 14:45:25.345678",
                "external_uuid": "550e8400-e29b-41d4-a716-446655440000",
                "status": "CREATED",
                "sub_status": "PENDING_PROCESS_USER_ONBOARDING",
                "action_required": "USER",
                "products": ["USER_VERIFIED"],
                "label_user": {
                    "uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
                    "display_name": "User Name",
                    "country": "NL",
                    "avatar": {...},
                    "public_nick_name": "UserNick",
                    "type": "PERSON"
                },
                "oauth_request": {
                    "id": 456,
                    "created": "2025-08-13 14:45:24.123456",
                    "updated": "2025-08-13 14:45:24.123456",
                    "status": "ACTIVE",
                    "scope": ["PAYMENT_INFORMATION"],
                    "redirect_url": "https://www.bunq.com/",
                    "authorization_code": "auth_code_123",
                    "client_id": "client_id_456"
                },
                "credential": {
                    "id": 789,
                    "created": "2025-08-13 14:45:24.567890",
                    "updated": "2025-08-13 14:45:24.567890",
                    "status": "ACTIVE",
                    "expiry_time": "2025-08-20 14:45:24.567890",
                    "token_value": "credential_token_abc123def456",
                    "permitted_device": {
                        "description": "Partner API Device",
                        "ip": "192.168.1.100"
                    }
                }
            }
        }
    ]
}

Status Explanation:

• Status: ACTIVE - The provision is fully active and ready to use

• Sub Status: NONE - No further processing required

• oauth_request: Contains OAuth details for API access

• credential: Contains user credential information

At this point, the user account is fully provisioned and you can use the OAuth details to make API calls on behalf of the user.