Adds the ability to list Payment Records
What’s new
Adds a list endpoint for Payment Records. You can retrieve all Payment Records for your account using GET /v1/payment_records, with results returned in reverse chronological order. You can paginate results with starting_after and ending_before and filter by creation time range ( created_after and created_before) and processor type ( processor_details_type).
Impact
If you use Payment Records to track payments processed through external processors, you can now query them directly without expanding from a PaymentIntent. This gives you a single flow to load both on-Stripe and off-Stripe payments for reporting or orchestration.
Changes
| Endpoint | Change | Resource |
|---|---|---|
| list | Added | PaymentRecord |
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-07-29. 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.
Related changes
- Adds the ability to update shipping options, consent collection, and future usage support on Payment Links
- Adds the ability to indicate that you don’t intend to reuse Samsung Pay and the related setting payment method types
- Adds customer and payment method details to the Refunds API
- Adds support for new banks to FPX payments
- Adds the related setting as a supported network for funding instructions
- Adds the allowed payment method types parameter to Payment Intents and Setup Intents
- Adds MB WAY support to the hosted invoice page
- Adds card network details to the Dispute object
