GCash
Collection1.8%
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 18 PHP fee.
Payment channel comparison
Choose collection and payout routes for your gaming platform's player deposits and withdrawals. Compare GCash wallet checkout, QR Ph collection and local payout options by payment experience, reference fees and order handling. Each route has its own limits, availability and settlement arrangements.
Payment capabilities
Published channel fees are shown separately for collections and payouts. Ask support about settlement and any additional charges.
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.
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.
Discuss integration and pricing on Telegram
Contact the team about problem orders
Real-time settlement may be available, depending on the channel and business
Compare a GCash wallet handoff with a QR Ph payment through participating apps. Keep the platform's deposit reference and expected PHP amount with the order, then use the route's verified callback or query result to confirm the payment.
Choose player-payout routes separately from incoming collections. InstaPay, bank transfer and USDT have their own delivery and pricing arrangements; USDT can also be used for merchant-balance withdrawals and settlement. Ask about the applicable route rather than applying one displayed fee to every direction.
Send your requirements by form, or use online support on Telegram. Email and requirements are required; name and Telegram username are optional.
Payment flow, callbacks, order queries and reconciliation.
The front-end path determines what the payer sees, but the server result still determines the final order state.
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.
A merchant-presented QR can be scanned through participating wallet or bank apps. Distinguish static and order-bound dynamic QR flows.
Account details and transfer references replace the wallet handoff. Define how an incoming transfer is identified and matched to the merchant order.
Incoming confirmation and outgoing delivery are different money movements even when they belong to one business event.
Record the expected amount and payment path, then confirm the incoming result through the agreed callback or order query.
Record the wallet or bank destination and track accepted, processing, delivered, failed and unknown results independently.
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.
A channel decision is incomplete until normal and exceptional orders can be confirmed and reconciled.
Retain the redirect or QR reference, amount, currency, expiry and selected payment method generated for the order.
Verify callbacks, update idempotently and query the original order when a notification is delayed, missing or inconsistent.
Match merchant and returned references, amount, final state, timestamps and settlement identifiers; move differences to a review record.
No. GCash is a wallet-specific experience. QR Ph is an interoperable QR standard used through participating wallet or bank apps.
No. Compare payment direction, payer handoff or destination, amount range, server confirmation, exception recovery and reconciliation fields.
They may be linked in one business record, but each money direction should keep its own reference, status model and final result.
Keep the original order and use the issued query method. Do not create a replacement order while the result is unknown.
No. Confirm the route, amount range, operating information, pricing and issued technical specification before implementation.
Related payment resources
Follow the wallet handoff, server confirmation, pending-order and reconciliation workflow in detail.
Read resourceReview static and dynamic merchant QR flows and reconciliation controls.
Read resourceSee the operational split between incoming and outgoing payments.
Read resourceReview the payment direction, payer experience or destination, order lifecycle, exception controls and reconciliation record.
Contact support