Skip to main content
Use the collections API to service active loans: create and update loans, report payment events, and stop servicing when a loan reaches a final state. Collections works alongside origination but has its own lifecycle and its own endpoints; see Origination Overview for pre-funding application outreach.

​
Collections vs. origination

  • Origination handles applications before funding. Enroll with Enroll an Application and finish with Close Origination (FUNDED, WITHDRAWN, or REJECTED).
  • Collections handles loans after funding. Create them with the Loans API and finish with Cancel Loan Servicing using a stop-servicing reason such as PAID_OFF or BANKRUPTCY.
  • Payment events are collections-only. ACH returns and settlement confirms apply to serviced loans; origination applications have no payments.
Customers, calls, texts, emails, and scheduled calls are shared Core Resources used by both products.

​
Start here

  1. Obtain an API key for the company you will send records to. The key determines the company; a request cannot select another company by changing a body field.
  2. Choose the collections task type for your setup.
  3. Create loans individually with Create Loan or in bulk with Batch Create Loans, and keep them current with Update Loan.
  4. Report payment events as they happen: Submit ACH Return for returned payments and Confirm ACH Settlement for settled ones (each also supports batch).
  5. When a loan reaches a final state, stop outreach with Cancel Loan Servicing for a single loan or Cancel Customer Servicing for every loan a customer owns.