Integration

paywise Case Management integration

paywise is a German debt-collection (Inkasso) service. Hand unpaid invoices, rent or titled claims to paywise: create debtors, build a draft order with its claims and documents, finalize it for review, then follow the accepted case (mandate): its state, balance, history, debtor emails, payments you report, paywise's questions to answer, messages, payout statements and webhooks. Debtor records and case data are personal data. Left out: the unauthenticated health check, webhook secret rotation (it returns a new signing secret), the Partner API (a Partner key acting for client companies) and the Mahnservice dunning API. Authentication is a company Case Management API key from the paywise developer portal, sent as a Bearer token; choose the production or sandbox host it belongs to (sandbox keys start with pw_sbx_).

Connect paywise Case Management How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in paywise Case Management.Built from the 112 paywise Case Management tools below, on the connection you add once.

What you can do with paywise Case Management

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Order, 7 operations

create_orderCreate orderPOSTAgents: ask firstCreates a DRAFT collection order (type invoice, rental or titled) for an existing debtor_id, optionally with its claims inline. Nothing is submitted until finalize_order. Returns the order.
delete_draft_orderDelete draft orderDELETEAgents: ask firstPermanently deletes a DRAFT order and its claims. A submitted order cannot be deleted (use withdraw_order).
finalize_orderFinalize orderPOSTAgents: ask firstSubmits a DRAFT order to paywise for review: validates it, makes it immutable and hands the debt over for collection once paywise accepts it (event order.accepted). Acts on real debtors. Returns the order.
get_orderGet orderGETAgents: ask firstReturns one order by id: type, status, debtor summary, claims, totals, starting_approach, expiry of a draft, rejection reason and the mandate once accepted. Contains personal data of debtors.
list_ordersList ordersGETAgents: ask firstLists the company's collection orders, filterable by status, type, created or updated time and a search q, sortable by ordering: debtor summary, claims, totals, status and the mandate once accepted. Contains personal data of debtors.
update_orderUpdate orderPATCHAgents: ask firstChanges a DRAFT order (PATCH: omitted fields stay): debtor_id, additional_debtor_ids (replaces the list), confirmation_email, starting_approach, creditor_obligation_fulfilled, success_fee_confirmed. Returns the order.
withdraw_orderWithdraw orderPOSTAgents: ask firstWithdraws a submitted order before paywise starts accepting it, with an optional reason. Returns the order.

Claim, 6 operations

create_receivable_claimCreate receivable claimPOSTAgents: ask firstAdds a receivable claim (an unpaid invoice or contract amount) to a DRAFT invoice, rental or titled order: principal_amount, is_disputed, dates, items, reminders, charges. Creates a record. Returns the claim.
create_titled_claimCreate titled claimPOSTAgents: ask firstAdds a titled claim (one backed by an enforceable title such as a court order) to a DRAFT titled order, with its enforceable_title. Creates a record. Returns the claim.
delete_claimDelete claimDELETEAgents: ask firstPermanently deletes a claim from a DRAFT order. A claim of a submitted order answers 409 claim_not_editable.
get_claimGet claimGETAgents: ask firstReturns one claim by id: type, status, amounts and open total, dates, items, reminders, charges, payments, legal basis, documents, enforceable title, current order_id and mandate_id.
list_claimsList claimsGETAgents: ask firstLists the company's claims (debts inside orders), filterable by order_id, status, document_reference, your_reference or updated_since: type, status, amounts, dates, items, reminders, payments, order_id and mandate_id.
update_claimUpdate claimPATCHAgents: ask firstChanges a claim in a DRAFT order (PATCH: omitted fields stay; a supplied items, reminders or additional_charges array replaces the whole list). Receivable-only fields are refused on titled claims. Returns the claim.

Webhook, 6 operations

create_webhookCreate webhookPOSTAgents: ask firstSubscribes a public HTTPS url to paywise events (all with ["*"]). The one-time signing secret is withheld, so deliveries to this endpoint cannot be verified. Returns the webhook.
delete_webhookDelete webhookDELETEAgents: ask firstPermanently deletes a webhook endpoint; no further deliveries are sent to it.
get_webhookGet webhookGETAgents: ask firstReturns one webhook endpoint: URL, subscribed events, enabled, auto_disabled, consecutive failures and last failure time.
list_webhooksList webhooksGETAgents: ask firstLists the company's webhook endpoints, filterable by enabled: URL, subscribed events, enabled, auto-disable state, failure counters. The signing secret is never returned.
test_webhookTest webhookPOSTAgents: ask firstSends a synthetic test delivery of one subscribed event type to a webhook endpoint (shares a limit of 20 per hour with redeliveries). Returns detail, delivery_id and event_id.
update_webhookUpdate webhookPATCHAgents: ask firstChanges a webhook endpoint (PATCH: omitted fields stay): url, events (replaces the list), description, enabled (true re-enables and resets failures), max_consecutive_failures. Returns it.

