I. Introduction

The Philippine online gaming industry is heavily regulated, commercially significant, and legally sensitive. Any person or entity intending to participate in online gaming operations connected with the Philippines must first understand the role of the Philippine Amusement and Gaming Corporation, commonly known as PAGCOR, and the licensing framework that governs gaming activities.

A PAGCOR B2B Online Gaming Aggregator License generally refers to a regulatory authorization for a business-to-business service provider that aggregates, supplies, integrates, or facilitates online gaming content, platforms, systems, products, or related services for licensed gaming operators. Unlike a consumer-facing online gaming operator, a B2B aggregator typically does not directly take bets from players. Instead, it provides technology, game content, platform integration, wallet or back-office connectivity, reporting systems, or other gaming-related services to licensed operators.

In the Philippine context, this license is important because PAGCOR regulates not only gaming operators but also many categories of gaming service providers that support the industry. A company that supplies online gaming content or infrastructure without the proper approval may expose itself and its counterparties to regulatory enforcement, contract invalidity risks, tax issues, banking difficulties, and reputational harm.

This article explains the legal context, regulatory rationale, probable application requirements, corporate structuring issues, compliance obligations, operational expectations, and legal risks involved in applying for a PAGCOR B2B Online Gaming Aggregator License.

II. PAGCOR’s Legal Role in Philippine Gaming Regulation

PAGCOR is a government-owned and controlled corporation with a dual role in Philippine gaming. It may operate gaming activities and also regulate certain gaming businesses. Its powers come from its legislative charter and related laws, rules, executive issuances, and regulatory frameworks.

In broad terms, PAGCOR’s regulatory authority covers casino gaming, electronic gaming, online gaming, gaming service providers, gaming platforms, and related gaming activities that fall within its jurisdiction. PAGCOR may issue licenses, accreditations, approvals, provisional authorities, certificates, and other regulatory permissions depending on the category of activity.

The legal significance of PAGCOR licensing is that gaming is not an ordinary commercial activity. In the Philippines, gambling is generally prohibited unless expressly authorized by law or by a competent regulator. A license or authority from PAGCOR is therefore not merely a business permit. It is the legal basis that separates lawful regulated gaming participation from unlawful gambling activity.

III. Meaning of a B2B Online Gaming Aggregator

A B2B online gaming aggregator is usually a company that acts as a technological or commercial intermediary between game suppliers and licensed gaming operators. It may provide one or more of the following:

Aggregated game content from multiple studios or game providers.
A single application programming interface or integration layer for operators.
Remote game server connectivity.
Platform management tools.
Game lobby systems.
Player account integration tools.
Reporting dashboards.
Risk monitoring and transaction logs.
Game certification coordination.
Technical support for operator integrations.
Back-office systems.
Wallet or payment integration support, where allowed.
Compliance reporting tools.
Game launch, testing, and production deployment services.

The “B2B” character is important. The aggregator’s client is normally another business, such as a PAGCOR-licensed operator, and not the end user or player. However, the distinction is not always enough to avoid licensing. If the aggregator touches gaming systems, games of chance, player data, game outcomes, wagering flow, revenue share, or platform functionality, PAGCOR may require licensing, accreditation, or approval.

IV. Difference Between a B2B Aggregator and an Online Gaming Operator

A gaming operator usually has the primary relationship with players. It may register players, accept wagers, manage player accounts, pay winnings, market the gaming site, and assume operational responsibility for gaming activity.

A B2B aggregator, by contrast, usually supports the operator. It may provide the games, the technical platform, the integration layer, the reporting system, or the content aggregation function. It may earn fees through revenue share, fixed monthly charges, integration fees, transaction-based fees, or licensing fees.

The distinction matters because regulatory obligations differ. Operators typically face heavier duties relating to player onboarding, know-your-customer procedures, responsible gaming, anti-money laundering compliance, player fund controls, marketing rules, and consumer protection. Aggregators, however, may still be required to meet high standards on system integrity, game fairness, cybersecurity, audit logs, data protection, testing, revenue reporting, and contractual controls with operators.

A B2B aggregator should not assume that it is outside PAGCOR’s jurisdiction merely because it does not directly deal with players. If its services are material to the conduct of licensed gaming, PAGCOR may regulate it.

V. Why PAGCOR Requires Licensing or Approval for Aggregators

PAGCOR’s interest in licensing B2B aggregators is rooted in several regulatory concerns.

