Skip to main content
Question

Monthly subscription with 12-month commitment

  • May 25, 2026
  • 1 reply
  • 30 views

Forum|alt.badge.img

Hey everyone,

I came across this previous discussion about Apple’s new “monthly subscriptions with a 12-month commitment” feature:
https://community.revenuecat.com/sdks-51/monthly-subscriptions-with-a-12-month-commitment-7629?tid=7629&fid=51

Since that topic is now closed, I wanted to ask about the current state of support on the RevenueCat side.

If we enable this billing option in App Store Connect for an existing yearly subscription product, should everything continue working normally in RevenueCat without any additional changes?

Main things I’m wondering about:

- Will entitlements continue behaving normally?
- Will RevenueCat webhooks continue firing the same way?
- Any differences in renewals / expiration handling?
- Is there any way to detect this billing model via SDK or webhooks?
- Any known issues or edge cases before enabling it in production?

We rely pretty heavily on RevenueCat webhooks + entitlement logic, so I just want to make sure enabling this on Apple’s side won’t unexpectedly break anything.

Thanks!

1 reply

alejandra-wetsch
RevenueCat Staff
Forum|alt.badge.img+6

Hey ​@amir-2735d8

Thank you for reaching out!

The team is currently working on supporting this billing plan and is expecting to ship it next week. So this is not supported at the moment. 

Given that this is not yet supported, importing products with this configuration may not work as expected, so I would recommend waiting until it is released.

Will entitlements continue behaving normally?

Yes! You’ll need to attach your entitlement to the monthly commitment product in RC, and entitlements will get granted as usual.

Will RevenueCat webhooks continue firing the same way?

Yes, same as with any other purchase

Any differences in renewals / expiration handling?

No difference.

Is there any way to detect this billing model via SDK or webhooks?

On the SDK side, when you fetch your products, you’ll be able to detect the billing model by looking at a new installmentsInfo property on StoreProduct once it’s released.

When you’re looking at CustomerInfo/Webhooks, you can identify the billing model by looking for :monthly suffix in the product IDs. Product ID example: com.your.productID:monthly 

Any known issues or edge cases before enabling it in production?

The team has noticed that it is difficult to make product upgrades/downgrades from inside the app, mainly because you get random errors, but they work correctly when done via Apple’s subscription management screen. They have already reported this to Apple to see if a fix is available.

I’ll let you know once this gets shipped!