BLIK fraud: recognise payment schemes before you ship
BLIK fraud tricks customers or merchants into approving fast bank transfers or BLIK codes. Shops should separate honest mistakes from deliberate abuse, collect consistent order context, and score risk before fulfilment. RiskCogs returns a 0–1 score with reasons next to your existing payment provider; it does not process payments or move funds.
Updated · RiskCogs team
Key facts
- BLIK fraud often mixes social engineering with new accounts and pressure to complete payment quickly.
- A high score is a signal to verify, not proof of intent.
- RiskCogs scores beside your provider and does not replace bank BLIK procedures.
Fraud vs customer mistake
A customer may enter the wrong code, cancel an order, or fail to recognise a statement descriptor. BLIK fraud more often combines urgency, a fresh account, an unusual device, or account takeover.
Keep separate support and risk queues so each path gets the right escalation.
Patterns worth monitoring
- BLIK code obtained from a victim through social engineering.
- New shop account plus an expensive BLIK-paid basket immediately.
- Many accounts or addresses tied to the same device or network.
- Returns or disputes right after delivery with no purchase history.
- Small test payments before a larger order.
What to collect on each BLIK payment
Define a minimum context set: order ID, customer account, device or session (with consent), IP, amount, time, and authorisation outcome from your payment provider.
Without stable identifiers you cannot link events into one abuse path later.
Score without changing provider
RiskCogs scores events on a 0–1 scale with readable reasons and lets you test rules in shadow mode while payments stay on your provider. It is not a payment institution and does not move funds.
Start in observe mode: compare flagged cases with later returns and confirmed abuse before you enforce blocking rules. Product scope and plans are on the product and pricing pages.
See what you would have blocked — free shadow modeFrequently asked questions
Does RiskCogs block BLIK transfers directly?
No. RiskCogs does not sit in the BLIK authorisation path or move funds. You receive a 0–1 risk score, readable reasons, and optional rules. Your checkout, order system, or payment provider decides approve, review, or cancel using that signal and your written policy.
How is this different from general online fraud?
BLIK fraud is a payment-scheme pattern: fast bank transfers, BLIK codes, and social engineering around approval. General online fraud covers phishing, fake shops, and account takeover at login. Keep separate pages and metrics so searchers and support teams land on the right playbook.
Where should I start integration?
Read the fraud detection API docs and shadow mode section on the product page. Create a sandbox key in the console, send a few test orders with stable order IDs, and compare scores to later chargebacks before you turn on enforce mode in production traffic.