More easily distinguish between transactions created for one-time charges for a subscription, and transactions created for subscription changes or renewals.
We added a new
subscription_charge allowed value for the transaction
origin field. It's set by Paddle when a transaction is created for a one-time charge for a subscription.
Describes how this transaction was created.
origin field against a transaction tells you how it was created. It's set automatically by Paddle.
Previously, all immediate transactions created for a subscription had the origin
subscription_update. This includes changes to recurring items on a subscription where you choose
prorated_immediately as the
proration_billing_mode, as well as one-time charges.
subscription_charge allowed value is now used for transactions created for one-time charges.
subscription_update remains the value for changes to recurring items that are billed now, making it easier to distinguish between transactions created for one-time charges and transactions created for recurring items.
subscription_recurring is still used when making changes to items on a subscription where you choose
full_next_billing_period, as well as for subscription renewals.
Here's a summary of the allowed values for
origin against a transaction:
|New||One-time charge for a subscription, billed now.|
|Change||Changes to recurring items for a subscription, billed now.|
|No change||Subscription renewals and changes to items for a subscription, billed on the next billing period.|
|No change||Zero-value transaction created for updating a payment method.|
This change is available in version
1 of the Paddle API.
It's a non-breaking change, meaning it doesn't impact existing integrations.
You can work with transactions using the API to see the new