First, online gaming depends heavily on technology. If the software, game server, random number generator, payout table, wallet interface, or reporting system is compromised, the integrity of the entire gaming operation may be affected.

Second, aggregators may have access to sensitive data, including player identifiers, transaction histories, bet records, game outcomes, and financial reporting. This creates data privacy and cybersecurity risks.

Third, aggregators may participate in revenue flows. Even if they do not directly receive player funds, they may earn revenue from wagers, gross gaming revenue, net gaming revenue, or other gaming-related metrics. PAGCOR has a legitimate interest in monitoring such arrangements.

Fourth, operators may rely on aggregators for compliance reports. If the aggregator’s system does not produce accurate and complete data, the operator’s reporting to PAGCOR may also become defective.

Fifth, unlicensed service providers can become a channel for illegal gaming, unauthorized game deployment, tax leakage, money laundering, fraud, or circumvention of player protection rules.

For these reasons, a B2B aggregator license or approval is a regulatory gatekeeping mechanism.

VI. Who Should Consider Applying

A company should consider applying for a PAGCOR B2B Online Gaming Aggregator License or equivalent approval if it intends to provide online gaming-related services to PAGCOR-regulated operators and its role involves any of the following:

Supplying online casino games, slots, live dealer games, table games, betting games, virtual games, or similar content.
Aggregating games from multiple providers.
Operating a remote game server.
Providing platform-as-a-service for gaming operators.
Integrating third-party gaming content into operator websites or applications.
Providing back-office gaming management systems.
Managing game launch infrastructure.
Providing game outcome, payout, or randomization technology.
Participating in gaming revenue.
Providing systems used for regulatory reports.
Handling player gaming records.
Hosting or transmitting gaming data.
Providing wallet, payment, or settlement-related gaming support.
Offering white-label or turnkey gaming technology solutions.

Even where the exact licensing category is uncertain, a prudent company should seek a formal regulatory classification before commencing activity.

VII. Corporate Eligibility and Philippine Presence

A foreign or domestic company intending to apply must consider Philippine corporate, foreign investment, tax, licensing, and local presence requirements.

Depending on the applicable PAGCOR rules and the business model, PAGCOR may require the applicant to be a Philippine corporation, a foreign corporation registered to do business in the Philippines, or an offshore entity with locally approved arrangements. The proper structure depends on whether the aggregator will perform services in the Philippines, contract with Philippine licensees, host systems locally, employ local personnel, receive Philippine-source income, or maintain local operations.

Common structuring options include:

A Philippine domestic corporation.
A Philippine subsidiary of a foreign parent.
A Philippine branch of a foreign corporation.
A foreign service provider with PAGCOR recognition or accreditation.
A joint venture with a licensed Philippine gaming entity.
A contractual B2B provider arrangement approved by PAGCOR.

Each structure has different implications for liability, taxation, capitalization, licensing, corporate governance, immigration, labor, banking, and local permits.

VIII. Key Philippine Legal Areas Affecting the Application

A B2B Online Gaming Aggregator License application does not exist in isolation. It intersects with several legal regimes.

A. Gaming Law

Gaming law determines whether the activity is lawful, who may conduct it, what license is required, what games may be offered, what systems may be used, and what regulatory approvals are necessary.

B. Corporate Law

The applicant’s corporate existence, authority, ownership, directors, officers, capitalization, and governance must comply with Philippine corporate law if the applicant is locally incorporated or registered.

C. Foreign Investment Law

Foreign ownership restrictions may be relevant depending on the precise classification of the business activity. Gaming itself is a sensitive regulated area. Legal review is necessary to determine whether the applicant’s activities are treated as gaming operations, technology services, software licensing, management services, or another category.

D. Tax Law

Gaming-related revenues may be subject to special taxes, franchise taxes, income taxes, withholding taxes, value-added tax, percentage tax, local taxes, or other fiscal obligations depending on the structure and revenue model.

E. Anti-Money Laundering Law

Gaming businesses and certain gaming-related service providers may be subject to anti-money laundering obligations. Even B2B providers may need to support transaction monitoring, audit trails, suspicious transaction detection, and recordkeeping.

F. Data Privacy Law

The Data Privacy Act applies when personal information or sensitive personal information is processed. Aggregators may be personal information processors or controllers depending on their role.

G. Cybercrime and Cybersecurity Law

Gaming platforms are exposed to hacking, fraud, bot activity, account takeover, denial-of-service attacks, and system manipulation. Cybersecurity controls are therefore a major licensing concern.

H. Consumer Protection and Responsible Gaming

