GCash
Collection1.8%
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 18 PHP fee.
GCash wallet payments
Accept GCash wallet payments with a clear checkout and a confirmed order result. Bifu Payments (bifu.us) explains available routes, fees, limits and settlement, with integration support for callbacks, status queries and reconciliation.
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
Payment flow, callbacks, order queries and reconciliation.
Checkout options vary by payment route. Support can explain the available options and costs for your business.
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.
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.
Show the exact PHP amount, a recognizable order reference and a clear pending state. A browser return or screenshot is not proof of payment.
Keep the customer experience separate from the server-side decision that changes an order or balance.
Create and store one merchant reference with the expected amount and currency before requesting a payment instruction.
Mark the order paid only after a valid callback or an agreed status query confirms the same reference and amount.
A repeated callback or query result must update the existing order without crediting the payment a second time.
A useful launch plan includes the exceptions that occur after the checkout screen closes.
Keep the original order open and query it with controlled retries. Confirm a final state before offering another payment attempt.
Move mismatched records to review instead of automatically changing the intended order amount or customer balance.
Match merchant references, returned transaction identifiers, amounts, final states and settlement records for the same business period.
No. It is a merchant-side planning guide. Production endpoints, fields, credentials, limits and signatures must come from the specification for the contracted route.
No. Use a valid server callback or the agreed status-query result to confirm the same order and amount.
Keep the original reference, query its status and wait for a final result before creating another payment attempt.
Collection receives a customer's wallet payment. Payout sends money to a recipient, with a separate order, destination and delivery result.
Contact Bifu on Telegram for the available routes, fees, limits and settlement terms. Prices vary by payment route and direction.
Related payment resources
Review order creation, callback, query and reconciliation controls.
Read resourceCompare an interoperable QR Ph merchant flow with a wallet-specific GCash flow.
Read resourceSee how collection and payout operations remain separate in a two-way payment setup.
Read resourceDiscuss fees, limits, settlement and checkout options directly with Bifu support on Telegram.
Contact support