01
Credit and obligation
context before outreach
Digital collections for credit fintechs
Automate credit collections without replacing your lending core
Certeza organizes obligations, delinquency, promises, and payments; coordinates outreach under approved rules; and keeps fraud, disputes, and exceptions visible.
Your core keeps origination, balances, and interest. Your gateway processes funds. Certeza does not lend money, negotiate consumer debt, or hold funds.
- balance and aging context
- By obligation
- coordinated channels
- 4+
- of the lending core
- No replacement
Certeza key points
02
Aging and response
rule-based prioritization
03
Promises and payments
verifiable follow-up
04
Fraud and disputes
cases outside automation
Fintech receivables operations
Scale follow-up without losing control of each obligation
Certeza runs repetitive operations under approved rules while keeping sensitive decisions with the accountable team.
01
01
Portfolio by credit and obligation
Relate customer, product, obligation, installment, due date, balance, and status so each message uses current, minimal information.
02
02
Operational segmentation
Prioritize by aging, balance, response, and promise under approved criteria; Certeza does not replace risk scoring or underwriting decisions.
03
03
Coordinated authorized outreach
WhatsApp, SMS, email, calls, and tasks follow authorized channels, timing, frequency, exclusions, and do-not-contact requests.
04
04
Promises, agreements, and partial payments
Record promised date, amount, response, partial payment, and next step without offering terms the fintech has not approved.
05
05
Reconciliation by obligation
Match reference, obligation, amount, and date. Ambiguous, duplicate, or reversed payments remain in review before status changes.
06
06
Pause fraud, impersonation, and disputes
Cases reported as fraud, identity theft, or dispute immediately leave the flow and preserve evidence for the relevant investigation.
How it works
From a controlled sample to an auditable operation
Integration starts read-only, with minimal data and rules reviewed by operations, risk, security, and legal teams.
- 01
Connect obligations and payments
Use a file or assessed API with identifier, product, obligation, installment, balance, due date, authorized contact, dispute, and payment.
- 02
Test real exceptions
Validate partial payments, approved restructures, promises, reversals, duplicates, fraud, impersonation, disputes, and do-not-contact requests.
- 03
Approve rules and controls
The fintech defines segments, messages, authorized terms, timing, frequency, escalation, retention, and role-based access.
- 04
Run coordinated follow-up
Certeza records responses and promises and stops activity after payment, dispute, fraud, or an authorized team instruction.
- 05
Reconcile and audit
Reliable payments follow the agreed flow; exceptions are reviewed and every action preserves its owner, time, and outcome.
On top of your lending core
Connect receivables and outcomes without turning Certeza into a lender or gateway
Technical scope is validated before any integration is advertised. A pilot can start with encrypted files and a limited sample.
1Excel, CSV, or encrypted exchange
2Lending or receivables core
3Bank, gateway, and references
4WhatsApp, SMS, email, and calls
Operational outcome
Continuous follow-up with sensitive exceptions under control
We measure contactability, promises, payments, correct stops, and manual work; we do not promise recovery or automatic compliance.
More operational continuity. Fewer sensitive decisions outside control.
- Obligations prioritized by approved rules and current data.
- Promises, partial payments, responses, and next steps remain traceable.
- Reliable payments are reconciled and exceptions isolated.
- Fraud, impersonation, dispute, and no-contact cases leave the flow.
Questions from fintech teams
What must be validated before connecting a credit portfolio
An operational collections and reconciliation layer that preserves the core, gateway, and risk decisions.
Credit fintechs
01Does Certeza lend money or negotiate debt?
No. Certeza is B2B software and operations for the creditor. It does not originate credit, buy portfolios, change rates, repair credit history, or offer consumers terms not authorized by the fintech.
02Must we replace our lending core?
No. The core keeps contracts, installments, interest, balances, risk, and official states. Certeza receives a minimal dataset for follow-up and returns responses, promises, payments, or exceptions.
03Does Certeza receive payments?
No. The contracted financial provider or gateway processes funds. Certeza can expose the existing payment link and match references to obligations; uncertain matches are never applied automatically.
04How are channels and timing controlled?
The fintech documents authorized channels and approves timing, frequency, tone, exclusions, and escalation. The pilot validates these constraints and preserves evidence; configuration alone is not a compliance guarantee.
05What happens after fraud, impersonation, or dispute?
The case is marked do not contact and automation stops for the affected amount. The fintech owns the investigation and legal decision; Certeza records evidence and resumes only after an authorized instruction.
06How is security assessed before a pilot?
We define allowed data, encryption, roles, logs, retention, deletion, incident handling, and owners. We start with a limited sample and no unnecessary data before considering production connectivity.
Assessment for credit fintechs
Let's review your portfolio, rules, and payment sources before automating
Tell us the credit type, obligation volume, current core, and major exceptions. Do not submit customer data in this form.