Philippines Website Payment Collection: How It Differs From Selling on Shopee or Lazada

Website Collection vs. Marketplace Collection: What Actually Changes

It's easy to lump "selling online in the Philippines" together, but selling through Shopee, Lazada or TikTok Shop and collecting payments on your own website are two different arrangements.

On a marketplace, payment collection is handled centrally by the platform: buyers choose GCash, a card, or cash on delivery inside the marketplace app, funds land in the platform's account first, and the platform settles to the seller on a set cycle after deducting fees. Sellers don't need to contract with a payment provider or do any technical integration themselves — this is the common path for sellers entering the Philippines through cross-border e-commerce.

Running your own website is a different arrangement. You become the merchant yourself, contracting directly with a licensed payment provider, and funds go straight into your own corporate bank account with no marketplace sitting in between. That means your own company has to supply KYC documentation, your own team (or a contracted developer) has to handle technical integration, and you're the one watching reconciliation and exceptions on an ongoing basis — see our overview of Philippines payment gateway integration for the fuller picture.

In short: marketplace collection borrows someone else's payment rails, while website collection means building your own. You get more control — no marketplace commission, full say over the checkout experience — but you also take on more of the technical and compliance workload yourself.

What Your Website Needs to Plug Into

Local digital payments in the Philippines are concentrated around two e-wallets, GCash and Maya, and QR Ph, the central bank's unified QR standard. GCash alone reports over 90 million registered users, and together GCash and Maya cover the large majority of active digital users in the country, with QR payments now accounting for more than half of all digital transaction volume. A website taking local payments has to plug into this ecosystem one way or another.

QR Ph is issued by the Bangko Sentral ng Pilipinas (BSP), the central bank — it isn't owned by any single wallet. A merchant displays one QR Ph code, and GCash, Maya, and dozens of participating bank apps can all scan the same code to complete a payment. The underlying technology follows the internationally common EMVCo QR framework, the same logic used by Singapore's SGQR and Thailand's PromptPay.

There are two common integration patterns: a redirect flow, where the buyer briefly leaves your website for a third-party checkout page and returns afterward, and 'native' integration, where the buyer stays on your own page the entire time, scanning a code or launching an app with one tap, with no redirect at all. Which one fits depends on your website's technical setup and how much you care about keeping buyers on-page.

For a website specifically, the usual activation method is web-based H5 activation — the option built for merchants who have a website but no native app. If you also run a native app alongside your website, you can layer in in-app SDK integration on top, though that requires your mobile team's involvement. On the transfer side, since February 2026 the central bank has required digital banks and e-wallets to route transfers through the two standardized clearing channels, InstaPay and PESONet, rather than each provider running its own separate rails — worth confirming your provider is already aligned with this when you're evaluating them.

Technical Details Worth Confirming Before You Sign

Unlike a marketplace listing, your own website's payment integration is a technical project your own team has to sit through. The typical framework runs: submit company documentation for due diligence (to satisfy the central bank's KYC/anti-money-laundering requirements) → the provider assigns a sandbox environment where your technical team integrates order creation, payment callbacks, and refunds → pre-launch acceptance testing (transaction reconciliation, payment success rates, risk-alerting mechanisms) → cutover to the production environment → ongoing reconciliation and exception monitoring through the merchant dashboard's transaction reports.

A few details are worth clarifying during the sandbox phase, before you're live and discovering problems the hard way:

• Whether payment results come back through your system actively polling, or the provider pushing a webhook notification to you — this decides whether your website needs extra polling logic.
• Whether duplicate notifications for the same payment can cause your order system to record it twice (in other words, whether the API is idempotent) — for a standalone website, this is a real bookkeeping risk if it isn't handled properly.
• Whether refunds go back through the original payment method or as a separate transfer, and whether the time-to-settlement matches the original payment.
• Settlement speed, commonly quoted as either 'D0' (same-day settlement) or 'T1' (next-day settlement) — not every provider does D0 across the board, so it's worth asking exactly which applies and whether there are exceptions.

On a marketplace, the platform has already handled all of this for you. Running your own website means confirming each point yourself, ideally in writing in the contract or technical documentation rather than taking a verbal assurance at face value.

The Compliance Baseline: Your Company and Verifying Licenses

Whichever integration pattern you use, one prerequisite doesn't change: your company has to be legally established in the Philippines first (SEC company registration). A payment provider's due diligence process will ask for registration documents, director information, and a business address — none of that moves forward until your entity exists, a point also covered in our guide to opening a corporate bank account.

Working with a licensed provider doesn't mean you can hand off compliance entirely, either. KYC and anti-money-laundering documentation that's meant to come from your company still has to come from your company — the provider connects you to the payment rails, but doesn't take on your compliance obligations for you.

On licensing specifically: an entity 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 Electronic Money Issuer (EMI) status. Both licenses are approved by the BSP, which evaluates whether the applicant has real financial capacity, operational capability, and governance in place, and the process typically runs on a quarterly timeline. Not every outfit that claims to do "payment integration" actually holds an OPS or EMI license — sub-licensing and pass-through arrangements aren't uncommon, so it's worth verifying independently rather than taking a sales pitch at face value.

Newly registered companies may also find due diligence takes longer than it does for an established company, simply because there's less operating history to check — worth building extra time into your launch timeline if your entity is recently formed.

Verifying and Choosing a Provider

Because not every provider that claims to handle payment integration is actually licensed, verification is a step worth not skipping: the central bank publishes its list of registered Electronic Money Issuers and Operators of Payment Systems, and you can check a provider's stated license number and registered company name against it. It doesn't take long, and it can save a lot of trouble later.

Fee structures, settlement cycles, and the number of channels a provider supports all vary, so it's worth comparing more than one option rather than settling on the first quote. GCash and QR Ph also update their interfaces or rules from time to time, so integration isn't a one-and-done project — it's worth asking a prospective provider how they handle notifying and supporting you through those changes.

One licensed provider we're aware of is SmartPay (paysmartph.com), which handles native GCash integration, QR Ph aggregated collection, and Maya disbursement, and holds both OPS and EMI licenses from the central bank. It's a reasonable reference point to check and compare against when you're evaluating options for your own website — worth confirming current terms directly with them; their business contact on Telegram is @LouisSMARTPAY.

If your website's payment flow also ties into ongoing tax filing, our guide to BIR tax payment channels covers which channels make reporting on that income more straightforward.

Official Sources

For licensing verification and QR Ph rules, go directly to the central bank rather than relying solely on a provider's own description:

• Bangko Sentral ng Pilipinas (BSP) — QR Ph rules and the registered EMI/OPS list.
• Securities and Exchange Commission (SEC) — company registration status.

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.