Claim document, 5 operations

create_claim_documentCreate claim documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_claim_document until status is ready. Claim must be in a draft order.
delete_claim_documentDelete claim documentDELETEAgents: ask firstPermanently deletes an editable document from a claim in a draft order.
download_claim_documentDownload claim documentGETAgents: ask firstDownloads the file of a ready claim document (status ready). Downloads count against 120 per hour per company.
get_claim_documentGet claim documentGETAgents: ask firstReturns one claim document: type, filename, MIME type, status (pending, ready or failed; poll after an upload until ready) and failure_reason.
list_claim_documentsList claim documentsGETAgents: ask firstLists the documents attached to one claim: id, type, filename, MIME type, status (pending, ready or failed), failure_reason and download_url.

Debtor, 5 operations

create_business_debtorCreate business debtorPOSTAgents: ask firstCreates a business debtor: legal_form (from list_legal_forms) with organization or person, addresses, emails and phones, bank accounts, legal representatives. Creates a record. Returns the debtor.
create_consumer_debtorCreate consumer debtorPOSTAgents: ask firstCreates a consumer debtor (a private person): person with first_name and last_name, addresses, emails and phones, bank accounts, legal representatives. Creates a record holding personal data. Returns the debtor.
get_debtorGet debtorGETAgents: ask firstReturns one debtor by id: person or organization, legal form, addresses, emails and phones, bank accounts (IBAN), legal representatives, metadata and events. Contains personal data of debtors.
list_debtorsList debtorsGETAgents: ask firstLists the company's reusable debtors, filterable by acting_as, id, your_reference or updated_since: names, birth dates, addresses, legal form, organization details. Contains personal data of debtors.
update_debtorUpdate debtorPATCHAgents: ask firstChanges a debtor (PATCH: omitted fields stay; a supplied addresses, bank_accounts, communication_channels or legal_representatives array replaces that whole list). Returns the debtor.

Enforceable title document, 5 operations

create_enforceable_title_documentCreate enforceable title documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_enforceable_title_document until status is ready. The enforceable_title type is required before finalizing.
delete_enforceable_title_documentDelete enforceable title documentDELETEAgents: ask firstPermanently deletes an editable enforceable-title document of a claim in a draft order.
download_enforceable_title_documentDownload enforceable title documentGETAgents: ask firstDownloads the file of a ready enforceable-title document. Downloads count against 120 per hour per company.
get_enforceable_title_documentGet enforceable title documentGETAgents: ask firstReturns one enforceable-title document: type, filename, MIME type, status (pending, ready or failed; poll after an upload until ready) and failure_reason.
list_enforceable_title_documentsList enforceable title documentsGETAgents: ask firstLists the documents of a claim's enforceable title: id, type (enforceable_title or other), filename, MIME type, status and download_url.

Mandate message document, 5 operations

create_mandate_message_documentCreate mandate message documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_mandate_message_document until status is ready.
delete_mandate_message_documentDelete mandate message documentDELETEAgents: ask firstPermanently deletes an editable document from a case message.
download_mandate_message_documentDownload mandate message documentGETAgents: ask firstDownloads the file of a ready case-message document. Downloads count against 120 per hour per company.
get_mandate_message_documentGet mandate message documentGETAgents: ask firstReturns one case-message document: type, filename, MIME type, status (pending, ready or failed; poll after an upload until ready) and failure_reason.
list_mandate_message_documentsList mandate message documentsGETAgents: ask firstLists the documents attached to one case message: id, type, filename, MIME type, status and download_url.

Mandate request answer document, 5 operations

create_mandate_request_answer_documentCreate mandate request answer documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_mandate_request_answer_document until status is ready. Allowed until paywise starts reviewing the answer.
delete_mandate_request_answer_documentDelete mandate request answer documentDELETEAgents: ask firstPermanently deletes a document from your answer to a case question, until paywise starts reviewing it.
download_mandate_request_answer_documentDownload mandate request answer documentGETAgents: ask firstDownloads the file of a ready document of your answer to a case question. Downloads count against 120 per hour per company.
get_mandate_request_answer_documentGet mandate request answer documentGETAgents: ask firstReturns one document of your answer to a case question: type, filename, MIME type, status (pending, ready or failed) and failure_reason.
list_mandate_request_answer_documentsList mandate request answer documentsGETAgents: ask firstLists the documents added to your answer to a question about an accepted case: id, type, filename, status and download_url.

