Adds support for Phantom Cash and the related setting to stablecoin payments
What’s new
The token_currency property of the Charge object’s payment_method_details.crypto hash now supports phantom_cash and usdt as property enum values.
Impact
The read-only token_currency property of the Charge object’s payment_method_details.crypto hash can now be phantom_cash or usdt. These values indicate that the customer completed a payment using one of these tokens.
If your integration manages crypto payments, update your integration to support the new phantom_cash and usdt token currency values when reading payment method details. This helps you identify and process crypto payments made with these tokens.
Changes
| Values | Change | Enums |
|---|---|---|
| phantom_cash usdt | Added | PaymentAttemptRecord. payment_method_details. crypto PaymentRecord. payment_method_details. crypto Charge. payment_method_details. crypto |
Upgrade
- View your current API version in Workbench.
- If you use an SDK, upgrade to the corresponding SDK version for this API version.
- If you don’t use an SDK, update your API requests to include Stripe-Version: 2026-04-22. dahlia
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.