For payments and remittance

AML and fraud monitoring for payment and remittance companies

With Archer Protect, you check every payin, payout, and transfer in every corridor, catch structuring and mule accounts, and stop a payment before the money leaves. Your compliance team writes, tests, and changes the rules itself.

Volume grows faster than your compliance team

  • Today An analyst reads a daily export, or an email for every payment, so each jump in volume means another hire.

    With Archer Each transaction is checked against your rules as it arrives. Your team reviews only what a rule flags.

  • Today A sponsor bank or payout partner wants to see your monitoring before it goes live with you.

    With Archer Monitoring, case records, and an audit trail you can show the partner.

  • Today The alert arrives after the beneficiary already has the money.

    With Archer A rule can hold or reject the payment before it completes.

  • Today Mule networks get traced by hand, one counterparty at a time.

    With Archer Linked senders and receivers appear as one network.

One rule set for every corridor

Scope a rule to a country, a corridor, or a product, with amounts converted to one currency. Each market gets its own thresholds and its own queue, and your team changes them without waiting on engineers.

Payins, payouts, card payments, and wallet transfers run through the same rules. Launching a new product means sending a new kind of event, not adding a new tool.

Structuring, mules, and other payment patterns

Rules compare what a customer does now with what they usually do, and look across everyone they send to or receive from. Typical rules:

  • Amounts split to stay under a reporting threshold, to one recipient or many.
  • Many senders paying one receiver.
  • Money that comes in and goes straight back out.
  • A transfer far above what the customer usually sends.
  • A dormant account that suddenly starts moving money.
  • Chargebacks and refunds, used in any rule alongside the payments they belong to.
See what a rule would have flagged on your own history, before it goes live.

Stop a payment before the money leaves

When a rule fires, Archer sends your system a decision by webhook: hold the transfer, freeze the account, or reject the payment. Where a flow needs it, Archer returns a verdict inline, before the payment completes.

Money mules and the networks behind them

Archer links senders and receivers who share a phone, a bank account, a wallet, a device, or a close spelling of the same name, then follows the money between them. Cluster View shows the whole network, and a rule can act on anyone linked to a confirmed mule.

Monitoring your partners will ask to see

Before a sponsor bank or payout partner goes live, it asks how you monitor. Archer gives you the answer: rules with a history of every change, sanctions and PEP screening of senders and beneficiaries, and a recorded reason for every decision.

If you serve end users your partners onboarded, send them to Archer too. They are linked and screened like your own customers.

Archer drafts goAML reports for Nigeria’s NFIU and FINTRAC reports for Canada straight from the case.

Merchant and business screening

Screen the businesses you serve, and their directors and shareholders, against sanctions and PEP lists. Then run rules on each merchant’s transactions: a spike in volume, refund and chargeback rates, or payments that don’t fit what the merchant sells.

Example: a structuring rule for one corridor

Example data. An analyst asks the assistant for a rule: flag any customer who sends three or more transfers just under the reporting threshold within 24 hours. Archer builds it, backtests it on the last 30 days, and lists every customer it would have flagged. The analyst limits it to new customers, reruns the backtest, and publishes. From then on, each hit opens a case in that corridor’s queue.

Customer results

What teams found running Archer

“Archer’s solution is really powerful. I wish we had it years ago!”

Justin Poiroux Cofounder and CTO, Yellow Card
< 60 s
for Numida’s risk team to create or change a fraud rule, without engineering

“We review rule performance weekly and adjust directly in the platform. If we identify a new pattern, we don’t need to wait for engineering.”

Joyce Leads risk, Numida
Read the Numida case study 

FAQ

Questions compliance teams ask us

Can Archer stop a payment, or only alert?

Both. A rule can send your system a decision such as hold, freeze, or reject by webhook, or Archer can return a verdict inline before the payment completes.

Our partners onboard the end users. Can Archer monitor them?

Yes. Send Archer the senders and receivers your partners pass to you, and they are linked, screened, and monitored like your own customers.

Does Archer screen senders and beneficiaries?

Yes. People and businesses are screened against sanctions and PEP lists. You tune matching by date of birth, nationality, and match threshold.

Which regulator reports can Archer produce?

goAML suspicious transaction reports (STR) and currency transaction reports (CTR) for Nigeria’s NFIU, and FINTRAC reports for Canada, drafted from your cases.

We built our own rules engine. Why move?

Your compliance team writes, tests, and changes rules itself, backtests them on your own history, and works cases with a full record and audit trail. Your engineers go back to building your product.

How quickly can our team change a rule?

Numida’s risk team creates or changes a rule in under 60 seconds, without engineering.

See how Archer works on your own data

Book a demo