Order message document, 5 operations

create_order_message_documentCreate order message documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_order_message_document until status is ready.
delete_order_message_documentDelete order message documentDELETEAgents: ask firstPermanently deletes an editable document from an order message.
download_order_message_documentDownload order message documentGETAgents: ask firstDownloads the file of a ready order-message document. Downloads count against 120 per hour per company.
get_order_message_documentGet order message documentGETAgents: ask firstReturns one order-message document: type, filename, MIME type, status (pending, ready or failed; poll after an upload until ready) and failure_reason.
list_order_message_documentsList order message documentsGETAgents: ask firstLists the documents attached to one order message: id, type, filename, MIME type, status and download_url.

Order request answer document, 5 operations

create_order_request_answer_documentCreate order request answer documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_order_request_answer_document until status is ready. Allowed until paywise starts reviewing the answer.
delete_order_request_answer_documentDelete order request answer documentDELETEAgents: ask firstPermanently deletes a document from your answer to an order question, until paywise starts reviewing it.
download_order_request_answer_documentDownload order request answer documentGETAgents: ask firstDownloads the file of a ready document of your answer to an order question. Downloads count against 120 per hour per company.
get_order_request_answer_documentGet order request answer documentGETAgents: ask firstReturns one document of your answer to an order question: type, filename, MIME type, status (pending, ready or failed) and failure_reason.
list_order_request_answer_documentsList order request answer documentsGETAgents: ask firstLists the documents added to your answer to a question about an order: id, type, filename, status and download_url.

Rental agreement document, 5 operations

create_rental_agreement_documentCreate rental agreement documentPOSTAgents: ask firstUploads a PDF, JPEG or PNG (at most 10 MiB, PDFs at most 100 pages) as a multipart file with its type; processing is asynchronous: poll get_rental_agreement_document until status is ready.
delete_rental_agreement_documentDelete rental agreement documentDELETEAgents: ask firstPermanently deletes an editable document of a draft rental order's agreement.
download_rental_agreement_documentDownload rental agreement documentGETAgents: ask firstDownloads the file of a ready rental-agreement document. Downloads count against 120 per hour per company.
get_rental_agreement_documentGet rental agreement documentGETAgents: ask firstReturns one rental-agreement document: type, filename, MIME type, status (pending, ready or failed; poll after an upload until ready) and failure_reason.
list_rental_agreement_documentsList rental agreement documentsGETAgents: ask firstLists the documents of a rental order's agreement: id, type (rental_agreement, claim_statement or other), filename, status and download_url.

Enforceable title, 4 operations

delete_enforceable_titleDelete enforceable titleDELETEAgents: ask firstPermanently removes the enforceable title from a titled claim in a draft order.
get_enforceable_titleGet enforceable titleGETAgents: ask firstReturns the enforceable title of a titled claim: title_type, file number, issuing authority, issue, service and binding dates, amount and its documents.
replace_enforceable_titleReplace enforceable titlePUTAgents: ask firstCreates or replaces the WHOLE enforceable title of a titled claim in a draft order: fields left out are cleared. Read get_enforceable_title first and send every field to keep. Returns the title.
update_enforceable_titleUpdate enforceable titlePATCHAgents: ask firstChanges individual fields of a titled claim's enforceable title in a draft order (PATCH: omitted fields stay). Returns the title.

Mandate message, 4 operations

create_mandate_messageCreate mandate messagePOSTAgents: ask firstSends a message (title and body, optional documents) to paywise about one accepted case. paywise staff read it. Returns the message.
get_mandate_messageGet mandate messageGETAgents: ask firstReturns one message about an accepted case: title, body, sender, author, state, documents and whether it is still editable.
list_mandate_messagesList mandate messagesGETAgents: ask firstLists the messages exchanged with paywise about one accepted case: title, body, sender, author, state, documents and whether each is still editable.
update_mandate_messageUpdate mandate messagePATCHAgents: ask firstChanges the title or body of an editable message you sent about an accepted case. Returns the message.

Order message, 4 operations

create_order_messageCreate order messagePOSTAgents: ask firstSends a message (title and body, optional documents) to paywise about one order. paywise staff read it. Returns the message.
get_order_messageGet order messageGETAgents: ask firstReturns one message about an order: title, body, sender, author, state, documents and whether it is still editable.
list_order_messagesList order messagesGETAgents: ask firstLists the messages exchanged with paywise about one order: title, body, sender, author, state, documents and whether each is still editable.
update_order_messageUpdate order messagePATCHAgents: ask firstChanges the title or body of an editable message you sent about an order. Returns the message.

