Skip to content

Compliance built into the platform.

KYB, KYC, sanctions and PEP screening, and financial-risk assessment on every counterparty, not a vendor stack you assemble.

POST/v1/identity
HTTP
x-api-key: $CFX_API_KEY
x-api-secret: $CFX_API_SECRET
Content-Type: application/json

{
  "referenceId": "customer-ref-123",
  "countryOfResidence": "US",
  "email": "user@example.com",
  "phone": "+12125551234",
  "name": { "firstName": "John", "lastName": "Doe" },
  "dateOfBirth": "1980-10-23"
}
Verified
Person
id_VfsdSMtd8…
Status
Active
AML screening
Approved
ID document
Approved

Screening approved; the person can transact.

Controls, not a checklist.

Counterparties run through KYB, KYC, sanctions, and PEP screening at onboarding, sanctions screening runs as transactions initiate, and financial-risk is assessed in line — all with an audit-grade record you can hand to a regulator. Screening runs through ComplyAdvantage, Middesk, and IRS TIN Match, with financial-risk signals from Heron and decisioning on the CFX Risk Engine.

  • KYB and KYC onboarding
  • Sanctions and PEP screening
  • Financial-risk assessment
  • Audit-grade records

Screening results, and the review queue.

Screening runs on every party, with an audit-grade trail: clear results flow through, edge cases route to a reviewer.

How it works.

  1. Verify

    Register a business or a person; KYB or KYC and document checks run on it.

  2. Screen

    Sanctions, PEP, and adverse-media screening run on every counterparty.

  3. Monitor

    Financial-risk signals are assessed on every transaction, continuously.

In the API.

POST /v1/organizationRegister a business and its related people for verification.
POST /v1/identityRegister a person; KYC, AML, and document checks run on them.
identity.verification.statusUpdatedA webhook as each check resolves. A person is verified once every check approves.

Ready to build on regulated U.S. banking rails?

Sign up, spin up a sandbox, and make your first call the same day.