GCash collections for game operators

GCash collections for gaming platforms

Accept GCash deposits from players in the Philippines and connect confirmed payments to the right gaming-platform balance. Discuss the available checkout, collection fees, PHP limits and settlement with Bifu Payments (bifu.us). Keep each deposit traceable from payment instruction to confirmed result and reconciliation. Player withdrawals are handled through a separate payout flow.

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

From player payment to confirmed platform deposit

Example: one player deposit, one balance credit

A player starts a GCash deposit from your platform. Keep the same deposit reference and PHP amount through checkout and payment confirmation. Credit the balance only when a verified callback or agreed status query confirms payment—not from a screenshot or browser return. If the result is delayed, check the original order; a duplicate result must not credit the balance again.

Collection costs and payment exceptions

Discuss the available GCash checkout, per-payment fees, amount limits and settlement arrangements for your platform. Keep unpaid deposits, missing callbacks and reconciliation differences visible to operations. Withdrawal delivery and merchant settlement are separate from collecting a player's payment.

Submit your platform's payment requirements

Send your requirements by form, or use online support on Telegram. Email and requirements are required; name and Telegram username are optional.

Integration details

Payment flow, callbacks, order queries and reconciliation.

GCash checkout options

Checkout options vary by payment route. Support can explain the available options and costs for your business.

Hosted checkout

When the selected route returns a hosted page, preserve the merchant order reference and expiry while the payer completes the GCash step outside the merchant server.

App handoff or QR instruction

Use only the checkout artifact returned by the applicable integration. Do not invent an undocumented deep link or assume every route offers the same handoff.

Merchant-side presentation

Show the exact PHP amount, a recognizable order reference and a clear pending state. A browser return or screenshot is not proof of payment.

Confirm one order exactly once

Keep the customer experience separate from the server-side decision that changes an order or balance.

Unique order reference

Create and store one merchant reference with the expected amount and currency before requesting a payment instruction.

Authoritative result

Mark the order paid only after a valid callback or an agreed status query confirms the same reference and amount.

Idempotent update

A repeated callback or query result must update the existing order without crediting the payment a second time.

Prepare for delayed and unmatched payments

A useful launch plan includes the exceptions that occur after the checkout screen closes.

Pending result

Keep the original order open and query it with controlled retries. Confirm a final state before offering another payment attempt.

Amount or reference mismatch

Move mismatched records to review instead of automatically changing the intended order amount or customer balance.

Daily reconciliation

Match merchant references, returned transaction identifiers, amounts, final states and settlement records for the same business period.

Common questions

  • Is this official GCash API documentation?

    No. It is a merchant-side planning guide. Production endpoints, fields, credentials, limits and signatures must come from the specification for the contracted route.

  • Does a successful browser return mean the order is paid?

    No. Use a valid server callback or the agreed status-query result to confirm the same order and amount.

  • What should happen when the result stays pending?

    Keep the original reference, query its status and wait for a final result before creating another payment attempt.

  • How are GCash payments and payouts different?

    Collection receives a customer's wallet payment. Payout sends money to a recipient, with a separate order, destination and delivery result.

  • Where can I check prices and payment limits?

    The reference fee cards separate collection and payout prices. Submit your platform's requirements by form or ask online support on Telegram about available routes, limits, settlement and any additional charges.

Discuss GCash collections for your gaming platform

Ask about available checkout options, collection fees, limits, settlement and deposit confirmation. Submit your platform's payment requirements by form or speak with online support on Telegram.

Contact support