What Is a BSP NOPS License? Non-Bank Operator of Payment Systems Explained

The first time a compliance reviewer in Manila asked whether our payment partner actually held a "NOPS" license, I assumed it was a typo. I searched it, found "OPS," found "operator of payment systems," and realized all four phrasings pointed at the same thing: a licensing category under the Bangko Sentral ng Pilipinas (BSP) that almost nobody explains in plain language. As the tech lead for a China-based team running payment integrations into the Philippines, I had to get this straight before signing off on any new provider contract. This is what I wish I had found on day one: what OPS actually is, who needs to hold it, how it differs from an EMI license, and how I verify whether a provider holds it before routing a transaction through them.

Why "NOPS," "OPS," and "Operator of Payment Systems" All Mean the Same Thing

Let me clear up the terminology first, because it tripped me up longer than I want to admit. "OPS" is short for Operator of Payment Systems, the BSP license category covering entities that operate a payment system in the Philippines. "NOPS" is the same thing with one extra word baked in: Non-bank Operator of Payment Systems, the subset of OPS entities that are not themselves banks. Since most payment gateways, remittance companies, and switching operators are non-bank entities, people drop the "Non-bank" in everyday conversation and just say "OPS," which is why search queries bounce between "bsp nops," "nops bsp," "ops bsp," and "operator of payment system bsp" without anyone meaning anything different. For the rest of this article I use "OPS" as the general term, calling out "non-bank OPS" only where the distinction from a bank-operated system actually matters.

What the BSP's Operator of Payment Systems Category Actually Covers

Under the National Payment Systems Act (Republic Act No. 11127), the BSP has oversight authority over payment systems operating in the Philippines, not just over banks and e-money issuers individually. A payment system, in this context, is the infrastructure that moves and clears payment instructions between participants — the switch that routes a transaction from a sender's account to a receiver's account, validates it, and passes it along the chain until settlement happens. The OPS license covers the entity performing that operating function.

This matters because the BSP's framework separates two questions that get collapsed into one in casual conversation: what kind of institution a company is, and what function it performs. A company can be a bank, a non-bank financial institution, or an electronic money issuer — that is "what it is." Separately, a company can operate a payment system, a switch, a clearing arrangement, or a payment gateway — that is "what it does." Some companies only do one of these. Larger platforms that both issue stored-value accounts and operate the rails those accounts move through typically need authorization for both functions. The OPS category is the piece that tells you whether a company is actually authorized to operate the switching and routing infrastructure your transactions pass through, rather than simply being registered as a business.

Who Actually Needs to Hold an OPS License

In practice, the OPS category applies to a fairly specific set of roles, and it is worth being precise about who falls inside it and who does not.

Entities that typically need an OPS registration include payment gateways and aggregators that route and switch transactions across channels and institutions, remittance and money transfer operators that move funds through their own processing infrastructure, bill payment aggregators consolidating payments across multiple billers, and the payment-system-operating function inside a larger electronic money issuer — the part of an e-wallet company's business that handles switching and routing, distinct from the part that issues and holds stored-value balances. Clearing and switching operators behind interoperable QR standards and real-time payment rails also fall into this category.

What does not automatically require an OPS license is simpler than people assume: a merchant accepting payments through a properly licensed gateway does not need its own OPS registration, because the merchant is a customer of the payment system, not an operator of one. The requirement sits with the intermediary actually operating the infrastructure moving the money, not with every business that touches a transaction along the way.

OPS vs EMI: Two Different License Categories, Not Competing Labels

This is the point that caused us the most confusion when we first started comparing providers. An Electronic Money Issuer (EMI) license and an OPS license are not two tiers of the same thing, and neither is a "better" or "more complete" version of the other. They authorize different functions.

An EMI license governs entities that issue electronic money — they hold customer funds as stored value in an account-like format, the way a typical e-wallet does. An OPS license governs entities that operate a payment system — they run the switching and routing infrastructure that moves payment instructions between parties. A company can hold an EMI authorization while routing transactions through someone else's rails, without operating much switching infrastructure of its own. A company can hold an OPS registration without ever issuing electronic money at all. A company that does both — issues e-money and operates the rails it moves through — typically needs both authorizations, since each covers a distinct regulated activity.

