InstaPay
Payout8 PHP
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 8 PHP fee.
Local payment method comparison
Choose a payment method by what the payer needs to do and what the merchant must confirm afterwards. Wallet checkout, interoperable QR and bank transfer can serve different collection or payout requirements.
Payment capabilities
Published channel fees are shown separately for collections and payouts. Ask support about settlement and any additional charges.
8 PHP
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 8 PHP fee.
1.8%
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 18 PHP fee.
1.8%
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 18 PHP fee.
Discuss integration and pricing on Telegram
Contact the team about problem orders
Real-time settlement may be available, depending on the channel and business
Payment flow, callbacks, order queries and reconciliation.
The best option depends on where the payer starts, which app they use and whether the flow is a merchant collection or an outgoing payment.
A wallet-specific checkout can be appropriate when the payer already uses that app and the available route supports the intended merchant flow.
An interoperable QR Ph flow may let participating wallet or bank apps scan one merchant-presented code, depending on the acquiring setup.
A bank-account destination can suit collection or payout cases that require account-based transfer and a separate delivery status.
Payment-method coverage alone does not show how an order is confirmed or recovered.
Record the expected amount and merchant reference, then use the agreed callback or query result to confirm the incoming payment.
Track the destination, accepted state and final delivery result separately. A submitted instruction is not proof that funds arrived.
Plan for expired checkout instructions, delayed callbacks, unknown states, amount mismatches and safe retry decisions.
Public payment-method names do not guarantee that every route, amount range or integration mode is available.
Confirm the payment direction, checkout method, destination type, amount range and operating availability before development.
Use the fields, signature rules, status values, callback acknowledgements and query method issued for the selected route.
Retain merchant and provider references, amount, currency, final state, timestamps and settlement identifiers needed for daily matching.
It refers to payment experiences commonly used in the Philippines, such as wallets, interoperable QR and account-based transfers; it does not imply an official partnership.
No. GCash is a wallet-specific experience, while QR Ph is an interoperable QR standard used through participating wallet or bank apps.
They may relate to the same business event, but each direction should have its own reference, status and final confirmation.
No. Confirm the route, amount range, payment direction, processing information and pricing before integration.
Related payment resources
Go deeper into the payer handoff, order confirmation and exception path for GCash.
Read resourceSee how incoming and outgoing orders remain separate while sharing reconciliation records.
Read resourceLearn how interoperable merchant QR payments work in the Philippines.
Read resourceCompare wallet, QR and bank-transfer paths by payment direction, confirmation flow, destination and reconciliation model.
Contact support