regulation

Labuan FSA PSO License Explained: Why It Matters for ASEAN Cross-Border Payments

A practical guide to the Labuan Financial Services Authority Payment System Operator license — what it permits, who needs it, and how it compares to BNM, MAS, and offshore alternatives.

April 28, 20266 min readBy Kaadxpay Compliance

If you're a fintech operator looking at ASEAN cross-border payments in 2026, you've almost certainly encountered the Labuan FSA Payment System Operator (PSO) license. It powers a growing share of the regional payment-orchestration market, yet remains poorly understood outside Malaysia.

This piece is the explainer we wished existed when we sat for our own PSO submission. We'll cover what the license actually permits, how it compares to mainland Malaysian (BNM) and Singaporean (MAS) regimes, and where it does — and doesn't — fit in a real cross-border payment stack.

Disclosure

Kaadxpay holds Labuan FSA PSO license #LFSA.700-14/LFA/PS/25/2026 (3) issued 16 January 2026. Capital paid-up: USD 150,000. We're writing this as practitioners, not as legal advisors — speak to qualified counsel before any licensing decision.

What is the Labuan FSA?

The Labuan Financial Services Authority is the statutory body responsible for the Labuan International Business and Financial Centre (Labuan IBFC), a special economic zone established under Malaysia's Labuan Companies Act 1990. It's a mid-shore (not offshore) jurisdiction — fully on Malaysia's regulatory map, with bilateral tax treaties active in 90+ countries.

Labuan FSA regulates everything from captive insurance to digital banking. The piece relevant for payments people is the Labuan Financial Services and Securities Act 2010 (LFSSA), specifically the Money-Broking and Payment System Operator provisions.

What the PSO license actually authorizes

The PSO license authorizes a Labuan-incorporated entity to:

  • Operate a payment system (the legal definition is broad — any system that handles transfer, clearing, or settlement of payment obligations)
  • Issue or acquire payment instruments including cards, e-money, and tokenized stored value
  • Provide remittance services including cross-border B2B and B2C transfers
  • Offer foreign exchange settlement as part of the payment flow

Critically, the PSO is a wholesale-style license: you can serve businesses (other licensed financial institutions, merchants, and corporates) without separately registering as a money services business in each ASEAN jurisdiction, provided you transact through licensed local partners.

Capital and substance requirements

Labuan FSA imposes meaningful but not crushing requirements:

Paid-up capital
USD 150K
Minimum for PSO; higher for full payment-system operator status
Local employees
≥2
Minimum substance — most active PSOs run 5-15 in Labuan
Local office
Required
Physical presence in Labuan, not just registered address

Compare this to Singapore's MAS Major Payment Institution (MPI) license, which imposes SGD 1M paid-up capital plus substantially higher operating costs, or BNM's eMoney issuer regime, which has stricter consumer-facing obligations.

How it compares to neighbouring regimes

DimensionLabuan FSA PSOBNM (Malaysia mainland)MAS (Singapore)
Paid-up capitalUSD 150KMYR 5M for eMoney issuerSGD 1M for MPI
Tax treaty access90+ countriesYes (MY treaties)Yes (SG treaties)
Regulatory tonePragmatic, mid-shoreConservative, retail-focusedSophisticated, fintech-friendly
Time to license6–12 months typical12–18 months9–15 months
Permitted FXYes, with restrictionsYes, BNM-supervisedYes, MAS-supervised
Cross-border by defaultYesDomestic-firstYes, but stricter scope

The honest comparison: Labuan FSA is to ASEAN payments what Hong Kong is to China-facing finance — a mid-shore optimization that lets you operate cross-border without taking on the full surveillance burden of an onshore retail license.

Where Labuan PSO does and doesn't fit

It fits when you are:

  • A B2B cross-border payment platform serving merchants in multiple ASEAN markets
  • A remittance provider whose corridors include Malaysia plus 2-3 other jurisdictions
  • An FX settlement layer behind a regulated reseller
  • A payment orchestrator routing through licensed local partners

