Registration, approval and sign-in
Create the right account, understand retailer approval, and sign in safely on web and app.
English · Edition 1.1.0 · Updated 14 November 2026
Follow the guide for your account type. Available options depend on approval, current settings and app version.
Create a customer account
Workflow U-01
Before you start
- Use a mobile number you control and can receive SMS on.
- Read the current terms, refund policy and privacy notice.
Steps
- Choose Customer / personal account on registration and enter your mobile number.
- Enter the SMS verification code. If delivery fails, wait for the resend control and verify the number rather than repeatedly requesting codes.
- Complete the required profile details, create a password and six-digit payment PIN, and confirm the credentials.
- Accept the current terms/refund policy and acknowledge the privacy notice, then submit.
A valid personal registration activates the customer account without a retailer NIC or registration-fee review. Normal customer transaction and balance limits still apply.
Exceptions and controls
- An existing number must use sign-in/recovery instead of creating another account.
- Invalid, expired or over-attempted codes require a fresh permitted verification attempt. Never share a code with support.
Create a retailer account
Workflow U-02
Before you start
- Have your own mobile number, identity documents and genuine retailer registration-payment receipt ready.
- Use the receiving bank instructions shown in the application; do not copy bank details from an old message.
Steps
- Choose Retailer and complete phone SMS verification.
- Enter the required person/shop details, password and payment PIN. Upload the requested NIC images.
- Upload the LKR 1,500 registration-payment receipt and enter its bank transfer reference.
- Review the policy acknowledgements and submit. Follow the displayed WhatsApp support instruction using the registered number and transfer reference; the application opens the contact action but does not send a message for you.
- Wait while Finance verifies the actual receiving-bank credit and authorized staff review identity/account eligibility.
- If the fee receipt is rejected, inspect the reason and use the replacement-receipt workflow. Do not replace an already approved payment.
Submission creates a pending application. Fee approval and account approval are separate. The registration fee is registration income, not wallet funding; approval does not add spendable wallet money.
Exceptions and controls
- An unverified/rejected fee blocks self-registered retailer activation.
- The same transfer cannot be used again as a wallet deposit or another registration payment.
- Existing accounts and staff-created/converted accounts follow their applicable staff workflow; the fee is not automatically backfilled to historical accounts.
Sign in and use a trusted device
Workflow U-03
Steps
- Use the registered mobile number and password. Complete the verification shown on the screen.
- The ordinary website member flow asks for an SMS login code. Native customer/retailer password sign-in does not request an SMS login code.
- For customers and retailers, quick six-digit PIN sign-in is enabled by default after the first successful app password sign-in. Refreshing or reopening a remembered app returns to the locked PIN screen; the server checks the PIN before opening the account. Manage or disable this in Account → Sign-in settings. Native biometric unlock is optional on supported devices.
- Use Sign out on shared devices. Lock NowPay is a local protection action, not a replacement for signing out or revoking a lost device.
You reach your account’s permitted Home/Dashboard. Pending, suspended or rejected accounts do not gain normal spending permissions.
Exceptions and controls
- Repeated wrong passwords/PINs trigger security lockouts. Follow the recovery screen instead of repeatedly guessing.
- Signing out, disabling quick PIN, clearing app/site data, or revoking the trusted device can require mobile number and password again. The hosted app needs its security cookies; remembered identity alone cannot unlock an account.
- An older app or hosted version may not include persistent PIN sign-in. Contact support if refreshing or reopening a remembered app still asks for a password. Staff still follow staff sign-in verification.
Recover a password or payment PIN
Workflow U-04
Steps
- For a forgotten password, open the password recovery flow, verify ownership as requested, and choose/confirm a valid new password.
- For a forgotten member payment PIN, sign in, open Account security, recheck your current password, and complete the requested SMS ownership proof before choosing the new PIN.
- After a credential change, sign in again on other devices if requested. Credential/security changes can revoke sessions, trusted devices and API access.
The new credential is usable after the server completes verification. A recovery request alone does not change it.
Exceptions and controls
- If you no longer control the registered number, contact support for an ownership review; there is no public bypass code.