Just launched
We're actively working on new content and improvements to our documentation. We'd love to hear your thoughts, launch quick survey
Paddle Billing

Identify transactions created for one-time charges

More easily distinguish between transactions created for one-time charges for a subscription, and transactions created for subscription changes or renewals.

What's new?

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.

How it works

The 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 full_immediately or prorated_immediately as the proration_billing_mode, as well as one-time charges.

The new 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 prorated_next_billing_period or full_next_billing_period, as well as for subscription renewals.

Next steps

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 origin value.

Learn more