Skip to content
Registration Authority
/
/
/
Classic workflow
Last updated

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 with the RA id. Use the returned sn in the Create Request call.

  2. Create request — Create Request 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 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 (POST .../generates_tbs_receipt/) with rao and type: "APPROVE". The response contains the receipt for the RAO to sign.

  5. Generate contract — Get document with type: "contract" and rao_id (POST .../pl_get_document/). Present the contract to the RAO and the subscriber.

  6. Approve request — Approve request (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 (POST .../preauthlink/). The user receives an email with the link to complete certificate issuance (OTP, PIN, sign contract).

Previous page
Next page