Home › Free tools › Stripe basil field checker

Stripe basil field checker for webhook payloads

current_period_end is undefined, or invoice.subscription is missing? Stripe removed or moved those fields in API version 2025-03-31.basil. Paste a webhook event or an API object below. This page lists every affected field it finds, where to read it now, and reads the subscription id and billing-period end from either shape.

What the checker looks for

These are the payload fields Stripe's changelog lists as removed in 2025-03-31.basil, by object:

• Subscription: current_period_start and current_period_end moved to each subscription item (items.data[].current_period_end). Source: Stripe changelog: subscription item-level billing periods.
• Invoice, invoice item, invoice line item: subscription, subscription_details, quote, subscription_proration_date, and on line items subscription_item, invoice_item, proration, proration_details and type, moved under a new parent field. Source: Stripe changelog: invoicing resources specify how they were generated.
• Invoice payments: payment_intent, charge, paid, paid_out_of_band, application_fee_amount and transfer_data were removed from the invoice, and invoice from PaymentIntent and Charge. Invoices now have an expandable payments list. Source: Stripe changelog: multiple (partial) payments on invoices.
• Prices on invoice items and line items: price and plan moved to pricing (pricing.price_details.price). Source: Stripe changelog: price modeling on invoice items.
• Taxes: tax and total_tax_amounts on the invoice became total_taxes; tax_amounts and tax_rates on line items became taxes. Source: Stripe changelog: tax modeling on invoices.
• Checkout Session: shipping_details moved to collected_information.shipping_details. Source: Stripe changelog: Checkout Session removes shipping details.

Checked 26 Oct 2026. A field that is present with the value null still counts as the old shape: older versions include it as null on, for example, one-off invoices.

Why your webhook still gets the old shape

Each webhook endpoint has its own API version, and Stripe uses it to structure the event payloads it sends there. An event's api_version is the version used to render its data, and it never changes afterwards. So after an SDK upgrade, API calls can return the basil shape while webhook events keep arriving in the old one until you upgrade the endpoint, and resent old events keep their original shape. The checker compares the event's api_version with the fields it finds.

Sources: Stripe: Handle webhook versioning; Stripe API reference: the Event object.

What this checker doesn't do

• It checks field names in the JSON you paste. It doesn't call Stripe or read your account's settings.
• It covers the payload changes above, not every basil change (for example request parameters, coupons or usage-based billing).
• Fields that are only returned when expanded, such as an invoice's payments, appear only if your payload includes them.