Skip to content
Core · NextAPI

Embed Philippine payments into your platform

Use one BSP-covered API for QR Ph collections, InstaPay and PESONet payouts, multi-merchant accounts, webhooks, and ledger-backed reconciliation.

View Developer Docs Talk to Sales

Free sandbox. No approval required.

Signed Webhooks
prove every payment state change
Ledger Reconciliation
trace balances from one source
Merchant Wallets
isolate funds across platform users
BSP OPS Coverage
embed payments without your own license

Build vs. embed

The API replaces the payment company you did not mean to build

Platform teams need payment features, not a year of licensing work, bank coordination, and reconciliation tooling before product launch.

Build It Yourself

12+ months pursuing an OPS license before launch

Embed NextAPI

Embed payment flows under NextPay BSP OPS coverage

Build It Yourself

Separate bank and wallet integrations for every rail

Embed NextAPI

One REST API for QR Ph, InstaPay, and PESONet movement

Build It Yourself

Manual statement matching after payouts and collections

Embed NextAPI

Double-entry ledger entries and webhook confirmations

Build It Yourself

Rail health, retries, and failures handled by hand

Embed NextAPI

Provider routing, status events, and traceable payout records

Platform fit

Built for teams that need more than a dashboard

NextAPI is for software platforms where payment movement is part of the product experience.

POS and Kiosk Networks

+
Give every store, terminal, or kiosk its own QR Ph collection path and reconcile payments centrally.

Lending Companies

+
Disburse approved loans, collect repayments, and keep every borrower movement traceable.

HRIS and Payroll Platforms

+
Send salaries to employees across banks and wallets without exporting every cycle to a bank portal.

Gig and Marketplace Apps

+
Pay riders, sellers, or contractors after completed work with webhook-backed payout status.

Subscription Billing Platforms

+
Collect recurring bills through QR Ph and keep account balances aligned to your product state.

E-commerce and Payment Platforms

+
Accept customer payments, split funds by merchant, and pay suppliers from the same integration.

System model

One platform integration. Many merchants. Many accounts. One audit trail.

Model your product the way money actually moves: the partner owns the integration, merchants keep isolated accounts, and every collection or payout posts to the ledger.

Your Platform

Product logic, users, permissions, and payment experience

API Keys Webhooks Ledger

NextAPI

Partner

Merchants

Accounts

QR Ph Collections

InstaPay Payouts

PESONet Batches

Capabilities

Everything payment-critical stays traceable

Collections, payouts, balances, and status changes share one infrastructure layer instead of separate vendors and spreadsheets.

Money-in + money-out

Collect, hold, pay out, and reconcile from the same ledger

Use QR Ph for customer collection, send payouts through Philippine rails, and query the ledger when finance or support needs an exact record. 

POST /v2/payment-intents
{ "amount": 50000, "currency": "PHP", "channels": ["qrph"] }
// -> { "status": "pending", "qr_code": "..." }

GET /v2/ledger/accounts/{account_id}
// -> { "balance": 125000, "currency": "PHP" }

Webhooks & status

Signed events replace payout guesswork

Your product can update balances, unlock access, notify support, or retry workflows when a payment state changes.

payout.processing
payout.succeeded
payment_intent.succeeded

Merchants

Partner, Merchant, and Account Hierarchy

+
Create isolated merchant wallets under your platform so funds, fees, and balances stay separated.

Routing

Rail Selection Without Per-Bank Work

+
Use QR Ph, InstaPay, and PESONet through one integration while NextPay handles provider coordination.

Sandbox

Sandbox to Production

+
Build against test credentials, validate event handling, then move through commercial and compliance onboarding.

Security and compliance

The regulated work sits below your product

NextAPI is built for platform teams that need a credible compliance answer before engineering can ship payment features.

BSP OPS Coverage

+
NextPay operates under its Operator of Payment System license so partners can embed payments without becoming the licensed payment operator.

Secuna-Tested Security

+
Independent penetration testing, TLS-only transport, and server-side credentials for financial transaction workflows.

Signed Event Delivery

+
HMAC-signed webhooks and timestamped audit records help teams prove what happened when a payment state changes.

AML Monitoring

+
Compliance operations and transaction monitoring are handled through NextPay's regulated payment infrastructure.

Access & pricing

Start in sandbox. Price production around volume.

NextAPI is available through Pro Plus or a partner agreement. Sandbox access is open for evaluation; production access is volume-based and requires commercial and compliance onboarding.

View Developer Docs Talk to Sales

Free sandbox. We respond to production requests within one business day.

Sandbox

Start with test credentials

Explore the API surface, simulate payment events, and validate webhook handling before a sales conversation.

Free sandbox. No approval required.

Production

Move through partner onboarding

Live rails are enabled after platform model review, KYB, compliance checks, and a signed partner agreement.

Production access is configured for your use case.

Pricing

Pay for processed volume

Pricing is governed by partner terms and transaction volume, not a fixed fee for every merchant account you create.

No per-merchant account fees.

Path to production

Production access follows your money movement model

Review docs, validate how money moves through your product, complete commercial and compliance onboarding, then enable production rails.

  1. 1

    Review the API surface

    Start with the NextAPI developer docs to understand QR Ph collections, InstaPay and PESONet payouts, merchant accounts, webhooks, and ledger records.

  2. 2

    Validate the platform model

    Confirm how your product will map partners, merchants, accounts, balances, and payment events before production access is configured.

  3. 3

    Complete commercial and compliance onboarding

    Work with the NextPay team on pricing, KYB requirements, compliance review, and the commercial agreement for your platform volume.

  4. 4

    Enable production rails

    Move from test credentials to live QR Ph, InstaPay, PESONet, webhook, and ledger flows once onboarding is complete.

Before you integrate

Questions platform teams ask before embedding payments

What is NextAPI?

NextAPI is NextPay's embedded payments API for Philippine platforms. It lets software teams add QR Ph collections, InstaPay and PESONet payouts, merchant and account structures, signed webhooks, and ledger-backed reconciliation without building every bank, wallet, and compliance integration themselves.

Which Philippine banks and e-wallets does NextAPI support?

NextAPI is built for Philippine payment flows across QR Ph collections, InstaPay payouts, PESONet batches, and local bank and wallet destinations. It runs on NextPay infrastructure with coverage across 90+ Philippine banks and e-wallets, including common destinations such as GCash and Maya.

Do platforms need their own OPS license to use NextAPI?

NextAPI is designed for platforms that want embedded payment capabilities without becoming the licensed payment operator themselves. NextPay operates under its BSP Operator of Payment System license while partners complete commercial and compliance onboarding before production rails are enabled for live use.

Does NextAPI include webhooks?

NextAPI includes signed webhooks for payment state changes, so platforms can update balances, unlock access, notify support, or retry workflows when collections or payouts move. Webhook events are part of the audit trail alongside ledger records and payment status.

How do teams move from sandbox to production?

NextAPI teams start by reviewing the API surface and validating how their platform maps partners, merchants, accounts, balances, and payment events. Production access follows commercial and compliance onboarding, then live QR Ph, InstaPay, PESONet, webhook, and ledger flows are enabled for launch.

Next step

Build the payment layer your platform needs

Start with the API surface, then talk with NextPay when your platform model is ready for production.

View Developer Docs Talk to Sales

Free sandbox. No approval required.