A provider's marketing material often just says "BSP-licensed" without specifying which authorization applies. Confirming whether a provider holds OPS authorization, EMI authorization, or both changes what questions you should be asking about fund custody, settlement responsibility, and dispute recourse.

For the fuller breakdown, we wrote a separate piece on how the EMI license defines the business boundaries of an electronic money issuer, and a dedicated explainer on what the BSP OPS license actually authorizes.

Dimension	Operator of Payment Systems (OPS)	Electronic Money Issuer (EMI)
Primary regulated activity	Operating the switching and routing infrastructure that moves payment instructions between participants	Issuing electronic money and holding customer funds as stored value
Holds customer balances directly?	Not inherently part of the OPS function itself	Yes, this is the core of what an EMI does
Typical business model	Payment gateways, switches, remittance processors, bill payment aggregators	E-wallets, prepaid stored-value accounts, digital cash platforms
Can a company hold both?	Yes, common for platforms that both issue e-money and operate their own rails	Yes, same as above
What a merchant should verify	Whether the switching entity you are integrating with is actually the registered operator, or an unregistered layer sitting on top of one	Whether the entity holding your settlement funds between collection and payout is the licensed issuer, not an intermediary

How I Verify a Provider Actually Holds This License Before We Sign

Once I understood the distinction, verification became a much more concrete process than "ask them if they're licensed and take the answer at face value." Here is roughly what we do before signing any new payment partner contract.

First, we ask for the exact registered legal name of the entity we would be contracting with, not just the consumer-facing brand name — a brand can be operated by a licensed entity, an unlicensed affiliate, or a reseller layered on top of one, and the difference matters for who is actually accountable. Second, we cross-reference that legal name against the BSP's published list of supervised financial institutions, the authoritative source for confirming whether an entity is recognized in a given license category. Third, we ask the provider directly, in writing, to state their license type — OPS, EMI, or both — and treat a vague or evasive answer as a signal in itself. Fourth, we check SEC registration as a supporting signal only, never as a substitute for BSP licensing, since they answer different questions. Fifth, because licensing status is not static, we keep a habit of periodic re-verification rather than treating a single onboarding check as permanent proof. We go through this same logic in more structured form in our five-step due diligence checklist for verifying a payment provider's BSP compliance.

What Happens When a Provider Operates Without This License

I want to be careful here — this is not about naming any specific company, but about the structural risk that exists whenever a provider in this market operates without full, disclosed licensing. Some providers in the Philippines payments space do operate without holding or clearly disclosing the relevant BSP authorization, sometimes presenting themselves as a licensed entity's reseller or sub-agent without making that relationship explicit.

The consequences of routing funds through an unlicensed or undisclosed operator are structural, not hypothetical. There is no regulatory obligation on an unlicensed entity to safeguard or segregate the funds passing through it the way a BSP-supervised institution is required to. There is no supervisory body to escalate a dispute to, because the entity sits outside the framework a regulator actually governs. If the operator ceases operations or simply becomes unresponsive, your recourse is whatever is written into a private commercial contract, not a regulatory protection. And because an unlicensed intermediary is not subject to the same audit and reporting obligations, the paper trail behind your settlement can be far thinner than the merchant-facing dashboard suggests. We laid out a fuller comparison in how to choose between a licensed BSP OPS/EMI entity and an unlicensed agent layered on top of one.

Aspect	Licensed OPS / EMI Provider	Unlicensed or Undisclosed Operator
Regulatory status	Registered and supervised by the BSP under a named license category	Not recognized under any BSP license category, or presenting an affiliate's license as its own
Fund safeguarding obligation	Subject to BSP requirements on handling and segregating customer and merchant funds	No equivalent regulatory requirement; safeguarding depends entirely on the operator's own practices
Recourse if the provider disappears	A regulator exists to escalate to, and the entity is identifiable and accountable	Recourse is limited to whatever is written in a private contract, with no regulatory backstop
Contractual transparency	The contracting entity is the actual licensed operator	The contracting entity may be a reseller or agent, not the licensed party itself
Audit trail behind settlement	Subject to reporting and audit obligations tied to the license	No equivalent obligation; the trail may stop at the unlicensed layer

A Simple Internal Verification Checklist We Use

