Private preview

Deposit mode stablecoin payments Private preview

Accept stablecoin payments with API-only deposit addresses.

Deposit mode is an API-only crypto payment flow where we return deposit addresses for each requested network. When your customer sends funds to a deposit address, we automatically capture the PaymentIntent after the funds settle on-chain.

Before you begin

Access to deposit mode is required.

Regional considerations United States

Stablecoin payments are available to businesses in all US states, except New York.

To start accepting stablecoin payments:

1. Make sure you’ve set up your Stripe account .
2. Go to your Payment methods settings in the Dashboard and request the Stablecoins and Cryptocurrency payment method. If you want to accept stablecoin or cryptocurrency payments only for machine payments , create a separate payment method configuration dedicated to machine payments.
3. Stripe reviews your access request and contacts you for more details if necessary. The payment method appears as Pending while we review your request.
4. After we approve your request, the Stablecoins and Cryptocurrency payment method becomes active in the Dashboard.

Create a PaymentIntent

Create a PaymentIntent with the crypto payment method and mode: "deposit". Specify the networks that you want deposit addresses for by using deposit_options.networks.

API version

This feature requires the 2026-03-25.preview API version. Set the Stripe-Version header to 2026-03-25.preview when initialising your Stripe client.

Command Line

Select a language

cURL

Stripe CLI

Ruby

Python

PHP

Java

Node.js

Go

.NET

No results

PaymentIntent response

The confirmed PaymentIntent includes crypto_display_details in next_action, which contains deposit addresses and supported_tokens for each network:

{
 "id": "pi_123",
 "amount": 5000,
 "currency": "usd",
 "status": "requires_action",
 "next_action": {
 "type": "crypto_display_details",
 "crypto_display_details": {
 "deposit_addresses": {
 "base": {
 "address": "0xbase_address",
 "supported_tokens": [
 {
 "token_currency": "usdc",
 "token_contract_address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
 }
 ]
 },
 "tempo": {
 "address": "0xtempo_address",
 "supported_tokens": [
 {
 "token_currency": "usdc",
 "token_contract_address": "0x20c000000000000000000000b9537d11c60e8b50"
 }
 ]
 },
 "solana": {
 "address": "So1ana_deposit_address",
 "supported_tokens": [
 {
 "token_currency": "usdc",
 "token_contract_address": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"
 }
 ]
 }
 }
 }
 }
}

Present the deposit address to your customer along with the expected amount and supported tokens. Your customer sends the correct token to the deposit address on the specified network.

Payment lifecycle

Use the following steps to understand how a deposit-mode PaymentIntent moves from confirmation to completion.

1. After you confirm the PaymentIntent , it enters the requires _ action status with deposit address details. The Stripe Dashboard displays these PaymentIntents as Incomplete while it waits for your customer to send funds.
2. Your customer sends funds to the deposit address on-chain.
3. Stripe detects the on-chain transaction and move the PaymentIntent to processing while we validate the transaction details.
4. After validations complete, the PaymentIntent moves to succeeded .

Transfer detection delay

It can take a few minutes for us to detect the transfer after the network confirms it.

If the transaction fails validation or we can’t match the deposit, the PaymentIntent returns to requires_payment_method. Otherwise, the PaymentIntent remains in requires_action.

Transaction details

After the PaymentIntent succeeds, retrieve on-chain transaction details by expanding latest_charge on the PaymentIntent. The payment_method_details.crypto hash on the charge includes fields such as the transaction hash, buyer wallet address, network, and token currency.

Failure modes

Use the following scenarios to understand when we can’t match a deposit to a PaymentIntent.

• Wrong network or asset : If your customer sends tokens on a network or with a token contract that doesn’t match the deposit address, we can’t automatically match or return the funds.
• Funds after expiry : If your customer sends funds after the PaymentIntent expires, we can’t automatically match or return the funds.
• Overpayment or underpayment : The token amount that your customer transfers must exactly match the amount on the PaymentIntent . If your customer sends more or less than the specified amount, we can’t automatically match or return the funds.
• The transferred token amount must exactly match the PaymentIntent amount. Because fiat currencies and stablecoins use different decimal precisions, account for this difference when you calculate the transfer. For example, USD uses two decimal places, while the related setting uses six. To fulfil a PaymentIntent for 1.01 USD (101 minor units), your customer must transfer exactly 1.010000 the related setting (1,010,000 minor units).

Refunds

When you refund a deposit mode payment, we return funds to the sending wallet address from the detected on-chain transaction.

Caution

Make sure that you verify the destination address before you initiate the refund. If your customer paid from an exchange or omnibus wallet, they might not be able to recover refunded funds.

Token and network support

PaymentIntents with the crypto payment method in mode: deposit support the related setting on the following networks:

Test your integration

Sandboxes don’t monitor crypto testnets, so we can’t automatically detect testnet transactions that you send. Instead, use the test helper endpoint to simulate crypto deposits for sandbox PaymentIntents. This lets you verify your integration immediately without relying on on-chain transactions.

Command Line

cURL

To simulate different outcomes, set transaction_hash to one of the following:

See also

• Machine Payments