Integrating with CreditPulse
Your engineers will read a technical reference full of endpoints, JSON, and status codes. This page explains the same thing without any of that — what connecting your systems to CreditPulse actually means, and what to ask your engineering team before they start.
What "integrating" means here
Your loan system already knows about every loan you disburse. Integrating means your engineers connect that system directly to CreditPulse, so a new loan, a new borrower, or a repayment schedule change flows across automatically — instead of someone re-typing it into a second system by hand.
The alternative is that your staff use CreditPulse's own screens directly, with no connection to your other systems at all. Most lenders end up doing some of both: staff work day-to-day inside CreditPulse, while the loan and borrower data underneath stays synced from your core system automatically.
The connection, in plain English
What happens once, and then what happens continuously.
You register once
Your engineering team creates your organization's account. This is a one-time setup step, not something repeated per loan or per borrower.
Your system sends loans across
Whenever you disburse a loan, your system tells CreditPulse about it — the borrower, the amount, and the repayment schedule. This can run automatically, e.g. every night, or be triggered the moment a loan is disbursed.
CreditPulse takes it from there
Once a loan is in, CreditPulse handles setting up the direct-debit authorization, collecting instalments, and running recovery if needed — without further input from your system.
Your system checks back for updates
If you want your own dashboards or ledger to reflect what's happening — a mandate activating, an instalment collected, a case resolved — your system asks CreditPulse periodically. See "What you won't get automatically" below before assuming this happens instantly.
What your system can ask CreditPulse to do
A capability catalogue — not a sequence, just what's available.
Manage staff & access
Create accounts for your ops and recovery staff, and control exactly what each one can see or do.
Add borrowers
Register a borrower's profile, employment details, and salary history used to predict their pay dates.
Import loans
Send loans one at a time or in bulk, matched against your own loan reference so re-sending the same loan updates it instead of duplicating it.
Set up automatic debits
Initiate the bank mandate a borrower authorizes, and check whether it's active before relying on it.
Track collections
Pull a live queue of instalments due, a debit calendar, and the outcome of every attempted collection.
Escalate to recovery
Move a loan into recovery, and follow the case — contact history, promises to pay, disputes, hardship requests — through to resolution.
Pull reports
Portfolio performance, collections performance, agent performance, and a full audit trail of every automated action taken.
Check your wallet
See your prepaid balance for SMS/WhatsApp/voice usage and top it up — this is billing infrastructure, not a collections feature.
What you won't get automatically
The one gap worth flagging to your engineers early
CreditPulse doesn't currently tap your system on the shoulder the instant something changes — a mandate activating, a debit succeeding, a recovery case resolving. Your engineers have to periodically ask ("poll") rather than being alerted in real time.
For most lenders this is fine — checking every few minutes is more than enough. But if a specific event needs to reach your system within seconds, say so before your integration is built, not after — it changes what needs to be scoped.
Terms your engineers will use
- API
- The set of instructions your system sends to CreditPulse's servers and the responses it gets back — the mechanism behind everything on this page.
- Token
- A temporary digital key your system presents with every request to prove which organization it's acting on behalf of.
- Webhook
- A message a system sends unprompted when something happens, instead of waiting to be asked. CreditPulse receives these from its own providers today, but doesn't yet send them to you — see below.
- Idempotency
- A safeguard so that retrying a request after a network hiccup can't accidentally create the same thing (like a mandate) twice.
- Tenant
- The technical name for your organization's private, isolated slice of CreditPulse — your data is never visible to another lender on the platform.
- Mock mode
- The safe default state: CreditPulse behaves exactly as it would live, but no real SMS, call, or bank debit ever actually goes out. This is a platform-wide setting, the same for every lender at any given moment.