Stacks Pay: A Payment Request Standard for Stacks Blockchain Payments #202

dantrevino · 2024-12-02T07:25:02Z

Stacks Pay is a proposed standard for wrapping transaction information in a standard way for easy sharing.

binxbrigandine · 2024-12-02T22:08:44Z

Love standardization!

markmhendrickson · 2024-12-04T11:18:34Z

Thanks for proposing, @dantrevino! We'll review on the Leather team and provide thoughts.

kyranjamie

Great work @dantrevino

kyranjamie · 2024-12-04T12:55:20Z

sips/sip-02x/sip-02x-stacks-pay.md

+
+contractName, functionName: Wallets MUST ignore these parameters if present.
+
+### `mint`


What's the rationale for having mint operations as part of this spec? Couldn't this be seen as outside the realm of making payments?

Worried about how malicious contacts with a mint method, that otherwise looks like a SIP-009 contract, tricking users into draining their wallets.

I believe that enabling payments to smart contracts is within the realm of payments. And malicious 'mint' operations can happen anywhere today. At Boom we're putting default post conditions on every request.

@dantrevino as SIP-009 doesn't specify a mint function in the spec this would mean that you can only mint Boom NFTs? As there is no spec for the params it wouldn't work with other platforms mint I guess

Sorry no this is not intended to be a Boom thing. The intention here was to make a generic name ... maybe to be more clear, for the mint function we make the functionName parameter required so that a wallet/app does not have to do the function lookup itself.

kyranjamie · 2024-12-04T12:57:06Z

sips/sip-02x/sip-02x-stacks-pay.md

+
+Stacks Pay defines several standard operations that specify the type of payment action to be performed. Each operation type has specific required and optional parameters.
+
+### `support`


Are there not other use cases for a user-defined amount beyond supporting an org/project? Wondering if this name is too scoped to an individual use case, and could better be broader?

Open to other ideas here ... i tried to find a word that would encapsulate tips, donations, and gifts.

whoabuddy

Overall looks good, happy to see you're putting this forward! I left a few small comments.

@human058382928 @r0zar @biwasbhandari these encoded URLs describe a Stacks transaction, might be something cool we can do there with @aibtcdev tooling!

whoabuddy · 2024-12-13T18:10:52Z

sips/sip-02x/sip-02x-stacks-pay.md

+
+**Optional Parameters:**
+
+- recipient: MAY be included; if present, MUST be a valid Stacks address. The NFT will be minted for the specified address.


Where is it minted if this is not specified?

By default, the mint recipient is the user paying for the mint. If you include a recipient, you mint for that recipient.

whoabuddy · 2024-12-13T18:13:52Z

sips/sip-02x/sip-02x-stacks-pay.md

+### Custom Operations
+
+Applications **MAY** define custom operations for specific use cases. Custom operation types **MUST** be prefixed to prevent naming conflicts (e.g., `'custom-example'`).
+
+- **Handling Unrecognized Operations**: If a wallet encounters an unrecognized operation type, it **SHOULD**:
+
+- **Warn the User**: Inform the user that the operation type is unrecognized.
+
+- **Provide Safe Defaults**: Default to a standard payment flow if possible.
+
+- **Fail Gracefully**: Prevent unexpected behavior or security risks.


Felt like this made it more readable

Suggested change

### Custom Operations

Applications **MAY** define custom operations for specific use cases. Custom operation types **MUST** be prefixed to prevent naming conflicts (e.g., `'custom-example'`).

- **Handling Unrecognized Operations**: If a wallet encounters an unrecognized operation type, it **SHOULD**:

- **Warn the User**: Inform the user that the operation type is unrecognized.

- **Provide Safe Defaults**: Default to a standard payment flow if possible.

- **Fail Gracefully**: Prevent unexpected behavior or security risks.

### Custom Operations

Applications **MAY** define custom operations for specific use cases.

Custom operation types **MUST** be prefixed to prevent naming conflicts (e.g., `'custom-example'`).

**Handling Unrecognized Operations**: If a wallet encounters an unrecognized operation type, it **SHOULD**:

- **Warn the User**: Inform the user that the operation type is unrecognized.

- **Provide Safe Defaults**: Default to a standard payment flow if possible.

- **Fail Gracefully**: Prevent unexpected behavior or security risks.

whoabuddy · 2024-12-13T18:14:21Z

sips/sip-02x/sip-02x-stacks-pay.md

