We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 73 since January 2026, each linked to its source.
stripeWhen handling a GB bank account payout method on API version `2026-09-30.preview`, treat `usage_status.payments: eligible` as payment eligible and stop waiting for `confirmation_of_payee` or an Outbound Setup Intent `requires_action`.
If an Accounts v2 integration needs to accept Satispay payments, set `configuration.merchant.capabilities.satispay_payments.requested` to `true` when creating or updating the v2 Account. Read `status` and `status_details` for the capability state and context.
POST /v2/core/accounts
{"configuration":{"merchant":{"capabilities":{"satispay_payments":{"requested":true}}}}}When investigating account security, authentication, payout, or Issuing changes, list Activity Logs filtered to the relevant action groups. Inspect each entry’s type and details, plus actor, related_object, and request for investigation context.
curl https://api.stripe.com/v2/iam/activity_logs?action_groups[]=<action_group> -H "Authorization: Bearer <YOUR_SECRET_KEY>" -H "Stripe-Version: 2026-09-30.preview" -H "Stripe-Context: <CONTEXT>"If your integration filters or processes Balance Transaction `type` values, handle `issuing_dispute_provisional_credit` and `issuing_dispute_provisional_credit_reversal`. Use those types to distinguish provisional credit movements during reconciliation, and review Balance Reports that use `reporting_category`.
curl -G https://api.stripe.com/v1/balance_transactions -u "<secret_key>:" -d "type=issuing_dispute_provisional_credit"When configuring portal cancellation feedback, set the cancellation feature and its documented reason settings on the customer portal configuration. The available documentation does not show how to attach Billing Feedback Option resources.
curl https://api.stripe.com/v1/billing_portal/configurations/<configuration_id> -u "<secret_key>:" --data-urlencode "features[subscription_cancel][cancellation_reason][enabled]=true"When saving a card for future use, set `payment_method_options.card.setup_credential_usage` on a SetupIntent or a PaymentIntent with `setup_future_usage`. When charging a saved card off-session, set `payment_method_options.card.stored_credential_usage` to the usage type for that charge.
curl https://api.stripe.com/v1/setup_intents -u "<YOUR_SECRET_KEY>:" -d "customer=<CUSTOMER_ID>" -d "automatic_payment_methods[enabled]=true" -d "payment_method_options[card][setup_credential_usage]=unscheduled"For a Charge on a card payment with an associated mandate, retrieve the Charge with `expand[]=payment_method_details.card.mandate` to include the full Mandate object in the response. Without expansion, the field is the mandate ID when present, or `null`.
curl -G https://api.stripe.com/v1/charges/<CHARGE_ID> \
-u "<YOUR_SECRET_KEY>:" \
-d "expand[]=payment_method_details.card.mandate"If creating Checkout Sessions with `payment_method_types`, remove that parameter because it now returns HTTP 400. Use Dashboard-managed dynamic payment methods, or set `allowed_payment_method_types` to filter compatible methods; use `excluded_payment_method_types` to exclude methods.
curl https://api.stripe.com/v1/checkout/sessions \
-u <secret_key>: \
-d success_url="https://example.com/success" \
-d "line_items[0][price]"=<price_id> \
-d "line_items[0][quantity]"=2 \
-d mode=paymentFor an active Checkout Session in payment mode using `ui_mode=elements`, update it with `payment_intent_data` before confirming payment. Set the documented PaymentIntent fields there to change them without recreating the session.
When creating a portal session that should be recoverable after expiration, set `after_expiration[type]` to `customer_login`. Customers can verify their email and receive a replacement session using the original URL; set `after_expiration[customer_login][expires_at]` to limit recovery.
curl https://api.stripe.com/v1/billing_portal/sessions \
-u "<YOUR_SECRET_KEY>:" \
-H "Stripe-Version: 2026-09-30.preview" \
-d "customer=<CUSTOMER_ID>" \
--data-urlencode "return_url=https://example.com/account" \
-d "after_expiration[type]"=customer_login