Claim payment, 3 operations

create_claim_paymentCreate claim paymentPOSTAgents: ask firstReports a payment the debtor made directly to you on one claim (amount, value_date not in the future). On an accepted case it reduces the case balance. Needs case:payments:write. Returns the payment.
delete_claim_paymentDelete claim paymentDELETEAgents: ask firstPermanently deletes a payment reported on a claim, only while its order is a draft. Needs the case:payments:write scope.
list_claim_paymentsList claim paymentsGETAgents: ask firstLists the payments you reported on one claim, in every lifecycle state: amount, value_date, your_reference and metadata. Needs the case:payments:read scope.

Mandate correspondence, 3 operations

download_correspondence_pdfDownload correspondence pdfGETAgents: ask firstDownloads a debtor email on a case as a PDF (header block and plain text) rendered by paywise. Downloads count against 120 per hour per company.
get_mandate_correspondence_itemGet mandate correspondence itemGETAgents: ask firstReturns one email between paywise and the debtor on a case: subject, addresses, plain-text body and attachments. Needs case:correspondence:read. Contains personal data of debtors.
list_mandate_correspondenceList mandate correspondenceGETAgents: ask firstLists the emails exchanged between paywise and the debtor on a case, filterable by direction and channel: subject, time, addresses. Needs case:correspondence:read. Contains personal data of debtors.

Mandate request to client, 3 operations

answer_mandate_request_to_clientAnswer mandate request to clientPOSTAgents: ask firstAnswers a paywise question about an accepted case, once: text (yes, no, dontknow or free text per allowed_answer_types), booking_date, additional_comment, documents. Cannot be changed afterwards.
get_mandate_request_to_clientGet mandate request to clientGETAgents: ask firstReturns one question paywise asked about an accepted case: title, description, allowed_answer_types, question attachments and the answer once given.
list_mandate_requests_to_clientList mandate requests to clientGETAgents: ask firstLists the questions paywise published about an accepted case, filterable by answered: title, description, allowed_answer_types, attachments and any answer.

Order request to client, 3 operations

answer_order_request_to_clientAnswer order request to clientPOSTAgents: ask firstAnswers a paywise question about an order, once: text (yes, no, dontknow or free text per allowed_answer_types), booking_date, additional_comment, documents. Cannot be changed afterwards.
get_order_request_to_clientGet order request to clientGETAgents: ask firstReturns one question paywise asked about an order: title, description, allowed_answer_types, question attachments and the answer once given.
list_order_requests_to_clientList order requests to clientGETAgents: ask firstLists the questions paywise published about one order (review pauses until all are answered), filterable by answered: title, description, allowed_answer_types, attachments and any answer.

Single mandate statement, 3 operations

download_single_mandate_statementDownload single mandate statementGETAgents: ask firstDownloads the PDF of one per-case settlement (Aktenabrechnung). Downloads count against 120 per hour per company.
get_single_mandate_statementGet single mandate statementGETAgents: ask firstReturns one per-case settlement (Aktenabrechnung): type, status, booking date, invoice number and financial breakdown.
list_single_mandate_statementsList single mandate statementsGETAgents: ask firstLists published per-case settlements (Aktenabrechnungen), filterable by case, type, status, booking date, invoice or clearing number: amounts and booking dates.

Statement, 3 operations

download_statementDownload statementGETAgents: ask firstDownloads a payout statement file: the PDF (type full-pdf, the vendor default) or one of the three Excel exports. Downloads count against 120 per hour per company.
get_statementGet statementGETAgents: ask firstReturns one payout statement: period, booking date, invoice and clearing numbers, financial breakdown and the cases it includes.
list_statementsList statementsGETAgents: ask firstLists published payout statements (Sammelabrechnungen), filterable by period, booking date, status, invoice or clearing number: totals and the money paid out to you.

Webhook delivery, 3 operations

get_webhook_deliveryGet webhook deliveryGETAgents: ask firstReturns one webhook delivery: status, attempts, last response code and body, error message, next retry and the exact payload sent.
list_webhook_deliveriesList webhook deliveriesGETAgents: ask firstLists webhook delivery attempts, filterable by webhook, event_type, status or updated_since: status, attempts, response code and body, error message and the payload sent.
redeliver_webhook_deliveryRedeliver webhook deliveryPOSTAgents: ask firstSends a settled delivery (success or failed) again as a new delivery with the same event_id (shares a limit of 20 per hour with tests). Returns detail, delivery_id and event_id.

