For Platforms, SaaS & Marketplaces · Without your own licence

Build money movement into your product without becoming a bank.

Turn payments into a revenue line inside your product. Wallets, payouts and onboarding run on our licences.

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

Give every merchant a balance.

Provision a wallet per merchant or user from your own signup flow. Every balance reconciles on one ledger, across every method and rail.

  • Wallets · a sub-account per merchant, under your brand
  • Ledgers · every merchant reconciled on one ledger
  • Payouts · InstaPay, PESONet and QR Ph

Split revenue the moment it lands.

Route one incoming payment across sellers, partners and your own take rate as it clears. Merchant-of-record patterns included.

  • Workflows · percentage or fixed splits on payment.paid
  • Payments · cards, GCash, Maya, QR Ph, BNPL
  • Your take rate, configurable per merchant

Onboard sub-merchants without leaving your product.

Run KYC and KYB from your own screens. The account is live on licensed rails the moment checks clear.

  • Onboarding & Verification · KYB with SEC and DTI registries
  • Control · policies every linked account inherits
  • Evidence trail · exportable per sub-merchant

Developer API

Size the build before sales is involved.

Wallets, payments and onboarding are REST endpoints with webhooks on every state change. Read the contract, count the endpoints, decide.

Read documentation
POST /v1/wallets
{  "id": "wlt_9f2c",  "object": "wallet",  "name": "Waystar Royco",  "reference": "merchant_4c8e",  "currency": "PHP",  "balance": 0,  "status": "active",  "rails": ["instapay", "pesonet", "qrph"]}
How it runs

Start managed. Graduate when volume justifies it.

Ship managed on our licences and rails, or build against the API. Graduating later never means re-integrating.

  1. 01Integrate

    Wallets, payments and onboarding against the API reference. Sandbox keys on submission.

  2. 02Launch managed

    Wallets, payouts, KYC and the ledger arrive running.

  3. 03Graduate

    Take on more of the stack as volume grows, including your own payfac.

Built to be examined.

What “without becoming a bank” means in specifics. Request the due-diligence pack from the form.

Talk to an expert
You never hold the balance
Merchant balances are electronic money issued by PayMongo Payments, Inc., the licensed Electronic Money Issuer. Not deposits, not PDIC-insured, and never on your balance sheet. You earn on the movement without carrying the obligation.
No licence to take on, and none conferred
Shipping on TNKR does not require your own authorisation, extend ours to you, or change your regulatory perimeter. Becoming your own payfac later is your decision, on your timeline.
Your merchants stay yours
Everything customer-facing runs in your name. We never contract with your merchants, and we never market to them.
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

Platform questions, answered.

What your team will ask, answered in writing.

Talk to an expert

Do we have to become a bank or payfac?

No. You start fully managed on TNKR’s regulated rails and graduate — integrated API, then your own payfac — when volume justifies it. Building on TNKR confers no licence on you.

Do my merchants’ balances sit under my licence?

No. Balances are electronic money issued by PayMongo Payments, Inc., the licensed Electronic Money Issuer, not held under your company. You book revenue on the movement without carrying the e-money obligation.

How do platforms make money from embedded finance?

On the money moving through the product — take rate on payments, payouts and wallet activity, with fees configurable at the customer level.

Which financial primitives can I embed?

Wallets, payments and payouts, onboarding and KYC, and a reconciled ledger, all in your own product. Start with one and add the rest on the same rails underneath.

How hard is it to integrate?

TNKR publishes an API reference with runnable examples and SDKs. Wallets, payments and onboarding are REST endpoints, so your engineers size the work before sales is involved.

What about concentration risk?

Reliability evidence in the open, and a portable stack. No proprietary lock-in, and your data exports with you.

Tell us what you’d build into your product.

Talk to an expert