Payment integration
Review integration scope by country of operation, currency, and the deposit and withdrawal methods you need. The methods below come from our product guide.
For licensed operators in markets where these services are permitted.
At a glance
Grey items need confirmation. Confirm every method for your market.
Philippines · PHP
Availability of each method, and permission to provide the service, must be confirmed for your market. Deposits and withdrawals are checked separately.
| Type | Payment method | Status in source material |
|---|---|---|
| Bank transfer | General bank transfer | Deposit and withdrawal |
| Bank transfer | BDO | Deposit |
| Bank transfer | BPI | Deposit |
| Bank transfer | Landbank | Deposit |
| Bank transfer | Metrobank | Deposit |
| Bank transfer | UnionBank (UBP) | Deposit and withdrawal |
| Bank transfer | Bank of China | Withdrawal only |
| Bank transfer | Deutsche Bank | Withdrawal only |
| E-wallet | GCash | Deposit and withdrawal |
| E-wallet | Maya (PayMaya) | Deposit and withdrawal |
| E-wallet | GrabPay | Deposit and withdrawal |
| E-wallet | ShopeePay | Deposit and withdrawal |
| QR | QR Ph | Deposit and withdrawal |
| Card | Credit and debit cards | Needs confirmation |
| Mobile pay | Apple Pay · Google Pay | Needs confirmation |
| Other | InstaPay · PESONet | Needs confirmation |
“Needs confirmation” applies to the whole country: the provider, contract scope or support for deposits and withdrawals still has to be verified. The list comes from reference material and is not a final confirmation.
Interactive preview
Choose a direction and a method to replay how a payment moves from request to reconciliation. Sample amounts only.
Methods shown are examples. Each method must be confirmed for your market.
How it connects
Process
Operator guide
Start with a method-by-method worksheet for your contracting entity. For each PHP method, record the direction, merchant approval, confirmation mechanism and settlement reporting available to your project. Read the existing table as a review of methods, then verify the live scope against written provider terms.
A provider can offer a deposit path without a matching payout route. Use the table above to identify the directions that need confirmation. Confirm merchant eligibility, thresholds, fees and settlement separately for each route.
Use a provider reference and your own order reference throughout the payment lifecycle. Test pending states, repeated callbacks, expiry and a mismatch between a webhook and the settlement report.
Ask finance to match net settlement, fees and reversals to the ledger. Ask support to trace a deposit or withdrawal from a single reference without exposing unnecessary payment details. Start with a payment integration enquiry.
FAQ
It depends on market, provider and license. We confirm the options with you in consultation.
Payment flow and settlement responsibilities are agreed in writing before launch.
The table is a scoping reference. The payment provider and the applicable approvals determine availability for a specific entity and operating market. Confirm the contract, permitted direction and limits.
Send the same reference more than once and confirm the wallet balance changes only once. Verify the callback signature, compare the provider status and retain a searchable audit record.
Record the provider reference and last status. Agree on the retry and support procedure with the provider, then check the settlement report before making a second payout.
Compare the fields you receive per method and normalize order references, amounts, fees, currency and settlement dates. Keep method-level records so finance can trace a mismatch to the originating provider.
Next step
Tell us your products, payment methods and timeline. We reply by email.
With your permission, Google Analytics uses cookies to measure page visits. You can change your choice at any time.
Privacy and analytics information