Although B2B aggregators may not directly deal with players, they may need to support operator compliance with responsible gaming tools, age restrictions, self-exclusion, player limits, and game information disclosures.

I. Labor and Immigration Law

If the applicant maintains Philippine staff or foreign personnel in the Philippines, it must comply with labor standards, work permits, visas, and local employment rules.

J. Local Government Permits

If the applicant maintains an office or operational facility in the Philippines, local business permits, barangay clearances, zoning approvals, fire safety clearances, and related permits may be needed.

IX. Typical Application Requirements

The exact requirements depend on PAGCOR’s current rules and the license category. However, a B2B aggregator applicant should generally prepare for a detailed documentary and technical submission.

Common requirements may include:

Letter of intent or formal application.
Corporate profile.
Articles of incorporation, bylaws, or equivalent constitutional documents.
Certificate of incorporation or registration.
Board authorization approving the application.
List of directors, officers, shareholders, and beneficial owners.
Organizational chart.
Group corporate structure chart.
Ultimate beneficial ownership disclosure.
Audited financial statements.
Proof of financial capacity.
Tax registration documents.
Business permits, if applicable.
Description of proposed business model.
Description of gaming products and services.
List of game providers or studios to be aggregated.
List of target operators or counterparties.
Draft or executed B2B contracts.
Revenue model and fee structure.
Technical architecture diagram.
System security documentation.
Game certification or testing reports.
Random number generator certifications, if applicable.
Platform certification reports, if applicable.
Data privacy compliance documents.
AML compliance framework, if applicable.
Responsible gaming support features.
Disaster recovery and business continuity plan.
Cybersecurity policies.
Internal control policies.
Regulatory reporting capability.
Fit-and-proper documents for key persons.
Police, court, or NBI clearances, where required.
Anti-bribery and anti-corruption undertaking.
Application fees and processing fees.
Other documents requested by PAGCOR.

The applicant should expect PAGCOR to review not only legal documents but also the applicant’s technology, financial credibility, ownership transparency, management integrity, and operational readiness.

X. Fit-and-Proper Review

PAGCOR may evaluate whether the applicant, its shareholders, directors, officers, key employees, beneficial owners, and related entities are fit and proper to participate in the gaming industry.

The fit-and-proper review may consider:

Criminal history.
Regulatory history.
Prior gaming licenses.
License suspensions or revocations.
Financial integrity.
Source of funds.
Tax compliance.
Litigation history.
Bankruptcy or insolvency history.
Association with illegal gaming.
Anti-money laundering concerns.
Sanctions exposure.
Reputation and business track record.

Because gaming is a trust-sensitive industry, undisclosed ownership, nominee arrangements, unclear funding, or adverse regulatory history can seriously damage an application.

XI. Beneficial Ownership and Control

A major issue in gaming applications is identifying the real persons who own, control, or benefit from the applicant.

PAGCOR may require disclosure of:

Direct shareholders.
Indirect shareholders.
Parent companies.
Ultimate beneficial owners.
Voting arrangements.
Nominee shareholders.
Trust structures.
Share pledges.
Convertible instruments.
Side agreements affecting control.
Persons with economic interests in gaming revenue.

The applicant should ensure that ownership information is accurate, consistent, and supported by corporate documents. Inconsistent beneficial ownership disclosures can trigger delays, enhanced due diligence, or denial.

XII. Capitalization and Financial Capacity

A B2B aggregator must demonstrate that it has enough financial capacity to operate reliably. PAGCOR may be concerned with whether the applicant can maintain systems, pay regulatory fees, support operators, protect data, respond to incidents, and remain solvent.

Financial documents may include audited accounts, bank certificates, capitalization records, source-of-funds documents, parent company guarantees, financial projections, and proof of paid-up capital.

A weak balance sheet may not automatically prevent approval, but it can raise concerns, especially where the applicant will operate critical infrastructure.

XIII. Technology and System Integrity

Technology review is central to a B2B aggregator license. PAGCOR will likely want assurance that the aggregator’s systems are secure, auditable, reliable, and fair.

Relevant technical issues include:

System architecture.
Hosting environment.
Server location.
Cloud service providers.
Encryption.
Access controls.
User privilege management.
Audit logs.
Game result integrity.
Random number generation.
Game payout configuration.
Version control.
Incident response.
Penetration testing.
Vulnerability management.
Disaster recovery.
Uptime and availability.
Data retention.
Segregation of operator data.
Regulatory access to reports.

