[email protected] or later.
Enable it
No SDK configuration is required — Stripe appears in the funding method list once the Trails API reports it as enabled for your project. Unlike the Mesh exchange tile, it does not depend on theonramp prop.
Pass the onramp.stripe config only when you need the sandbox:
No Stripe key is ever passed to the SDK. Stripe credentials live in the Trails API configuration, and the browser receives only a publishable key.
Contact the Trails team to have Stripe enabled for your project.
Control its placement
Stripe’s identifier infundOptions.fundMethodsList is "stripe-onramp":
[email protected] the default order is connected wallet, Stripe, credit card (Meld), crypto transfer, then exchange (Mesh). In 0.18.3 and 0.18.4
Stripe is last.
In pay mode the payment method screen ignores fundMethodsList and hideUnlistedFundMethods; Stripe shows there whenever it is enabled.
Flow
- The user picks Pay with Stripe on the funding or payment method screen.
- They enter an amount (in pay mode the amount is fixed by the payment request); Trails quotes the purchase.
- On submit, a popup opens, the intent is committed, and Trails creates a Stripe onramp session keyed to the intent.
- The user completes the card payment in the popup while the widget monitors session status.
- Funds arrive as USDC on Base and the intent proceeds to its normal pending and receipt screens.
Restrictions
Stripe enforces finer restrictions of its own at session creation — certain US states and per-asset rules — which surface as an unsupported-country
error during checkout rather than hiding the tile up front.
Below the $1.00 minimum, production refuses to quote and the widget shows a minimum-amount message.