Payments
Mainland risk, screened at source.
How Mainland risk is checked
BeforeSelf-declared
With Fill EasyScreened at source
Merchant KYB and user KYC through one API.
Every market has its own registry and its own ID scheme. Fill Easy returns both, from source, in one call.
Request
POST /v1/orders
{
"search": "company_search",
"company_name": "Lion Gate Payments Pte. Ltd.",
"jurisdiction": "SG",
"reference": "MER-55120"
}Response
200 OK
{
"status": "completed",
"source": "Company registry, Singapore",
"retrieved_at": "2026-09-25T15:31:40+08:00",
"reference": "MER-55120",
"report_pdf": "https://…/MER-55120.pdf"
}1 · The problem
Onboarding at volume, under a rising bar.
Volume
90.38m
stored value facility accounts in use in Hong Kong in Q2 2026
HK$264.7bn in transactions over the same quarter.
Licensing
2 of 36
stablecoin issuer licence applications granted
Granted by the HKMA under the Stablecoins Ordinance.
Illicit flows
US$154bn
received by illicit crypto addresses worldwide in 2025
Knowing who owns a counterparty is the first control.
2 · Where the time goes
The same case, today and with Fill Easy.
Pick your desk. The worked example below follows it.
The case
A Singapore merchant signs up for acquiring
Today
A registry check per market- Company documents uploaded by the merchantA certificate and shareholder list, as supplied.
- Each registry checked on its own portalA different site, format and language for every market.
- Owners taken from a declarationBeneficial owners as the merchant lists them.
- The gapEvery new market means another registry to connect to, or to check by hand.
With Fill Easy
1 API call, any market- One call to the APIThe registry record, in any of 60+ jurisdictions.
- Owners from the registryThe shareholder and UBO structure behind the merchant.
- Structured JSON with a PDFOn the merchant record, with source and retrieval time.
- Verified at sourceCorpVerify
3 · What it saves
What each desk saves in a year.
Five minutes instead of hours, across a year on that desk.
The example
- Merchants onboarded a month
- 300
- Analyst cost per hour (HK$)
- 350
Analyst time per check
Working days to get the registry records
Saved per year
HK$2,415,000
Analyst cost freed
3.5 analysts' full-time work
6,900
Analyst hours freed
7
Working days sooner
25,163
Customer-days sooner
Illustrative figures, not client data.
4 · Proof
Results at Evertop Rich.
Evertop Rich screens its Mainland customers for risk with Fill Easy, before it takes them on.
5 · How to start
Built into onboarding, with email for the exceptions.
The API for the flow; the mailbox for cases that need a person to look.
Mailbox Available
For risk and operations teams
- Email the order to agent@fill-easy.com
- The agent confirms what it will run
- Reports land in the same thread
API Available
For onboarding flows, merchant portals and risk engines
- Your onboarding flow calls the API
- Consent and retrieval run at source
- Structured JSON back, with a PDF
CRM Coming soonDelivery into the CRM your team uses is not available yet. Tell us which one you use.
CRM statusQuestions payment and virtual asset firms ask
Not covered here? Ask our team
Can we run merchant KYB and user KYC through one API?
Yes. Company registry searches, UBO structures and Mainland bank account verification for merchants, and government-confirmed identity for users, all come through one REST API as structured JSON with a PDF.
Which markets can we search?
Hong Kong, Mainland China, the BVI and the Cayman Islands, and registry search across 60+ jurisdictions. The search catalogue lists every search type.
Can we confirm a Mainland merchant's settlement account?
Yes. Corporate bank account verification confirms that the account belongs to the company, through the API, alongside the company search and KYB report.
Which identity schemes can users verify with?
iAM Smart in Hong Kong, China eID in Mainland China, Singpass in Singapore and UAE Pass in the United Arab Emirates, each with the user's consent.
Do you trace a merchant's beneficial owners?
Yes. The shareholder and UBO structure comes from the registry, traced layer by layer to the people behind the merchant, instead of from the merchant's own declaration.
Can we test the API before going live?
Yes. Requests with dryRun set return sample results without calling a source or being billed, while you build.
Does every result come back in the same format?
Yes. JSON and PDF in one shape, whichever registry answered, with the source and retrieval time on the merchant record.