Sync vs Async Event Ingestion for Fraud Decisions

Fraud integrations usually need both synchronous and asynchronous paths. Use synchronous decisioning when the product must decide before it continues. Use asynchronous ingest when the event should be monitored, enriched, or reviewed without blocking the customer.

Use Sync for Product Gates

POST /api/v1/decisions/evaluate

Good sync candidates include payments, withdrawals, password resets, and high-risk profile changes. The product should apply ALLOW, BLOCK, or REVIEW immediately.

Use Async for Monitoring

POST /api/v1/events/async

Good async candidates include low-risk logins, portfolio monitoring, analytics enrichment, and event streams that drive operations through webhooks.

Choosing the Mode

• If the customer cannot continue without the answer, use sync.
• If operations can review after the fact, use async.
• If traffic arrives in bursts, use async plus webhooks.
• If the action moves money or changes account access, start with sync.

Follow the event tutorial to send your first event.