No working fiat onramp path for Cadence-native dApps

Summary

There is no clear, working fiat onramp solution for Cadence-native dApps on Flow. Developers building on Cadence have no documented path to let users pay with credit card and start interacting with the chain.

What we tried

Stripe

• Multiple LLMs and our own research confirm Stripe does not support Flow as an onramp
• Flow team acknowledged this was "aspirational" rather than a currently available option

Magic.link

• Walletless onboarding works — users can log in with email and get a Flow wallet
• Problem: Magic.link wallets are under-funded. Users log in, have a wallet, but can't do anything because they have no FLOW to pay for transactions
• No built-in way for users to fund their Magic.link wallet with a credit card

MoonPay

• Reportedly shifted from Flow Cadence to Flow EVM support
• Unclear which tokens are supported (may be FLOW only, not stables)
• For Cadence-native dApps, this requires creating a COA (Cadence-Owned Account) for EVM bridging — adding complexity with no documentation

Crossmint

• Recommended for Flow EVM, not Cadence-native

The developer experience today

1. Developer builds Cadence-native dApp
2. Integrates Magic.link for walletless onboarding (works great)
3. User signs up with email, gets a wallet
4. User wants to do something → needs FLOW → no way to buy it in-app
5. Developer is stuck

There's no "insert credit card → get FLOW → use dApp" flow that works end-to-end for Cadence-native apps.

What would solve this

Any one of:

1. Magic.link + fiat onramp integration — Let Magic.link wallets be funded via credit card directly (requires Magic.link to increase FLOW funding and/or integrate an onramp)
2. MoonPay Cadence support — Confirm and document MoonPay working with Cadence wallets, not just EVM
3. Stripe onramp for Flow — Even sandbox support would unblock developers
4. A documented recommended path — If the answer is "use MoonPay via COA bridging," document it end-to-end with code examples

Context

This came up during active dApp development (Vaultopolis — NFT marketplace on Flow Cadence). Discussed with Flow team in Discord who confirmed the gaps and said they'd push internally on both Magic.link and Stripe sides. Filing publicly so other developers hitting the same wall can track progress.

Impact

This is a significant barrier to user onboarding for any Cadence-native dApp targeting non-crypto users. The whole promise of walletless onboarding breaks down if users can't fund their wallet without already owning crypto.

The issue does not name files, tests, or a code entry point. Start by verifying the current Cadence-compatible onramp options and their funding and bridging requirements; done means either a confirmed end-to-end path or documentation of the supported limitations and recommended flow.