It does not fit when you are:

  • Issuing consumer e-wallets directly to Malaysian retail users (that's BNM territory)
  • Operating a domestic Singapore card scheme (that's MAS territory)
  • Custodying client crypto with significant Malaysian retail exposure (Securities Commission Malaysia plus BNM, complex)
The substance test is real

Labuan has tightened its economic substance requirements considerably since the 2018 EU code-of-conduct review. Shell companies with a registered address but no actual local operations face withholding-tax penalties (currently 24%) on their domestic-source income. Plan to staff a real Labuan office, not just rent a mailbox.

What it costs to operate

Beyond the USD 150K paid-up capital, expect annual recurring costs of:

  • License renewal: ~USD 5K
  • Local director/CO/AML officer: USD 80–150K depending on outsourcing model
  • Office + utilities: USD 25–50K
  • Audit + secretarial: USD 15–30K

Total annual run-rate for a lean operation: USD 150–250K plus headcount. This is roughly half the equivalent in Singapore and a third of Hong Kong.

How we use ours

For Kaadxpay specifically, the PSO license is the legal foundation that allows us to:

  1. Hold balances on behalf of merchants pending settlement (escrow + safeguarding)
  2. Execute cross-border FX as part of the payment flow
  3. Operate as the contracting entity for our channel partners across Malaysia, Singapore, Indonesia, and the Philippines
  4. Issue branded virtual accounts for B2B remittance customers

Without a license of this class, you'd need to either (a) operate as a non-regulated technology vendor (which prevents you from holding funds), or (b) stack 4-5 jurisdiction-specific licenses (which most early-stage fintechs cannot afford to maintain).

Practical advice if you're considering this path

  1. Engage Labuan-resident counsel early. Local firms know the FSA's current preferences in ways that international firms don't.
  2. Build the substance plan before applying. FSA increasingly evaluates "intention to operate" alongside paper compliance.
  3. Don't confuse PSO with money broker. They're different licenses with different scope. Map your business to the right one.
  4. Plan for AML capability from day one. Even a "B2B-only" PSO will face FATF-aligned AML obligations.
  5. Keep your tax position clean. The 3% Labuan trading tax is attractive but only available if you maintain the substance test.

The Labuan FSA PSO license is one of the more pragmatic fintech-friendly regimes in Asia. It's not the right fit for every business, but for cross-border payment orchestrators serving ASEAN, it's increasingly the default starting point.

If you're working on something in this space and want to compare notes, we're happy to chat — drop us a line via the contact page.

Author
Kaadxpay Compliance
Regulation & AML

Compliance, licensing, and AML perspectives from the team responsible for keeping Kaadxpay aligned with Labuan FSA, BNM, MAS and the broader ASEAN regulatory landscape.

Related Reading

ASEAN Payment Corridors 2026: State of the Market

ASEAN Payment Corridors 2026: State of the Market

A corridor-by-corridor breakdown of how ASEAN cross-border payments actually flow today — from MY-SG QR linkage to the IDR-PHP backwater. What's working, what's broken, and what's worth integrating.

Apr 22, 20267 min read
Stripe vs Airwallex vs Kaadxpay: ASEAN Payments Comparison (2026)

Stripe vs Airwallex vs Kaadxpay: ASEAN Payments Comparison (2026)

An honest, opinionated comparison of three cross-border payment platforms serving ASEAN merchants. Pricing, coverage, settlement speed, FX margin, and where each one actually shines.

Mar 25, 20268 min read
Idempotency for Payment APIs: The Engineering Playbook

Idempotency for Payment APIs: The Engineering Playbook

How to design idempotency keys that survive retries, network partitions, and creative client behavior. The patterns we use in production at Kaadxpay, written for engineers who actually have to debug double-charge tickets.

Apr 15, 20268 min read

Subscribe to Kaadxpay Insights

Monthly insights on cross-border payment corridors, regulation, and engineering practice.