diff --git a/buds/07.md b/buds/07.md
index 071f6e9..37355f9 100644
--- a/buds/07.md
+++ b/buds/07.md
@@ -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:
 
-Header Format:
-
 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.
-- `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.
+- `amount`: Payment amount in the method’s smallest unit.
\ No newline at end of file