Skip to content

[blocked] Add MoonPay Apple Pay onramp#150

Open
mashbean wants to merge 2 commits into
developfrom
codex/moonpay-onramp
Open

[blocked] Add MoonPay Apple Pay onramp#150
mashbean wants to merge 2 commits into
developfrom
codex/moonpay-onramp

Conversation

@mashbean

@mashbean mashbean commented May 22, 2026

Copy link
Copy Markdown

Blocked

  • MoonPay partner application was rejected on 2026-05-29.

  • Do not merge this as the production on-ramp path unless MoonPay approval is reopened or the integration is repurposed behind a disabled/fallback path.

  • Next on-ramp evaluation is Onramper/Ramp/Transak/Banxa; open bidding itself should continue separately from fiat on-ramp.

Summary

  • add a server-signed MoonPay Apple Pay top-up route for Optimism USDT (usdt_optimism)
  • replace the insufficient-balance top-up button in the bid flow with the MoonPay path
  • enforce a 20 USDT minimum MoonPay top-up to avoid disproportionately expensive tiny purchases
  • document MoonPay/Vercel setup, release-evaluation gates, cost policy, and cross-system acceptance checks

Validation

  • Rebased branch onto origin/develop; PR base is now develop.
  • Confirmed PR diff against origin/develop only contains MoonPay/env/docs/bid-flow changes.
  • git diff --check origin/develop...codex/moonpay-onramp passed.
  • Checked changed files for conflict markers after rebase; none found.
  • Vercel check passed on develop-based PR head bbdacc7.
  • Before the develop rebase, npm run lint, npm run build, and local /api/moonpay smoke test passed on the previous main-based branch.
  • After the develop rebase, local Node tooling hangs on eslint, tsc --noEmit, and remix vite:build without producing diagnostics; relying on the passing Vercel check for the develop-based head until local tooling is refreshed.

Notes

  • Production still needs MoonPay production keys approved for usdt_optimism, Apple Pay, active domains, and launch countries.
  • Confirm MoonPay commercial terms before production approval: setup fee, monthly minimum, minimum volume commitment, and whether ecosystem/affiliate fees are enabled.
  • This PR assumes Matters should not add an ecosystem or affiliate fee at launch.
  • Production payment or bid smoke tests require explicit human approval under the release-evaluation SOP.

@vercel

vercel Bot commented May 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
matters-billboard-app Ready Ready Preview May 28, 2026 1:41pm

Request Review

@mashbean mashbean force-pushed the codex/moonpay-onramp branch from 6b00b38 to bbdacc7 Compare May 28, 2026 13:41
@mashbean mashbean changed the base branch from main to develop May 28, 2026 13:41
@mashbean mashbean changed the title [codex] Add MoonPay Apple Pay onramp [blocked] Add MoonPay Apple Pay onramp May 29, 2026
@mashbean

Copy link
Copy Markdown
Author

Blocked: MoonPay partner application was rejected on 2026-05-29. This PR should not be merged as the production on-ramp path unless MoonPay approval is reopened or the integration is repurposed behind a disabled/fallback path. Evaluating Onramper next.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant