Skip to main content

Block Rules & Fraud Prevention

Block rules stop checkouts and payments from matching IPs, emails, PAN/BIN patterns, specific customers, or payment IDs. Rules use an AND / OR operator across the criteria you set.

Create a block rule

Use OR when any single signal should block; use AND when all filled criteria must match.

Rule criteria reference

Additional flags include autoCreated, metadata, isPermanent, and ttlHours.

Temporary vs permanent blocks

ttlHours is only meaningful when isPermanent is false. Allowed range is 1–8760 hours.

List, retrieve, update, delete

The list endpoint accepts pagination and filters via the HTTP API (pagination, sortBy, filters); the SDK currently posts an empty body for list() — extend the call if you pass a typed body through your integration.

SDK methods reference


Next steps

Payments

Process and route payments after hardening with block rules

Customer management

Tie blocks to customerId and customer-level review

Checkout sessions

Share checkout links and monitor async payment status

Funnel orchestrator

Routing and conditions alongside fraud controls