laantungir/blossom
1
0
Fork 0
mirror of https://github.com/hzrd149/blossom.git synced 2025-12-12 07:48:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

remove some texts

Browse Source
This commit is contained in:
Quentin
2024-11-18 12:41:43 +01:00
parent b450680b00
commit 8a4728e3e6
1 changed files with 2 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
buds/07.md
View File

@@ -148,19 +148,9 @@ If the client fails to provide the payment proof (expired invoice, invalid token
To support future payment methods (e.g., other Layer 2 solutions), the specification allows the addition of new X-{payment_method} headers. Each new method MUST adhere to the following: To support future payment methods (e.g., other Layer 2 solutions), the specification allows the addition of new X-{payment_method} headers. Each new method MUST adhere to the following:
Header Format:
New methods MUST use a unique `X-{payment_method}` header containing Base64 UrlSafe encoded JSON. New methods MUST use a unique `X-{payment_method}` header containing Base64 UrlSafe encoded JSON.
Required Fields: **Required Fields:**
- `identifier`: Unique reference for the payment. - `identifier`: Unique reference for the payment.
- `amount`: Payment amount in the method’s smallest unit. - `amount`: Payment amount in the method’s smallest unit.
Backward Compatibility:
Servers and clients MUST ignore unknown X-{payment_method} headers.
Documentation:
Any new payment method added in the future MUST follow the same structure as existing methods, ensuring that the `identifier` and `amount` fields are always present and well-defined. This consistency allows seamless integration of new methods without breaking compatibility for existing clients and servers.