> ## Documentation Index > Fetch the complete documentation index at: https://docs.paywise.de/llms.txt > Use this file to discover all available pages before exploring further. # Pause the dunning process > Pauses dunning for this invoice (pause_reason "user"). Idempotent on a repeat. 409 (codes: not_released, invoice_in_inkasso, already_paused -- paused under a different hold, invalid_status, invoice_paid / invoice_cancelled / invoice_written_off, not_api_invoice) when there is no dunning process yet or it is paused otherwise, settled or at debt collection. **Draft documentation — API not yet rolled out.** This endpoint describes the preview contract and may change before release. Sandbox access is provided separately. See [access and limitations](/api-docs/mahnservice-api/introduction). ## OpenAPI ````yaml api-docs/mahnservice-api/openapi.json POST /mahnservice/v1/invoices/{uuid}/dunning/pause/ openapi: 3.0.3 info: title: paywise Mahnservice API version: v1 description: >- Public REST API for the paywise Mahnservice (pre-collection dunning), an alternative input path to the bookkeeping integrations (Lexware Office, sevDesk) and the CSV import. Authentication uses a Bearer token (the same token works for the Inkasso API). Each token is bound to a company and a legacy access mode: `test` or `production`. Access mode is a data-isolation lane, not the API environment: modern credentials use `production` in both production and sandbox. Read `/info/`'s `environment` (`production` or `sandbox`) to identify the environment serving your request. Resources: token introspection (`/info/`), debtors (create/list/get), and the invoice lifecycle -- submit (held), upload the invoice PDF (multipart or base64; scanned asynchronously, poll the document `status`), release for dunning, report payments, cancel / write off, and read the dunning state (`dunning_state`, the dunning flow and the sent dunnings with their fees), pause and resume the dunning, and read the dunning-flow configuration (`/dunning-flows/`). Webhooks notify you about `invoice.created`, `invoice.paid`, `invoice.cancelled`, `invoice.written_off`, `dunning.level_advanced` and `dunning.handed_to_collection`. Test-mode invoices are visible everywhere but never dunned, and their events only reach test-mode endpoints. Contract: requests are JSON only (documents may also be multipart); unknown or read-only body fields and unknown query parameters are rejected with `400`; list pages take `limit` (1-100, default 10) and `offset`. Errors are English and machine-readable: every error body is `{detail, code[, errors]}` -- branch on `code` (`validation_error` with per-field `errors`, `not_authenticated`, `permission_denied` -- the token lacks the scope, `subscription_required` -- no active Mahnservice subscription (writes other than payment reporting), `company_locked` -- the account is locked by paywise (every write), `not_found`, `unsupported_media_type`, `request_too_large`, `throttled`, `unexpected_body`, and the documented `409` codes). A repeat submission of an invoice number that was cancelled, written off or archived is a `409` (`invoice_cancelled` / `invoice_written_off` / `invoice_archived`), not a replay. `HEAD` mirrors `GET` and never writes. Every response carries `X-Paywise-Request-Id`, `X-Paywise-Environment` and `Cache-Control: private, no-store`. Token scopes apply: `mahnservice:debtors:read` / `:write` and `mahnservice:invoices:read` / `:write` (a `:write` grant includes `:read`; keys minted with the full `*` grant have everything). Rate limits: 600 requests per minute per key and per company, shared with the Case Management API, plus per-operation windows of 600 reads or 120 writes per minute; a `429` carries `Retry-After`. servers: - url: https://api.paywise.de description: Production environment security: [] tags: - name: Info description: The authenticated credential and its context. - name: Debtors description: Debtors invoices are addressed to. - name: Invoices description: Held invoices, their release, payments and documents. - name: Dunning flows description: Dunning flow configurations referenced by invoices. externalDocs: url: https://docs.paywise.de/api-docs/mahnservice-api/introduction paths: /mahnservice/v1/invoices/{uuid}/dunning/pause/: post: tags: - Invoices summary: Pause the dunning process description: >- Pauses dunning for this invoice (pause_reason "user"). Idempotent on a repeat. 409 (codes: not_released, invoice_in_inkasso, already_paused -- paused under a different hold, invalid_status, invoice_paid / invoice_cancelled / invoice_written_off, not_api_invoice) when there is no dunning process yet or it is paused otherwise, settled or at debt collection. operationId: pause-dunning parameters: - in: path name: uuid schema: type: string format: uuid required: true description: UUID of the invoice in this request. responses: '200': content: application/json: schema: $ref: '#/components/schemas/DunningState' examples: paused: value: state: paused pause_reason: user paused_at: '2026-09-03T09:00:00Z' current_level: 1 next_action_date: '2026-09-04T00:00:00+02:00' dunning_flow: id: 73000000-0000-4000-8000-000000000001 name: Standard reminders levels: 3 level_count: 3 dunnings: [] summary: Dunning process paused description: '' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string '400': description: Standard error response. content: application/json: schema: $ref: '#/components/schemas/Error' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string '401': description: Standard error response. content: application/json: schema: $ref: '#/components/schemas/Error' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string '403': description: Standard error response. content: application/json: schema: $ref: '#/components/schemas/Error' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string '404': description: Standard error response. content: application/json: schema: $ref: '#/components/schemas/Error' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string '409': content: application/json: schema: $ref: '#/components/schemas/Error' description: '' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string '429': description: Standard error response. content: application/json: schema: $ref: '#/components/schemas/Error' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string Retry-After: description: Integer seconds to wait before retrying a throttled request. schema: type: integer minimum: 1 '500': description: Standard error response. content: application/json: schema: $ref: '#/components/schemas/Error' headers: X-Paywise-Request-Id: description: >- Fresh server-assigned correlation id for this response. Caller-provided request ids are ignored. schema: type: string format: uuid X-Paywise-Environment: description: Environment that produced the response. schema: enum: - production - sandbox type: string Cache-Control: description: >- Cacheability directive. Authenticated responses use `private, no-store`; the legal-form catalog may use `private, max-age=86400`. schema: type: string security: - tokenAuth: [] components: schemas: DunningState: type: object description: |- The dunning state of one invoice: the dunning process plus the history of sent notices. A held, never-released invoice reports the held shape with no process. properties: state: allOf: - $ref: '#/components/schemas/MahnserviceDunningStateEnum' readOnly: true nullable: true description: >- Current dunning process state. held means an API invoice awaits release; an invoice settled while held reports paid, cancelled, or written_off. Null means a bookkeeping invoice has never been enrolled. pause_reason: allOf: - $ref: '#/components/schemas/PauseReasonEnum' readOnly: true nullable: true description: >- Reason recorded for the process hold (manual user pause, subscription, administrator, debtor hold, or disconnected integration); null when no reason is recorded. paused_at: type: string format: date-time readOnly: true nullable: true description: >- Time the process entered its current pause. Null when not paused, when no process exists, or when a legacy pause has no recorded timestamp. current_level: type: integer readOnly: true nullable: true description: >- One-based next dunning level. It can be one beyond the final configured level after the last notice; null when no dunning process exists. next_action_date: type: string format: date-time readOnly: true nullable: true description: >- Scheduled time of the next dunning action, which can be a notice or automatic debt-collection handover. Null when no action is scheduled or no process exists. dunning_flow: allOf: - $ref: '#/components/schemas/DunningFlowSummary' readOnly: true nullable: true description: >- Flow assigned to this invoice's dunning process, which can be an older configuration version. Null when no process or assigned flow exists. dunnings: type: array items: $ref: '#/components/schemas/Dunning' readOnly: true description: >- History of sent or attempted dunning notices. Empty when the invoice has no dunning process. required: - current_level - dunning_flow - dunnings - next_action_date - pause_reason - paused_at - state Error: type: object properties: detail: type: string description: Short human-readable summary of the error. code: type: string description: Machine-readable error category. errors: type: array items: $ref: '#/components/schemas/ErrorItem' description: Field-level validation errors, when applicable. required: - detail - code additionalProperties: false MahnserviceDunningStateEnum: enum: - held - pending - active - paused - completed - paid - cancelled - written_off - inkasso type: string description: |- * `held` - Held * `pending` - Pending * `active` - Aktiv * `paused` - Pausiert * `completed` - Abgeschlossen * `paid` - Paid * `cancelled` - Storniert * `written_off` - Ausgebucht * `inkasso` - An Inkasso übergeben PauseReasonEnum: enum: - user - subscription - admin - debtor - integration type: string description: |- * `user` - Manuell pausiert * `subscription` - Abo gekündigt * `admin` - Vom Administrator pausiert * `debtor` - Schuldner pausiert * `integration` - Buchhaltungs-Verbindung getrennt DunningFlowSummary: type: object description: |- The flow the process runs on (summary; the full config lives at GET /dunning-flows/). Fixed shape, not a free-form dict, so SDK generators get real types. properties: id: type: string format: uuid readOnly: true name: type: string readOnly: true levels: type: integer readOnly: true description: >- Number of levels (same value as level_count; kept for compatibility). level_count: type: integer readOnly: true required: - id - level_count - levels - name Dunning: type: object description: One sent (or attempted) dunning notice. properties: level: type: integer readOnly: true description: One-based dunning level for this sent or attempted notice. channel: allOf: - $ref: '#/components/schemas/ChannelEnum' readOnly: true description: 'Delivery channel for this notice: email, postal letter, or both.' state: allOf: - $ref: '#/components/schemas/MahnserviceMahnungStatusEnum' readOnly: true description: >- Delivery state of this individual notice, separate from the invoice's dunning process state. manual means manual sending is required. sent_at: type: string format: date-time readOnly: true nullable: true description: Time the notice was sent; null if no send time is recorded. error_message: type: string readOnly: true nullable: true description: >- Public explanation of the notice's delivery error, or null when no error is recorded. dunning_fee: allOf: - $ref: '#/components/schemas/DunningFee' readOnly: true nullable: true description: >- Fee charged with this notice, recorded at send time; null if no fee was charged. Later flow changes do not change this historical amount. required: - channel - dunning_fee - error_message - level - sent_at - state ErrorItem: type: object properties: field: type: string nullable: true description: >- Path to the field that caused the error, using dots for objects and brackets for list indexes, for example `claims[0].amount`; null for an error without a field path. code: type: string description: Machine-readable field error code. message: type: string description: Human-readable explanation of the field error. required: - field - code - message additionalProperties: false ChannelEnum: enum: - email - letter - both type: string description: |- * `email` - E-Mail * `letter` - Brief * `both` - E-Mail & Brief MahnserviceMahnungStatusEnum: enum: - pending - sent - delivered - opened - bounced - failed - manual type: string description: |- * `pending` - Pending * `sent` - Versendet * `delivered` - Zugestellt * `opened` - Geöffnet * `bounced` - Unzustellbar * `failed` - Fehlgeschlagen * `manual` - Manuell versenden DunningFee: type: object description: The Mahngebühr charged with a sent Mahnung (snapshotted at send time). properties: amount: type: string format: decimal pattern: ^-?\d{0,6}(?:\.\d{0,2})?$ readOnly: true description: Dunning fee in EUR, recorded at send time. charged_at: type: string format: date-time readOnly: true required: - amount - charged_at securitySchemes: tokenAuth: type: http scheme: bearer ````