Mandate, 2 operations

get_mandateGet mandateGETAgents: ask firstReturns one accepted case by id: reference number, debtor, claims, processing, legal and payment state, legal balance, subcases, and with history=true up to 100 history entries. Contains personal data of debtors.
list_mandatesList mandatesGETAgents: ask firstLists accepted cases (mandates, main cases only), filterable by states, open client requests, archived, dates, reference_number or q: reference number, debtor, claims, state and balance. Contains personal data of debtors.

Mandate document, 2 operations

download_mandate_documentDownload mandate documentGETAgents: ask firstDownloads one claim document of an accepted case. Downloads count against 120 per hour per company.
list_mandate_documentsList mandate documentsGETAgents: ask firstLists the claim documents of an accepted case: id, type, filename, MIME type, status and download_url.

Mandate payment, 2 operations

create_mandate_paymentCreate mandate paymentPOSTAgents: ask firstReports a payment the debtor made directly to you on an accepted case (amount, value_date not in the future); it reduces the case balance. Reports are immutable. Needs case:payments:write. Returns it.
list_mandate_paymentsList mandate paymentsGETAgents: ask firstLists the payments reported on an accepted case (main case or subcase): amount, value_date, your_reference and metadata.

Payment, 2 operations

get_paymentGet paymentGETAgents: ask firstReturns one reported payment by id: amount, value_date, your_reference, metadata, claim and mandate.
list_paymentsList paymentsGETAgents: ask firstLists every payment reported on the company's claims and cases, filterable by claim, mandate, value date range, your_reference or updated_since: amount, value_date, claim and mandate.

Rental agreement, 2 operations

get_rental_agreementGet rental agreementGETAgents: ask firstReturns the rental agreement of a rental order: contract date, monthly rent (Warmmiete), due-date rule, property address and its documents.
update_rental_agreementUpdate rental agreementPATCHAgents: ask firstChanges the rental agreement of a DRAFT rental order (PATCH: omitted fields stay): contract_date, monthly_rent, due_rule, property_address. Returns the agreement.

Correspondence attachment, 1 operation

download_correspondence_attachmentDownload correspondence attachmentGETAgents: ask firstDownloads one attachment of a debtor email on a case. Downloads count against 120 per hour per company.

Credential, 1 operation

get_credential_infoGet credential infoGETAgents: ask firstReturns the API key in use: its id and name, company id, environment (production or sandbox) and granted scopes.

Event, 1 operation

list_eventsList eventsGETAgents: ask firstReturns one page of the company's event feed (last 30 days), oldest first, filterable by event_type: id, type, time and affected resource ids. Pass the answer's cursor as since on the next call.

Legal form, 1 operation

list_legal_formsList legal formsGETAgents: ask firstReturns the catalog of legal forms a business debtor can have: code (for legal_form), label, group and the representative roles each requires.

Mandate history attachment, 1 operation

download_mandate_history_attachmentDownload mandate history attachmentGETAgents: ask firstDownloads a file published with a history entry of an accepted case. Downloads count against 120 per hour per company.

Mandate history entry, 1 operation

list_mandate_historyList mandate historyGETAgents: ask firstLists the published history of an accepted case (main case with its subcases): title, description, type, state values, attachments and related resources (bodies with expand).

Mandate request attachment, 1 operation

download_mandate_request_attachmentDownload mandate request attachmentGETAgents: ask firstDownloads a file paywise attached to a question about an accepted case. Downloads count against 120 per hour per company.

Order request attachment, 1 operation

download_order_request_attachmentDownload order request attachmentGETAgents: ask firstDownloads a file paywise attached to a question about an order. Downloads count against 120 per hour per company.

Rate limit, 1 operation

get_rate_limit_usageGet rate limit usageGETAgents: ask firstReturns the current usage of every rate-limit bucket of the API key: limit, used, remaining, window and reset time. The call itself counts against the limits.

Statement case, 1 operation

list_statement_casesList statement casesGETAgents: ask firstLists the accepted cases included in one payout statement, page by page, filterable by case or claim reference: per-case amounts, costs and money paid out. Contains personal data of debtors.

Use paywise Case Management from Claude Code, Cursor or Codex

Connect paywise Case Management in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its paywise Case Management operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect paywise Case Management

Create your workspace
Sign up free. Nothing to install.
Connect paywise Case Management once
Add your paywise Case Management connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.