This endpoint initiates the rejection of an ownership transfer request for a document governed by a Title Escrow smart contract. When an ownership transfer is initiated by another party, the current owner has the authority to either approve or reject the request. This endpoint allows the current owner to explicitly decline the pending ownership transfer.

When the document file is submitted, its embedded metadata is extracted to determine the exact token associated with the document. Using this token reference together with the registry address, the system identifies the specific Title Escrow instance managing the token on the blockchain.

The user’s identity and authorization are validated through their wallet, using the authorization token provided in the request header. The authenticated wallet must match the current owner reflected on the Title Escrow contract. If the caller is not the recognized owner, the rejection request is denied.

Any remarks provided in the request are formatted as structured metadata and included in the blockchain transaction as part of the official record of the rejection.

The system constructs the necessary smart-contract call to initiate the ownership transfer rejection. A blockchain transaction is prepared, gas usage is estimated, and a transaction hash is generated. This hash is then used to create a signing challenge.

All relevant details—including the document metadata, challenge information, and unsigned transaction.

The endpoint responds with a redirect URL to the signing interface. The caller must visit this URL to authenticate and authorize the on-chain rejection of the ownership transfer request.