Cancel Subscription is an action used on the Kuika platform with Iyzico integration to cancel a user's active subscription. The subscription process can be securely terminated at the user's request or based on certain system conditions.
Technical Features
Subscription Cancellation: Cancels the user's active subscription through the system.
Automatic Renewal Disabled: With the cancellation, future automatic payment renewals are stopped.
Web and Mobile App Support: Available on web and mobile apps.
Iyzico API Integration: The action communicates directly with the Iyzico subscription API and terminates the subscription systemically.
Cancel Subscription Action Application Steps
Log in to the Kuika platform and open your project.
From the UI Design module, open the screen where the subscription cancellation will be performed.
Go to the Properties panel on the right side.
Click on the + ADD ACTION menu.
From the + ADD ACTION menu, add the Payment Iyzico> Cancel Subscription action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).
Configure the following field in the section that opens:
User Name: The username of the user whose subscription will be canceled.
Click the SAVE button to complete the process.
Usage Scenario: User Cancels Subscription on Their Own
A digital magazine platform has a subscription model. If the user does not want the subscription fee to be charged at the end of the month, they can cancel their subscription.
Scenario Flow:
The user clicks the “Cancel My Subscription” button.
The Cancel Subscription action has been added to the OnClick action of this button.
The User Name parameter is dynamically linked to the user's email address.
The action is executed and the user's active subscription is canceled via Iyzico.
The message “Your subscription has been successfully canceled” is displayed to the user.
Automatic renewal is disabled, and the user will not be charged again.
If necessary, the user's “premium” role is removed from the system.
Subscription Status Check: Unnecessary actions can be prevented by checking whether the user has an active subscription before the action is performed.
Cancellation Feedback Survey: Before the cancellation process, a survey can be sent to the user asking why they want to leave.
Role Update: After cancellation, the user's premium role can be removed to restrict access.
Notification Integration: After the subscription is canceled, an informational email or app notification can be sent to the user.
Technical Risks
Invalid User Name: The action will not work if the User Name field is empty, incorrect, or contains a user that is not registered in the system.
Already Cancelled Subscription: The system may return an error if an inactive subscription is attempted to be cancelled again. A pre-check is recommended.
Chain Actions: Multiple cancellation processes should not be triggered at the same time. Double clicks on mobile devices should be taken into account.
API Response Management: Error messages returned from the Iyzico service should be correctly transferred to the user. For example: “Subscription not found.”
Access Control After Cancellation: If the user can still access premium content after cancellation, the role or permission mechanism should be checked separately.
Cancel Subscription is a critical action for making the user experience more transparent and subscription management more secure. With the Kuika + Iyzico integration, you can effectively control subscription processes with just one click.
