Payment channel comparison

Compare Philippines payment channels by workflow

GCash, Maya, QR Ph, bank transfers and InstaPay are not interchangeable labels. Compare the payer handoff or payout destination, money direction, server confirmation, exception path and reconciliation record before implementation.

Collection and payout fees

Published channel fees are shown separately for collections and payouts. Ask support about settlement and any additional charges.

GCash

Collection

1.8%

Per transaction: 100 - 50,000 PHP

Example: 1,000 PHP → 18 PHP fee.

QRPH

Collection

1.8%

Per transaction: 100 - 50,000 PHP

Example: 1,000 PHP → 18 PHP fee.

InstaPay

Payout

8 PHP

Per transaction: 100 - 50,000 PHP

Example: 1,000 PHP → 8 PHP fee.

Discuss fees and settlement

Talk directly to our 24-hour team about collections, payouts and API integration.

Get a quote on Telegram

24-hour support

Discuss integration and pricing on Telegram

Human support for exceptions

Contact the team about problem orders

Settlement options

Real-time settlement may be available, depending on the channel and business

Integration details

Payment flow, callbacks, order queries and reconciliation.

Compare the payer experience

The front-end path determines what the payer sees, but the server result still determines the final order state.

Wallet-specific checkout

A GCash or Maya flow may hand the payer to a named wallet or hosted checkout. Keep the merchant reference, expected amount, expiry and return path with the order.

QR Ph merchant payment

A merchant-presented QR can be scanned through participating wallet or bank apps. Distinguish static and order-bound dynamic QR flows.

Bank-transfer instruction

Account details and transfer references replace the wallet handoff. Define how an incoming transfer is identified and matched to the merchant order.

Separate collection from payout delivery

Incoming confirmation and outgoing delivery are different money movements even when they belong to one business event.

Collection order

Record the expected amount and payment path, then confirm the incoming result through the agreed callback or order query.

Payout order

Record the wallet or bank destination and track accepted, processing, delivered, failed and unknown results independently.

Two-way operation

Link collection and payout references in the business record, but do not reuse an order number or treat one direction as proof of the other.

Compare technical and operating evidence

A channel decision is incomplete until normal and exceptional orders can be confirmed and reconciled.

Checkout artifact

Retain the redirect or QR reference, amount, currency, expiry and selected payment method generated for the order.

Server confirmation

Verify callbacks, update idempotently and query the original order when a notification is delayed, missing or inconsistent.

Reconciliation record

Match merchant and returned references, amount, final state, timestamps and settlement identifiers; move differences to a review record.

Common questions

  • Are GCash and QR Ph the same payment flow?

    No. GCash is a wallet-specific experience. QR Ph is an interoperable QR standard used through participating wallet or bank apps.

  • Should a channel be chosen only by payment-method name?

    No. Compare payment direction, payer handoff or destination, amount range, server confirmation, exception recovery and reconciliation fields.

  • Can collection and payout share an order number?

    They may be linked in one business record, but each money direction should keep its own reference, status model and final result.

  • What happens when a callback is delayed?

    Keep the original order and use the issued query method. Do not create a replacement order while the result is unknown.

  • Are all listed paths always available?

    No. Confirm the route, amount range, operating information, pricing and issued technical specification before implementation.

Compare a Philippines payment path

Review the payment direction, payer experience or destination, order lifecycle, exception controls and reconciliation record.

Contact support