Available today
Production integration surfaces.
These are the current ways to connect Verifex to your own product, alerting, review, and audit workflows.
REST API and OpenAPI
Screen entities, retrieve usage, manage watches, and export Evidence Capsules through documented API endpoints.
Official SDKs
Use the Node.js, Python, Go, and Rust SDKs to add screening to onboarding, payment, and batch workflows.
HMAC webhooks
Receive signed risk-change events from continuous monitoring and verify payload integrity with your webhook secret.
Slack alerts
Send watchlist risk-change notifications into Slack through an incoming webhook configured from the dashboard.
Evidence Capsule JSON
Attach structured decision evidence to internal cases, CRM records, audit files, or data warehouse rows.
Dashboard exports
Export screening history and alert records for review, audit preparation, and internal compliance reporting.
Integration patterns
Route screening evidence where decisions happen.
These patterns are intentionally labeled. Verifex does not claim native packaged connectors for every vendor below. The current product gives teams the API, webhook, and evidence payloads needed to wire the workflow themselves.
Salesforce and HubSpot
Store request IDs, risk levels, reviewer status, and Evidence Capsule links on leads, accounts, or compliance objects.
Sumsub and Alloy
Run Verifex after KYC identity collection and send the screening result into the KYC decision or case workflow.
Stripe and Wise flows
Screen beneficiaries, merchants, senders, or recipients before payment execution using your own payment orchestration logic.
Snowflake warehouse
Land screening records, capsule IDs, list versions, and reviewer outcomes in your audit or compliance analytics tables.
Telegram alerts
Telegram is used internally today. Customer-configurable Telegram alert delivery should remain labeled as roadmap.
Native app connectors
Packaged marketplace-style connectors can be prioritized after customer validation of specific workflows.
Workflow map
Four common places Verifex plugs in.
Onboarding screening
Call Verifex after signup or KYC collection. Store the request ID, verdict, and Evidence Capsule link in your user or account record.
Payment checkpoints
Screen beneficiaries and counterparties before transfer execution. Block, hold, or escalate according to your internal policy.
Continuous monitoring
Register watched entities and receive webhook events when a list update changes a risk profile.
Audit export
Retrieve Evidence Capsules and screening history when compliance teams need to reconstruct decisions.
Example handoff
Store the verdict and the evidence reference.
A typical integration stores compact decision fields in the operational system, while the full Evidence Capsule remains retrievable for audit review.
- request_id links the operational record to Verifex
- risk_level and recommended_action drive internal policy
- capsule_id and capsule_hash preserve the evidence trail
- webhook signatures let your system verify event delivery
{
"external_system": "case_queue",
"external_record_id": "case_48192",
"verifex": {
"request_id": "scr_01HSX2T6WJH4YBGNZ7M2P9J9T2",
"risk_level": "medium",
"recommended_action": "REVIEW",
"capsule_id": "cap_01HSX2T7K8M3ZCHPA8N3Q0K0U3",
"capsule_hash": "sha256:a1b2c3d4..."
},
"webhook": {
"event": "screening.match_changed",
"signature_header": "X-Webhook-Signature"
}
}Honest connector status. Verifex currently provides API, webhook, SDK, Slack notification, dashboard export, and Evidence Capsule surfaces. Vendor-specific native apps should be treated as integration patterns or roadmap work until shipped.