+
+```
+R - required
+O - optionalas determined


whoabuddy · 2024-12-13T18:16:07Z

sips/sip-02x/sip-02x-stacks-pay.md

+Example encoded Stack Pay url:
+
+`stx1wajky2mnw3u8qcte8ghj76twwehkjcm98ahhqetjv96xjmmw845kuan0d93k2fnjv43kjurfv4h8g02n2qe9y4z9xarryv2wxer4zdjzgfd9yd62gar4y46p2sc9gd23xddrjkjgggu5k5jnye6x76m9dc74x4zcyesk6mm4de6r6vfsxqczver9wd3hy6tsw35k7m3a2pshjmt9de6zken0wg4hxetjwe5kxetnyejhsurfwfjhxst585erqv3595cnytfnx92ryve9xdqn2wf9xdqn2w26juk65n`


This was confusing to read before we got to the encoding section. Maybe save the example for later and focus on defining the web+stx format leading into it?

It might help to use triple backticks instead of single on the code for readability, e.g.

stx1wajky2mnw3u8qcte8ghj76twwehkjcm98ahhqetjv96xjmmw845kuan0d93k2fnjv43kjurfv4h8g02n2qe9y4z9xarryv2wxer4zdjzgfd9yd62gar4y46p2sc9gd23xddrjkjgggu5k5jnye6x76m9dc74x4zcyesk6mm4de6r6vfsxqczver9wd3hy6tsw35k7m3a2pshjmt9de6zken0wg4hxetjwe5kxetnyejhsurfwfjhxst585erqv3595cnytfnx92ryve9xdqn2wf9xdqn2w26juk65n

vs

stx1wajky2mnw3u8qcte8ghj76twwehkjcm98ahhqetjv96xjmmw845kuan0d93k2fnjv43kjurfv4h8g02n2qe9y4z9xarryv2wxer4zdjzgfd9yd62gar4y46p2sc9gd23xddrjkjgggu5k5jnye6x76m9dc74x4zcyesk6mm4de6r6vfsxqczver9wd3hy6tsw35k7m3a2pshjmt9de6zken0wg4hxetjwe5kxetnyejhsurfwfjhxst585erqv3595cnytfnx92ryve9xdqn2wf9xdqn2w26juk65n

whoabuddy · 2024-12-13T18:20:05Z

sips/sip-02x/sip-02x-stacks-pay.md

+
+### Encoding and Decoding
+
+Stacks Pay URLs **MUST** be encoded using **Bech32m encoding** with the human-readable part (HRP) set to `'stx'` and a `limit` of 512. This ensures compatibility and data integrity, making it suitable for QR codes and platforms with URL limitations.


It would be great to have a code snippet or example walking us through getting from parameters -> unencoded URL -> encoded URL and back. Where do we set the HRP and limit? What do I run to encode it?

friedger · 2025-03-07T11:03:52Z

How difficult is it to integrate into existing payment flows? E.g. compared to eth integration. Maybe something for the introduction.

flormpecasique · 2025-04-01T22:37:20Z

Hey Dan 👋

Awesome work on this! I wanted to share some thoughts based on my experience building Stacks Invoice Generator, where I tackled invoice generation for STX and Stacks tokens without smart contracts. One of the biggest challenges I faced was QR code functionality.

Initially, I wanted users to scan a QR code and have it automatically open their wallet (Xverse/Leather) with all payment details pre-filled—similar to Bitcoin or Ethereum payment URIs (e.g., bitcoin:address?amount=0.1). However, Stacks doesn’t currently support a universal payment link format, so I had to settle for QR codes that only contain the recipient’s address, requiring users to manually enter the amount and memo.

I believe adding universal payment links for STX and tokens (e.g., stackspay:stx1abc...xyz?amount=100&token=STX&memo=Invoice123) would be a game-changer for the ecosystem. It would:
✅ Enable seamless integration between wallets and apps.
✅ Improve the user experience by eliminating manual data entry.
✅ Make STX payments feel as smooth as Lightning payments in Bitcoin.

Would love to hear your thoughts on this! Is this something that could fit into Stacks Pay?

dantrevino · 2025-04-02T19:42:37Z

Hey Dan 👋

Awesome work on this! I wanted to share some thoughts based on my experience building Stacks Invoice Generator, where I tackled invoice generation for STX and Stacks tokens without smart contracts. One of the biggest challenges I faced was QR code functionality.

Initially, I wanted users to scan a QR code and have it automatically open their wallet (Xverse/Leather) with all payment details pre-filled—similar to Bitcoin or Ethereum payment URIs (e.g., bitcoin:address?amount=0.1). However, Stacks doesn’t currently support a universal payment link format, so I had to settle for QR codes that only contain the recipient’s address, requiring users to manually enter the amount and memo.

I believe adding universal payment links for STX and tokens (e.g., stackspay:stx1abc...xyz?amount=100&token=STX&memo=Invoice123) would be a game-changer for the ecosystem. It would: ✅ Enable seamless integration between wallets and apps. ✅ Improve the user experience by eliminating manual data entry. ✅ Make STX payments feel as smooth as Lightning payments in Bitcoin.

Would love to hear your thoughts on this! Is this something that could fit into Stacks Pay?

QR codes are a core part of the experience i the proposal. Check out https://stackspay.org/ and the Merchant Section in the spec for details. The encoding also has the benefit of providing checksum so that users (stackpay parsers) can ensure that the QR codes have not been tampered with.

dantrevino added 5 commits September 26, 2024 10:10

add sip

a67e190

update per recommendations

8ca9162

clarify purpose, clarify default functions for mint and transfer

cfcd542

clarify transfer default, code layout

fa5f8ba

Merge branch 'main' into feature/stacks-pay

6866f12

dantrevino mentioned this pull request Dec 2, 2024

Boom Payment Request Standard - Dan T. stacksgov/decentralized-grants#8

Open

dantrevino changed the title ~~Feature/stacks pay~~ Stacks Pay: A Payment Request Standard for Stacks Blockchain Payments Dec 2, 2024

kyranjamie reviewed Dec 4, 2024

View reviewed changes

whoabuddy reviewed Dec 13, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Stacks Pay: A Payment Request Standard for Stacks Blockchain Payments #202

Stacks Pay: A Payment Request Standard for Stacks Blockchain Payments #202

dantrevino commented Dec 2, 2024

binxbrigandine commented Dec 2, 2024

markmhendrickson commented Dec 4, 2024

kyranjamie left a comment

kyranjamie Dec 4, 2024

dantrevino Dec 4, 2024

pradel Dec 21, 2024

dantrevino Dec 23, 2024

kyranjamie Dec 4, 2024

dantrevino Dec 4, 2024

whoabuddy left a comment

whoabuddy Dec 13, 2024

dantrevino Dec 15, 2024

whoabuddy Dec 13, 2024

whoabuddy Dec 13, 2024

whoabuddy Dec 13, 2024

whoabuddy Dec 13, 2024

whoabuddy Dec 13, 2024

friedger commented Mar 7, 2025

flormpecasique commented Apr 1, 2025 •

edited

Loading

dantrevino commented Apr 2, 2025


		contractName, functionName: Wallets MUST ignore these parameters if present.

		### `mint`


		Stacks Pay defines several standard operations that specify the type of payment action to be performed. Each operation type has specific required and optional parameters.

		### `support`


		Optional Parameters:

		- recipient: MAY be included; if present, MUST be a valid Stacks address. The NFT will be minted for the specified address.

		Example encoded Stack Pay url:

		`stx1wajky2mnw3u8qcte8ghj76twwehkjcm98ahhqetjv96xjmmw845kuan0d93k2fnjv43kjurfv4h8g02n2qe9y4z9xarryv2wxer4zdjzgfd9yd62gar4y46p2sc9gd23xddrjkjgggu5k5jnye6x76m9dc74x4zcyesk6mm4de6r6vfsxqczver9wd3hy6tsw35k7m3a2pshjmt9de6zken0wg4hxetjwe5kxetnyejhsurfwfjhxst585erqv3595cnytfnx92ryve9xdqn2wf9xdqn2w26juk65n`


		### Encoding and Decoding

		Stacks Pay URLs MUST be encoded using Bech32m encoding with the human-readable part (HRP) set to `'stx'` and a `limit` of 512. This ensures compatibility and data integrity, making it suitable for QR codes and platforms with URL limitations.

Stacks Pay: A Payment Request Standard for Stacks Blockchain Payments #202

Are you sure you want to change the base?

Stacks Pay: A Payment Request Standard for Stacks Blockchain Payments #202

Conversation

dantrevino commented Dec 2, 2024

binxbrigandine commented Dec 2, 2024

markmhendrickson commented Dec 4, 2024

kyranjamie left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

whoabuddy left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

friedger commented Mar 7, 2025

flormpecasique commented Apr 1, 2025 • edited Loading

dantrevino commented Apr 2, 2025

flormpecasique commented Apr 1, 2025 •

edited

Loading