> For the complete documentation index, see [llms.txt](https://swopple.gitbook.io/swop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swopple.gitbook.io/swop/major-concepts/nfc.md). # NFC show the different nfc use cases The Near Field Communication (NFC) functionality within the Swopple ecosystem is envisioned as a public good, designed to enhance the platform's usability and accessibility. By offering open-source code for NFC integration, Swopple empowers developers and users to leverage NFC technology for a variety of blockchain-based applications, including payments, identity verification, and secure access. #### NFC for Payments * **Simplified Transactions:** NFC technology facilitates contactless payments directly through the blockchain, streamlining the process of transferring digital assets. Users can make payments by simply bringing their NFC-enabled device close to another NFC point, such as a payment terminal or another user's device, initiating a secure and instantaneous transaction. * **Integration with Swop.ID:** Payments through NFC can be linked to the user's Swop.ID, allowing for seamless identification and authentication during transactions. This integration ensures that each payment is securely associated with the user's decentralized identity, enhancing trust and transparency in the transaction process. #### NFC for Wallet Creation and Access * **Wallet Creation:** The open-source NFC code provided by Swopple enables users to create a digital wallet that is compatible with NFC technology. This wallet can store digital assets and facilitate transactions within the Swopple ecosystem, offering a convenient and secure method for managing blockchain-based assets. * **Secure Login:** NFC technology can also be utilized for secure login purposes, allowing users to access their digital wallets or other sensitive areas of the Swopple ecosystem by tapping an NFC-enabled device. This method provides an additional layer of security, ensuring that only the rightful owner can gain access to the wallet or sensitive information. #### Open-Source Accessibility * **Empowering the Community:** By making the NFC integration code available as a public good, Swopple encourages innovation and experimentation within the community. Developers can customize and extend the NFC functionality to suit their specific needs or create new applications that leverage this technology. * **Promoting Standardization:** Offering open-source NFC code helps promote standardization across the ecosystem, ensuring that NFC-based applications and services are compatible and interoperable. This fosters a cohesive user experience and encourages wider adoption of NFC technology within the Swopple ecosystem. #### Conclusion The adoption of NFC as a public good within the Swopple ecosystem underscores the platform's commitment to leveraging advanced technologies to enhance user experiences and security. By providing open-source NFC integration code, Swopple not only empowers developers to innovate but also enables users to engage in secure, convenient, and seamless transactions and interactions. This approach reflects Swopple's dedication to building a user-centric, accessible, and secure blockchain ecosystem. --- # 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://swopple.gitbook.io/swop/major-concepts/nfc.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.