From e10185c4fec4e7964b7ac8829b1e75f76310ab45 Mon Sep 17 00:00:00 2001
From: Abu Olumi <96758182+2TheMoom@users.noreply.github.com>
Date: Sat, 20 Jun 2026 08:13:55 +0100
Subject: [PATCH] docs: use X-PAYMENT header consistently in x402 Next.js
 example

The PAYMENT-SIGNATURE fallback is not part of the x402 spec.
The protocol uses only X-PAYMENT. Simplified to one consistent header.
---
 build-on-celo/build-with-ai/x402.mdx | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/build-on-celo/build-with-ai/x402.mdx b/build-on-celo/build-with-ai/x402.mdx
index 9da931379..e6d684eb3 100644
--- a/build-on-celo/build-with-ai/x402.mdx
+++ b/build-on-celo/build-with-ai/x402.mdx
@@ -142,9 +142,7 @@ const thirdwebFacilitator = facilitator({
 });
 
 export async function GET(request: Request) {
-  const paymentData =
-    request.headers.get("PAYMENT-SIGNATURE") ||
-    request.headers.get("X-PAYMENT");
+  const paymentData = request.headers.get("X-PAYMENT");
 
   const result = await settlePayment({
     resourceUrl: "https://your-api.com/premium-content",