> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ringup.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Check payment completion

> Whether the caller has completed payment, for example after send_link while the call is still going.



## OpenAPI

````yaml /api-reference/openapi.json post /payment_status
openapi: 3.1.0
info:
  title: Ringup tools API
  description: >-
    Five REST tools for taking payment on a voice call. Identity rides trusted
    headers; the model never types a phone number or merchant id.
  version: 1.0.0
servers:
  - url: https://ringup.dev/api/tools
security: []
paths:
  /payment_status:
    post:
      summary: Check payment completion
      description: >-
        Whether the caller has completed payment, for example after send_link
        while the call is still going.
      operationId: payment_status
      parameters:
        - $ref: '#/components/parameters/CallerNumber'
        - $ref: '#/components/parameters/Merchant'
        - $ref: '#/components/parameters/CallId'
      responses:
        '200':
          description: The current payment state for this call.
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - paid
                      - pending
              example:
                status: pending
components:
  parameters:
    CallerNumber:
      name: X-Caller-Number
      in: header
      required: true
      description: >-
        The caller's phone number in E.164, templated from the platform's
        caller-ID variable. Never model-generated.
      schema:
        type: string
        example: '+14155550142'
    Merchant:
      name: X-Ringup-Merchant
      in: header
      required: true
      description: >-
        The dialed number in E.164 (resolved to a merchant server-side) or an
        explicit merchant id.
      schema:
        type: string
        example: tonys-pizza
    CallId:
      name: X-Call-Id
      in: header
      required: false
      description: >-
        The platform's call id. Used for charge idempotency: retries within a
        call can never double-charge.
      schema:
        type: string

````