Printable Guide
LakiPay Integration Checklist
Use this checklist to confirm every onboarding milestone before launching live payments. Click print to generate a PDF or keep this tab open while you work through the steps.
1. Account Setup & Phone Verification
- Create your merchant account at dashboard.lakipay.com/signup.
- Provide phone number (+251 format), title, first/last name, password, and hint.
- Accept the service agreement and submit the form.
- Enter the 6-digit SMS OTP (request a new code if the first one expires).
- Confirm the verified phone appears in your profile before continuing.
2. Business Approval Package
- Business info: TIN, legal name, trading name, registration number, industry, business type, established date, website URL.
- Contact info: authorized representative name, email, phone, region, city, sub-city, woreda, postal code, optional secondary phone.
- Upload documents: TIN Certificate (required), Business License (required), Betting Certificate (optional for gaming).
- Review every field and submit—approval SLA is typically 1–2 business days.
3. Security & Access Controls
- Enable MFA for all dashboard users and enforce strong passwords.
- Assign least-privilege roles; audit access quarterly.
- Document escalation contacts for fraud/incident response.
- Whitelist trusted IPs for critical dashboard roles when possible.
4. API Keys & Environment
- Navigate to Settings → API Keys and select “Create New API Key.”
- Name the key (e.g., “My Web App - Production”) and add a description.
- Select capabilities (process payments, withdraw funds) appropriate to the workload.
- Copy the secret key immediately—it's shown only once—and store it securely.
- Configure webhooks/callback URLs; test in sandbox before production cutover.
5. Pre-Launch Validation
- Run end-to-end flows for payment initiation, success, failure, and refunds.
- Validate settlement schedules, wallet balances, and reporting exports.
- Deploy QR placeholders or checkout copy across touchpoints.
- Share support/escalation plan with internal teams before go-live.