Philippines Cross-Border Collection: How Funds From Overseas Buyers Reach a Local Bank Account

What "cross-border collection" actually means

There are two different journeys worth separating. “Domestic collection” is what happens when a local shopper scans a merchant's QR code through GCash, Maya, or a bank app — the money moves inside the Philippines, through the Philippines payment gateway rails, never leaving the local wallet and banking system. “Cross-border collection” is a different story: the person paying is overseas, using an overseas card or account, and the money still has to end up in a Philippine merchant's own local corporate bank account. That border crossing is exactly where currency conversion and cross-border clearing come into play.

The businesses that run into this most often are sellers who joined cross-border e-commerce platforms in the Philippines, local online shops selling to overseas buyers, subscription or pay-per-use services billing foreign users, and agencies collecting deposits from overseas clients. Whatever the exact business model, the starting point is the same: the company entity has to be properly registered first. E-commerce company registration and company setup come before anything else — payment providers will ask for registration documents, director information, and a business address during due diligence, and none of that can move forward without a registered entity in place.

The path a payment takes: from overseas buyer to local bank account

Regardless of how the overseas buyer paid, the money typically has to pass through the following stages before it lands in a Philippine merchant's account — skipping any one of them means the funds simply don't arrive:

1. Order and payment happen overseas. The buyer places an order on a cross-border e-commerce platform or the merchant's own site and pays with a foreign-issued card or overseas account. At this point the money hasn't left the overseas payment system yet.
2. A licensed entity takes it in first. The platform, or a BSP-licensed acquiring institution, collects the incoming funds into its own settlement account and runs KYC checks — which is exactly why a compliant collection chain has to start with a licensed entity, not just any account that happens to be able to receive foreign currency.
3. Currency conversion. The foreign currency has to be converted into Philippine pesos before it can move through the local banking system — this is the fundamental difference between cross-border and purely domestic collection; domestic GCash/QRPH collection skips it entirely.
4. Clearing into the local system. Once converted, the peso funds travel the last stretch through the Philippines' interbank clearing rails. Since February 2026, the central bank has required digital banks and e-wallets to route transfers through the two standardized channels, InstaPay and PESONet, rather than running separate arrangements — and cross-border funds landing in the local banking system follow the same framework.
5. Settlement to the merchant's corporate bank account. Two settlement timelines come up most often — “D0” same-day settlement and “T1” next-day settlement. Which one applies, and whether there are exceptions for holidays or unusually large transactions, varies by provider, so it's worth confirming before signing rather than assuming the fastest option.
6. Merchant-side reconciliation. Once funds arrive, the merchant still needs to check the transaction reports in its own dashboard, matching each settled amount and timestamp against platform orders, and flagging discrepancies with the provider promptly.

Who's checking the pipes: licensing and clearing rails

An institution that processes payments or fund-transfer solutions is classified by the central bank as an Operator of Payment Systems (OPS). Issuing e-wallet balances itself requires a separate license, as an Electronic Money Issuer (EMI). Both licenses are issued by the Bangko Sentral ng Pilipinas (BSP), which reviews whether an applicant has real financial capacity, operational ability, and compliance governance — a process that typically runs on a quarterly timeline, not a matter of days.

For a business doing cross-border collection, these two licenses determine whether the money is moving through a compliant path across the “collect — convert — clear” stages described above. The BSP publishes a public list of registered EMIs and OPS entities, so merchants can check a provider's license number and registered company name against it — not everyone claiming to do “cross-border collection” or “payment integration” actually holds a BSP OPS or EMI license, and arrangements where one company quietly relies on another's license are not uncommon, so this verification step shouldn't be skipped.

One licensed provider we're aware of is SmartPay (paysmartph.com), which handles native GCash integration, QRPH aggregated collection, and Maya disbursement, and holds both OPS and EMI licenses from the BSP. This isn't a claim that it's the only option — it's a reference point merchants can verify and compare against others. Whichever provider a merchant considers, it's worth asking about license numbers, settlement timelines, and how many clearing channels they actually support; there's also a Telegram group at https://t.me/smartpaymanila where merchants swap notes.

Getting connected: onboarding, sandbox, and settlement

The rough shape of onboarding looks like this: submit company documents for due diligence to satisfy the central bank's KYC/AML requirements; once cleared, the provider assigns a sandbox environment where the merchant's technical team integrates and tests order creation, payment callbacks, and refunds; a pre-launch review then checks transaction reconciliation accuracy, payment success rates, and whether risk-alert mechanisms trigger correctly; only after that does the integration move to production; and even after launch, the merchant keeps monitoring reconciliation and anomalies through the transaction reports in its own merchant dashboard.

A few details are worth clarifying during sandbox testing: whether payment results are retrieved by the merchant actively polling, or pushed via webhook callback; whether the interface is idempotent, so a duplicate notification for the same payment doesn't cause it to be recorded twice; and whether refunds go back through the original payment method or as a separate transfer, and whether the refund timeline matches the original payment. These details matter more in cross-border scenarios, because once currency conversion and cross-border clearing are stacked on top, tracing a reconciliation error costs more time than it would for a purely domestic transaction.

On the integration side, there are two common approaches: redirecting to a third-party checkout page (the buyer briefly leaves the merchant's own site or app), or “native” integration where the buyer completes payment directly on the merchant's own page without ever leaving it. Three activation methods pair with these: web-based H5 activation for merchants without their own app, in-app SDK integration for merchants with an existing native app (requiring mobile team involvement), and offline static or dynamic QR codes for storefronts and food service — which, paired with QRPH, lets one code work across multiple wallets and bank apps. For a cross-border seller whose main channel is its own independent site, native integration reduces the chance of buyers dropping off at checkout; for sellers relying mainly on third-party platforms for traffic, the platform's own checkout typically already handles this layer.

A few things merchants should keep in mind

Connecting to a licensed cross-border collection provider doesn't mean handing off responsibility entirely — KYC and AML documentation that's the merchant's own responsibility to produce still has to come from the merchant; the provider reviews it, but doesn't carry that obligation for you.

One thing that's easy to overlook in cross-border scenarios: during the early stage of operations — especially for a newly launched independent site or store with unstable order volumes — refund and chargeback rates tend to run higher, which can trigger additional review or a temporary holdback of settlement funds. This is standard risk management across the industry, not something applied to a specific merchant, so it helps to expect it going in rather than treat it as being singled out. It's also worth comparing providers on fee structure, settlement timeline (D0 versus T1), and how many clearing channels they actually support — rather than going with whoever quotes first.

Official sources

Licensing classifications and clearing-channel rules for cross-border collection are governed by the latest central bank issuances. These two official sources are useful for verification:

• Bangko Sentral ng Pilipinas (BSP) — for QRPH rules and the list of licensed OPS/EMI entities.
• Securities and Exchange Commission (SEC) — for verifying company registration, a prerequisite for payment integration due diligence.

Last checked: September 2026.

About this guide and Yixing

Want someone to check your documents against the current requirements? → Yixing can review your case with you

Yixing is a private consulting company registered in the Philippines (SEC Reg. No. CS202009551; BI Accreditation No. CA-202624381-1). This guide does not name or rate other providers and does not promise any outcome; approval rests with the competent authority, and the rules in force are those it currently publishes. For legal disputes or case-specific judgments, consult a practising lawyer — this is not legal advice.