Payment providers

Check the names on both ends of a payment

Screen merchants when they sign up, and the payer and payee on a payment when your rules call for it — through one API, with a limit per key so checkout and batch jobs never compete.

Get Started How the API works

Illustrative. AMLPRO screens the names; your system decides what happens to the payment.

Two jobs

Merchants once, payments every time

At onboarding

Merchants and the people behind them

Screen the merchant as a company, with its country and registration number.
Screen each director and owner as an individual.
Keep a merchant whose owner or director is sanctioned, even when the merchant itself isn’t listed.

On a payment

Payers and payees

Send the names from your payment system through the API.
Tag each screening with your payment ID and find it again in the usage log.
Every result comes with a PDF report for the file.

One account, many integrations

A key for every job in your stack

Each key has its own permissions, allowed addresses, end date and rate limit — so a reporting job can never run a billed screening, and a batch run can never slow checkout.

Illustrative key names and settings.

Engineering notes

Made to sit in a payment stack

The details your engineers will ask about, answered up front.

Rate limits: Counted per key. Give checkout and batch re-screening a key each and neither slows the other.
Refusals: A refused call says why — the balance, the plan, the key’s permissions or the rate — so your code can act on it.
Access: Keys limited to screening or to reports, to your servers’ addresses, and to an end date.
Replays: Every call is signed and time-stamped; one older than five minutes is refused.
Cost: Each search is priced by your plan and charged to a prepaid balance.
Records: One usage log for API and console searches, searchable by your own reference.

Questions

What payment teams ask us

Something we haven’t covered? Ask us — we’ll answer for your case.

Is there a rate limit?

Yes, counted per key. When a key goes over it, the refusal says how long to wait before trying again — and your other keys aren’t affected.

Do you monitor transactions or payment patterns?

No. AMLPRO screens the names you send it. Transaction monitoring is a separate tool; AMLPRO is the name check your rules call for.

Can we tie a screening to a payment?

Yes. Send your own reference with each screening — a payment ID, a merchant ID — and search the usage log by it later.

What does a merchant screening cover?

The merchant as a company, with its country and registration number, and each director and owner as an individual. A company workflow can also keep a merchant whose owner or director is sanctioned in the data.

Other industries

Screening that fits your payment flow

Start with a key on the free plan, or talk to us about merchant onboarding and the volume your rails carry.

Get Started Talk to an Expert