Charges a customer for their managed subscription.

This API processes charges immediately and sends notifications to the customer. It is used for managed subscriptions that rely on seller actions for charges, reminders, and deactivation, with no internal subscription date tracking.

For large rebill volumes (e.g., January 1st annual renewals), we recommend to divide workloads into batches and call the endpoint sequentially, waiting for each batch to complete.Partial failures in a batch are detailed in the response for each subscription.

Note: Routine payment failures (e.g., insufficient funds, soft decline) are now returned with a 200 status instead of 400. The per-subscription result field indicates whether that subscription succeeded or failed; see the error object for failure details. 400 is now reserved for requests that were rejected outright — a hard decline blocking retry until the payment method is updated, or a subscription that has exceeded its max retry limit.