GCash
Collection1.8%
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 18 PHP fee.
GCash collection and payout
GCash collection and payout for two-way payment operations
Connect incoming GCash payments and outgoing payouts without treating them as the same transaction. Define each order lifecycle, confirm final results, reconcile both directions and handle exceptions before moving money again.
Payment capabilities
Collection orders and payment confirmation
Payout orders and delivery status
Reconciliation and exception handling
Collection and payout fees
Published channel fees are shown separately for collections and payouts. Ask support about settlement and any additional charges.
InstaPay
Payout8 PHP
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 8 PHP fee.
QRPH
Collection1.8%
Per transaction: 100 - 50,000 PHP
Example: 1,000 PHP → 18 PHP fee.
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.
Two directions, two controlled flows
Collection receives a payment; payout sends one. Each direction needs its own reference, status model and final confirmation.
Collection order
Create a unique merchant reference and expected amount, then wait for a confirmed callback or status query before crediting the payment.
Payout order
Create a separate payout reference for the destination and amount, then track it until the route returns a final success or failure state.
Shared payment record
Store the direction, merchant reference, provider reference, selected route, timestamps and final state so either flow can be traced later.
Order lifecycle
Keep pending, successful and failed orders distinct so a delayed result does not become a duplicate payment or payout.
Collection lifecycle
Follow the order from created to awaiting payment, processing and a final result. Update the balance only from an authoritative final state.
Payout lifecycle
Treat accepted, processing and delivered as different states. An accepted request is not proof that funds reached the destination.
Pending orders
Keep the original reference open while its state is checked. Do not start a replacement money movement merely because a result is delayed.
Callbacks, queries and idempotency
Use callbacks for timely updates, queries for confirmation and idempotency controls for safe repeat delivery.
Callback processing
Validate the callback against the current integration specification, match its order reference and amount, and acknowledge it only after durable processing.
Idempotent updates
Repeated callbacks for the same order and final state should not credit a collection twice or trigger another payout instruction.
Status query fallback
Query an order when a callback is late, missing or inconsistent. Resolve the existing order before deciding whether another attempt is safe.
Reconciliation across both directions
Match merchant orders, route results and settlement records instead of relying on a single callback as the accounting record.
Daily matching
Compare collection and payout references, amounts, final states and returned transaction identifiers with the records in your own system.
Separate ledgers
Report incoming collection and outgoing payout separately, then connect both to the same account or business event where appropriate.
Exception queue
Move missing, mismatched or long-pending records into a review queue with the last query result and a clear next action.
Failed orders and safe recovery
Confirm what happened to the original order before retrying, refunding or creating another transfer.
Failed collection
Keep the failed reference for audit and follow the current route rules before creating a fresh collection order for another attempt.
Failed payout
Distinguish a final failure from an unknown or processing state. Query the original payout before issuing a new instruction.
Late status changes
Allow delayed callbacks and query results to update the same order safely, without repeating the related balance movement.
Route selection
Choose collection and payout routes independently according to the payment direction and current channel capability.
Collection route
Select an available GCash collection path based on the checkout flow, amount range and integration mode required for the order.
Payout route
GCash, bank transfer or InstaPay may be considered according to the destination, amount and confirmed route capability.
Routing rules
Record the selected route and its result for every order. Limits, processing times and availability should be confirmed before launch.
Common questions
Can collection and payout be integrated together?
Yes. They can share merchant-side account and reconciliation records, while keeping separate order creation, status and exception workflows for each direction.
Do collection and payout use the same order states?
Not necessarily. Collection confirms an incoming payment, while payout tracks an outgoing delivery. Use the states and fields defined for each current route.
How are duplicate callbacks or payout requests handled?
Use a unique merchant reference and idempotent processing. A repeated callback should update the existing order, and a repeated payout instruction should not send funds twice.
What should happen when an order remains pending?
Keep the original order open and query its status. Confirm a final result before retrying or creating a replacement order.
Is every payout delivered through GCash?
No fixed route is implied. The destination type and issued route information determine whether a wallet, bank-transfer or InstaPay path applies.
Where can current limits, timing and pricing be confirmed?
Contact support to confirm the applicable route, limits, processing information and pricing.
Related payment resources
Continue with the technical and channel details
GCash wallet payment flow
Review the incoming wallet checkout and server-confirmation path before connecting payout operations.
Read resourceGCash payment API
Review callback, idempotency, order-state and reconciliation handling.
Read resourceAPI structure example
Inspect reserved examples for request signing, callbacks and queries.
Read resourceContact us about GCash collection and payout
Review the collection and payout directions, order lifecycle, callback and query flow, reconciliation fields, exception handling and confirmed route information.
Contact support