For issuing banks & EMIs · PSD3 / PSR 2027

Stop the transfer while the scammer is still on the line.

From 2027, when a fraudster impersonates your bank, you reimburse the customer — uncapped. Zeptric lives inside your mobile app, reads the signals a scam leaves on the device, and pauses the payment before it clears.

< 50 msdecision latency, p99
0 bytesof PII leave the device unhashed
7 yearsimmutable evidence retention
01 — The liability shift

The customer pressed "confirm". You still pay.

Under PSD2 an authorised push payment was the customer's loss. The PSD3 / PSR package reclassifies payments induced by bank impersonation as unauthorised — full reimbursement by the payer's PSP, no monetary ceiling. The only lever left is prevention at the moment of payment.

AI acts as a force multiplier for impersonation and social engineering.EBA / ECB · 2025 Payment Fraud Report
  • €4.2 bnPayment fraud reported across the EU/EEA in 2024, concentrated in remote credit transfers.EBA / ECB 2025 Payment Fraud Report
  • 85 %Share of credit-transfer fraud losses that customers currently absorb. PSD3 moves this line to the issuer.EBA / ECB, 2024 data
  • +19 %Year-on-year growth of APP fraud in the UK, 2025 — the market that already runs mandatory reimbursement.UK Finance Annual Fraud Report 2026
  • 2027Expected application of the PSD3 impersonation rule in the first transposing member states.Final texts agreed April 2026
02 — Anatomy of one scam

Fourteen minutes. One tap. Irreversible in seconds.

Verification of Payee checks that a name matches an IBAN. It cannot see that your customer has been on the phone with "your security department" for a quarter of an hour. Zeptric can.

  1. Inbound call

    Spoofed caller ID matching the bank's published number.

  2. The script

    "Your account is compromised. We'll move your funds to a protected account."

  3. App opened

    Transfer screen. New recipient. Amount 8× the customer's usual.

  4. Zeptric decision · 23 ms

    Call + new payee + amount + stressed input → score 0.94 → pause.

  5. One question

    "Were you told this is your bank's security team?" Real number offered.

  6. Evidence sealed

    Signals, prompt shown, customer response — hashed, timestamped, locked for 7 years.

03 — What the device knows

Signals a fraudster cannot fake.

Collected by the SDK inside your own app, hashed on the device, and scored against the customer's own baseline — never against a generic population.

SignalWhat it revealsSource · privacy
Call before paymentA long call that ends minutes before a transfer is the single strongest impersonation marker. Duration, direction and timing are enough — no audio.CallKit · Telecom API
number hashed
Message urgency"Verify now", "protected account", an IBAN in the text that matches the payee. Metadata and pattern match, on-device.SMS metadata
content never uploaded
Input behaviourPasted IBAN, rushed field order, tremor in touch pressure, warnings dismissed without reading. Coercion shows in the hands.Touch & motion sensors
baseline per customer
Payee & amountFirst-seen recipient, amount outside the customer's envelope, unusual hour — the classic signals, weighted by context rather than alone.Your core data
tokenised
Device integrityRemote-access tooling, screen overlays, jailbreak — the setup for "let me guide you through it".App Attest · Play Integrity
block on compromise
04 — Integration

One SDK. One call. Your core banking stays untouched.

Drop the SDK into your iOS and Android apps, call assess() before you execute a transfer, and act on one of four answers. If we are unreachable, your configured fallback applies — the app never waits on us.

4decisions: allow · pause · verify · block
mTLSbank-to-Zeptric, per-bank certificates
EUhosted in Germany, no data leaves the EU
PaymentViewController.swiftZeptricSDK 1.0
let assessment = try await Zeptric.assess(
    .transfer(amount: 12_400, currency: "EUR",
              iban: iban, name: name)
)

switch assessment.action {
case .allow:   execute()
case .pause:   showPause(assessment.prompt)   // one question
case .verify:  stepUpAuth()
case .block:   showBlocked(assessment.prompt)
}

// assessment.evidenceURL → sealed, 7-year PSD3 package
05 — Evidence, not just a score

Every pause becomes a file you can put in front of a regulator.

When a dispute arrives, you need to show what the customer saw, what they were asked, and how they answered — with timestamps nobody can edit. Zeptric seals that package automatically on every assessment and keeps it for seven years under WORM storage.

Question in a disputeWithout ZeptricWith Zeptric
Was the customer warned?Screenshots, if anyone saved themPrompt text + timestamp, sealed
Why was it flagged?Model score, unexplainedNamed signals with values
What did they answer?UnknownResponse + response time
Is the record intact?Mutable DB rowSHA-256 chain, Object Lock
Can it be retrieved in 2033?Depends on retention policyYes — 7-year WORM by default
06 — Pricing

Priced against the losses you'd otherwise carry.

One prevented €50,000 impersonation covers the Professional plan for five months. Pilots run free for 30 days on 5 % of traffic.

Starter
€3,000
per month · annual
  • 100k assessments / month
  • Call, payee, amount & time signals
  • Evidence packages, 7-year retention
  • Email support
Professionalmost banks
€10,000
per month · annual
  • 1M assessments / month
  • All signals incl. behavioural & device
  • Custom rules & thresholds per segment
  • Dispute-ready PSD3 exports
  • Priority support, named engineer
Enterprise
Custom
volume-based
  • Unlimited assessments
  • Models trained on your fraud history
  • 99.99 % SLA, dedicated tenancy
  • On-premise or private cloud option
  • White-label for PSP resale

The 2027 deadline is closer than your next core banking upgrade.

Zeptric is in private development with a first issuing partner. Public pilots open in 2027.

zeptric.io · Berlin