Skip to main content
Use the collections API to service active loans: create and update loans, manage ACH authorizations, 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.

Manage ACH authorization

ACH authorization revocation is available for Collections only. The authorization belongs to a specific bank-account payment method, so identify that method before submitting a revocation.
  1. List Customer Payment Methods using the customer’s external reference and your company API key.
  2. Identify the intended BANK_ACCOUNT entry and retain its Finosu paymentMethodId. Last-four digits are not unique; do not choose the first or default method merely because it is listed. Method status does not establish ACH authorization.
  3. Revoke ACH Authorization for that exact customer and method with revokeAuthorization: true.
Revocation applies to one bank-account payment method. If the intent is to revoke all of the customer’s bank authorizations, paginate the full list and submit a separate request for each BANK_ACCOUNT ID. Inspect every response; these requests are not an atomic bulk action. Repeating true is idempotent. Sending false cannot restore revoked consent; a new customer authorization must be captured through the normal authorization workflow. See the endpoint for its full request and error contract.