If the aggregator supplies games, those games may need certification by an approved testing laboratory. If the aggregator provides a platform, the platform may also require testing or inspection.

XIV. Game Certification

Game certification is one of the most important parts of online gaming compliance. A regulator must be satisfied that games operate fairly and according to approved mathematical rules.

Game certification may cover:

Random number generator integrity.
Return-to-player percentage.
Game rules.
Paytables.
Volatility and mathematical model.
Bonus features.
Jackpot mechanics.
Error handling.
Incomplete game treatment.
Game logs.
Version control.
Player display information.
Jurisdictional configuration.

An aggregator that offers third-party games should ensure that each game has certification acceptable to PAGCOR and that no uncertified game version is deployed.

XV. Contracts With Operators

A B2B aggregator’s contracts with licensed operators are legally significant. PAGCOR may require copies or summaries of these agreements.

Important contract provisions include:

Scope of services.
Regulatory compliance obligations.
PAGCOR approval condition.
Game list and approved products.
Technical integration responsibilities.
Service-level commitments.
Data ownership and processing roles.
Audit rights.
Revenue share or fee computation.
Tax responsibility.
AML cooperation.
Responsible gaming support.
Incident notification.
Suspension rights.
Termination for regulatory breach.
Confidentiality.
Intellectual property licensing.
Indemnity.
Limitation of liability.
Dispute resolution.
Governing law.
Regulator access and cooperation.

Contracts should avoid provisions suggesting that the aggregator is secretly operating the gaming business if it is licensed only as a B2B provider. The division of responsibilities must be clear.

XVI. Revenue Models and Regulatory Issues

B2B aggregators may earn revenue in different ways:

Fixed monthly fees.
Setup or integration fees.
Per-game licensing fees.
Transaction fees.
Revenue share based on gross gaming revenue.
Revenue share based on net gaming revenue.
Minimum guarantees.
Tiered fees based on volume.
Hybrid fee structures.

Revenue share models are common but sensitive because they connect the aggregator economically to gaming activity. PAGCOR may scrutinize whether the arrangement effectively makes the aggregator a participant in gaming operations rather than a mere service provider.

The tax consequences also differ depending on how fees are characterized. A payment for software licensing, technical services, management services, or gaming revenue participation may be treated differently for tax and withholding purposes.

XVII. Data Privacy Compliance

A B2B aggregator may process personal data relating to players, operator staff, affiliates, or other users. Under Philippine data privacy principles, the company must establish a lawful basis for processing, implement security measures, observe data subject rights, and comply with cross-border transfer requirements where applicable.

Key documents may include:

Privacy policy.
Data processing agreement.
Data retention policy.
Information security policy.
Breach response procedure.
Data subject rights procedure.
Cross-border data transfer assessment.
Subprocessor list.
Data inventory.
Appointment of a data protection officer, where required.

The aggregator should determine whether it acts as a personal information controller, personal information processor, or both. In many B2B settings, the operator controls the player relationship, while the aggregator processes data on the operator’s behalf. However, if the aggregator independently determines the use of data, it may assume controller obligations.

XVIII. Anti-Money Laundering Considerations

Online gaming can be vulnerable to money laundering, fraud, mule accounts, collusion, and suspicious transaction patterns. Operators usually bear primary AML duties, but aggregators may still play an important supporting role.

An aggregator may need systems that allow operators to:

Track wagers and winnings.
Identify unusual betting patterns.
Generate transaction reports.
Preserve logs.
Support suspicious transaction investigation.
Freeze or suspend suspicious activity where technically required.
Provide audit trails.
Respond to regulator inquiries.

If the aggregator has access to relevant transaction data, it should maintain policies for cooperation with operators and regulators.

XIX. Responsible Gaming

Responsible gaming is a core regulatory policy. Even if an aggregator does not interact with players, its systems may need to support responsible gaming controls.

Relevant features may include:

Age restriction controls.
Self-exclusion integration.
Deposit or wagering limit integration.
Reality checks.
Session time reminders.
Game information displays.
Responsible gaming messaging.
Cool-off periods.
Operator-initiated account restriction tools.
Reporting of risky play indicators.

If the aggregator supplies games, game design should avoid misleading representations, undisclosed odds, hidden mechanics, or unfair bonus features.

XX. Cybersecurity and Operational Resilience

PAGCOR and licensed operators will expect a B2B aggregator to maintain robust cybersecurity controls. Weak cybersecurity can lead to game manipulation, data breaches, financial loss, and regulatory sanctions.

