[email protected] or later; destination-chain landing and the card provider picker arrive in [email protected].
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
The card category’s identifier infundOptions.fundMethodsList is "cc-onramp" (the old "stripe-onramp" alias was removed in [email protected]):
[email protected] the default order is connected wallet, card (Meld, "cc-onramp"), crypto transfer, then exchange (Mesh). Stripe has no
row of its own: the single Credit or debit card row opens a provider picker (titled “Pay by card”) listing Stripe, Meld, or both — Stripe or
Meld is chosen automatically by country, with a chooser only when both are available. In pay mode the card option is Stripe-only.
Filter the provider list with onramp.cardProviders:
cardProviders accepts "stripe" and "meld". Omit it to offer every provider the deployment advertises; unknown values are ignored, and a
list with no known value behaves like no list. Because pay mode is Stripe-only, ['meld'] leaves no card option in pay mode.
In pay mode the payment method screen ignores fundMethodsList and hideUnlistedFundMethods; the card option shows there whenever it is enabled.
Flow
- The user picks Credit or debit card on the funding or payment method screen. If both card providers are available for their country, a picker titled Pay by card lists them.
- They enter an amount (in pay mode the amount is fixed by the payment request); Trails resolves the landing token — the destination chain’s token when the provider supports it, else USDC on Base — then 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 on the landing chain 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.