Skip to main content

Responsibility Matrix

Who does what in a referral partner integration.

:::warning Debitura does not email your clients Debitura never emails onboarding, approval, signing, or KYC URLs to your clients. You are responsible for delivering every URL — in-app, by redirect, or via your own emails. :::

Client Communication

ResponsibilityOwner
Deliver onboarding URLs to clientsYou
Deliver signing URLs (solutionUrl from 422 errors) to clientsYou
Deliver 409 approval URLs to clientsYou
Deliver KYC form URLs to clientsYou
Send welcome email after SDCA signing (if SendGrid template configured)Debitura (using your template and domain)

Client Onboarding

ResponsibilityOwner
Initiate onboarding via POST /clientsYou
Host the white-label onboarding UI (company details, SDCA signing)Debitura
Choose and store externalTenantIdYou
Handle all POST /clients response codes (201, 202, 409 variants)You
Re-present onboarding URL if client abandons mid-flowYou
Apply partner branding (logo, colors, fonts) to hosted flowsDebitura
Expire link requests after the configured TTL (default 7 days, max 30, set per-partner)Debitura
Receive client.link_requested / client.link_expired webhooks and re-issue approval URLs on expiryYou

Case Submission and Collection

ResponsibilityOwner
Mint bearer tokens and submit cases to the Customer APIYou
Validate required case fields before submissionYou
Route cases to collection partners by jurisdictionDebitura
Enforce contract and KYC requirements (return 422 with solutionUrl)Debitura
Perform debt recovery (contact debtors, legal escalation, payment collection)Collection partner (not Debitura)
Surface case status to your clients via webhooks or pollingYou

Contract Management

ResponsibilityOwner
Host SDCA, PoA, KYC, and JPA signing flowsDebitura
Detect missing signatures and return solutionUrlDebitura
Catch 422 errors and redirect clients to signing URLsYou
Implement retry-after-signing flowYou
Decide allowPendingContracts rollout strategyYou

Revenue and Invoicing

ResponsibilityOwner
Calculate referral fees at each pipeline stageDebitura
Lock USD amount when collection partner pays platform commissionDebitura
Call GET /reporting/transactions to retrieve fee dataYou
Send monthly invoice to Debitura for "Ready to Invoice" feesYou
Process payment after receiving the partner's invoice (net 10 business days)Debitura
Reconcile invoice amounts against API dataYou

Business context: See Referral program overview for commercial terms and fee structure.

Webhooks

ResponsibilityOwner
Fire webhook events on state changesDebitura
Retry failed deliveries (up to 8 times, exponential backoff)Debitura
Auto-disable subscriptions after 8 consecutive failuresDebitura
Register and maintain webhook subscriptionsYou
Save the signing secret at creation (shown only once)You
Verify HMAC signatures on every incoming eventYou
Respond within 10 seconds, process asynchronouslyYou
Implement idempotency using event.idYou
Monitor and re-enable disabled subscriptionsYou

Common Assumption Violations

Things partners frequently assume Debitura handles — but does not:

AssumptionReality
Debitura sends onboarding emailsNo. You must deliver every URL.
Debitura sends follow-up emails for signing or KYCNo. You must surface solutionUrl from 422 errors.
Debitura pays referral fees automaticallyNo. You must invoice Debitura monthly.
allowPendingContracts bypasses KYCNo. KYC is always a hard 422 block.
Bearer tokens can be refreshedNo. Mint a new token on expiry (30-min lifetime).
Webhook delivery is exactly-onceNo. At-least-once — implement idempotency.
Once SDCA is signed, no further signing is neededNo. New jurisdictions, carveouts, and renewals can require new signatures.
Partners can choose which collection partner handles a caseNo. Debitura routes by jurisdiction.
Fee percentage changes apply to existing clientsNo. Fee is snapshotted at link creation and frozen.
Debitura performs debt collectionNo. Collection partners (agencies) do the recovery work.