Common requirements or best practices include:

Secure software development lifecycle.
Code review.
Penetration testing.
Vulnerability scanning.
Encryption in transit and at rest.
Multi-factor authentication.
Role-based access control.
Security logging.
Security information and event monitoring.
Incident response plan.
Disaster recovery plan.
Business continuity plan.
Backup policy.
Change management.
Patch management.
Vendor risk management.
Employee security training.

For cloud-based systems, the applicant should be ready to explain where data is hosted, who has access, what security certifications exist, and how PAGCOR can audit relevant records.

XXI. Local Hosting and Cross-Border Services

A recurring issue in online gaming regulation is whether systems must be hosted in the Philippines or whether offshore hosting is permitted. The answer may depend on the applicable license, PAGCOR rules, data access requirements, cybersecurity arrangements, and the nature of the service.

If systems are hosted offshore, the aggregator should be ready to address:

PAGCOR access to records.
Data localization concerns.
Cross-border data transfer compliance.
Server auditability.
Disaster recovery.
Law enforcement cooperation.
Latency and service reliability.
Applicable foreign laws.
Subcontractor controls.
Regulatory inspection rights.

Even when offshore hosting is allowed, the applicant should ensure that contracts and technical arrangements permit PAGCOR and licensed operators to obtain necessary information promptly.

XXII. Intellectual Property Issues

Aggregators frequently deal with software, games, trademarks, artwork, game math, source code, APIs, databases, and proprietary platforms. The applicant must be able to prove that it has rights to provide the products it offers.

Important intellectual property documents include:

Software license agreements.
Game distribution agreements.
Studio agreements.
Trademark licenses.
Source code escrow agreements, where applicable.
API documentation ownership terms.
White-label platform licenses.
Content sublicensing authority.
Certification rights.
Restrictions by territory or operator type.

The aggregator should ensure that it is authorized to offer the games in the Philippine regulated market. Some game providers restrict use by jurisdiction, operator, platform, currency, or player location.

XXIII. Tax Considerations

Tax treatment depends on corporate structure, source of income, service location, contract terms, and payment flows.

Relevant Philippine tax issues may include:

Corporate income tax.
Withholding tax on service fees.
Withholding tax on royalties.
Value-added tax.
Percentage tax.
Local business tax.
Documentary stamp tax.
Transfer pricing.
Tax treaty relief.
Permanent establishment risk.
Tax registration and invoicing.
Special tax treatment for gaming revenue, where applicable.

If a foreign aggregator contracts with a Philippine operator, the parties must analyze whether payments are Philippine-source income and whether withholding applies. If the foreign aggregator has personnel, servers, agents, or dependent representatives in the Philippines, permanent establishment or local tax registration issues may arise.

XXIV. Local Permits and Business Registration

A Philippine-based applicant may need several registrations before or alongside the PAGCOR process:

Securities and Exchange Commission registration.
Bureau of Internal Revenue registration.
Local government business permit.
Barangay clearance.
Mayor’s permit.
Fire safety inspection certificate.
Occupancy permit, where applicable.
Social security, health insurance, and housing fund registrations for employees.
Data privacy registration, where applicable.
Immigration and labor permits for foreign staff.

PAGCOR licensing does not automatically replace ordinary business registrations unless a specific rule provides otherwise.

XXV. Application Process

The process usually involves several stages.

1. Regulatory Classification

Before filing, the applicant should determine the correct license or accreditation category. This may involve informal consultation, written inquiry, or engagement with PAGCOR’s licensing department.

2. Corporate Structuring

The applicant should choose the appropriate entity structure and ensure that ownership, capitalization, tax, and governance are acceptable.

3. Document Preparation

Corporate, financial, technical, compliance, and fit-and-proper documents must be assembled.

4. Submission of Application

The applicant files the application and pays the required fees.

5. PAGCOR Evaluation

PAGCOR reviews the documents, asks questions, requests clarifications, and evaluates the applicant’s suitability.

6. Technical Review

Systems, games, platforms, reports, and security controls may be reviewed.

7. Due Diligence

PAGCOR may conduct background checks on the applicant, its officers, shareholders, beneficial owners, and affiliates.

8. Approval, Provisional Authority, or Conditional Clearance

The applicant may receive approval subject to conditions, additional submissions, testing, payment of fees, or execution of undertakings.

9. Launch Approval

Even after licensing, specific games, operators, systems, or integrations may require additional approval before going live.

10. Continuing Compliance

