SignTransaction
Last updated
Was this helpful?
Last updated
Was this helpful?
The easiest and most recommended way to send a transaction is via . It is safer for users, and a simpler API for developers, for Phantom to submit the transaction immediately after signing it instead of relying on the application to do so.
However, it is also possible for an app to request just the signature from Phantom. Once signed, an app can submit the transaction itself using .
dapp_encryption_public_key (required): The original encryption public key used from the app side for an existing session.
nonce (required): A nonce used for encrypting the request, encoded in base58.
redirect_link (required): The URI where Phantom should redirect the user upon completion. Please review for more details. URL-encoded.
payload (required): An encrypted JSON string with the following fields:
transaction (required): The that Phantom will sign, serialized and encoded in base58.
session (required): The session token received from the method. Please see for more details.
nonce: A nonce used for encrypting the response, encoded in base58.
data: An encrypted JSON string. Refer to to learn how apps can decrypt data using a shared secret. Encrypted bytes are encoded in base58.
transaction: The signed, serialized transaction that is base58 encoded. Phantom will not submit this transactions. An application can submit this transactions itself via .
An errorCode and errorMessage as query parameters. Please refer to for a full list of possible error codes.
Please refer to the .