The signer's certificate
In live mode, a customer whose KYC gives an NID number holds one certificate at Radiant, whatever bank or app they sign through. It is valid for a year and it is theirs: your bank’s signings use it, and so do other banks’ and the ePahichan app.
Send signer.kyc with the NID number and signer.identity on every live request. ePahichan draws the certificate application (Schedule 5) from them and has it signed only when the certificate has to be issued.
What a signing does with it
Section titled “What a signing does with it”| The customer’s certificate | Your signing | Billed to you |
|---|---|---|
| Valid | Signs with it; the application is marked not_needed |
No |
| None yet, expired, or revoked | Issues a new one from your KYC, then signs the application and your documents with the same code | Yes |
| Owed free by Radiant | Issues it | No |
| Suspended | Refused: certificate_suspended |
No |
Your KYC must be under 24 hours old. A signed document stays valid after the certificate expires: every live signature carries a trusted timestamp and the revocation lists that show the certificate was good when it signed.
POST /v1/signers/certificate with the customer’s phone tells you which it will be (next_signing).
A new mobile
Section titled “A new mobile”If the NID number is registered with another mobile, accept answers mobile_confirmation_required and a code goes to the request’s number. The customer types it in your app; send it to POST /v1/signing-requests/{id}/mobile-confirmation, then accept again. Their old number is told.
A second person on the same mobile is refused. Everyone needs their own number.
A forgotten PIN
Section titled “A forgotten PIN”A customer who forgot or locked their eSign PIN resets it from your app: POST /v1/signing-requests/{id}/pin-reset (your request’s KYC must match the one registered), then …/pin-reset/confirm with the code Radiant texts them and the new PIN. Then confirm the request with the new PIN.
A request that was waiting
Section titled “A request that was waiting”If the customer’s certificate is revoked or suspended while a request waits for their code, the request fails with failure_code certificate_revoked or certificate_suspended, and you receive signing_request.failed. A new request issues a new certificate after a revocation; after a suspension it waits until the suspension ends.
What your bank can do
Section titled “What your bank can do”Your bank is a KYC source, not a registration authority, so it does not revoke certificates on its own authority.
| The customer… | Call | What happens |
|---|---|---|
| Asks you to revoke it | POST /v1/signers/revocation-requests, then …/{id}/confirm with the code Radiant texts them |
Revoked once they confirm, within a day. Documents signed before stay valid |
| Lost their phone | POST /v1/signers/compromise-reports |
Suspended at once. Once they verify a new mobile, their next signing issues a new one |
| May be a victim of fraud, gave false details, has died, or is under a court or Controller order | POST /v1/signers/review-requests |
NCC decides, with the notice periods the Electronic Transactions Rules set. A death needs the death certificate, uploaded first with POST /v1/files |
A loan default or a closed account is not a reason to revoke. To stop your own signings for a customer at once, use POST /v1/signer-blocks: requests waiting for them are canceled, and the certificate is untouched. POST /v1/signer-blocks/{id}/lift lets them resume.