The licensee must submit reports, pay fees, maintain records, pass audits, and comply with PAGCOR directives.

XXVI. Fees, Bonds, and Financial Obligations

A B2B aggregator should expect monetary obligations, which may include:

Application fees.
Processing fees.
License fees.
Accreditation fees.
Renewal fees.
Regulatory monitoring fees.
Testing and certification costs.
Security deposits.
Performance bonds.
Minimum guarantees, if applicable.
Penalties for non-compliance.
Taxes and withholding obligations.

The exact amounts depend on PAGCOR’s applicable schedule and the license category. Applicants should budget not only for government fees but also for legal counsel, technical consultants, testing laboratories, cybersecurity assessments, accounting, and corporate compliance.

XXVII. Ongoing Compliance Obligations

After approval, the licensee may be required to comply with continuing obligations, including:

Maintaining good corporate standing.
Paying annual or periodic fees.
Submitting regular reports.
Reporting material changes.
Seeking approval for new games.
Seeking approval for new operators.
Reporting system incidents.
Maintaining certified game versions.
Keeping audit logs.
Preserving records.
Allowing regulatory inspection.
Maintaining AML and data privacy controls.
Reporting changes in ownership or control.
Reporting changes in directors or officers.
Maintaining financial capacity.
Renewing the license before expiry.
Complying with responsible gaming requirements.
Complying with PAGCOR circulars, notices, and directives.

A common mistake is treating the license as a one-time approval. In practice, regulated gaming compliance is continuous.

XXVIII. Material Changes Requiring Prior Approval

A B2B aggregator should be cautious before making major changes. PAGCOR may require prior notice or approval for:

Change in ownership.
Change in beneficial ownership.
Change in directors or key officers.
Change in corporate name.
Merger or acquisition.
Transfer of license.
New game providers.
New games.
New platform versions.
New hosting location.
New operator integrations.
New payment or wallet arrangements.
Change in revenue model.
Outsourcing of critical functions.
Appointment of new key vendors.
System migration.
Cessation of operations.

Failure to obtain approval for material changes can result in sanctions.

XXIX. Restrictions on Assignment or Transfer

Gaming licenses are generally personal to the licensee. They are not freely transferable like ordinary commercial assets. A B2B aggregator should not assign, sell, pledge, sublicense, or transfer its license or approval without PAGCOR consent.

In mergers, acquisitions, or investment rounds, gaming regulatory approval may be required before closing. Transaction documents should include regulatory conditions precedent.

XXX. Common Reasons for Delay or Denial

Applications may be delayed or denied due to:

Incomplete documents.
Unclear business model.
Unverified beneficial ownership.
Adverse background findings.
Insufficient financial capacity.
Uncertified games.
Weak cybersecurity controls.
Inadequate AML support.
Data privacy gaps.
Unclear source of funds.
Conflicting corporate documents.
Non-compliant contracts.
Unauthorized prior operations.
Association with illegal gaming sites.
Failure to pay fees.
Inconsistent tax position.
Lack of local permits.
Use of prohibited or high-risk vendors.
Misrepresentation or omission.

The most serious problems are usually lack of transparency, unauthorized operations, and unclear ownership.

XXXI. Enforcement Risks

Operating without the proper license or approval may expose the company and its officers to serious consequences.

Possible risks include:

Cease-and-desist orders.
Monetary penalties.
License denial.
Blacklisting.
Termination of operator contracts.
Contract unenforceability.
Tax assessments.
Criminal exposure under gambling laws.
AML investigation.
Data privacy enforcement.
Cybercrime investigation.
Bank account closure.
Payment processor termination.
Reputational damage.

Licensed operators may also be penalized for dealing with unlicensed or unauthorized service providers.

XXXII. Relationship With Offshore Gaming

The Philippine gaming framework has historically included different categories of online or offshore gaming activities. B2B aggregators must be careful to distinguish whether they are supporting domestic-facing gaming, offshore-facing gaming, land-based casino online extensions, e-games, sports betting, or other regulated formats.

The intended player market matters. Gaming offered to persons located in the Philippines may be treated differently from gaming offered to persons located outside the Philippines. The operator’s license category, target jurisdiction, payment flow, server location, and marketing practices all affect the analysis.

An aggregator should not assume that a license for one type of activity permits support for another. Each operator, product, and market should be reviewed separately.

XXXIII. Advertising and Marketing

A B2B aggregator usually does not market to players. However, if it promotes games, brands, jackpot products, or platform services, advertising rules may still be relevant.

