Platform · Risk
A risk engine that protects conversion, not just cards
LekkaPay's risk engine scores every transaction in real time, inside the authorisation path: velocity checks, configurable rules and per-merchant allow and block lists decide in milliseconds whether a payment is approved, challenged or declined. The engine is calibrated, not paranoid - industry studies consistently find that falsely declining good customers costs merchants more than fraud itself.
LAST UPDATED ·
- Real-time scoring Every transaction scored in the authorisation path, before approval - not flagged after the fact.
- Velocity checks Catch the patterns humans miss - one card hit repeatedly, one device cycling through many cards.
- Allow and block lists Per-merchant lists that let trusted customers through and keep known offenders out.
- Configurable rules Thresholds and rules tuned to your business - a fraud pattern in gaming looks nothing like one in retail.
- Decline analytics See what was declined and why, in the same back office as your settlements.
How it works
How it works
-
A payment arrives
Risk scoring runs while the authorisation is in flight - before the money moves, without adding a step the customer can see.
-
Signals combine into a score
Velocity checks, your allow and block lists and your configured rules produce a decision in milliseconds.
-
Approve, challenge or decline
Low-risk payments sail through; doubtful ones get a 3-D Secure 2 challenge - a chance to prove themselves - rather than an outright block.
-
Analytics close the loop
Decline analytics show what was blocked and why, so rules are tuned on evidence instead of anecdotes.
Fraud prevention is a conversion feature
The most expensive fraud decision most merchants make is the decline that was not fraud. Industry studies of card-not-present payments consistently find that revenue lost to falsely declined good customers exceeds losses to fraud itself - and unlike fraud, a false decline also costs the relationship, because few customers try again after being refused. LekkaPay builds its risk engine around that arithmetic: the goal is not the lowest possible fraud number, it is the best possible trade between fraud stopped and genuine sales approved. Every screening feature on this page exists to serve that trade.
How does risk scoring work?
Scoring happens in real time, inside the authorisation path - while the transaction is in flight, before the money moves, without adding a step the customer can see. Velocity checks catch the patterns no human reviewer would: the same card attempted many times in minutes, one device cycling through many cards, bursts of activity that do not look like shopping. Per-merchant allow and block lists apply your own knowledge of your customers. Configurable rules put thresholds where your business needs them. The combined decision comes back in milliseconds: approve, challenge, or decline.
Rules you control - with a challenge before a block
Risk appetite is a business decision, so the rules are yours to set: what gets challenged, what gets declined, who bypasses screening entirely. Where a card transaction is doubtful rather than damning, the engine prefers a 3-D Secure 2 step-up to an outright decline - a genuine customer passes in seconds, while a fraudster with a stolen card usually cannot. And every outcome lands in decline analytics with its reason attached, so you can see exactly what a rule is costing you and tune it on evidence.
Where AI fits - honestly
AI-assisted fraud detection is an area of active development at LekkaPay, and we describe it that way deliberately. Machine-learnt models are genuinely good at spotting fraud patterns that rule sets miss, and we are building toward them - but the screening protecting your transactions today is the real-time scoring, velocity checking and configurable rules described above. When AI-driven capability ships on the platform, this page will say so plainly; overclaiming on fraud tooling is exactly the behaviour a fraud team should distrust.
- is lost to falsely declined good customers than to fraud itself, a consistent finding across the industry
- More
- Industry studies of card-not-present fraud, 2025
FAQ
Your questions, answered
How does risk scoring work?
Every transaction is scored in real time, inside the authorisation path. Velocity checks, per-merchant allow and block lists and your configured rules combine into a decision in milliseconds - approve, challenge with 3-D Secure 2, or decline - before the authorisation is sent onwards. The customer sees nothing except, occasionally, an authentication step.
Can I configure my own rules?
Yes. Risk appetite is a business decision, not a technical constant, so thresholds, rules and allow and block lists are configurable per merchant. A pattern that screams fraud for a digital-goods seller can be perfectly normal for a wholesaler - your rules should reflect your business, and with LekkaPay they do.
Does 3-D Secure 2 replace fraud screening?
No - they are complementary. 3-D Secure 2 authenticates the customer and shifts chargeback liability on enrolled cards; risk screening decides whether and how a transaction should proceed at all, across every payment method. LekkaPay uses them together: scoring decides, and a 3-D Secure 2 challenge is one of its outcomes.
What happens when a payment is flagged?
It depends on the severity, and you stay in control. Moderate-risk card payments can be stepped up to a 3-D Secure 2 challenge - a chance for a genuine customer to prove themselves - while clear rule breaches are declined outright. Every flagged transaction appears in your decline analytics with the reason attached, so nothing is blocked silently.
Will fraud screening block my real customers?
A badly tuned engine will - and that costs more than fraud, which is why LekkaPay treats false declines as failures, not caution. Doubtful transactions are challenged rather than blocked where possible, allow lists protect your known-good customers, and decline analytics make every block visible so over-strict rules get caught and corrected.
One platform, two models.
Start on LekkaPay merchant accounts or bring your own MID - same API, same back office, no re-integration.