Philippines · Payout API

PHP payout API for the Philippines

CVPay’s Philippines payout API lets businesses send Philippine peso disbursements to bank accounts and e-wallet-linked accounts over InstaPay and PESONet from a single REST integration, funded from a PHP balance or converted from USDT, with final status delivered by webhook.

Get started Talk to us on Telegram

What a Philippines payout API does

A payout API turns a disbursement into a single HTTP call: you pass the recipient’s account, name and amount, and the provider handles routing, dispatch, status tracking and reconciliation. In the Philippines the relevant rails are InstaPay for near-real-time transfers and PESONet for larger batch transfers, both reaching the country’s banks and the major e-wallets through interoperable accounts.

CVPay exposes those rails through one endpoint. Payouts can target a bank account or a wallet-linked account, be funded from your PHP balance or from USDT converted at a quoted rate, and return a final success or failed state to your webhook. Order-bound references keep every transfer traceable from your system to the receiving account.

What the payout API covers

Banks and e-wallets, one endpoint

Reach Philippine bank accounts and e-wallet-linked accounts through the same call. The destination is selected by a bank or wallet code, so the integration does not change per recipient type.

InstaPay and PESONet routing

Eligible amounts go near-real-time over InstaPay; larger transfers route over PESONet and follow its settlement cycle. You submit once and CVPay handles the rail.

Fund from PHP or USDT

Hold a PHP balance, or keep a USDT treasury and convert to peso at a quoted rate right before dispatch. Both paths feed the same payout endpoint.

Webhook final status

Every transfer ends in a signed success or failed callback with your order reference. No polling loops, no guessing whether a transfer landed.

Batch and single payouts

Send one transfer per API call or upload a batch from the merchant dashboard. Both use the same validation, limits and reporting.

Payout QR parsing

Recipients who share a payout QR can have their bank or wallet details pre-filled from it, reducing typos in account numbers and names.

From API call to landed transfer

1
Fund the balance
Top up PHP through local collections, or convert USDT to peso at a quoted rate. The balance is available for payouts immediately.
2
Create the transfer
POST the recipient account, name, amount and destination code with your order reference. CVPay validates and accepts it synchronously.
3
Dispatch over local rails
The transfer is routed over InstaPay or PESONet depending on amount and destination, with rail-side references stored against your order.
4
Receive final status
Your webhook gets the final success or failed state. Query the order any time by reference, and export reports from the dashboard.

Key facts

Currency: PHP (Philippine peso); VND and USDT available on the same account
Rails: InstaPay (near-real-time) and PESONet (larger transfers, settlement cycle applies)
Destinations: Philippine bank accounts and e-wallet-linked accounts, selected by bank or wallet code
Speed: Near-real-time over InstaPay for eligible amounts; PESONet transfers follow its clearing schedule
Funding: PHP balance from local collections, or USDT converted at a quoted rate
Status: Synchronous acceptance, then final success / failed state by signed webhook; order query by reference
Compliance: Singapore Payment Services Act licence; KYB on every merchant; transaction monitoring
Limits: Rail-side and merchant-side per-transaction and daily limits apply per your configuration

Who uses a PHP payout API

Exchanges and OTC desks

Process peso withdrawals for Filipino users to their bank or wallet without operating your own local payout desk.

Freelancer and creator platforms

Pay Filipino freelancers, creators and gig workers in peso on their preferred wallet while your clients fund the platform in USDT.

Remittance and cross-border payment companies

Terminate inbound flows into Philippine accounts through one API instead of maintaining separate bank and wallet integrations.

Gaming and social platforms

Distribute winnings, rewards and affiliate commissions in peso with order-level tracking and webhook confirmation.

Marketplaces and SaaS

Settle Philippine sellers and partners in PHP from a global USDT or PHP balance with one ledger for every disbursement.

Payroll and vendor settlement

Run scheduled or batch peso payouts to staff and suppliers with the same validation and reporting as single transfers.

Why an API instead of a local bank portal or a wallet business account

Each option can move peso. The difference is how much of the work your team has to do by hand every day.

Bank business portal

Requires a Philippine entity and bank onboarding. Batches are uploaded manually, status is checked by hand, and wallet destinations usually need a separate process.

E-wallet business account

Reaches that wallet’s users well, but bank accounts and other wallets need their own integrations, each with its own limits, files and reconciliation.

CVPay payout API

One endpoint for banks and wallets, one balance that can be funded in PHP or USDT, webhook status on every transfer, and no Philippine entity required to start.

Integration

Payouts share the same REST API and signature scheme as collections and FX, so a team that has integrated one CVPay flow already has the other. Create a transfer, store the returned order reference, and act on the webhook. A sandbox is provided after KYB approval, and most merchants complete integration within days.

Read the API docs Get started

# Create a PHP payout to an e-wallet

curl -X POST 'https://{api-base}/api/transfer/create' \
  -d 'mchNo=M1234567890' \
  -d 'appId=YOUR_APP_ID' \
  -d 'mchOrderNo=PAYOUT-2026-0001' \
  -d 'currency=php' \
  -d 'amount=5000' \
  -d 'accountNo=09171234567' \
  -d 'accountName=JUAN DELA CRUZ' \
  -d 'bankName=GCASH' \
  -d 'sign=...'

# bankName is the destination bank or wallet code.
# Final status (success / failed) is delivered to
# your webhook. Simplified example — see the API
# docs for the full field list and signature spec.

Frequently asked questions

Which destinations can I pay out to in the Philippines?+

Philippine bank accounts and e-wallet-linked accounts reachable over InstaPay and PESONet. The destination is chosen by a bank or wallet code in the same API call. See the individual payment method pages for the wallets and banks most commonly used.

How fast do PHP payouts arrive?+

Eligible amounts are routed over InstaPay and typically arrive near-real-time. Larger transfers route over PESONet and follow its clearing schedule. The final state is pushed to your webhook either way.

Can I fund payouts with USDT?+

Yes. Request a USDT to PHP quote, confirm it, and the peso is credited to your balance for immediate payout. The same works in reverse for converting PHP collections to USDT.

Do I need a Philippine company?+

No. CVPay onboards the operating entity wherever it is incorporated. KYB is required and typically completes within 1–3 business days, after which sandbox credentials are issued.

How do I know a payout succeeded?+

Every transfer ends in a signed webhook with a success or failed state and your order reference. You can also query any order by reference through the API or dashboard.

What happens if a transfer fails?+

The failed state and reason are returned on your webhook and the funds remain in your balance. You can correct the recipient details and resubmit with a new order reference.

Are there per-transaction limits?+

Yes. Rail-side limits apply per InstaPay and PESONet rules, and your merchant configuration sets per-transaction and daily limits. Larger amounts route over PESONet automatically where eligible.