What's new?
We've added a consent_requirements field to the subscription entity. It's returned by all subscription endpoints and included in subscription webhook event payloads.
List of active consent requirements for the subscription's current billing period. Returns an empty array if no consent requirement exists.
How it works
To comply with renewal notification requirements from the Korea Fair Trade Commission (KFTC), customers in South Korea must explicitly consent to continued subscription charges when free trials or introductory discounts end. This consent system has been part of the Paddle platform since July 2025.
Previously, consent requirement data wasn't accessible through the API. With this release, the consent requirements for the subscription's current billing period are listed in the consent_requirements field on the subscription entity for all subscription API responses and webhook payloads.
Customers in countries other than South Korea don't need to provide consent to continue subscription charges. For most subscriptions, the consent_requirements field returns an empty array [].
You can check the status of the consent requirement to see whether consent is pending, has been granted, or has been voided. You can also check the granted_at and voided_at timestamps to see when consent was granted or voided.
New webhook notification triggers
subscription.updated now occurs in two additional consent-related scenarios:
- When a consent requirement is created — A South Korean subscription enters a state that requires renewal consent, such as a trial nearing its end, or an introductory discount ending or being removed. The payload includes
consent_requirementswithstatus: "pending". - When consent is granted — Consent is granted when a customer completes the consent flow via the customer portal. The payload includes
consent_requirementswithstatus: "granted"andgranted_atwith a timestamp.
If you have South Korean subscribers, you can listen to subscription.updated and inspect consent_requirements to react to state changes for customer consents. For example, you could build retention flows if consent hasn't been provided yet, or suppress renewal reminder communications once consent has been granted.
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.
If you have South Korean subscribers, you can list subscriptions or listen to subscription.updated to observe the status of consent requirements and build retention flows from it.
Summary of changes
Subscription
Resource-
Array of active consent requirements for the subscription's current billing period. Returns an empty array if no consent requirement exists.
-
Consent state — `pending`, `granted`, or `voided`.
-
Timestamp when consent was granted, if applicable.
subscription.updated
Webhook event-
Now also fires when a consent requirement is created and when consent is granted.