Understand Debitura
Explanations of how Debitura works for referral partners, including roles, incentives, and lifecycle expectations.
8 articles
- Referral Partners: What your client sees during onboardingWalkthrough of the Debitura onboarding experience your customer goes through after you click 'Send to Collection'. Covers the 7 steps, the white-label branding, and the rare jurisdiction pricing edge case.
- Referral Partners: White-label customization and branding optionsDebitura offers white-label customization so your customers experience a seamless, branded journey when using debt collection services through your platform.
- Referral Partners: Referral program overview (what you earn, when, and what counts)The Debitura Referral Partner Program lets you earn ongoing revenue by embedding debt collection capabilities into your platform. You earn a share of Debitura's platform revenue whenever your customers successfully…
- Referral Partners: API & integration overview (what's possible)Debitura provides a comprehensive API that allows referral partners to embed debt collection capabilities directly into their platforms. This overview explains what you can build, helping you scope an integration
- Referral Partners: Data privacy and DPA considerationsThis article explains how data privacy works within the Debitura platform, what Data Processing Agreements (DPAs) are, and what you should know as a referral partner about the handling of…
- Referral Partners: Revenue sharing and financial reconciliationAs a referral partner, you earn a percentage of Debitura's platform revenue each time a case you helped bring to the platform results in a successful collection.
- Referral Partners: Using the dashboard to track cases and earningsThe Referral Partner Dashboard is a web-based portal where you can track all collection cases across your linked clients, monitor your referral earnings through each revenue stage, and manage your…
- Referral Partners: 409 conflict path - what your customer sees and what your platform doesWalkthrough of the 409 ClientExistsNeedsLinking path: what your customer sees, what your platform receives, how cases carry through automatically, and which webhooks fire.