• CBUAE — RPSCS & Payment Token Services

RPSCS & PTS — Two Frameworks, One Regulator

How the Retail Payment Services and Card Schemes Regulation (RPSCS) and the Payment Token Services (PTS) framework interact — and what it means for stablecoin issuers, payment platforms, and fintech operators in the UAE.

Book a Regulatory Structuring Call
Get RPSCS–PTS Activity Matrix
Key Interactions
 

🔄

PTS triggers Category I under RPSCS

💰

Capital threshold alignment (AED 10m)

⚙️

Safeguarding & custody overlap

🗺️

AML/CFT convergence

🏛️

Licensing sequencing impact

⚠️

They are not separate silos — structuring correctly is critical

We analyse licence perimeter triggers, capital exposure, prudential overlap, token governance, safeguarding structures, and supervisory alignment under the Central Bank of the UAE.

01 / The Big Picture

One Regulator, Two Interconnected Frameworks

Both RPSCS and PTS are regulated by the Central Bank of the UAE. They are not separate silos. Understanding how these two regimes interact is critical for structuring, capital planning, and licensing strategy.

RPSCS — The Foundation

Retail Payment Services & Card Schemes

The overarching retail payments framework governing entities providing payment services in the UAE (outside DIFC and ADGM).

RPSCS Covers

  • Payment Account & Instrument Issuance
  • Merchant Acquiring & Aggregation
  • Domestic & Cross-Border Fund Transfers
  • Payment Initiation & Account Information
  • Card Scheme Operations

RPSCS Establishes

  • Licence Categories (I–IV)
  • Initial capital thresholds
  • Governance & AML/CFT requirements
  • Safeguarding obligations

PTS — The Token Layer

Payment Token Services (Stablecoins)

The specialised framework regulating activities involving Payment Tokens — fiat-referenced stablecoins used for payment purposes.

PTS Governs

  • Issuing & offering Payment Tokens
  • Buying and selling Payment Tokens
  • Facilitating token exchange
  • Merchant & P2P token payments
  • Custody of Payment Tokens

PTS Introduces

  • Token-specific capital thresholds
  • White Paper approval requirements
  • Reserve governance & custody standards
  • Enhanced transaction monitoring

ℹ️

RPSCS is the umbrella. PTS sits within the retail payments ecosystem. PTS is prudentially sensitive due to systemic and monetary stability considerations.

02 / How They Interact

How RPSCS and PTS Interact

Five critical interaction points that determine your licensing strategy, capital exposure, and supervisory intensity.

01

Payment Token Services Trigger Category I Under RPSCS

If your business includes Payment Token Services, you automatically fall within Category I licensing — the highest retail payments tier. This carries AED 1.5m–3m initial capital (volume dependent), heightened supervisory intensity, and enhanced reporting expectations.

🚫

Payment Token Services cannot be structured under Category II or III.

02

Capital Threshold Alignment

Both frameworks use a transaction-based threshold (AED 10m monthly average), escalation rules if thresholds are exceeded, and ongoing capital maintenance obligations. Scaling stablecoin activity can trigger capital tier escalation, increased supervision, and reporting obligations.

⚠️

Capital modelling must account for both regimes simultaneously.

03

Safeguarding & Custody Overlap

Where a firm issues Payment Tokens and also holds client funds, RPSCS safeguarding rules and PTS custody standards operate together — creating dual exposure in segregation, reconciliation, operational resilience, and technology governance.

⚠️

Improper structuring can create compounded regulatory risk.

04

AML/CFT Convergence

Both RPSCS and PTS require enterprise-wide AML frameworks, transaction monitoring, sanctions screening, and STR. However, Payment Token activity may additionally require blockchain analytics capability, Travel Rule readiness, and enhanced cross-border risk controls.

⚠️

Stablecoin models face heightened AML scrutiny.

05

Licensing Sequencing Matters

Founders often underestimate how introducing token functionality escalates licence category and capital. Common structuring pathways are shown below.

