Skip to content

Know where your data goes.

Follow the invoice into the collection operation, understand who can access the file, and inspect the records returned to your business.

Request a security walkthrough

The collection file connects the work.

Your invoice

Business details, balance, contact information, and supporting documents.

Modern Collections

The placement holds outreach, correspondence, disputes, and payment records. Connected providers perform specific collection tasks.

Review provider information

Updates back to you

Activity, payment and remittance records through the dashboard, API and webhooks.

Collection data flow. The exact provider and deployment scope is part of your security review.

Access follows the job.

The creditor workspace, debtor portal, and administrative tools use separate authorization paths.

Creditor workspace
Account-scoped access to placements, correspondence, evidence, and financial records.
Debtor portal
A separate access flow for the debtor’s collection file, with verification for protected actions.
Operations
Administrator authorization is separate from creditor and portal access.

Records you can trace.

Understand what happened without treating an attempted payment as money already received.

Signed webhook deliveries
Outbound webhooks include signature information. The integration guide shows how to verify the signature and handle duplicate deliveries. Inspect the examples.
Append-only audit events
Decisions and activity add to the audit record. Later events preserve the history of earlier actions.
Separate payment handling
Card checkout uses a hosted payment flow. Payment processing, received cash, and creditor remittance have distinct records. Explore the portal example.

Bring your requirements.

Share the data categories, access requirements, and security questionnaire relevant to your evaluation. We can discuss the current deployment, hosting regions, encryption, retention, and recovery practices.

A SOC 2 report is not currently available.