Accept every local method through one integration.
Give your merchants GCash, Maya, QR Ph and Philippine bank transfers, without a BSP enrollment of your own.
- Payments
- Payouts
- Wallets
- Onboarding & Verification
- Ledgers
- Control
- Workflows
Accept every method your buyers use.
Take cards, GCash, Maya, GrabPay, QR Ph, online banking, BNPL and over-the-counter, settled to you. Your merchant stays yours.
- Payments · cards, e-wallets, QR Ph, BNPL, OTC
- Ledgers · every method on one ledger
- Settlement · PHP, one schedule
Pay out and hold balances locally.
Disburse to any bank or e-wallet over InstaPay and PESONet. Hold merchant and user balances in-country, with real-time cash-out.
- Payouts · InstaPay and PESONet
- Wallets · balances in-country
- Workflows · splits and scheduled payouts
Onboard sub-merchants under our policy.
Run local KYB — SEC and DTI registrations, beneficial ownership, sanctions. Your risk team signs one policy, not a new registry.
- Onboarding & Verification · SEC, DTI, beneficial ownership
- Control · one policy for every sub-merchant
- Evidence trail · exportable per sub-merchant
Developer API
One integration, not one per rail.
One request shape for every local method. We pick the rail, not your engineers.
{ "id": "pay_7b21", "object": "payment", "amount": 250000, "currency": "PHP", "payment_method": "qrph", "status": "pending", "metadata": { "sub_merchant": "sub_4c8e" }, "settlement": { "currency": "PHP", "window": "same_business_day_batch" }}One API, one contract, one settlement schedule.
Settlement timing is stated per corridor and per rail, and confirmed before you sign.
01Integrate once
Size the build against the reference. Sandbox key on submission.
02Certify
Certification runs against the rails you need, on a schedule signed per engagement.
03Settle
PHP in-country. Settlement out of PHP is scoped per engagement.
Built to be examined.
Licences, certifications, data handling and incident process, in one due-diligence pack. Request it from the form.
- The licence is ours; the customer is yours
- Flows run under the PayMongo licensed entity named below. Everything customer-facing stays in your name. We never contract with your merchants.
- Nothing here confers a licence on you
- Building on TNKR does not extend our authorisation to you or change your regulatory perimeter. It removes a separate local enrollment for these flows. Nothing more.
- Stored balances are electronic money
- Balances on TNKR rails are electronic money issued by PayMongo Payments, Inc., the licensed Electronic Money Issuer. Not deposits, not PDIC-insured, not under your licence.
- 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.
PSP & payfac questions, answered.
What your committee will ask, answered in writing.
Can a foreign PSP process payments in the Philippines?
Yes. Reach Philippine buyers on licensed local rails without your own BSP enrollment. You integrate once and keep your ledger, orchestration and customers.
Do I need a BSP licence to enter the PH market?
No. PayMongo holds the regulated layer. Building on TNKR confers no licence on you and leaves your perimeter unchanged. It removes a separate local enrollment for these flows.
How is settlement handled in the Philippines?
In PHP, locally, with timing stated per corridor. Settlement out of PHP is confirmed for your corridor before you sign.
Will you disintermediate us?
No. Everything runs white-label, in your name. You keep the customer and the data.
How many bank integrations does this replace?
Every bank API you would otherwise stitch together, each with its own file format and cut-off. TNKR is one integration, reconciled on one ledger.
Can we leave?
Yes. No token-vault lock-in, and your data is portable.