Business Model

Regulatory Path

Domestic PSP (no tokens) → Token Issuance

→

Category III → Category I

Cross-border fintech → Token payments

→

Category II → Category I

Stablecoin issuer from Day 1

→

Direct Category I

03 / Strategic Impact

Strategic Structuring Implications

Introducing Payment Token functionality into a payment platform is not merely a product expansion. It is a regulatory reclassification event.

Introducing Token Functionality Changes

Licence Category

Capital Requirement

Governance Expectations

Technology Scrutiny

Supervisory Intensity

⚠️

Stablecoin issuance is not a product expansion — it is a regulatory reclassification event. Every dimension of your regulatory posture changes.

04 / Dual Framework Exposure

When Both Frameworks Apply Simultaneously

Dual-framework exposure occurs when a PSP integrates stablecoin settlement, an acquirer accepts Payment Tokens, a wallet offers token custody, or a platform facilitates fiat-to-token conversion.

CBUAE Will Assess

💰

Capital Sustainability

🏦

Reserve Backing Integrity

🔐

Custody Controls

💻

Technology Resilience

🌐

Cross-Border AML

🚫

Regulatory perimeter analysis becomes essential whenever both RPSCS and PTS frameworks apply simultaneously to a business model.

05 / Common Mistakes

Common Structuring Mistakes

Where Founders Get It Wrong

  • Assuming stablecoin issuance is separate from retail payments licensing
  • Applying for Category II while intending token services
  • Underestimating capital escalation triggers
  • Overlooking custody governance requirements
  • Failing to model transaction growth impact on capital obligations across both frameworks

06 / Practical Guidance

Practical Founder Guidance

Before launching Payment Token functionality, complete these five steps. Stablecoin integration requires proactive regulatory planning.

01

Confirm licence category implications

02

Model capital under AED 10m threshold

03

Assess custody exposure

04

Align token governance with safeguarding

05

Stress-test transaction growth scenarios

✔

Structuring correctly at the outset avoids capital shocks, supervisory friction, and regulatory delays.

What We Deliver

How We Support RPSCS & PTS Structuring

🔬

Regulatory Perimeter Analysis

RPSCS & PTS trigger mapping

🎯

Licence Category Determination

Category I–IV classification

📊

Capital Escalation Modelling

Dual-regime threshold planning

📜

Token Governance Design

White Paper & reserve frameworks

🔐

Custody & Safeguarding

Dual-exposure architecture review

⚖️

AML Enhancement

Blockchain analytics & Travel Rule

🤝

Regulator Engagement

Pre-application positioning

📁

Full CBUAE Application

End-to-end file management

Final Takeaway

RPSCS + PTS = The Complete Prudential Framework

Together, RPSCS and PTS Govern:

  • Fiat payments
  • Stablecoin issuance
  • Token-based settlement
  • Custody and safeguarding
  • Cross-border digital value transfer

FAQs

Frequently Asked Questions

Is PTS separate from RPSCS?

No. Payment Token Services operate within the retail payments regulatory ecosystem and trigger Category I under RPSCS. They are governed by the same regulator (CBUAE) and interact at multiple levels.

Can we add stablecoin functionality later?

Yes, but it may require licence variation and capital escalation. Introducing token functionality is a regulatory reclassification event that changes your licence category, capital, governance, and supervisory intensity.

Does token issuance automatically increase capital?

Yes. It places you within Category I and subjects you to higher prudential oversight. Capital ranges from AED 1.5m to AED 3m depending on monthly transaction volumes.

Can we operate tokens under Category II?

No. Payment Token Services require Category I licensing. They cannot be structured under Category II or III under the RPSCS framework.

Get Started

Structure Your RPSCS & PTS Position Correctly

Structuring correctly at the outset avoids capital shocks, supervisory friction, and regulatory delays. We analyse your licence perimeter, model capital across both frameworks, and manage the full CBUAE application.

Book an RPSCS Strategy Call