@relai-fi/x402 0.6.9 → 0.6.11-rc.0

package/README.md

@@ -1751,6 +1751,8 @@ import {
   getPayRequest,
   payPayRequest,
   payPayRequestWithCode,
+  payPayRequestWithStoredCode,
+  type PaymentRequestObject,
 } from '@relai-fi/x402';
 
 const config = { facilitatorUrl: 'https://relai.fi/facilitator' };
@@ -1784,6 +1786,16 @@ console.log('Explorer:', result.explorerUrl);
 if (result.changeCode) {
   console.log(`Change $${Number(result.change) / 1e6} USDC → code: ${result.changeCode}`);
 }
+
+// ── Agent / vault flow: reuse a fetched request object directly ─────────────
+const fetchedRequest: PaymentRequestObject = await getPayRequest(config, 'MW78SGTW');
+const storedCodeResult = await payPayRequestWithStoredCode(
+  config,
+  fetchedRequest,
+  'MYVAULT78',
+  { returnChange: 'code' },
+);
+console.log('Stored code payment success:', storedCodeResult.success);
 ```
 
 ### `payPayRequestWithCode` options
@@ -1793,6 +1805,13 @@ if (result.changeCode) {
 | `returnChange` | `'code' \| 'wallet'` | `'code'` | How to return surplus when code value > invoice |
 | `allowOverpayment` | `boolean` | `true` | If `false`, throws when code value ≠ invoice amount |
 
+`payPayRequestWithStoredCode()` accepts either:
+
+- a payment request code string, or
+- a fetched `PaymentRequestObject` from `getPayRequest()`
+
+Passing the object lets agents skip the extra request lookup when they already have the decoded request in memory. For stored Solana codes, the object must include a valid `code` field because the Solana facilitator endpoint still resolves the merchant request by `requestCode`.
+
 **`returnChange` behaviour:**
 
 | Value | Mechanism | Requires buyer wallet? |