Hey — We’re super excited to deeply integrate some of our support and workflow tools to use the new App Store APIs to extend subscriptions and issue refunds.
The request body containing subscription-renewal-extension data.
But it requires to access the transaction ID, which the RC SDKs don’t expose easily.
What’s the recommended way to get this done with RC?
Best answer by cody
Hey @Leon Sasson!
This API is on our product team’s radar, but we don’t have an ETA for launch just yet.
In the mean time, we provide the transaction ID in webhook event bodies and in the dashboard for specific events in a customer’s history timeline. If you click into an event, you can see the original transaction identifier.
This API is on our product team’s radar, but we don’t have an ETA for launch just yet.
In the mean time, we provide the transaction ID in webhook event bodies and in the dashboard for specific events in a customer’s history timeline. If you click into an event, you can see the original transaction identifier.