Potential issues include:

Misleading claims about licensing.
Use of PAGCOR name or logo without permission.
Promotion of unauthorized games.
Marketing to prohibited persons.
Marketing in restricted jurisdictions.
Claims about guaranteed winnings.
Unapproved public-facing game demos.
Affiliate marketing arrangements.
Social media promotions.
Responsible gaming messaging.

The safest approach is to ensure that marketing materials accurately state the company’s regulatory status and do not imply broader authorization than actually granted.

XXXIV. Payment and Wallet Arrangements

B2B aggregators should be cautious when handling payment-related functions. If the aggregator touches player funds, settlement, wallet balances, deposits, withdrawals, or payment routing, additional regulatory obligations may arise.

Payment-related activity can implicate:

Operator licensing rules.
AML obligations.
Payment system regulations.
E-money rules.
Data privacy rules.
Consumer protection laws.
Tax reporting.
Fraud monitoring.
Chargeback management.
Cross-border remittance concerns.

A pure game aggregator should avoid assuming payment responsibilities unless expressly authorized and properly structured.

XXXV. Labor, Office, and Local Operations

If the aggregator will maintain a Philippine office, employ Filipino staff, or station foreign technical personnel in the Philippines, it must comply with local laws.

Relevant matters include:

Employment contracts.
Mandatory benefits.
Working hours and leave.
Occupational safety.
Registration with labor agencies.
Tax withholding on compensation.
Work permits for foreign nationals.
Visas.
Office lease compliance.
Local government permits.

Gaming-related businesses may face additional scrutiny in office location, security, staffing, and foreign worker compliance.

XXXVI. Compliance Program

A strong application should include a practical compliance program. At minimum, the applicant should consider having:

Compliance officer.
Data protection officer.
Information security officer.
AML liaison, where applicable.
Written compliance manual.
Regulatory reporting calendar.
Incident response protocol.
Vendor due diligence procedure.
Employee training program.
Internal audit procedure.
Contract approval workflow.
Game release approval process.
Change management policy.
Record retention policy.
Escalation procedure for regulator inquiries.

PAGCOR will be more comfortable with applicants that can show operational discipline rather than merely legal paperwork.

XXXVII. Practical Pre-Application Checklist

Before applying, a B2B aggregator should be able to answer the following questions:

What exact services will the company provide?
Will it provide games, platform technology, wallet tools, reporting tools, or all of these?
Will it directly interact with players?
Will it receive player funds?
Will it share in gaming revenue?
Who are its target operators?
Are those operators licensed by PAGCOR?
Are all games certified?
Where are the servers located?
Who owns the software?
Who owns the game content?
Who are the beneficial owners?
What is the source of capital?
What Philippine entity or registration will be used?
What taxes will apply?
What personal data will be processed?
What AML support will be provided?
What reports can the system generate?
What cybersecurity controls exist?
What happens during downtime or cyber incidents?
What approvals are needed before launch?
What continuing obligations will apply?

Clear answers to these questions usually make the application process smoother.

XXXVIII. Suggested Document Package

A serious applicant should prepare a comprehensive package consisting of:

Legal memorandum on proposed structure.
Corporate documents.
Shareholder and beneficial ownership chart.
Director and officer profiles.
Financial statements.
Proof of capitalization.
Tax registration documents.
Business plan.
Product description.
Technical architecture.
Game list.
Certification reports.
Sample operator agreement.
Data privacy documents.
AML support policy.
Cybersecurity policy.
Disaster recovery plan.
Compliance manual.
Fit-and-proper declarations.
Regulatory undertakings.
Fee payment documents.

The application should be internally consistent. PAGCOR reviewers may compare the business plan, contracts, technical architecture, revenue model, and corporate documents against each other.

XXXIX. Legal Drafting Points for Operator Agreements

A B2B aggregator should ensure that operator agreements contain strong regulatory clauses. Useful provisions include:

License dependency clause The agreement should state that services are subject to PAGCOR approval and applicable gaming laws.
Operator responsibility clause The operator should remain responsible for player-facing obligations unless the aggregator is expressly authorized to perform them.
Regulatory cooperation clause Both parties should cooperate with PAGCOR inquiries, audits, and reporting.
Approved games clause Only approved and certified games may be deployed.
Change control clause System or game changes should be subject to approval where required.
Suspension clause Services may be suspended if continued operation would breach law or PAGCOR rules.
Data processing clause The agreement should define controller and processor roles.
Audit log clause The aggregator should maintain records sufficient for regulatory review.
Incident notice clause Cybersecurity, data breach, game malfunction, and reporting errors should be promptly reported.
Termination for regulatory breach clause The agreement should terminate or suspend upon license revocation, regulatory prohibition, or illegal use.

