How airwallex/airwallex-payment-demo works
Project type and purpose
• This is not a single production service but a monorepo of “demo integrations” for the Airwallex Payment Element.
• Its purpose is to show merchants how to integrate the Airwallex JS SDK / REST API through various web frameworks (static HTML/CDN, React-TS SPA) and API examples (Node).
File structure
• Top-level:
• README.md, commitlint.config.js, version.sh, GitHub config (.github, .gitignore)
• docs/ – markdown docs for each payment method
• integrations/ – current, supported integration samples:
– cdn/ (static HTML + sandbox config + package.json)
– node/ (TypeScript Node backend, Express-style controllers in src/controller, config, app.ts)
– react-ts/ (Create-React-App TypeScript SPA under src/, components folder, util.ts, public/)
• integrations@deprecated/ – older framework samples (Angular, Vue, React w/o TS, ReactNative)
• payment-method-logos/ and special-cases/ – static assets
• Key patterns:
• A monorepo with multiple independent sub-projects
• Each integration has its own package.json, config (tsconfig, .eslintrc) and runs independently
• The Node sample is the only true “backend” that actually calls Airwallex REST API
Insights from the README
• Focus is on demonstrating the “Airwallex payment element” via several front-end frameworks
• Describes “Creating a Payment Intent” – merchant must insert secret via API (Node sample)
• Mentions sandboxes for live testing of CDN and React-TS samples
Details to capture
• The monorepo structure hosting multiple independent integration projects
• The role of the Node sample as the server-side component for secrets
• The client-side use of the Airwallex JS SDK
• The end-to-end checkout flow: user → front-end → back-end (optional) → Airwallex
• CI/CD or versioning (GitHub Actions, version.sh) as an optional build pipeline component