Feature/examples cloudfront and lambda as x402 seller middleware #980
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat(examples): add CloudFront Lambda@Edge server example Reference implementation for adding x402 payments at the edge without modifying backend code. - Add complete Lambda@Edge handler implementation for x402 payment verification - Include configuration system for route-based pricing and payment settings - Add payment verification and settlement logic via x402 facilitator - Include response formatting for 402 Payment Required and success cases - Include advanced patterns for WAF integration, caching optimization, and cookie-based sessions
…bda-as-x402-seller-middleware
🟡 Heimdall Review Status
|
|
@arditti is attempting to deploy a commit to the Coinbase Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a CloudFront + Lambda@Edge example demonstrating how to add x402 payments to any web server without modifying the backend. This pattern allows payment verification at the edge, working with any HTTP origin (AWS, GCP, Azure, on-prem, or third-party APIs).
Key features:
Zero backend changes required - origin server stays untouched
Route-based payment configuration with glob pattern matching (* and **)
Facilitator integration for payment verification and settlement
Support for Base Sepolia (testnet) and Base Mainnet networks
Files added:
Tests
This is a reference implementation example. Verified by:
Checklist