> For the complete documentation index, see [llms.txt](https://pavan-joshi.gitbook.io/making-payment-transactions-smart/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pavan-joshi.gitbook.io/making-payment-transactions-smart/introduction/making-payment-transactions-smart-with-structured-metadata.md). # Making Payment Transactions Smart With Structured Metadata ![Making Payments Transactions Smart With Structured Metadata](https://user-images.githubusercontent.com/55848322/177914181-886c6415-8b20-4dde-904b-7b027b744201.png) > A new future of Bitcoin transactions resulting into numerous usecases💰 Many different specifications such as LNURL, WebLN and many more bought a better solution to the UX of lightning network and enhanced applications of Bitcoin. On top of this, many broad applications such as: * Instant payments via a web browser using Bitcoin Sats (Eg. Alby) * Tippings for content writers, podcasts and streamers * Streaming sats * Instant purchases on the Web and many more came into working. Transaction lists, as we know them from our private bank accounts, are often a simple list of transactions sorted by date. Each transaction has data like sender, receiver, amount, reason and date. Similarly, Bitcoin transactions hold static data that doesn’t include much more relevant information to dive into it. What if transactions can have additional information(metadata)? Such as: * Purpose of transaction * What was given away to the user with that particular transaction * Accessing given away items right away from and out of the wallet * Allow users to interact with transactions depending on the additional information each transaction holds Every transaction can store additional information as metadata which can make specifications such as WebLN more broad and applicative in terms of interactivity and extend the scope of the Bitcoin use cases in numerous ways, building a whole different future for the lightning network and Bitcoin. This specification aims to extend existing technology standards such as **WebLN** to enrich transactions with additional information as structured metadata so that transactions containing static data contain more meaningful information, giving more interactivity to the transactions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://pavan-joshi.gitbook.io/making-payment-transactions-smart/introduction/making-payment-transactions-smart-with-structured-metadata.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.