Read the conditionsRequest a brief

Request a brief
Read the conditionsRequest a brief
APIX (Application Programming Interface Exchange) a global Fintech Platform is officially launched by Narendra Modi, Prime Minister of India and Tharman Shanmugaratnam, Deputy Prime Minister of Singapore at the Singapore FinTech Festival on November 14, 2018, in the presence of (From Left) Vivek Pathak, Regional Director - East Asia and Pacific, IFC (World Bank Group), Paul CG Gwee, Secretary-General of ASEAN Bankers Association (ABA) and (Far Right) Sopnendu Mohanty, Chief Fintech Officer, Monetary Authority of Singapore (MAS). APIX is an initiative of the ASEAN Financial Innovation Network (AFIN) , a not-for-profit entity that was jointly formed by the Monetary Authority of Singapore (MAS), the World Bank Group’s International Finance Corporation (IFC) and the ASEAN Bankers Association. It is a global, open-architecture platform that supports financial innovation and inclusion in ASEAN and around the world.
Documentary context: APIX (Application Programming Interface Exchange) a global Fintech Platform is officially launched by Narendra Modi, Prime Minister of India and Tharman Shanmugaratnam, Deputy Prime Minister of Singapore at the Singapore FinTech Festival on November 14, 2018, in the presence of (From Left) Vivek Pathak, Regional Director - East Asia and Pacific, IFC (World Bank Group), Paul CG Gwee, Secretary-General of ASEAN Bankers Association (ABA) and (Far Right) Sopnendu Mohanty, Chief Fintech Officer, Monetary Authority of Singapore (MAS). APIX is an initiative of the ASEAN Financial Innovation Network (AFIN) , a not-for-profit entity that was jointly formed by the Monetary Authority of Singapore (MAS), the World Bank Group’s International Finance Corporation (IFC) and the ASEAN Bankers Association. It is a global, open-architecture platform that supports financial innovation and inclusion in ASEAN and around the world.Photo: Prime Minister's OfficeLicense: GODL-IndiaView original source Documentary context only. No Panasia participation, client relationship, affiliation, endorsement, result, or guarantee is implied. Changes: resized without upscaling and re-encoded to AVIF/WebP; no content was added or removed.

SINGAPORE / DPT LICENSING · ISSUE 04

Singapore DPT counterparties — licence is the first check

A directory result establishes a public starting point, not end-to-end permission. This paper maps the institution, licensed activity, client and transaction scope, customer-asset controls, technology risk, and operating evidence that a Singapore DPT mandate should verify.

9 min readVersion 1.0
James L.Panasia leadership

Accountable reviewPanasia Research DeskEditorial review and source audit

Research question

What must an operating team verify beyond an MAS directory match before relying on a Singapore DPT counterparty?

Core conclusion · Panasia analyst inference

Counterparty approval should join four records: current licence status, exact activity and conditions, the mandate's customer and transaction scope, and tested customer-asset and technology controls.

02 / VERIFICATION LANES

Four checks before a counterparty becomes usable.

Institution record

Directory current

Observed signal

The MAS directory offers a public activity-filtered list of institutions associated with Digital Payment Token Service and links to institution records.

S01

Decision implication · Panasia analyst inference

A dated directory capture is evidence of public status at retrieval, not a warranty of future status or mandate acceptance.

Recommended next action · Panasia analysis

Record legal name, MAS reference, licence type, listed DPT activity, status, conditions shown, retrieval date, and the person confirming mandate fit.

Evidence confidenceHigh

Service and transaction scope

Match exact activity

Observed signal

The Payment Services Act sets the licensing perimeter for payment services, including DPT service, while licence type and conditions govern the institution's permitted operations.

S02 S03

Decision implication · Panasia analyst inference

A DPT label should not be stretched across a different service, customer, asset, geography, transfer, custody, solicitation, or settlement model.

Recommended next action · Panasia analysis

Describe the end-to-end flow in verbs, parties, assets, wallets, jurisdictions, customers, funding sources, settlement steps, and exceptions; obtain a written scope match.

Evidence confidenceHigh

Customer assets

Safeguards evidenced

Observed signal

The Payment Services Regulations include customer-asset safeguarding and record requirements for DPT service providers.

S03

Decision implication · Panasia analyst inference

The operating team needs evidence of how customer money and tokens are identified, held, segregated or safeguarded, reconciled, recovered, and returned under the proposed model.

Recommended next action · Panasia analysis

