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

# Delete Sell and Pay transaction

> Cancels and deletes a Sell and Pay transaction. This operation can be performed on transactions in INCOMPLETE, PENDING, or WAITING_DEPOSIT status. Transactions in RECEIVED_DEPOSIT, CONFIRMED_DEPOSIT, TRADE_COMPLETED, QR_EXECUTION_PENDING, COMPLETED, CANCELED, REFUND_PENDING, or REFUNDED status cannot be deleted as they are already being processed, have been completed, or are in a final state.



## OpenAPI

````yaml ramps-api/openapi.json DELETE /api/v1/sellAndPays/{sell_and_pay_id}/
openapi: 3.1.0
info:
  title: Ripio Ramp API
  version: v1
  description: >-
    API for Ripio ramp services, enabling partners to integrate On-Ramp,
    Off-Ramp, customer management, KYC processes, and other financial
    functionalities. This API is RESTful, uses JSON for requests and responses,
    and standard HTTP status codes. This document is based on the
    'onramp-api.pdf' provided and aims to be compliant with OpenAPI
    Specification v3.1.0. The PDF indicates that the API documentation is a
    draft and subject to change.
servers:
  - url: https://skala-sandbox.ripio.com
    description: Sandbox environment
  - url: https://skala.ripio.com
    description: Production environment
security:
  - BearerToken: []
tags:
  - name: Authentication
    description: Operations related to API authentication and authorization.
  - name: Support Tickets
    description: >-
      Operations for raising and tracking customer support tickets with Ripio's
      support team. This feature must be enabled for your account by the Ripio
      team.
  - name: Customers
    description: Operations related to customer management.
  - name: KYC
    description: Operations related to Know Your Customer processes.
  - name: Fiat Accounts
    description: Operations related to managing fiat accounts and their requirements.
  - name: Quotes
    description: Operations related to obtaining and managing conversion quotes.
  - name: On-Ramp
    description: Operations related to fiat-to-crypto (on-ramp) processes.
  - name: Off-Ramp
    description: Operations related to crypto-to-fiat (off-ramp) processes.
  - name: Transactions
    description: Operations related to listing and managing all transaction types.
  - name: Networks
    description: >-
      Operations related to retrieving available deposit and withdrawal
      networks.
  - name: Rates
    description: Operations related to retrieving market rates.
  - name: Transaction Limits
    description: >-
      Operations related to retrieving per-transaction limits by currency and
      ramp operation.
  - name: Sandbox
    description: Operations specific to the sandbox environment for testing purposes.
  - name: Webhooks
    description: Webhook event notifications from Ripio Ramp API.
  - name: Sell and Pay
    description: >-
      Endpoints for managing Sell and Pay transactions, which allow customers to
      convert cryptocurrency to fiat currency and pay merchants via QR codes
paths:
  /api/v1/sellAndPays/{sell_and_pay_id}/:
    delete:
      tags:
        - Sell and Pay
      summary: Delete Sell and Pay transaction
      description: >-
        Cancels and deletes a Sell and Pay transaction. This operation can be
        performed on transactions in INCOMPLETE, PENDING, or WAITING_DEPOSIT
        status. Transactions in RECEIVED_DEPOSIT, CONFIRMED_DEPOSIT,
        TRADE_COMPLETED, QR_EXECUTION_PENDING, COMPLETED, CANCELED,
        REFUND_PENDING, or REFUNDED status cannot be deleted as they are already
        being processed, have been completed, or are in a final state.
      operationId: deleteSellAndPay
      parameters:
        - name: sell_and_pay_id
          in: path
          required: true
          description: Unique identifier of the Sell and Pay transaction to delete
          schema:
            type: string
            format: uuid
      responses:
        '204':
          description: Sell and Pay transaction successfully deleted
        '400':
          description: >-
            Bad Request - e.g., transaction cannot be deleted in its current
            status.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized - Invalid or missing access token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                code: 40001
                type: NotAuthenticated
                detail:
                  message: Authentication credentials were not provided.
                  code: not_authenticated
                status: 401
        '403':
          description: >-
            Forbidden - QR payments are not enabled for this account. Every Sell
            and Pay endpoint requires QR payments to be enabled; contact Ripio
            to enable it.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                code: 40003
                type: QrPaymentsNotEnabledException
                detail:
                  message: QR payments are not enabled for this account.
                status: 403
        '404':
          description: Not Found - e.g., Sell and Pay transaction not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                code: 40016
                type: SellAndPayNotFoundException
                detail:
                  message: Sell and Pay not found.
                status: 404
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        code:
          type: integer
          description: Application-specific error code.
        type:
          type: string
          description: Type of error or exception.
        detail:
          type: object
          properties:
            message:
              type: string
              description: Detailed error message.
          additionalProperties: true
        status:
          type: integer
          description: HTTP status code.
      required:
        - code
        - type
        - detail
        - status
  securitySchemes:
    BearerToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Access token obtained via
        [/oauth2/token/](/ramps-api/authentication/acquire-access-token). Use as
        `Authorization: Bearer <access_token>`.

````