I will be direct about one thing: there is no public BSP API that lets you programmatically query a provider's license status. What we actually built instead is a small internal compliance record our team keeps for every provider we onboard, combining the manual verification steps above with a reminder so nobody forgets to re-check. It is intentionally simple — the value is in the discipline of checking, not in any clever automation.

// Internal compliance record we keep for every payment provider we onboard.
// This is NOT a call to any BSP API — no such public endpoint exists.
// It is our own tracking structure, built from manual verification steps.

const providerLicenseRecord = {
  registeredLegalName: "Example Payment Solutions Corp.",
  brandName: "ExamplePay",
  bspLicenseType: "OPS", // "OPS", "EMI", or "OPS+EMI"
  licenseStatus: "ACTIVE", // ACTIVE | SUSPENDED | NOT_FOUND
  verifiedAgainst: "BSP published list of supervised financial institutions",
  verifiedOn: "2026-09-15",
  verifiedBy: "compliance_lead",
  reverificationIntervalDays: 90,
};

function flagForReverification(record, todayIso) {
  const daysSinceVerified = diffInDays(todayIso, record.verifiedOn);

  if (record.licenseStatus !== "ACTIVE") {
    return {
      needsReview: true,
      reason: `License status is "${record.licenseStatus}", not ACTIVE`,
    };
  }

  if (daysSinceVerified > record.reverificationIntervalDays) {
    return {
      needsReview: true,
      reason: `Last verified ${daysSinceVerified} days ago, exceeds internal review interval`,
    };
  }

  return { needsReview: false };
}

function diffInDays(isoA, isoB) {
  const msPerDay = 24 * 60 * 60 * 1000;
  return Math.round((new Date(isoA) - new Date(isoB)) / msPerDay);
}

Every provider record goes through this structure before being approved for live settlement. It has caught more than one case where a brand name we trusted turned out to be operated through a different legal entity than the one we originally verified — exactly the kind of drift this checklist exists to catch. Once the compliance side is settled, the technical integration path is covered in our developer's guide to payment collection and disbursement in the Philippines.

Frequently Asked Questions

Is NOPS a separate license from OPS?

No. NOPS stands for Non-bank Operator of Payment Systems, simply the non-bank subset of the broader OPS category. People say "OPS" and "NOPS" to mean the same licensing concept, since most entities in this category are non-bank companies anyway.

If a provider already holds an EMI license, do they still need an OPS registration?

It depends on what they actually do. An EMI license covers issuing electronic money and holding customer balances. If that same company also operates its own switching or routing infrastructure rather than relying entirely on someone else's rails, that is a separate activity that typically falls under the OPS category and needs its own authorization.

Can I ask a provider to show me their BSP license directly?

Yes, and you should. A legitimate, properly licensed provider should confirm their registered legal name and license category without hesitation, and that name should be checkable against the BSP's published list of supervised institutions. Hesitation on this specific point is itself useful information.

What is the difference between "BSP-registered" and "BSP-licensed"?

These terms often get used interchangeably in marketing, but the distinction matters: being listed as a BSP-supervised institution under a category like OPS or EMI is a different claim than simply being a registered corporation. Standard SEC registration does not, on its own, mean a company holds any BSP authorization.

Does holding an OPS license mean transactions will never fail?

No. Licensing tells you whether an entity is authorized and supervised to operate payment infrastructure, not that every transaction on it will always process smoothly. Operational issues and individual bank or wallet processing can still affect any given transaction regardless of licensing status.

What law actually gives the BSP authority over payment systems in the Philippines?

The National Payment Systems Act, Republic Act No. 11127, established the BSP's oversight authority over payment systems operating in the country, including the registration framework the OPS category falls under.

For a foreign business owner evaluating payment partners in the Philippines, confirming OPS and EMI status is not a bureaucratic box to tick before the pricing conversation. It determines who is actually accountable for the funds sitting between your customer's payment and your settlement, which regulator exists to escalate to if something goes wrong, and whether the paper trail behind your money stops at a supervised institution or at an unregistered layer you have no visibility into. The confusion between "NOPS," "OPS," and "operator of payment systems" is harmless once you realize it is one category described four ways. Skipping the verification step because the acronyms sounded close enough to something official is not.

If you are evaluating a payment partner in the Philippines and want a second set of eyes on how their license category lines up with your settlement structure, you can reach our team directly on Telegram at @LouisSMARTPAY or by email at [email protected].