Compliance & security — a compliance collections platform
Built around the operating principles regulated Nigerian lenders need — stated plainly, with no claim beyond what is actually implemented.
Compliance is a determination, not a checkbox
Using CreditPulse does not by itself constitute legal or regulatory compliance. It is technology and orchestration for your team — the compliance determination rests with your organisation and counsel, informed by FCCPC and CBN guidance.
We never hold customer funds
CreditPulse does not hold, pool, or settle customer funds. Debits are authorised by mandate and executed through your licensed payment provider.
Sensitive data is masked
Mandate credentials, call transcripts, and message bodies are excluded from ordinary logs and masked in API responses by role.
Multi-tenant isolation
Every tenant-scoped record is isolated at both the query and database-filter level, verified by dedicated cross-tenant integration tests.
Append-only audit trail
Every automated debit or recovery action is attributable to the actor, the exact rule version evaluated, and the provider reference — never mutated after the fact.
Disputes and hardship pause automation
Raising a dispute or hardship case creates a compliance hold that blocks further automated debit or contact for that customer until it is resolved.
Idempotent, no silent duplicates
Debit attempts, webhooks, imports, and notifications all carry stable idempotency keys, so retries and replayed provider events can never double-charge or double-contact a customer.
Sandbox-first integrations
Voice, SMS, and WhatsApp providers ship with a mock/sandbox implementation by default. Moving to a live provider is a configuration change, documented for your engineering team before you flip it.
Questions from your compliance or risk team? Reach out before your demo and we'll come prepared with answers specific to your regulatory context.