Skip to main content
This guide is available on four different programming languages: Typescript, Kotlin, Flutter (Dart) and Swift. You can change the shown version on each page via the buttons above.
The Sep-7 standard defines a way for a non-wallet application to construct a URI scheme that represents a specific transaction for an account to sign. The scheme used is web+stellar, followed by a colon. Example: web+stellar:<operation>?<param1>=<value1>&<param2>=<value2>

Tx Operation

The tx operation represents a request to sign a specific transaction envelope, with some configurable parameters.
You can set replacements to be made in the xdr for specific fields by the application, these will be added in the Sep-11 transaction representation format to the URI.
You can assign parameters after creating the initial instance using the appropriate setter for the parameter.

Pay Operation

The pay operation represents a request to pay a specific address with a specific asset, regardless of the source asset used by the payer. You can configure parameters to build the payment operation.
You can assign parameters after creating the initial instance using the appropriate setter for the parameter.
The last step after building a Sep7Tx or Sep7Pay is to add a signature to your uri. This will create a payload out of the transaction and sign it with the provided keypair.
The signature can then be verified by fetching the Stellar toml file from the origin domain in the uri, and using the included signing key to verify the uri signature. This is all done as part of the verifySignature method.