Merchant SaaS Platforms

"I run a POS system used by 500 restaurants. My merchants want QR Ph payments built into the checkout screen."

If you build software for a network of merchants — restaurants, sari-sari stores, clinics, retail shops — NextAPI lets you offer embedded QRPH collection to every merchant on your platform through a single integration.

The problem

Your merchants ask for QR Ph. Building it yourself means getting a BSP license (12+ months, millions of pesos), integrating with banks one by one, and maintaining compliance workflows for each merchant. Your product is a POS or ordering platform — not a payment company.

Other platforms charge per-merchant account fees — at 500 merchants, that can reach tens of thousands of pesos monthly in account fees before a single transaction processes. And most are months away from having platform APIs that actually work.

How NextAPI fits

NextAPI's three-tier hierarchy maps directly to your platform:

Your Platform (Partner)
├── Restaurant A (Merchant)
│   └── Collections Account (Account)
├── Restaurant B (Merchant)
│   └── Collections Account (Account)
└── ...

• No per-merchant fees. Create unlimited merchants and accounts. You pay only on transaction volume.
• Each merchant gets their own QR code and collection account — funds don't commingle.
• Your platform's dashboard shows transaction data per merchant via GET /v2/accounts/{id}/postings.
• Fee splits are handled through the ledger — collect the full amount, then use internal transfers to split between merchant net and platform fee.

Typical integration pattern

sequenceDiagram
    participant P as Your Platform
    participant N as NextAPI
    participant M as Merchant's Customer

    P->>N: POST /v2/merchants (onboard merchant)
    P->>N: POST /v2/accounts (create collection account)
    P->>N: POST /v2/accounts/{id}/funding-methods (generate QR)
    N-->>P: QRPH code / virtual account number
    P-->>M: Display QR at checkout
    M->>N: Scan & pay via GCash/Maya/bank app
    N-->>P: Webhook: payment_intent.paid
    P->>P: Update order status, credit merchant balance

Key API endpoints

Action	Endpoint
Onboard a merchant	POST /v2/merchants
Create collection account	POST /v2/accounts
Generate static QR	POST /v2/accounts/{id}/funding-methods
Generate one-time QR	POST /v2/payment-intents
Check merchant balance	GET /v2/accounts/{id}/balances
View transaction history	GET /v2/accounts/{id}/postings
Pay out to merchant's bank	POST /v2/payout-requests

What to build

Merchant onboarding flow: When a merchant signs up on your platform, call POST /v2/merchants and POST /v2/accounts to provision their payment infrastructure automatically. No manual steps required.

Checkout integration: Before displaying a checkout screen, call POST /v2/payment-intents to generate a QRPH code for the exact order amount. When the customer pays, NextAPI sends a webhook — your platform marks the order as paid.

Merchant dashboard: Use GET /v2/accounts/{id}/postings to show each merchant their real-time transaction history, settled amounts, and pending balance.

Settlement payouts: When a merchant requests a withdrawal, call POST /v2/payout-requests to send funds from their NextAPI account to their bank account.

Getting started

1. Get sandbox credentials — test with no real money
2. Follow Your First API Call to verify auth
3. Follow Accept a QRPH Payment to implement collection for your merchants
4. Read Wallet Structure to understand the hierarchy
5. Read Collections Lifecycle for the QRPH flow
6. Build your merchant onboarding and collection flow