Review custody and wallet architecture, safeguarding arrangement, books and records, reconciliation, access authority, withdrawal controls, insolvency treatment, and exception processes.

Evidence confidenceHigh

Technology and operations

Resilience tested

Observed signal

MAS technology-risk notice PSN05 applies technology controls and incident obligations to relevant payment service licensees providing DPT services.

S04

Decision implication · Panasia analyst inference

Licence status without evidence for critical systems, availability, access, monitoring, incident response, and recovery leaves a material execution dependency open.

Recommended next action · Panasia analysis

Request system inventory, criticality, uptime and recovery objectives, privileged-access controls, monitoring, incident notification process, recent testing, and accountable operations contacts.

Evidence confidenceHigh

01 / KEY FINDINGS

Three findings to carry into the next decision.

A finding enters this brief only when it changes the operating question, the evidence required, or what a team should do next.

NODE 01 · The directory answers who, not the entire mandate.
The MAS Financial Institutions Directory provides a current public check for institutions listed with Digital Payment Token Service activity, but it does not evidence support for every service or flow.S01 S02
NODE 02 · Activity scope must match the actual verbs.
A proposal should identify who deals, transfers, safeguards, markets, advises, settles, or operates the technology and connect each verb to the applicable licence, condition, exemption, or control owner.S02 S03
NODE 03 · Operational resilience is part of counterparty fit.
Customer-asset and technology-risk requirements mean that wallet design, records, access control, incident response, and recovery evidence belong in counterparty review, not only in post-contract diligence.S03 S04

03 / EVIDENCE STANDARD

How the monitor is built.

Decision protocol

  1. 01

    Capture the current MAS institution record and listed Digital Payment Token Service activity.

  2. 02

    Translate the mandate into actors, verbs, assets, customers, jurisdictions, wallets, funding, settlement, and exception flows.

  3. 03

    Match each activity to licence scope, conditions, exemptions, safeguarding, AML, conduct, and technology-control owners.

  4. 04

    Collect institution-supplied evidence without treating marketing statements or a directory entry as proof of the full control environment.

  5. 05

    Set re-verification triggers for status, ownership, service, customer, geography, wallet, custody, incident, or regulatory change.

Confidence by lane

Public institution and legal baselineHigh
Control expectationsHigh
Specific mandate and counterparty fitOpen

05 / LIMITATIONS

What this brief does not establish.

  • The displayed MAS directory result count can change after the evidence cut-off and should be rechecked before use.
  • This paper does not cover every licensing condition, exemption, AML, conduct, consumer, advertising, sanctions, tax, data, or cross-border obligation.
  • Public status does not validate private control evidence or establish that MAS has approved a particular client arrangement.

Unresolved questions

  1. Does the institution's current record and licence condition cover every activity in the proposed end-to-end flow?
  2. What customer-asset, wallet, reconciliation, access, incident, recovery, and outsourcing evidence is available for review?
  3. Which changes require reapproval, regulator notification, client disclosure, migration, pause, or termination?
Research boundary

Research is general market intelligence, not legal, investment, licensing, safeguarding, technology, AML, or regulatory advice. Directory status, licence conditions, exemptions, customer type, transaction flow, asset handling, cross-border scope, and current requirements must be confirmed with qualified Singapore counsel, the counterparty, and MAS at the time of action.

Revision record

v1.0Initial publication and official-source counterparty map.

04 / PRIMARY SOURCES

Evidence ledger.

Current official publications and directories used for this issue. Dates distinguish publication from retrieval.

  1. S01Monetary Authority of SingaporeFinancial Institutions Directory — Digital Payment Token ServiceRetrieved 2026-08-13
  2. S02Singapore Statutes OnlinePayment Services Act 2019 — current versionRetrieved 2026-08-13
  3. S03Singapore Statutes OnlinePayment Services Regulations — current version and DPT customer-asset provisionsRetrieved 2026-08-13
  4. S04Monetary Authority of SingaporePSN05 Notice on Technology Risk ManagementPublished 2024-02-06 · Retrieved 2026-08-13
SGQR NETS payment sign at Liho Tea in Queensway Shopping Centre, Singapore
Documentary context: SGQR NETS payment sign at Liho Tea in Queensway Shopping Centre, SingaporePhoto: Chainwit.License: CC BY 4.0View original source Documentary context only. No Panasia participation, client relationship, affiliation, endorsement, result, or guarantee is implied. Changes: resized without upscaling and re-encoded to AVIF/WebP; no content was added or removed.

NEXT DECISION