## Classic workflow overview

In the **classic** (paperless) workflow, the RAO identifies the user, collects required documentation, creates the request, uploads documents, validates data, and approves the request. The user then receives an email with a link to complete certificate generation (pre-auth link).

## Steps

1. **Get first unused scratchcard** — [Get first unused scratchcard](/products/namirialpkiaas/registration-authority/openapi) with the RA id. Use the returned `sn` in the Create Request call.
2. **Create request** — [Create Request](/products/namirialpkiaas/registration-authority/openapi) with profile, `scratchcard`, `registration_authority`, user data (e.g. `country_name`, `serial_number`, `id_document_country`, `id_document_type`, `given_name`, `surname_1`, `surname_2`, `email`, `mobile_phone_number`), and `paperless_mode: 1`. Save the request `pk` for subsequent calls.
3. **Upload documents** — [Upload document](/products/namirialpkiaas/registration-authority/openapi) for each required type: `document_front`, `document_rear`, optionally `extra_document` and `document_owner` (selfie with ID). Use `POST /api/v1/requests/{id}/pl_upload_document/` with multipart/form-data.
4. **Generate RAO declaration** — [Generate RAO declaration](/products/namirialpkiaas/registration-authority/openapi) (`POST .../generates_tbs_receipt/`) with `rao` and `type: "APPROVE"`. The response contains the receipt for the RAO to sign.
5. **Generate contract** — [Get document](/products/namirialpkiaas/registration-authority/openapi) with `type: "contract"` and `rao_id` (`POST .../pl_get_document/`). Present the contract to the RAO and the subscriber.
6. **Approve request** — [Approve request](/products/namirialpkiaas/registration-authority/openapi) (`POST .../pl_approve/`) with RAO credentials (`username`, `password`, `pin`, `rao_id`) and the signed receipt. Request status becomes ENROLLREADY.
7. **Pre-auth link** — [Get pre-authentication link](/products/namirialpkiaas/registration-authority/openapi) (`POST .../preauthlink/`). The user receives an email with the link to complete certificate issuance (OTP, PIN, sign contract).


## Related documentation

- [Workflows overview](/products/namirialpkiaas/registration-authority/enterprise-documentation/products-and-modules/workflows/overview)
- [API reference (OpenAPI)](/products/namirialpkiaas/registration-authority/openapi)
- [Webhooks](/products/namirialpkiaas/registration-authority/enterprise-documentation/developer-documentation/callbacks/webhooks) (for VideoID; optional for classic)