> For the complete documentation index, see [llms.txt](https://dev.simplepay.ai/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.simplepay.ai/docs/introduction/protocol.md).
# Protocol
## Workflow
The SimplePay Transaction Protocol delineates a sophisticated framework for cryptocurrency-based payment processing, leveraging the immutable and decentralized properties of blockchain technology. By eschewing custodial intermediaries and prioritizing seamless integration, this protocol exemplifies a paradigm shift in digital commerce, offering enhanced security, operational efficiency, and user-centric adaptability.
***
### **Invoice Generation**
Merchants instantiate a payment request through the Simple Console interface or programmatically via the API.
An invoice encapsulates the requisite transactional parameters, including:
* **Monetary Value:** The precise cryptocurrency denomination required.
* **Asset Specification:** The digital token (e.g., BTC, ETH) and corresponding blockchain network.
* **Ancillary Metadata:** Supplementary identifiers such as client IDs or descriptive narratives, augmenting the invoice's contextual relevance in **Payload** field.
This stage establishes a deterministic reference for subsequent payment validation.
***
### **Dynamic Payment Artifacts**
Upon invoice instantiation, the system generates:
* **Hyperlinked Payment Gateway:** A URL enabling payment execution.
* **Encoded QR Artifact:** A graphical abstraction facilitating mobile-first payment initiation.
These artifacts are disseminated to end-users via merchant-defined communication channels, enhancing accessibility and convenience.
***
### **Transaction Initialization**
Users interact with the provided artifacts using compliant cryptocurrency wallets.
The wallet auto-populates key transactional attributes, including:
* Recipient blockchain address.
* Exact payment quantum.
* Token denomination, ensuring network compatibility.
User validation triggers blockchain propagation of the payment intent.
***
### **On-Chain Verification:**
The protocol executes real-time interrogation of the blockchain ledger to ascertain:
* Concordance between remittance and invoice specifications.
* Transactional integrity, ensuring funds are routed to the designated address.
Any anomalies prompt corrective feedback mechanisms, preserving transactional fidelity.
***
### **Transaction Finalization**
Post-verification, the invoice transitions to a "Success" state.
Merchant interfaces (e.g., dashboard, webhook notifications) reflect the updated status, facilitating:
* Immediate acknowledgment of payment receipt.
* Integration into auxiliary workflows such as inventory release or service provisioning.
All transactional data is archived within the protocol's analytics suite for longitudinal assessment and compliance verification.
***
## Security Features
* **Blockchain Transparency:** All transactions are visible on the blockchain for auditability.
* **End-to-End Encryption:** Secures data exchange between users and merchants.
* **Non-Custodial Model:** Merchants receive funds [directly into their wallets](/docs/introduction/core-concepts/direct-payments.md)
{% hint style="info" %}
**Hint:**\
See more details in [Security section](/docs/introduction/security.md)
{% endhint %}
{% content-ref url="/pages/OXGNSJnnqPNc6GzLti7W" %}
[Security](/docs/introduction/security.md)
{% endcontent-ref %}
{% content-ref url="/pages/3dprTPgecajIe4LiSb9t" %}
[Collected data](/docs/introduction/security/collected-data.md)
{% endcontent-ref %}
***
---
# 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:
```
GET https://dev.simplepay.ai/docs/introduction/protocol.md?ask=
```
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.