OTP Certificate Flow¶
This page explains the end-to-end OTP flow for company users in plain language. This is the operational OTP certificate process (customs workflow), not the login Email OTP code flow.
OTP screen layout¶

Highlighted sections:
- OTP status counters: pending, ready, issued, and compliance issues.
- Step tabs: Incoming Declarations, Apply by Customs Entry, Applications, Issued OTPs.
- Submit customs entry: start a new OTP request from iCMS declaration number.
- Built-in OTP flow guidance: visible process explanation inside the page.
- Entry number + submit action: the required input and action button.
Happy path (standard flow)¶
- Get customs entry number from iCMS.
- Open OTP – One Time Password in the Company Portal.
- Go to Apply by Customs Entry.
- Enter the customs entry number and submit.
- Wait for validation and approval checks.
- Complete payment when invoice is issued.
- System generates the OTP.
- Track issued OTP from Issued OTPs.
Sad path (common failure cases)¶
| Scenario | What you see | What to do |
|---|---|---|
| Entry number not found | Validation error or no matching declaration | Reconfirm entry number in iCMS and retry |
| Company document expired | Compliance warning / blocked progression | Upload renewed document, then reprocess |
| Membership inactive | Request blocked pending compliance | Contact association for membership status resolution |
| Payment not completed | OTP not issued after application review | Complete payment from invoices/wallet and refresh |
| iCMS integration delay | Application stays pending longer than expected | Wait for sync window, then check status again |
Quick operator checklist¶
- Entry number copied correctly
- KRA PIN and company profile up to date
- Mandatory compliance documents valid
- Invoice paid and payment confirmation posted
- Final OTP visible under Issued OTPs