Stripe Adds Actor Field to Subscription Mutations

Stripe has added an actor field to its subscription mutation API, enabling developers to record who initiated a billing or contract action. The new field accepts three string values: customer, merchant, and partner, representing actions taken by the buyer, a merchant staff member, or an automated partner system. It can be supplied in the subscriptionBillingAttemptInput.actor argument for billing attempts, and in the various subscriptionContract* mutations for contract creation, updates, and status changes. The field is also available in bulk charge mutations such as subscriptionBillingCycleBulkCharge.

The actor argument is optional; omitting it defaults to the system’s inferred initiator. It is present in the following Admin API mutations: subscriptionBillingAttemptCreate, subscriptionBillingCycleCharge, subscriptionBillingCycleBulkCharge, subscriptionContractCreate, subscriptionContractUpdate, subscriptionContractAtomicCreate, subscriptionContractProductChange, subscriptionBillingCycleContractEdit, subscriptionContractActivate, subscriptionContractPause, subscriptionContractCancel, subscriptionContractFail, and subscriptionContractExpire. This addition allows more granular audit trails for subscription workflows. No breaking changes are introduced, but code that logs or filters subscription events may need to handle the new field.