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

# Prepare a route ownership proof

> Get the exact message a self-custody wallet owner must sign to finish registering a pay-out route.

**Requires scope:** `manage:pay-outs` — see [Required scopes](/getting-started/authentication#required-scopes-finance-api).

Returns the exact text the owner of a self-custody wallet must sign to prove they control it, so the pay-out route can finish registering.

A route parks at `AWAITING_OWNERSHIP_PROOF` when its destination requires a Travel-Rule ownership proof and the source wallet is self-custody. Venly holds no key for that wallet, so only its owner can sign.

This step is **stateless** — nothing is stored, and there's no id or expiry. Calling it twice for the same route returns an equivalent message, so it's safe to repeat.

<Warning>
  The owner signs `message` **verbatim**. Don't reformat, re-encode, pretty-print or reconstruct it — the signature is checked against those exact bytes.

  Only an externally-owned account can sign: the scheme is EIP-191, and **ERC-1271 contract signatures are not supported**. A smart-contract wallet cannot complete this step.
</Warning>

The message is date-bound (`signedOnUtc`), so a proof prepared on one day can't be submitted against a message built for another. Sign and submit in the same session.

Submit the result with [Submit a route ownership proof](/api-reference/Finance-API/payout-routes/submit-a-route-ownership-proof). See [Pay-outs](/guides/finance/payouts#proving-you-control-the-source-wallet).


## OpenAPI

````yaml api-reference/Finance-API-Specs.yaml POST /accounts/{accountId}/payout-routes/{routeId}/ownership-proof/prepare
openapi: 3.1.0
info:
  title: Venly Finance API
  description: >
    REST API for the Venly Finance platform:

    - Party management (Individuals & Organisations)

    - Identity verification — hosted KYC/KYB links and Sumsub share-token
    forwarding

    - Account management with party association

    - Wallet balances & token allowances on supported chains

    - Virtual bank accounts for global pay-in (EUR SEPA, USD ACH/WIRE/RTP/SWIFT)

    - Fiat-to-crypto payment sessions (pay-in)

    - Bank pay-outs — beneficiary allow-listing, routes, and PULL/PUSH pay-outs

    - Account-to-account fiat & crypto transfers

    - EIP-2612 permits and allowances

    - Webhook registration for asynchronous event delivery


    ## Authentication


    All endpoints use OAuth2 client credentials. Obtain a token first, then
    include it in every request:


    **Step 1 — Get a token:**

    ```bash

    curl -X POST
    https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
    \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=client_credentials&client_id={CLIENT_ID}&client_secret={CLIENT_SECRET}"
    ```


    **Step 2 — Use the token:**

    ```

    Authorization: Bearer {access_token}

    ```


    Tokens expire after **5 minutes**. Implement refresh logic in your client.
  version: 1.5.0
  contact:
    name: Venly Support
    email: support@venly.io
    url: https://docs.venlyfinance.com
  license:
    name: Proprietary
  x-logo:
    url: https://venlyfinance.com/logo.png
  x-security-contact: security@venly.io
servers:
  - url: https://api.venlyfinance.com/v1
    description: Production
  - url: https://api-staging.venlyfinance.com/v1
    description: Staging
security:
  - OAuth2: []
tags:
  - name: Parties
    description: Party management (Individuals & Organisations)
  - name: Accounts
    description: Account management, party-role associations
  - name: Wallets
    description: Blockchain wallet balances
  - name: Virtual Bank Accounts
    description: Virtual bank account payment references for global payments
  - name: Fiat-to-crypto Payment Sessions
    description: Fiat-to-crypto payment session creation
  - name: Payout Bank Accounts
    description: Allow-listing beneficiary bank accounts as pay-out destinations
  - name: Payout Routes
    description: >-
      Account-scoped routes pairing a beneficiary bank account with a crypto
      deposit asset
  - name: Payouts
    description: Crypto-to-fiat pay-outs over a registered route
  - name: Transfers
    description: Fiat and crypto transfer operations between accounts
  - name: Permits
    description: EIP-712 permit signature management for token approvals
  - name: Supported Assets
    description: >-
      Discover which chains and assets your tenant can settle in, and whether an
      account can use them yet.
  - name: Allowances
    description: Token allowance management for wallets
  - name: Webhooks
    description: Webhook registration and delivery testing
paths:
  /accounts/{accountId}/payout-routes/{routeId}/ownership-proof/prepare:
    post:
      tags:
        - Payout Routes
      summary: Prepare a pay-out route ownership proof
      description: >
        **Requires scope:** `manage:pay-outs`


        Returns the exact text the owner of a self-custody wallet must sign to
        prove they control it,

        so the pay-out route can finish registering.


        A route parks at `AWAITING_OWNERSHIP_PROOF` when its destination
        requires a Travel-Rule

        ownership proof and the source wallet is self-custody — Venly holds no
        key for that wallet,

        so only its owner can sign. See
        [Pay-outs](/guides/finance/payouts#proving-you-control-the-source-wallet).


        Stateless: nothing is stored, and there is no id or expiry. Calling it
        twice for the same

        route returns an equivalent message, so it is safe to repeat.


        Only an externally-owned account can sign — the scheme is EIP-191, and
        ERC-1271 contract

        signatures are not supported.
      operationId: preparePayoutRouteOwnershipProof
      parameters:
        - $ref: '#/components/parameters/AccountId'
        - $ref: '#/components/parameters/RouteId'
      responses:
        '200':
          description: The message to sign
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SinglePayoutOwnershipProofResponse'
              example:
                success: true
                result:
                  walletAddress: '0x7c6b9095Ae1E0F1D0b1B9c8A5f4E3d2C1b0A9f8E'
                  blockchain: BASE
                  message: I confirm ownership of wallet 0x7c6b9095... on 20/08/2026
                  signedOnUtc: '2026-08-20'
        '400':
          description: >
            Bad request. Notable codes:

            - `ownership-proof-not-applicable` — this route needs no
            owner-signed proof, or its source wallet is Venly-managed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    AccountId:
      name: accountId
      in: path
      required: true
      description: Unique account identifier
      schema:
        type: string
        format: uuid
      example: b2a1f0e9-8c7d-4e3a-9f21-0a1b2c3d4e5f
    RouteId:
      name: routeId
      in: path
      required: true
      description: Unique pay-out route identifier
      schema:
        type: string
        format: uuid
      example: 7b683e87-4c73-4821-aa1d-52481805f40b
  schemas:
    SinglePayoutOwnershipProofResponse:
      allOf:
        - $ref: '#/components/schemas/BaseResponse'
        - type: object
          properties:
            result:
              $ref: '#/components/schemas/PayoutOwnershipProof'
    ErrorResponse:
      type: object
      description: Error response wrapper
      properties:
        success:
          type: boolean
          description: Always false for error responses
          example: false
        errors:
          type: array
          description: List of errors that occurred
          items:
            $ref: '#/components/schemas/ErrorBody'
        result:
          type: object
          nullable: true
          description: Null or omitted when success is false
    BaseResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Indicates whether the request was successful
    PayoutOwnershipProof:
      type: object
      description: >-
        The message a self-custody wallet owner must sign to prove they control
        the route's source wallet.
      properties:
        walletAddress:
          type: string
          description: The wallet that must sign
        blockchain:
          $ref: '#/components/schemas/BlockchainNetwork'
        message:
          type: string
          description: >
            Sign this **verbatim**. Do not reformat, re-encode, pretty-print or
            reconstruct it — the

            signature is checked against these exact bytes.
        signedOnUtc:
          type: string
          format: date
          description: >
            UTC date embedded in the message. The message is date-bound, so a
            proof prepared on one

            day cannot be submitted against a message built for another.
    ErrorBody:
      type: object
      description: Individual error details
      properties:
        code:
          type: string
          description: Machine-readable error code
          example: invalid-request
        message:
          type: string
          description: Human-readable error message
          example: The request contains invalid parameters.
    BlockchainNetwork:
      type: string
      description: >
        Supported blockchain network. Availability per chain depends on your
        company's configured

        `supportedChains` — see [Supported chains and
        assets](/guides/finance/supported-chains-and-assets).
      enum:
        - AVALANCHE
        - BASE
        - ETHEREUM
        - POLYGON
        - SOLANA
  responses:
    Unauthorized:
      description: Authentication required or failed (401)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: unauthenticated
                message: Please authenticate to perform this action.
    Forbidden:
      description: Caller lacks the required authority/role (403)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: forbidden
                message: You do not have permission to access this resource.
    NotFound:
      description: Resource not found (404)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: account-not-found
                message: The requested resource was not found.
    InternalServerError:
      description: Unexpected server error (500)
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            errors:
              - code: internal-error
                message: An unexpected error occurred. Please try again later.
  securitySchemes:
    OAuth2:
      type: oauth2
      description: >
        OAuth2 client credentials flow. Token endpoints:

        - Staging:
        https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token

        - Production:
        https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
      flows:
        clientCredentials:
          tokenUrl: >-
            https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token
          scopes: {}

````