Skip to content

Move Money Across the Philippines

BSP-regulated payment infrastructure for Philippine payouts, collections, and invoicing. Use the REST API, or run finance operations from a dashboard.

BSP-regulated · YC W21

BSP-Regulated
Operator of Payment System
YC W21
Backed by Y Combinator
₱28B+ Processed Volume
Across Philippine Payments

Payment operations still break in the same places

Bank portals, follow-up messages, and licensing workarounds slow teams down before money even moves.

What slows teams down

01

Payout day becomes portal work

Bank logins, CSV formats, cut-off windows, and status checks turn one batch into hours of manual work.

02

Collections turn into follow-up

Teams chase payment screenshots, send reminders by hand, and reconcile records after the fact.

03

Payment products stall before launch

APIs, bank coverage, compliance reviews, and licensing work stretch timelines before money can move.

What changes with NextPay

The workarounds collapse into one regulated payment layer

Teams move payouts, collections, and payment records through one operating layer.

API workflows01
Reconciliation02
Dashboard workflows03
Regulated infrastructure04

NextPay replaces the workaround stack with regulated payment infrastructure your team can use by dashboard or API.

For Developers & Platforms

One API for money-in and money-out

Embed collections, payouts, and multi-merchant accounts without applying for your own BSP license. Sandbox, webhooks, and Postman support are ready from day one.

  • 90+ Philippine banks and e-wallets connected
  • Money-in + money-out in one integration
  • Multi-merchant accounts with isolated settlement
  • Webhook delivery with idempotency keys
View API docs

Free sandbox. No approval required.

Products

One infrastructure layer for every payment workflow

Build by API, run payouts from the dashboard, send invoices, or let customers pay through self-service collection.

NEXTAPI · Core

Build directly on the payment infrastructure

Use NextAPI when your product needs embedded collections, payouts, or multi-merchant accounts instead of a ready-made workflow.

Why teams start here

REST API for payouts, collections, and multi-merchant accounts
Free sandbox with webhooks, idempotency keys, and Postman support
BSP-regulated rails without a 12-month licensing timeline
Best for platforms building payment flows into their own product

Workflow example

Send batch payouts

Review recipients, send funds, and watch status resolve in one workflow.

Explore NextPayout

Get Started

Choose the starting path that matches your workflow

Start with API access, a finance-operations walkthrough, or a simple collection link. Each path runs on the same regulated NextPay infrastructure.

For platformsNextAPI

Build payments into your product

Use the API path when payouts, collections, merchant wallets, webhooks, or reconciliation need to live inside your own product experience.

01

Explore the docs

Review the payment flows, webhook events, and sandbox behavior before writing production code.

02

Test in sandbox

Create test payment intents, payout calls, and ledger checks without moving real funds.

03

Scope production access

Work with NextPay on commercial fit, compliance requirements, and the path from test keys to live rails.

For finance teamsNextPayout + NextInvoice

Run payouts, invoices, and receivables

Use the dashboard path when your team needs payroll, supplier payouts, invoice sending, AR tracking, reminders, and reconciliation from one operating layer.

01

Book a walkthrough

Show us the payout, invoice, or receivables workflow your team wants to move out of spreadsheets and bank portals.

02

Map the right setup

Match your workflow to NextPayout, NextInvoice, or both, including users, approvals, payment rails, and reporting.

03

Launch with your team

Move real finance work into the dashboard with onboarding support and clear records for every payment state.

For solo professionalsNextCollect

Collect with a simple bill link

Use the lightweight path when you need to request payment, follow up politely, and see who has paid without setting up full invoicing.

01

Create the bill link

Enter the amount, due date, and short note for the client or customer who needs to pay.

02

Share it anywhere

Send the link through SMS, email, Messenger, Viber, or the channel where your client already replies.

03

Let reminders track payment

NextCollect can send professional SMS reminders and keep the status visible until the bill is paid.

Operational trust

Payment operations need accountable support

NextPay pairs regulated payment infrastructure with payment-operations support: award-winning CX, independent security testing, and a team that can trace payment issues instead of forwarding tickets.

86.9%
Customer Satisfaction Score

Exceeds the industry average, measured across all support interactions.

KMC Silver
Customer Experience Excellence

Awarded at the KMC Startup Awards 2025.

Security Tested
Independent Review by Secuna

External testers probe for exploitable weaknesses before they reach payment operations.

BSP-Regulated
Operator of Payment System

Regulated by the Bangko Sentral ng Pilipinas. Not a remittance agent; an Operator of Payment System.

Customer Stories

From payday errands to link approval

Stories from Philippine teams that moved payment work out of bank errands, spreadsheets, and account-opening detours.

Case 01/MarketConnect Inc./Payroll Approvals

One payday errand became one approval link.

"Our messengers used to spend an entire day on paydays just to have checks signed, encashed, and then deposited into our staff's respective bank accounts. With NextPay, we just approve by clicking links and done."

Stephanie Oller

MarketConnect Inc.

Manual work removed

01

Check signing

Replaced

02

Encashment run

Replaced

03

Deposit follow-up

Replaced

Final state: payroll approval by link.

Case 02

Finance Operations

Manual tracking and reconciliation move into one workflow.

What used to take hours of manual tracking is now done in just a few clicks. Reconciliation has also become significantly faster.

Builtamart·Christian Arvin Talosig, Finance Manager

Case 03

Bank Transfer Friction

Different banks, schedules, and transfer fees get consolidated.

Because of varying banks and unusual payment schedules, we spent a lot of time in different banks paying different transfer fees.

The Fourth Wall·Dae Lee

Case 04

Payroll Coverage

Payroll coverage without forcing every employee through another bank account.

NextPay allowed our clients to bypass the needlessly complicated account opening process of local banks.

Morningtide Capital Partners·Marvine Lawrence Sy, Managing Partner

Pricing

Know what you pay before money moves

Start with PayGo, compare monthly plans, or talk through API and volume pricing. No setup fees, no minimum balance, and VAT-inclusive listed fees.

Start with PayGo

For teams testing low-volume payouts before choosing a paid plan.

PHP 0

/mo

Scale with Plans

Lower payout fees as volume grows. NextInvoice starts at Pro; NextAPI starts at Pro Plus.

PHP 1,500+

/mo

Monthly Plans

Collect Separately

Start collecting without a subscription. Create and share bill links for free, then pay a collection fee only when money comes in.

2%

collection fee

Run Philippine payouts and collections on regulated infrastructure

Book a walkthrough for your payout, collection, or API use case. We will map the right NextPay path before you build or migrate.

BSP-regulated · Free sandbox available · No corporate bank account needed to start