For Payroll, Benefits & EWA · Without your own licence

Pay every worker on the rails they already use.

A wallet per worker, the whole payroll in one batch, every run reconciled. Worker balances never sit under your licence.

  • Wallets
  • Payouts
  • Workflows
  • Ledgers
  • Onboarding & Verification
  • Control
  • Payments
Talk to an expert

Give every worker a balance.

Provision a wallet for every worker, programmatically. On-demand and earned-wage top-ups land on the same wallet in real time.

  • Wallets · one per worker, under your brand
  • Payouts · earned-wage top-ups over InstaPay
  • Onboarding & Verification · KYC on every worker

Pay thousands in one run.

Push a payroll across InstaPay, PESONet and QR Ph in one batch, by API or upload. Timing is stated per rail and cut-off.

  • Payouts · InstaPay real-time, PESONet same-business-day
  • Workflows · scheduled runs, validated before disbursement
  • Failures · reason code, funds held, safe retry

Reconcile the run, worker by worker.

Every disbursement matches to one source of truth against the bank of record. A retry or reversal posts as new history, never an edit.

  • Ledgers · append-only postings per payout
  • Reconciled against the bank of record, every run
  • Exports for your eBIRForms and eFPS filing

Developer API

A payroll run is one call.

Rows validate before money moves, and every state change is a webhook. No return files.

Read documentation
POST /v1/payout_batches
{  "id": "bat_7b21",  "object": "payout_batch",  "reference": "payroll_2026_02_15",  "rail": "pesonet",  "count": 1240,  "status": "processing",  "settlement": { "window": "same_business_day_batch" }}
How it runs

From upload to reconciled, in one run.

You fund each run before disbursement. TNKR settles to each rail and reconciles the batch.

  1. 01Submit and validate

    An API call or bulk upload. Account checks fail the row, not the batch.

  2. 02Fund and disburse

    Cover the run. TNKR settles to each rail, within its cut-off.

  3. 03Reconcile

    Every payout lands or retries. The run closes reconciled.

Built to be examined.

The regulated layer is ours and the workforce is yours. Request the due-diligence pack from the form.

Talk to an expert
Worker balances are e-money
Worker balances are electronic money issued by PayMongo Payments, Inc., the licensed Electronic Money Issuer. Not deposits, not PDIC-insured, and never held under your own licence.
We don’t sit in your flow of funds
Every run reconciles against the bank of record. Building on TNKR confers no licence on you and leaves your regulatory perimeter unchanged.
Worker PII, handled correctly
Processed under RA 10173. TNKR is your personal information processor, with a data-processing agreement. You stay the controller of your workforce records.
The licensed entity is named
TNKR is a product of PayMongo. PayMongo is regulated by the Bangko Sentral ng Pilipinas: PayMongo Philippines, Inc. as Operator of Payment System; PayMongo Payments, Inc. as Electronic Money Issuer. PCI DSS and SOC 2 Type 2 certified. The licensed entity behind each flow is confirmed in your due-diligence pack.

The bundled stack

See all products
FAQ

Payroll & benefits questions, answered.

What payroll and ops teams ask, answered in writing.

Talk to an expert

How do I run bulk payroll disbursement across PH rails?

One batch across InstaPay, PESONet and QR Ph, submitted by API or bulk upload. Every payment’s status arrives by webhook, and the run reconciles to one ledger.

How fast do workers receive pay?

InstaPay clears in real time. PESONet settles in a same-business-day batch, within cut-off. Timing is stated per rail, never as a blanket “instant”.

Can earned-wage-access providers build on TNKR?

Yes. Provision a wallet per worker under your brand and push payouts on demand. TNKR moves the money, and the EWA product and its regulatory treatment stay yours.

Do I need to prefund payouts?

Yes. You fund each run before disbursement, and TNKR settles to each rail and reconciles the batch. Funding and settlement timing are stated per rail.

What happens if a payout fails or bounces?

TNKR returns a reason code and holds the funds, so nothing is lost. You correct the details and retry the row, never the whole batch. Every attempt posts to one reconciled ledger.

Who handles data privacy and BIR reporting?

TNKR processes worker data under RA 10173, with a data-processing agreement, and you stay the controller. Exports support your eBIRForms and eFPS filing. You remain the withholding agent.

Tell us how you pay your workers today.

Talk to an expert