OPS License for Payments in the Philippines: What It Covers and How It Differs from an EMI License

What an OPS License Actually Covers

OPS stands for Operator of Payment Systems, a license issued by the Philippine central bank, Bangko Sentral ng Pilipinas (BSP). The logic behind it is straightforward: any entity that actually processes payment or fund transfer solutions — whether that means acquiring merchant payments, aggregating multiple payment methods behind one interface, or moving funds for clearing between accounts — gets classified as an OPS, and needs this license before it can legally operate.

In other words, an OPS license does not regulate one specific product. It regulates the act of running a payment system itself. A company that simply builds a website for someone else to sell products, without ever touching the collection or clearing of funds, generally does not need this license. But the moment it starts handling merchant collections, pay-in/pay-out on behalf of others, or fund transfers across accounts, it falls under BSP's regulatory scope. That's also why entities genuinely licensed to operate payment systems are far fewer than the number of companies that simply claim they can “do payment integration.”

When a merchant works through a full payment gateway setup in the Philippines, the entity they're actually dealing with is often exactly this kind of OPS-licensed institution — it sits between the merchant's storefront or app and the final bank clearing rail, playing the regulated role of “running the payment system.”

OPS vs EMI: Two Different Licenses That Get Mixed Up

Many merchants confuse OPS and EMI, but they cover two entirely different things. EMI stands for Electronic Money Issuer, and it covers the issuance of the “balance” sitting inside an e-wallet — for example, what GCash actually is as an e-wallet: when a user tops up, that balance is itself a regulated form of electronic money, and the issuer needs EMI status. OPS, on the other hand, covers the act of running a payment or fund-transfer system — merchant acquiring, aggregating multiple payment methods behind one interface, moving and clearing funds between accounts. That's a “running the system” function, separate from whether an entity issues e-money balances at all.

Both licenses are approved by BSP, which reviews whether the applicant has real financial capacity, operational capability, and governance in place; the process typically runs on a quarterly timeline rather than weeks. In practice, an entity could in principle hold both functions — running a payment system and issuing e-money balances — or only one of them, for example a firm that focuses purely on acquiring aggregation without issuing e-wallet balances at all, which would fall under OPS only. When merchants verify a provider's credentials, these two licenses should be checked separately; hearing “we're licensed” is not enough to assume both are covered.

Why This Isn't Just the Provider's Problem

The common reaction is: “licensing is the provider's compliance headache, I'm just using their interface to collect payments, why does it concern me?” In practice, whether the OPS license is properly in place flows through to the merchant in at least three ways.

• The due-diligence chain runs through the merchant too. Opening a Philippine corporate bank account and signing with a payment provider both involve KYC checks that examine not just the provider, but the merchant's own registration documents, directors, business address, and fund flows. If the merchant is actually working with an unlicensed, pass-through arrangement, that whole due-diligence chain is built on shaky ground, and the fund-safety and compliance risk ultimately lands back on the merchant.
• Legal exposure can pass through. If a payment channel is eventually found to be operating a payment system without a license, it's not only the provider that's affected — the merchant's own collections could be disrupted, settlement and reconciliation could stall mid-stream, directly hitting cash flow and downstream fulfillment.
• Long-term stability differs. Licensed entities remain under ongoing BSP supervision, with baseline requirements on financial capacity and governance. Unlicensed, pass-through arrangements are more likely to shut down abruptly, leaving merchants with little warning and no clearly accountable party to turn to afterward.

For teams assessing e-commerce compliance risk in the Philippines, whether the payment channel is properly licensed is usually near the top of the checklist — whether collections settle reliably determines whether the whole business chain keeps running. If the corporate foundation itself isn't sorted, say company registration hasn't been completed yet, this step gets harder to push through too.

The Less Convenient Side

To be fair, working with a licensed provider isn't a “set it and forget it” situation. A couple of things merchants should keep in mind.

• Onboarding with a licensed provider doesn't mean handing off all responsibility — KYC and anti-money-laundering documentation that's the merchant's own to provide still has to come from the merchant, licensed provider or not.
• Not every entity that claims it can “do payment integration” actually holds a BSP-issued OPS or EMI license. Pass-through and subcontracted arrangements are not uncommon in the market, so merchants need to verify independently rather than take a provider's word for it.

On top of that, fee structures, settlement timing (same-day D0 vs next-day T1), and the number of payment channels supported all vary by provider, so it's worth comparing a few rather than signing on the first one that says it's licensed.

How to Actually Check Whether a Provider Is Licensed

Verifying whether an entity genuinely holds an OPS or EMI license isn't complicated. BSP publishes a public list of registered electronic money issuers and operators of payment systems, and merchants can take the license number and registered company name a provider gives them and check it against that list directly, without relying solely on the provider's own introduction.

If a merchant hasn't finished setting up its own corporate entity yet, completing Philippine company registration first tends to make the process with a payment provider smoother — provider due diligence typically asks for SEC registration documents too, and without a registered entity this step generally can't move forward.

As one example this site is aware of: SmartPay (paysmartph.com) holds BSP-issued OPS and EMI status and works on native GCash collection, QRPH aggregated collection, and Maya disbursement. This is information this site has come across, stated as-is and not presented as the only option — merchants are welcome to verify the license number themselves and compare a few providers. To learn more directly, reach out via Telegram (@LouisSMARTPAY), or check their discussion group at t.me/smartpaymanila to see what other merchants are asking.

Official Sources

For the regulatory details on OPS and EMI licensing, defer to BSP's own published information; where anything here differs from current guidance, the central bank's latest notice takes precedence.

• Bangko Sentral ng Pilipinas (BSP): regulatory information on payment systems and electronic money.
• Securities and Exchange Commission (SEC): verify company registration details, directors, and other entity documentation.

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.