Vilkax
VILKAX
Personal Business Partners Developers Trust layer
Protected Customer Link is free Talk to partnerships
Vilkax for banks, fintechs, exchanges, telcos and marketplaces

The fraud officer on your customer's device.

Start free: connect your customers' Vilkax protection to your fraud team in a day. One webhook, one lookup, a consent screen we host. Signals only, never content.

Consent per partner Signals, not content Fails closed
Scroll
The gap we fill

Your engine sees the payment.
It never sees the ten minutes before.

Every bank, exchange and fintech scores fraud on its own side of the wire. That works until the customer authorises the payment themselves. Authorised push payment fraud, account takeover and social engineering all happen in the minutes your servers cannot see: the unknown call, the remote-access tool that was just installed, the "account manager" on WhatsApp, the clipboard swap, the screen that is being shared.

Vilkax runs with the customer, on their device, with their consent. We see the situation forming. The offer is simple: we connect that view to your fraud decision in real time, and we take on the education, interruption and recovery work a call centre cannot do.

-10 minUnknown call, then the banking app opens.Vilkax sees this
-7 minA remote-access tool is installed and a session starts.Vilkax sees this
-3 minThe payee IBAN in the clipboard is swapped.Vilkax sees this
-1 minThe customer is coached to answer your step-up correctly.Vilkax sees this
0An authorised payment arrives at your fraud engine.Your engine sees this

Illustrative sequence of a typical authorised-payment scam, not a recorded case.

Products, lightest integration first

Start with the free link. Add depth when you are ready.

Every card says exactly what you integrate and where the piece stands today. We label status honestly: nothing here is dressed up as finished when it is not.

Availablein the Protect API today Pilotbeing built now, open to pilot partners Roadmapnext, after the pilots
P1 Free for partners Pilot

Protected Customer Link

Your customer links their Vilkax to you with an OAuth-style consent screen we host. From then on you receive a real-time Moment Risk Signal for that customer: remote session active, clipboard substitution, unknown call followed by the banking app, trojan-like install, an active scam situation, device posture. Typed signals with confidence and reasons. No messages, no URLs, no contacts.

No per-customer fee and no per-signal fee. The link is how your customers become protected everywhere and how we earn the relationship; paid products start at P2.

How to integrate
1 webhook + 1 REST lookup
The signals lookup is live today. Webhook push and the hosted consent link are being built now.
Get a developer key
P2Available
Pre-Transaction Check
Before you release a payment, call decide with the customer link id. You get allow, step-up or hold-and-call, with reasons in plain language your agent can read to the customer.
How to integrate
1 API call in the payment path
Per decision, metered
P7Pilot
Verification Fabric
Register a signed contact card: your real numbers, emails, domains and public key. Vilkax checks inbound calls and messages against it for every user, so impersonation of you is caught on the device.
How to integrate
One-time registration + key rotation
Annual fee; included in P3
P4Pilot
Interruption as a Service
When your own engine flags a payment, trigger an on-device interruption instead of a call or SMS: a full-screen card with the evidence, a cooling-off timer, "call the number on your card", and a second opinion. You get a verified delivery receipt.
How to integrate
Webhook from you to our push
Per interruption
P5Pilot
Recovery Desk
After an incident, our recovery playbooks run inside the app with your case id and deadlines: chargeback, recall, freeze, police report, identity re-issue. Fewer call-centre hours, shorter recall windows.
How to integrate
1 case webhook
Per case
P8Available
Staff Shield
The consumer client under tenant policy for your own staff: business email compromise, payee-change hold, deepfake-call playbook, remote-access blocking.
How to integrate
Business app tenant
Per seat
P6Roadmap
Intelligence Commons
An aggregated, differential-privacy threat map: first-seen mule accounts, payee IBAN and wallet reports, phone numbers, domains, playbooks by country, within minutes. Partners contribute and consume.
How to integrate
Feed subscription
Annual subscription; contributors get credits
P3Pilot
Co-branded Protection
Distribute Vilkax to all your customers as "your bank's protection app", white-label or as a co-branded section. You pay, your customers get the Protect tier, and you get P1 and P2 for everyone.
How to integrate
Distribution + SSO
Per active customer per month, volume tiers

Telcos: SIM-swap event exchange, call-labelling feeds and smishing sinkhole lists. Marketplaces: buyer and seller scam arcs, overpayment and fake-payment-screenshot detection. Ask us about either.

Savings calculator

Your numbers. Your assumption.

We do not have your fraud book, so we do not guess it. Enter what you already pay for authorised-payment and account-takeover fraud, then set the share of those cases you assume an on-device interruption would stop. The result is arithmetic on your inputs, nothing more.

0%

The share of the fraud cases above that you assume would be stopped or recovered by an on-device interruption. It starts at zero on purpose: we publish no default rate because we have no field figure to stand behind yet.

Projected annual savings
0
Reimbursements avoided0
Dispute handling avoided0
Call-centre time avoided0

Illustrative, based on your inputs. Not a forecast, not a quote, and not a claim about Vilkax's measured performance. Fines, legal costs and churn after an incident are not included.

Enter your figures and move the slider to see a projection.

How to start in 3 steps

Days, not quarters.

1
Get a developer key
Request a partner key from the platform page. We issue a vlx_live_ key with a tier, the plaintext is shown once, and every call is rate-limited and audited per partner.
Open the platform page
2
Add the consent link
Put one link in your app or onboarding. Your customer sees a consent screen we host, links their Vilkax to you, and can revoke it in-app at any time.
Read the OpenAPI spec
3
Receive signals
Look up a linked customer's moment signals before a payment, or receive them by webhook as they change. Add the decide call when you want a verdict, not just a signal.
Developer overview
Trust, privacy and compliance

Non-negotiable, by design.

Consent

Per partner, revocable in-app

The customer consents to each partner separately and sees a visible log of every signal shared. They can revoke it at any time, and the sharing stops.

Signals, never content

You get typed signals, not their life

A partner receives typed signals with confidence and reasons, and hashed identifiers. No messages, no URLs, no contacts. Ever.

Fail closed

Missing auth means deny

Partner keys, per-partner rate limits and an audit chain on every share. A missing or inactive partner account is denied, never allowed by default.

Never accuses

Signals describe the situation, not the person

A signal says "remote session active" or "clipboard substitution", never "this customer is a fraudster". We detect patterns; we do not classify people.

High-stakes categories

Never shared with a commercial partner

Coercion, abuse and similar categories go to human review and resources only. They are not a signal any partner can subscribe to, at any price.

EU data residency, retention limits, a DPA and a DPIA template for partners. Partner dashboards show real counts or an honest empty state, never fabricated results. Data Processing Agreement · Sub-processor list · Security

Partner inquiry

Tell us where the losses are.

A short note is enough. It lands with the partnerships team, and a person replies by email. No automated sales sequence.