XL. Common Misconceptions

Misconception 1: “We are only a software company, so we do not need PAGCOR approval.”

Software used to conduct gaming may still require regulatory approval. The label “software company” is not decisive.

Misconception 2: “We do not accept bets, so we are not regulated.”

B2B providers may still be regulated if they supply critical gaming systems or content.

Misconception 3: “The operator’s license covers us automatically.”

An operator’s license may not automatically authorize all third-party providers. PAGCOR may require separate accreditation or approval.

Misconception 4: “Foreign certification is enough.”

Foreign lab certification helps, but PAGCOR may still require local acceptance, additional review, or jurisdiction-specific approval.

Misconception 5: “A signed contract with a licensed operator is enough.”

A private contract does not replace regulatory approval.

Misconception 6: “Revenue share is just a commercial term.”

Revenue share may affect regulatory classification, tax treatment, and risk allocation.

Misconception 7: “Data privacy is only the operator’s problem.”

Aggregators that process player data have their own data protection obligations.

XLI. Risk-Based Structuring Advice

A conservative structure usually includes:

A clearly identified licensed or accredited entity.
Transparent beneficial ownership.
Written PAGCOR approval before launch.
Certified games.
Clear operator contracts.
No direct player fund handling unless authorized.
Strong data privacy and cybersecurity controls.
Accurate tax treatment.
No unauthorized marketing.
Prompt reporting of material changes.

Where the business model is complex, the company may need separate approvals for different functions: game aggregation, platform supply, technical services, payment-related support, and content distribution.

XLII. Due Diligence by Operators

Licensed operators dealing with a B2B aggregator should conduct their own due diligence. They should verify:

PAGCOR license or approval status.
Scope of authorized activities.
Corporate existence.
Beneficial ownership.
Game certifications.
Cybersecurity posture.
Data privacy compliance.
Financial stability.
Sanctions and adverse media.
Contractual authority to distribute games.
Tax documentation.
Support and incident response capability.

Operators may face regulatory liability if they onboard unauthorized or unreliable providers.

XLIII. Renewal and Post-License Management

A B2B aggregator license will usually be subject to renewal or periodic review. The licensee should maintain a renewal calendar and monitor compliance continuously.

Before renewal, the licensee should confirm:

All fees are paid.
Reports are complete.
Corporate documents are updated.
Tax filings are current.
Game certifications remain valid.
Material changes have been reported.
Contracts remain compliant.
Incidents have been properly documented.
Audit findings have been resolved.
Business permits remain valid.

Poor post-license management can jeopardize renewal even if the initial application was approved.

XLIV. Regulatory Strategy

The best regulatory strategy is to approach the application as a combined legal, technical, financial, and compliance project.

A useful strategy includes:

Early classification of the business model.
Pre-application gap assessment.
Corporate cleanup before filing.
Beneficial ownership verification.
Technical certification planning.
Contract review.
Tax structuring.
Data privacy mapping.
Cybersecurity testing.
Preparation for regulator questions.

Applicants should avoid launching, marketing, or signing broad commercial commitments before regulatory status is clear.

XLV. Conclusion

A PAGCOR B2B Online Gaming Aggregator License application is not a simple administrative filing. It is a comprehensive regulatory process that examines the applicant’s corporate structure, beneficial ownership, financial capacity, technical systems, game integrity, cybersecurity controls, data privacy compliance, contractual arrangements, and ongoing ability to support lawful gaming operations.

In the Philippine context, the central legal principle is that gaming-related activity must be expressly authorized. A B2B aggregator may not be player-facing, but if it supplies the technology, content, systems, or infrastructure that enables online gaming, it may fall within PAGCOR’s regulatory perimeter.

The strongest applicants are transparent, well-capitalized, technically prepared, contractually disciplined, and compliance-oriented. They understand that the license is not merely permission to do business; it is a continuing regulatory relationship with PAGCOR and with licensed operators.

For any company seeking to enter the Philippine regulated online gaming ecosystem as a B2B aggregator, the prudent approach is to secure the correct PAGCOR authorization before operations begin, structure the business carefully, maintain robust compliance controls, and treat regulatory obligations as part of the company’s core operations rather than an afterthought.