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

# Confirm External Sell On-chain Funding

> Confirm the on-chain funding transaction for an external sell.

This endpoint returns `202 Accepted`, not `200 OK`.

Some service branches still return a service-specific `400` error body such as `transaction not found`.




## OpenAPI

````yaml openapi-v2.json POST /api/v2/wallet/transaction/crypto/sell/{id}/confirm-onchain-funding
openapi: 3.1.0
info:
  title: Saber Money API (v2)
  version: v2
  description: >-
    ## Authentication


    There is no standalone API-key auth — every request must be **signed**. An
    API key by itself authenticates nothing. Each call requires four headers
    together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey +
    timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required —
    keyed with your API secret), `X-Timestamp` (unix seconds), and
    `X-Request-Id` (any unique string per request). The signature must be
    computed by a client script; there is no way to derive it by hand. Use the
    HMAC Generator flow to compute valid values for manual testing.


    ## Common Authentication Errors


    - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id
    invalid","success":false}

    - **Invalid Secret**: {"error_code":6090,"message":"invalid
    secret","success":false}

    - **Timestamp (Older than 10 secs)**:
    {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false}
servers:
  - url: https://api.saber.money
security: []
paths:
  /api/v2/wallet/transaction/crypto/sell/{id}/confirm-onchain-funding:
    post:
      tags:
        - Offramp
      summary: Confirm External Sell On-chain Funding
      description: >
        Confirm the on-chain funding transaction for an external sell.


        This endpoint returns `202 Accepted`, not `200 OK`.


        Some service branches still return a service-specific `400` error body
        such as `transaction not found`.
      operationId: confirm-sell-onchain-funding-v2
      parameters:
        - name: id
          in: path
          required: true
          description: Wallet transaction UUID.
          schema:
            type: string
            description: Wallet transaction UUID.
        - name: X-Api-Key
          in: header
          required: true
          description: Your API key (configured in credentials)
          schema:
            type: string
        - name: X-Signature
          in: header
          required: true
          description: >-
            HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256
            of `apiKey + timestamp` (or `apiKey + timestamp + userId` when
            X-User-Id is required), keyed with your API secret. The HMAC
            Generator flow computes this for you.
          schema:
            type: string
        - name: X-Timestamp
          in: header
          required: true
          description: >-
            Unix timestamp in seconds (auto-generated) Unix seconds, e.g.
            `Math.floor(Date.now() / 1000)`. Must match the timestamp used in
            the X-Signature computation.
          schema:
            type: string
        - name: X-Request-Id
          in: header
          required: true
          description: >-
            Unique request identifier (auto-generated) Any unique string per
            request, e.g. a UUID.
          schema:
            type: string
        - name: X-User-Id
          in: header
          required: true
          description: User UUID (set above)
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                transaction_hash:
                  type: string
                  description: On-chain funding transaction hash.
              required:
                - transaction_hash
            example:
              transaction_hash: '0x1234567890abcdef'
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: object
                    properties:
                      id:
                        type: string
                      status:
                        type: string
                      transaction_hash:
                        type: string
                      fiat_symbol:
                        type: string
                      crypto_symbol:
                        type: string
              example:
                success: true
                data:
                  id: 4e43fc12-4581-4e44-9469-1c4e3a5bf8bf
                  status: CREATED
                  transaction_hash: '0x1234567890abcdef'
                  fiat_symbol: EUR
                  crypto_symbol: USDT
        '400':
          description: '`400001`: missing or invalid parameters'
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    enum:
                      - false
                  errors:
                    type: array
                    items:
                      type: object
                      properties:
                        code:
                          type:
                            - integer
                            - string
                        text:
                          type: string
              example:
                success: false
                errors:
                  - code: 400001
                    text: missing or invalid parameters
        '500':
          description: '`499999`: Something went wrong!'
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    enum:
                      - false
                  errors:
                    type: array
                    items:
                      type: object
                      properties:
                        code:
                          type:
                            - integer
                            - string
                        text:
                          type: string
              example:
                success: false
                errors:
                  - code: 400001
                    text: missing or invalid parameters

````

## Related topics

- [Fetching Transaction Status](/offramp/operations/fetch-status.md)
- [Available Flows](/offramp/available-flows.md)
- [BDT Offramp](/offramp/currencies/bdt.md)
- [EUR/GBP Offramp](/offramp/currencies/eur-gbp.md)
- [IDR Offramp](/offramp/currencies/idr.md)