Merchant sandbox · KYC-gated access

Integrate LipaPay with a governed sandbox, then switch to live.

Four products. One operating model: onboard, authenticate, initiate, confirm settlement, fulfill. API contracts stay inside the signed-in workspace — not on public pages.

KYC at registration
Sandbox ↔ Live switch after approval
Contracts hidden until sign-in

Products on this platform

Capability overviews are public. Endpoint catalogs open after KYC sign-in, in the environment you select.

Engine

LipaPay

Core settlement. Collect, receive confirmation, pull status — the spine every other product hangs on.

Auth Initiate Callback Status

Overview · no live funds in sandbox

Inbound

Lipa Collection

MNO push, bank collections, and hosted checkout. Same settlement model, then status pull before you fulfill.

MNO / Bank Callback Status

MNO · bank · hosted checkout

Airtime

LipaAirtime

Vouchers and wallet recharge. Confirm fulfillment before issuing value — never on initiate alone.

Login Recharge Confirm

Recharge · confirm · fulfill

Outbound

LipaDisbursement

Payouts from wallet. Pull-model reconciliation via payment history — no async webhook required.

Login Payment History

Payout · history pull

System flow

Every product follows initiate → pending → push (if any) → pull → fulfill. Never trust a callback alone.

1 · Onboard

Create a KYC-registered merchant. Isolated sandbox credentials only.

2 · Authenticate

Issue a merchant or product token inside the signed-in workspace.

3 · Initiate

Collection, airtime, or disbursement — capture every reference.

4 · Callback

Platform notifies your endpoint when settlement lands. Inspect deliveries in the console.

5 · Status pull

Confirm outcome from your backend before fulfilling the customer.

6 · Go live

After KYC approval, switch the workspace to Live and point your app at production.

Start as a registered merchant

KYC unlocks sandbox testing. Live contracts appear in the same console after approval.

Create account Sign in