Canonical Labs

Custom Solutions

Any platform, any fraud problem.

Not on Stripe? Fighting disputes, ACH or identity fraud? Our team will cut the fraud and unlock revenue, no matter what platform you run on.

Talk to a Fraud Expert
Length
Scoped to the problem
First result
Diagnosis in week one
Where
On your platform
Engineering lift
Minimal

Who it is for

  • You take payments outside Stripe, or on more than one provider.
  • The fraud is in ACH, wires, payouts or identity, not only cards.
  • You have a risk question no fixed engagement answers.

What is included

  • Other payment providers, and ACH and wire fraud
  • Identity and KYC strategy: what to check, and when
  • Chargeback and card network programme monitoring
  • Your own risk data and reporting
  • A plan with targets for both fraud and revenue

What we have solved.

Problems outside a standard Stripe Radar engagement.

  • ACH and bank fraud

    Precious-metals dealer

    A $50K+ loss when one high-value ACH order turned out to be fraud.

    Bank-login verification for high-value ACH, and a red, yellow and green workflow for the phone brokers.

  • Identity and KYC

    Trading-card app

    Identity checks at signup turned good customers away and still let fraud reach the cash-out.

    Identity checks moved from signup to the first cash-out, with a fresh check on large withdrawals.

  • Your own risk data

    Collectibles marketplace

    Its own fraud model scored every payment, but Stripe Radar could not see the score.

    The model’s score passed into Stripe Radar through payment metadata, with thresholds set per customer segment.

  • Live attack

    Card-breaks marketplace

    Money deposited by ACH, spent on packs and withdrawn before the bank clawed it back.

    The attack shut down, card-testing rules backtested in shadow, and a recovery path through the payout banks mapped.

  • Moving to Stripe

    Marketplaces leaving a bundled payments provider

    Years of fraud history locked inside the provider they were leaving.

    That history analysed before the move, so Stripe Radar started from what had already happened.

“Thirty days without a single ACH dispute. I’m gonna party like a rock star tonight.”

CFO, precious-metals dealer

0

ACH disputes in 30 days, after multiple every month before

A month beforeThe last 30 days

How a Custom Solutions engagement runs.

Every one is different, so the shape is what stays the same: your data first, a diagnosis, a plan with targets, then the build.

  1. Week 0

    Intro call

    Twenty minutes on what you are seeing, where your payments run, and what a good result looks like for you.

    Scope

  2. Week 1

    Data access on your platform

    Exports, your warehouse, your provider’s dashboards, or Sigma if you are on Stripe. The least access the work needs.

    Data access

  3. Week 1

    Diagnosis memo

    Where the fraud comes from, what it costs, and which good customers your controls turn away.

    Diagnosis memo

  4. Week 2

    A plan with targets

    Clear targets for both fraud and revenue, and the controls to reach them, agreed with you before we build.

    Plan and targets

  5. Weeks 2 on

    Build

    Rules, checks, workflows, signals and reports, built with your team or your vendor.

    Controls live

  6. Then

    Measure

    Each change measured against the targets, and tuned until it meets them.

    Results report

  7. After

    Hand off or stay on

    A playbook your team can run, or we stay on and run it with you.

    Playbook or retainer

“I feel so much better about our defenses now. We finally know what is getting through, and why.”

CFO, precious-metals dealer

Questions buyers ask.

Yes. Custom Solutions works on whatever you run: another payment provider, ACH and wire, payouts or identity checks. We start from your own data and agree targets for fraud and revenue before we build anything.

Read access to wherever your payment data lives: exports, a warehouse, or your provider’s dashboards. Anything we change, we change with your team or vendor, after your sign-off.

Every rule is backtested first, with a list of the good customers it could touch. And we audit our own blocks: on one account we found good customers behind one of our own block rules, and relaxed it.

The configuration stays in your account and keeps working. You get the final report and the playbook, and we check in while disputes mature. A retainer is there if you want us to keep running it.

Each engagement is fixed in scope and priced on the engagement. We scope it with you on the first call.