Wu says that Privy officially announced that developers can now issue cards to users, allowing them to spend directly from their connected decentralized finance (DeFi) vault balances. Privy states that this solution is in collaboration with Stripe, and users' Privy balances can continuously generate yield before payment; when users pay with a stablecoin card, their wallet authorizes Stripe to pull vault shares, completing the share withdrawal, unwrapping, and settlement in a single transaction, without requiring users to manually redeem funds in advance. Stripe’s documentation shows that its stablecoin-supported card issuance service is currently in private preview, supporting connections to non-custodial wallets or stablecoin balances via Bridge, Privy, or third-party wallets.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 7
  • Repost
  • Share
Comment
Add a comment
Add a comment
MountainShadowsBeforeTheStorm
· 15h ago
Stripe now supports Bridge, Privy, and third-party wallets, the roadmap is quite open.
View OriginalReply0
SweepTheFloor
· 15h ago
Non-custodial + continuous interest generation + direct consumption, this three-piece combination puts pressure on traditional banks.
View OriginalReply0
BridgeBurner
· 15h ago
Wait, share withdrawal + unwrapping + settlement all in one transaction? The UX is indeed smooth.
View OriginalReply0
TvlDownBad
· 15h ago
Private preview, ah, still have to wait in line. Hope the public beta won't take too long.
View OriginalReply0
LunaCircuit
· 15h ago
If this Privy card becomes widespread, the idle USDC in my wallet can finally earn while I spend.
View OriginalReply0
GateUser-ebdc7d3a
· 15h ago
This wave of cooperation with Stripe is kind of interesting—DeFi earnings can be directly spent as money, finally no need to manually redeem.
View OriginalReply0