Skip to main content
A common use case: your app builds a transaction and needs the user to sign it.

The flow

  1. User generates code at actioncode.app
  2. User shares code with your app
  3. Your app builds a transaction and attaches it
  4. User approves in their wallet
  5. Your app gets the signed transaction

Full example

Submitting the transaction

After getting the signature, you can submit the transaction to the network:
The finalizedSignature returned by observeStatus is the signature from the user’s wallet. Depending on your setup, you may need to also add your own signature (if you’re a co-signer) before submitting.

With metadata

Add helpful context for the user:
The user will see this description in actioncode.app when reviewing the request.

Error handling