Solutions for payment providers
AML Screening for Crypto Payment Providers
A payment provider sits between a payer it has never met and a merchant whose licence depends on what it accepts. AMLOfficer gives that position a screening layer: incoming addresses checked through four AML data providers, merchant wallets kept under monitoring, and the whole portfolio visible to one compliance team instead of scattered across the services it runs.
Open Business AccountBusiness terms depend on your volumes and are shown in your account after registration.
You carry risk that was created somewhere else
An exchange screens its own users. A payment provider screens strangers on behalf of someone else's business. The payer is a customer of your merchant, chosen by your merchant, paying into a flow you built — and if those funds carry exposure, it lands on your side of the settlement first. That is the structural difference, and it changes what compliance tooling has to do.
It also multiplies. One merchant is a book of addresses; fifty merchants are fifty books, each with its own risk profile and its own settlement schedule. The hardest part of the job is not assessing one address well — it is keeping oversight across every merchant at once, which is exactly where scattered data across clients and services turns into missed anomalies.
The compliance work a provider actually does
Screening an incoming payment
The address a payment arrives from is read before the payment is treated as good funds. What comes back is a picture of what that money has been close to — enough to credit it, hold it, or put it in front of a person.
Releasing a settlement
Paying a merchant out is a decision about a destination address, and it is the moment your own exposure is fixed. Screening the payout address before it is signed keeps that decision documented rather than assumed.
Onboarding and reviewing a merchant
A merchant's own wallets say more about the business than its application form does. Screening them at onboarding, and again when the relationship changes, turns periodic review into something with evidence behind it.
Watching the portfolio over time
Merchant wallets can be added manually or put under automated real-time monitoring, with the depth you choose: deposits only, withdrawals only, or full history. A merchant whose exposure changes after onboarding is the case this is built to catch.
Checks that live inside your own product
For a provider, a compliance tool that requires a separate login is a tool that will be used selectively. AMLOfficer is designed to be embedded instead: Fast API puts reports into a dashboard your team works in together, and Pro API feeds AML data straight into your own systems in real time, so the check runs where the payment is processed.
Commercial terms follow the same logic: they are agreed with the team around the integration you actually run, rather than picked from a published tier.
Four providers, because one dataset is not the whole picture
AMLOfficer aggregates four AML providers, including BitOK, Global Ledger and Beosin. The point of aggregation is disagreement: providers draw on different datasets, and an address one of them calls clean is regularly flagged by another.
A provider feels that gap sooner than most, because the same address can pass through several merchants in a week. Reading it through several sources at once means a merchant is not declined on one vendor's opinion, and not accepted on one vendor's silence.
One team, many merchants
Oversight across a portfolio is a people problem before it is a data problem. Business accounts support role-based access and shared investigations, so account managers, the compliance officer and whoever is on duty can work on the same merchant case with different permissions and a shared history.
- Roles per person
Invite the people who need access and give each of them the level of access the job requires.
- Alerts in Telegram
Wallet reports and real-time alerts reach a Telegram group, which for most providers is where the duty channel already lives.
- Records that hold up
Reports stay with the address, so a question from a partner bank or a merchant months later has an answer.
AML for payment providers: common questions
Can the check run inside our own checkout?
Yes — that is what Pro API is for. AML data is returned to your systems in real time, so the screening step is part of your payment flow rather than a separate task somebody remembers to do.
Can we separate what each merchant looks like?
Wallets are added individually and monitored individually, and the team works on them through shared investigations with role-based access — so the picture per merchant stays distinct while the oversight stays in one place.
Does this cover identity verification of our merchants?
No. AMLOfficer works on blockchain addresses and the flows around them. Verifying who a merchant is remains a separate process; what this adds is what that merchant's money has been near.
What does it cost to run at our volume?
Business pricing depends on volume and is shown in your account after registration rather than published as a tariff table.
Bring your merchant portfolio under one screening layer
Open a business account to add merchant wallets, invite your compliance team and see how the checks fit into the payment flow you already run.
One integration that carries screening into your own payment flow, instead of four provider contracts.
The check on its own: a payer address screened against four AML data providers before you settle.
Watch the wallets behind a merchant portfolio and get an alert when their activity changes.