Stablecoin cards: from purchase to refund

Where does the money go when you pay with a stablecoin card, and where does it come back? You buy a pair of shoes and the payment is approved. A few days later you return them and the merchant confirms a refund, yet the funds have not reappeared in your wallet. The tap at checkout felt familiar; what follows is less clear.

A stablecoin card lets you spend a balance of tokens designed to track a currency’s value. But a purchase involves several systems that do not necessarily move together. Understanding where the money is means following the transaction beyond “approved.” The details below draw in particular on the Bridge and Stripe Issuing program; they do not describe every card on the market.

Approval starts the journey at checkout

Visa describes a payment that looks familiar to the merchant: the program checks the customer’s funds and arranges conversion where needed. The merchant can receive local currency without receiving the wallet’s tokens. [1]

Authorization and the final charge are separate steps. In Stripe Issuing, an approved authorization reserves an amount; the merchant can then collect it through capture. An authorization may also be reversed or expire without capture. [2]

The wallet can run on another timeline. Bridge says the authorization event may arrive before the blockchain transaction is confirmed. “Approved” therefore does not establish that every entry has finished processing. [3]

For the shoe purchase, these distinctions stay out of sight while everything goes as expected. They become useful when money appears stuck: a reserved amount and a collected payment call for different explanations.

The same tap can draw on differently controlled funds

Bridge offers two funding sources in particular: a wallet held in Bridge’s custody, or an external wallet debited under a prior permission. The second model avoids loading a separate card balance. [4]

This changes how money is entrusted and used, not merely what appears on the screen. Before funding a card, it helps to understand which balance it draws on. Owning tokens somewhere does not mean that this particular card can spend them.

For the external wallet flow, Stripe says Bridge declines an authorization when the permission is missing, its amount is insufficient or the wallet cannot cover the purchase. [5]

A decline could therefore reflect a spending permission that is too small even though money remains visible in your wallet. The app should help identify that situation before asking you to add funds.

Holding the keys can coexist with delegated spending

Spending without topping up depends on something done before the purchase. Bridge requires permission for its contract to pull money from the wallet. The payment at checkout uses that existing permission. [6]

For ERC-20 tokens, an approval names an address allowed to spend and an amount. That permission can cover repeated withdrawals within the allowance; another approval can change it. Signing for a single purchase and granting ongoing spending capacity are different actions. [7]

Control then depends on what you can understand and change: which contract has permission, which token it covers, how much it can spend and how to remove that permission. The label “non-custodial” does not answer those questions on its own.

Returning the shoes starts another transaction

Once a purchase has been captured, its refund is a separate transaction. Stripe says refunds can be processed even after a card has been deactivated or canceled. The card’s status and the refund’s status are different things. [8]

In the Bridge integration documented by Stripe, returning funds to the wallet requires another blockchain transaction, confirmed separately. Several returns may be batched together. [5]

Return to the shoes. The merchant’s agreement, the refund recorded by the card program and the arrival of tokens are separate pieces of information. Following the case may require more than the purchase date and amount: the refund reference and processing status can matter too.

A blockchain transaction can establish that tokens moved. It cannot explain the entire purchase on its own. The card service needs to connect those records so you can tell whether you are waiting on the merchant or the return of funds.

Control also depends on the authorized software

On June 1, 2026, a vulnerability affected modules used by Gnosis Pay. In its July report, Gnosis attributed the incident to a faulty signature check and said it had restored users’ funds. [9]

The case shows why control over a wallet does not describe every risk in a service. Software components permitted to act on funds matter too. The restoration reported in this incident does not guarantee reimbursement for every card or every failure.

The actions an app offers also need to be distinguished. Gnosis Pay describes freezing a card as a reversible suspension of its use, with funds remaining in the Safe, its blockchain account. [10]

Freezing a card and removing a token permission act on different things. An interface that does not explain the difference can imply more control than the action provides.

What an everyday card needs to explain

The appeal is a familiar way to spend a digital balance. The quality of the service also shows up when things are less smooth: a declined authorization, a pending amount or a refund that needs tracing.

Your purchase provides the useful reference point. You should be able to identify the balance charged, understand the permission you granted and find whoever can track returning funds. For the shoes, the story ends when the refund is available and identifiable in your records. Approval at checkout marked the beginning.

Further reading: the services Stripe is bringing together and how a wallet works.

Sources

• [1] Visa, stablecoin card flows, accessed October 10, 2026
• [2] Stripe, authorization lifecycle, accessed October 10, 2026
• [3] Bridge, card and blockchain events, accessed October 10, 2026
• [4] Bridge, card funding models, accessed October 10, 2026
• [5] Stripe, Bridge checks and returns of funds, accessed October 10, 2026
• [6] Bridge, wallet spending permissions, accessed October 10, 2026
• [7] Ethereum, ERC-20 standard and spending allowances
• [8] Stripe, captures and refunds, accessed October 10, 2026
• [9] Gnosis, June incident report, published July 3, 2026
• [10] Gnosis Pay, freezing a card, updated September 18, 2026