Skip to main content
Stripe is a card funding provider: the user pays with a card and Trails receives USDC on Base, which then routes to the intent’s destination like any other origin funds. It joins Meld as a card-category provider, and sits alongside the Mesh exchange provider. This page covers the onramp, where a card funds crypto. For the reverse direction, where a shopper pays in crypto and you settle in USD on your own Stripe account, see Stripe checkout. Requires 0xtrails@0.18.3 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 the onramp 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. Stripe is enabled per project as part of Polygon Checkout; book a demo or talk to sales there, or reach the Trails team on Telegram, to have it turned on for your project.
The tile renders only when the API reports Stripe as enabled for your project and country. Unlike the general onramp availability check, Stripe fails closed: while availability is pending or errored the tile stays hidden rather than showing and failing later.

​
Control its placement

Stripe’s identifier in fundOptions.fundMethodsList is "stripe-onramp":
From 0xtrails@0.18.5 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

  1. The user picks Pay with Stripe on the funding or payment method screen.
  2. They enter an amount (in pay mode the amount is fixed by the payment request); Trails quotes the purchase.
  3. On submit, a popup opens, the intent is committed, and Trails creates a Stripe onramp session keyed to the intent.
  4. The user completes the card payment in the popup while the widget monitors session status.
  5. Funds arrive as USDC on Base and the intent proceeds to its normal pending and receipt screens.
Stripe is available in fund, swap and pay modes.

​
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.
In sandbox, Stripe settles on Base Sepolia and always delivers a fixed 0.5 USDC regardless of the amount quoted, and source amounts below $1.00 are clamped up to $1.00. Do not read sandbox delivery amounts as a test of production quoting.

​
Compared with the other providers

​
Pre-selecting the tile

To open the widget directly on the Stripe onramp screen, set fundMethod="onramp-stripe" (WidgetFundMethod.OnrampStripe). Explicit selection bypasses the availability gate that only prunes default options, so Stripe must be enabled for your project or the checkout fails at quote time.

​
In a merchant checkout

A Stripe checkout integration can keep the onramp tile enabled so that a shopper with no crypto pays the same order with a card. The card purchase funds the intent, and the intent settles to the merchant’s Stripe account like any other checkout payment.