Know the card is real.
And the person holding it.

Amsel verifies the physical card and scores every deposit against 40+ risk signals — in the background of checkout, before the money moves. Merchants lift conversion by at least 5% while card fraud drops by up to 20%, with no added friction.

Higher conversion
40+ risk signals
PCI DSS SAQ D-SP
deposit · 120.00 EUR
worked example
Visa debit
4246 31•• •••• 2039
exp 09/28returning customer
reading card surface
risk score
0/200
Low ≤79MediumHigh ≥120
Low-Risk

A valid number proves nothing.
Amsel proves the card — and the hand it's in.

the problem

You validate the card.
Not the person holding it.

Number-only checks wave through stolen cards, static rules get learned and dodged, and the chargeback lands weeks later — long after the goods have shipped.

Valid number, stolen cardThe digits pass every check while the real cardholder never touched it.

Rules they learn to dodgeA fixed rule set is a puzzle fraudsters solve, then walk straight past.

Chargebacks land lateWeeks after dispatch — you've already lost the goods and the fee.

Card data you shouldn't holdStoring PANs turns every breach into someone else's catastrophe.

the approach

Built around the moment of payment

Amsel is opinionated about three things: verify the real card, decide in real time, and never keep what you don't need.

Get in touch
SCAN · FRONT✓ GENUINE
card presentyes
PAN storednever

Physical-card authenticity

The buyer scans the card and our own authenticity model confirms a real card is in hand — not a photo, not a number typed from a stolen list.

Low-Risk ≤79Medium-RiskHigh-Risk ≥120

One real-time verdict

Dozens of signals resolve in milliseconds into a single score — and one decision your checkout can act on, tunable per merchant.

HELD Attempt #4471score 100grey zone approvedecline

Grey zone: hold, or step up

Borderline attempts aren't guessed. Hold them for an operator to approve or decline — or ask the buyer to verify with a government ID before anything ships.

under the hood

One attempt.
Every signal.
One verdict.

A number-only check sees a valid card and stops. Amsel weighs the device, the network, the pace, the issuer, your blacklists and the buyer's own history — then commits to a verdict. When it lands in the grey zone, it holds for a person instead of guessing.

MC
Attempt #4471
visa •• 4471 · Tallinn, EE · 0:09 ago
6 signals weighed
signalweightstatus
Card front & back — scanned & genuine0clear
Cardholder name matches card0clear
Card issuing country ≠ IP location+15flag
Card velocity exceeded — 3+ in 1h+40flag
VPN detected+25flag
Phone country mismatch+20flag
risk score 100 · medium-risk band 80–119 Medium-Risk held for review
security & privacy

Handles cards without hoarding them.

The safest card data is the data we never keep. Amsel is engineered to check, decide, and forget — so a breach has nothing to take.

Zero
Full card numbers & CVVs stored. Ever.
No disk
Card images processed in memory, never written to storage.
SAQ D
Operating to PCI DSS v4.0 Service-Provider scope.
EU
GDPR-compliant, hosted entirely within the EEA.
AES-256
Encryption at rest & TLS 1.2+ in transit, end to end.
faq

No spin, just answers.

What it is, how it works, what it keeps.

Amsel is built and operated by SIA Mandet, a Latvian company. It runs in production today handling real checkout traffic — not a prototype or a slide deck.
No. Full card numbers and CVV are never stored, and card images are processed in memory and never written to disk. Only minimal, non-sensitive signals (last four digits, issuing bank, expiry) may be retained to recognise a returning card.
Every attempt resolves to one of three risk levels: Low-Risk, Medium-Risk, or High-Risk, based on a weighted risk score. Low-Risk proceeds instantly, Medium-Risk is held for a human, and High-Risk is stopped at the door. The thresholds are tunable per merchant.
Real time. The score is computed in milliseconds and the decision is delivered to your backend by an HMAC-signed webhook while the customer is still at checkout.
Borderline attempts are marked Medium-Risk and held for an operator to approve or decline from a focused review queue — nothing ships on a guess. You can also auto-handle them, or route them to an inline identity step-up (below).
Optionally, yes. For elevated-risk attempts you can trigger an inline identity step-up: the buyer scans a government-issued ID — passport, ID card or driving licence — which is read and matched against the cardholder name. Only the pass/fail outcome is kept; the ID image is processed in memory and never stored.
Drop the verification widget into your checkout and point a webhook at your backend to receive decisions. Most integrations are a single afternoon.
Amsel is hosted entirely within the EEA, is GDPR-compliant, and operates to PCI DSS v4.0 SAQ D-SP (Service Provider) scope. Data is encrypted with AES-256 at rest and TLS 1.2+ in transit.
Get in touch at vs@mandet.co and we'll walk you through a setup for your store.
ready when you are

Put a sharper eye on your checkout.

Verify the real card, decide in real time, and keep nothing you don't need. Let's set it up for your store.