NowPay user guide
Retailer selling, referrals and API integration
Operate a retailer account and connect your own POS or application using the supported API.
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.
Serve a customer from your retailer wallet
Workflow U-14
Steps
- Make sure your retailer account is approved and funded through a verified funding method.
- Confirm the customer’s intended service, operator, exact recipient and amount/package.
- Review the retailer price and currency. Your sale to the customer and your own accounting remain your responsibility.
- Authorize the NowPay payment with your PIN, or use a properly authorized server-side API integration.
- Give the customer the appropriate receipt/reference and reconcile the actual wallet debit and final status.
Expected result
The order spends your retailer wallet at current retailer pricing. Recipient registration with NowPay is not required.
Exceptions and controls
- Do not represent a commission/multiplier example as a permanent tariff.
- A failed/uncertain result must be traced before retrying or promising a refund.
Refer another retailer
Workflow U-15
Steps
- Open Refer & earn and share your own referral link/code.
- The new eligible retailer uses the code during the applicable signup workflow.
- Wait for the referred retailer’s first successful order and inspect the resulting reward/statement.
- Use the referral screen to review linked accounts and earned rewards.
Expected result
The configured eligible first-success referral reward is paid once. Personal customer registration is not the retailer referral programme, and registering alone is not a first sale.
Connect a POS, website or own application
Workflow U-16
Before you start
- An approved retailer account, enabled Reseller API feature and sufficient funds are required.
Steps
- Open Reseller API on the website, label a key and confirm your payment PIN. Save the full key immediately; it is displayed once.
- Keep the key on your own authenticated backend in a secret/environment store, never in browser/mobile client code or a URL.
- Read the balance, operator and package endpoints first. For paid submissions, save one unique reference and exact payload before POST.
- Inspect the returned order status and actual debit; HTTP success alone is not proof of delivery.
- After a timeout, query/retry the original reference rather than generating a second payment.
- Rotate/revoke keys when needed and use the complete English/Sinhala/Tamil API guide for examples, fields, pricing and errors.
Expected result
Key-authenticated API payments use the same wallet/order rules. The API key itself authorizes spending; each API request does not ask for a separate PIN.
Exceptions and controls
- Up to five active keys are allowed. Keys revoked by account security changes must be replaced.
- Feature disablement returns unavailable/not-found behavior. Reading documentation does not enable the API.