Fraud prevention
Halba puts your fraud vendor where it belongs: before the PSP, with complete data, and informed of what happens next. You keep your contract and your guarantee; Halba handles the integration.
Screened before any PSP is called
Halba checks the data your vendor needs, waits for its decision and records the guarantee, all before the authorization.
Decision before authorization
Every payment goes to your vendor first. A decline stops it before any PSP is called; an approval with SCA advice drives the 3DS decision; a guarantee is recorded on the payment.
Complete data, checked
Before calling the vendor, Halba checks that the fields it requires are present and tells you exactly what is missing, instead of a failed call.
Outcomes that keep the guarantee
The authorization result, then every capture, void and refund, are reported to the vendor: its models learn from real outcomes and the guarantee stays valid.
Refund abuse (Policy Protect)
Pass the customer's request with the refund: Riskified assesses the claim first, and a declined claim is not refunded. The final decision is reported back.
Account takeover
Call Halba on every login attempt with the device data from halba.js: Riskified Account Secure answers allow, notify or challenge.
Vendor script loaded for you
halba.js loads your vendor's behavioural script with the right session id, so your checkout integrates one script instead of two.
Available today
- Riskified: decision, outcomes, refunds and cancellations, Policy Protect, Account Secure
- Forter: decision and order status updates (captures, cancellations, refunds)
- Requests validated against each vendor's published API specification
Coming next
- Connect your fraud vendor yourself from the dashboard
- Forter account protection
Try it in the sandbox
Connect your test PSP accounts, create an API key and send your first payment in minutes. No real money moves in the sandbox.