# Examples

To demonstrate the concept more clearly, I decided to create a simple prototype through which a user can play a song (one of the digital content), and if the user likes it, the user can buy it. While purchasing any digital content such as a song (in this case) using the website, in a confirmation payment dialogue, they get to know about the song name, artist, and song image(send as base64 encoded string, decode on Alby side).

After successful payment, a song gets downloaded into users’ local storage. 🎉

* [**BuySong.mp4**](https://drive.google.com/file/d/1WUZybY3d-MTbcdlMRGQK_zTJHU7PVeIV/view) is a video that shows an example
* [Prototype Code](https://github.com/pavanjoshi914/Buy-songs-with-Alby-demo-for-transaction-metadata/pull/1)
* [Alby with extended webLN specification](https://github.com/pavanjoshi914/Alby-With-extended-Webln/commit/ed6f7559de47b7a9c932e655fb45be9481856714)


---

# Agent Instructions: 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:

```
GET https://pavan-joshi.gitbook.io/making-payment-transactions-smart/applications/examples.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.