A clearer picture of each payment
Connect device, network and payment context. See the contributing signals alongside the score.
Payment risk, without the guesswork
Add one script. See what you would have declined, what it cost, and why — beside your current PSP. Start in shadow mode. Change nothing until you’re ready.
npm i @riskcogs/js
Illustrative installation · see integration notes
One payment. The whole picture.
- Observe
- Understand
- Decide
Scroll to explore · Illustrative console screens
Example: shadow mode flags 312 payments with €18,420 in simulated avoided loss. The inspector explains a score of 0.86. Review that evidence before choosing whether to enforce a card-testing rule. These are illustrative figures, not customer results.
How shadow mode works
Start with evidence. Change your rules when you’re ready.
- 1 Install
Send the payment event
Install the script and send a server-side event for each payment. Keep your current PSP and fraud setup.
rc.track('payment', {
id: 'pay_9d6e12', amount: '89.00'
}); - 2 Observe
Score it. Change nothing.
RiskCogs scores every payment in shadow mode. No blocks, no changes to checkout.
risk_score: 0.86Shadowaction: observe_only - 3 Decide
Review, then enforce
See what would have been blocked and what it cost. Switch rules to enforce one by one when you trust the results.
Weekly shadow report · example312 payments€18,420
From evidence to confidence
Watch first.
Understand why.
Then decide.
You keep your payment flow. RiskCogs makes the signals visible, so you can choose what happens next.
- Observe in shadow
- Inspect the evidence
- Enforce one rule at a time
Interactive illustration · no live decisions
Would-have-blocked312payments
Estimated loss avoided€18,420last 7 days
False-positive rate0.4%scored traffic
Would-have-blocked / day312 total
Recent paymentsscore / 1.00
pay_7f2a910.93Card testing · 14 attempts / 2 minpay_8b4c830.88Device seen on 6 accountspay_9d6e120.86BIN country ≠ IP countrypay_a1f8400.12Trusted returning customerAll decisions simulated. Your PSP stays in control.
€89.00 · Visa debit · just now
Risk score
0.86Elevated risk
0.00 · low1.00 · high
Score contributions
- BIN country ≠ IP country+0.31
- Device linked to 6 accounts+0.22
- 3 successful payments−0.08
Would have declined. No action taken.
You decide when a rule is ready.
Card testing
card.attempts_2m > 10Example precision99.3%
Example hits · 7d142
PaymentRuleDecision
€ saved · simulated€18,420
Illustrative avoided loss, not a guarantee.
Your rules. Your thresholds. Your decision.
Separate the signal. Keep the context.
Different clues become useful when you can see how they fit together. Start by observing, then decide what deserves a response.
Every reason, one layer deeper
Move from a payment to its matched rules and supporting evidence, without losing the original context.
Recognise patterns across sessions
Device and browser signals help connect repeated activity. Capture replay only with consent.
Your thresholds. Your decision.
Observe a rule in shadow mode before choosing whether to enforce it. A score is evidence to review, not a verdict.
What’s inside the score
One score, with the evidence attached. Inspect the signals behind each payment decision.
- Velocity
- Attempts across card, device, IP and email.
- Device & browser fingerprint
- Recognise the same device across sessions.
- Network
- Proxy, VPN, TOR and IP reputation.
- Card BIN intelligence
- Card type, issuing country and prepaid status.
- Behaviour
- Journey and replay signals, with consent.
- Customer history
- Trust grows with successful payments.
- Your rules
- Your hard blocks and allowlists, in the same score.
€89.00 · Visa debit · just now
Risk score
0.86Elevated risk
0.00 · low1.00 · high
Score contributions
- BIN country ≠ IP country+0.31
- Device linked to 6 accounts+0.22
- 3 successful payments−0.08
Would have declined. No action taken.
Built for how you actually pay
E-commerce
Card testingSpot card testing and friendly fraud without adding friction to checkout.
iGaming
Multi-accountingConnect bonus abuse, multi-accounting and deposit velocity in one view.
PSPs & platforms
merchant_id · 0284Set per-merchant rules. One integration covers all your sub-merchants.
Subscriptions
Trial abuseCatch account takeover and trial abuse before the next billing cycle.
Rules you can read
Every rule shows its precision on your own traffic before you turn it on.
Illustrative evaluation · last 7 days| Name | Condition | Mode | Hits 7d | Precision |
|---|---|---|---|---|
| Card testing | card.attempts_2m > 10 | Shadow | 142 | 99.3% |
| Shared device | device.accounts_7d > 6 | Shadow | 96 | 98.0% |
| Country mismatch | bin.country != ip.country | Shadow | 74 | 94.6% |
| Trusted customer | customer.successful > 3 | Enforce | 1,284 | 99.8% |
| Known blocked device | device.id in blocklist | Enforce | 38 | 100.0% |
3 shadow rules · 312 would-have-blocked paymentsYour traffic. Your thresholds.
A small integration. A clear contract.
Quickstart
From install to your first scored payment.
5-minute quickstart · illustrative
npm i @riskcogs/js
# Add a browser signal
# Send a server-side eventSDKs
Use the language already in your stack.
JS · Node · PHP · Python · illustrative
const result = await riskcogs.score({
payment_id: 'pay_9d6e12',
amount: '89.00', currency: 'EUR'
});Webhooks & feedback API
Close the loop with confirmed outcomes.
Events + outcomes · illustrative
{
"payment_id": "pay_9d6e12",
"outcome": "chargeback"
}Start in shadow mode
No card. Delete your data any time. EU-hosted.