Compliance

Coordinate verification, screening, monitoring, jurisdictional requirements, and human review as part of the payment lifecycle.

Compliance workspace

Coordinate responsible payment activity

Bring identity requirements, sanctions screening, transaction monitoring, jurisdictional rules, and human review into the payment lifecycle before settlement.

No compliance providers connected

Open reviews

—

Requires connected compliance activity.

Verification status

—

Requires connected participants.

Monitoring alerts

—

Requires transaction-monitoring history.

Sanctions checks

—

Requires screening activity.

Overview

Review identity requirements, monitoring coverage, sanctions checks, and compliance readiness.

No verified records

RecordTypeStatusUpdated

No compliance activity yet

Connected verification, screening, monitoring, and review records will appear here after compliance providers and Runtime activity are available.

Identity-awareJurisdiction-awareMonitoredReviewable

Identity requirements

Apply the appropriate verification level based on participant type and transaction context.

Jurisdiction awareness

Coordinate requirements based on geography, business activity, and supported payment rails.

Ongoing monitoring

Evaluate activity over time instead of treating compliance as a single onboarding event.

Human review

Escalate uncertain or higher-risk activity when automated controls are not enough.

Before settlement

Evaluate requirements before value moves.

Verification, sanctions screening, jurisdictional rules, and monitoring signals can be coordinated before settlement becomes difficult to reverse.

Ongoing context

Treat compliance as a continuous process.

Participant status, transaction behavior, jurisdiction, and review outcomes should remain connected throughout the economic relationship.

Explainable review

Preserve why a decision was made.

Automated checks and human review can remain attached to the same event so approvals, holds, and escalations retain their context.