Practical overview
When it fits
Use it when you want to inspect or adapt a serverless AWS design that connects invoice creation, EVM payment detection and fund sweeping.
Who it is for
- Developers evaluating or adapting an AWS-based digital-asset payment workflow.
- Merchants or technical teams seeking a starting point for invoice generation and EVM payment tracking.
Documented uses
- Generate invoices with a derived wallet address and a QR code containing payment details.
- Monitor pending invoices for native-asset or ERC-20 payments and update their status.
- Trigger gas top-ups when needed and sweep detected funds to a configured treasury wallet.
Requirements & limits
The sample is available as a public GitHub repository and lists an MIT-0 license. Deployment requires an AWS account and the documented development and blockchain-access prerequisites.
- The main implementation targets EVM-compatible chains; the README directs Solana and Sui users to separate implementations.
- The deployment depends on AWS services including Lambda, API Gateway, DynamoDB, EventBridge, Secrets Manager and SNS.
- The configured hot wallet needs native tokens to cover sweeping gas, and the treasury address is provided by the deployer.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Deploy the AWS payment sample
Prepare the documented configuration and deploy the sample stack with its setup script.
Before you start
- An AWS account
- Node.js 18 or later
- AWS CDK CLI
- Ethereum or EVM-compatible node access and an HTTPS RPC URL
- A treasury public address
Steps
Clone the repository and change into its directory.
Copy
.env-sampleto.envand configure the RPC URL, treasury address and hot-wallet private key.Run the command below to perform the documented automated installation, deployment and configuration.
npm run setup
Expected outcome
The sample's AWS payment stack is set up and deployed.
Guide limitations
- The setup requires AWS credentials and configured blockchain access.
- A test payer private key is optional for the documented execute_payment script.
- This guide covers deployment setup, not a completed payment transaction.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- aws-samples/sample-serverless-digital-asset-payments · Official homepage title · retained in its source language

