Monetary Authority of Singapore
Supervisory authority for Singapore in the KeyBS Pay corridor dataset. This reference profile summarises the markets overseen and the documentation businesses typically need when paying into or out of them.
Markets supervised
Singapore
Currencies
SGD
Market type
Global delivery market(s)
Market requirements
- ·Beneficiary name and account details
- ·Commercial invoice referencing the payment
Singapore is Asia’s FX and commodity-finance hub; many regional trade invoices settle against Singapore entities in USD.
Corridors under this supervision
Compliance fundamentals
Other global regulators
Frequently asked questions
Which markets does Monetary Authority of Singapore supervise?
In the corridor dataset, Monetary Authority of Singapore is the supervisory authority for Singapore (SGD).
What documents does the Singapore market typically require?
Beneficiary name and account details; Commercial invoice referencing the payment. Requirements are route-dependent and confirmed during onboarding and per payment.
How does Monetary Authority of Singapore affect FX for business payments?
Singapore is Asia’s FX and commodity-finance hub; many regional trade invoices settle against Singapore entities in USD.
Explore the payments knowledge graph
Countries · 42
Market profiles: rails, regulators, documents and corridors
Currencies · 22
Currency profiles with every business FX pair
Payment Rails · 63
Domestic and cross-border rails, by settlement family
Providers · 37
Objective capability profiles for payment providers
Settlement Methods · 7
The seven settlement families behind every route
Central Banks & Regulators · 41
Who supervises payments in each market, and what they require
From reference data to an executable quote
This page is reference metadata — availability is route-dependent. A KeyBS Pay quote shows the committed rate, disclosed fee and exact receive amount before you approve anything.
Request a QuoteReference metadata summarising publicly known supervisory structures — not legal or compliance advice. Requirements are route-dependent and confirmed during onboarding and per payment. Also available via the free Knowledge API.