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

# Remove a payment instruction

> Removes a payment instruction from a beneficiary.



## OpenAPI

````yaml apis/fx-payment/openapi.yml DELETE /v1/beneficiaries/{beneficiaryId}/payment-instructions/{paymentInstructionId}
openapi: 3.1.1
info:
  title: Trace Finance Payments API
  version: 1.0.0
  description: >
    API for deposits, withdrawals, swaps, and beneficiary management on the
    Trace Finance platform.
servers:
  - url: https://api.sandbox.tracefinance.com
    description: Sandbox
security:
  - bearerAuth: []
tags:
  - name: Operations
    description: >-
      Create deposits, withdrawals, and swaps. Query operation status and
      history.
  - name: Reports
    description: Generate aggregated views of operations across a time window.
  - name: Beneficiaries
    description: >-
      Manage external beneficiaries and their payment instructions for
      withdrawals.
  - name: Payment instructions
    description: Add or remove payment instructions on an existing beneficiary.
paths:
  /v1/beneficiaries/{beneficiaryId}/payment-instructions/{paymentInstructionId}:
    delete:
      tags:
        - Payment instructions
      summary: Remove a payment instruction
      description: Removes a payment instruction from a beneficiary.
      operationId: removePaymentInstruction
      parameters:
        - $ref: '#/components/parameters/BeneficiaryId'
        - $ref: '#/components/parameters/PaymentInstructionId'
        - $ref: '#/components/parameters/TraceVersion'
      responses:
        '204':
          description: Payment instruction removed.
          headers:
            X-Request-Id:
              $ref: '#/components/headers/RequestId'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '404':
          description: Beneficiary or payment instruction not found.
          headers:
            X-Request-Id:
              $ref: '#/components/headers/RequestId'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                beneficiaryNotFound:
                  $ref: '#/components/examples/BeneficiaryNotFound'
                paymentInstructionNotFound:
                  summary: Payment instruction does not exist on the beneficiary
                  value:
                    code: RESOURCE_NOT_FOUND
                    message: >-
                      PaymentInstruction with given parameters
                      [id:pi-a1b2c3d4-5e6f-7890-abcd-ef1234567890] not found
                    details:
                      resource: PaymentInstruction
                      parameters:
                        id: pi-a1b2c3d4-5e6f-7890-abcd-ef1234567890
components:
  parameters:
    BeneficiaryId:
      name: beneficiaryId
      in: path
      required: true
      description: UUID of the beneficiary.
      schema:
        type: string
        format: uuid
    PaymentInstructionId:
      name: paymentInstructionId
      in: path
      required: true
      description: UUID of the payment instruction.
      schema:
        type: string
        format: uuid
    TraceVersion:
      name: X-Trace-Version
      in: header
      required: false
      description: API version. Omit to use the default version.
      schema:
        type: string
        example: '1'
  headers:
    RequestId:
      description: >-
        Unique request identifier emitted on every response. Reference it when
        contacting Trace Finance support so we can trace the request end-to-end.
        See [Errors](/guides/principles/errors).
      schema:
        type: string
        format: uuid
  responses:
    UnauthorizedError:
      description: Missing or invalid authentication token.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            invalidToken:
              $ref: '#/components/examples/InvalidToken'
            expiredToken:
              $ref: '#/components/examples/ExpiredToken'
  schemas:
    ErrorResponse:
      type: object
      properties:
        code:
          type: string
          description: Machine-readable error code.
        message:
          type: string
          description: Human-readable description.
        details:
          type: object
          additionalProperties: true
      required:
        - code
        - message
  examples:
    BeneficiaryNotFound:
      summary: Beneficiary does not exist for the authenticated customer
      value:
        code: RESOURCE_NOT_FOUND
        message: >-
          Beneficiary with given parameters
          [id:b2c3d4e5-f6a7-8901-bcde-f12345678901] not found
        details:
          resource: Beneficiary
          parameters:
            id: b2c3d4e5-f6a7-8901-bcde-f12345678901
    InvalidToken:
      summary: Bearer token is invalid or malformed
      value:
        code: INVALID_ACCESS_TOKEN
        message: Invalid access token
        details: {}
    ExpiredToken:
      summary: Bearer token has expired
      value:
        code: EXPIRED_ACCESS_TOKEN
        message: Expired access token
        details: {}
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT bearer token. Include as `Authorization: Bearer <token>`. See the
        [Authentication](/guides/authentication) guide for how to obtain one.

````