Retry Subscription is a system action used in your application with Kuika's Iyzico integration to retry failed subscription payments. It is used to retry payments that failed due to bank-related errors, limit issues, or temporary connection interruptions in automatic payment renewals with user intervention.
Technical Features
Payment Retry: A previously failed subscription payment is retriggered.
Manual or Automatic Use: Can be triggered either by user action (e.g., “Retry” button) or automatically by the system.
Web and Mobile App Support: Works seamlessly on both web and mobile apps.
Retry Subscription Action Application Steps
Log in to the Kuika platform.
Select your project from the Apps screen.
Go to the UI Design module.
Open the Properties panel on the right side.
From the + ADD ACTION menu, add the Payment Iyzico> Retry Subscription action according to the desired trigger event (Initial Actions, OnClick, OnBlur, etc.).
Configure the following area in the settings that open:
User Name: The username of the user whose payment will be retried.
Click the SAVE button to complete the process.
Usage Scenario: “Try Again” Flow After Failed Payment
When a user's subscription is about to be renewed, the payment fails due to insufficient credit card limit. The application displays a “Subscription Renewal Failed” warning on the user's profile with a “Try Again” button below it.
Scenario Flow:
The user sees the warning and clicks the “Try Again” button.
The Retry Subscription action is defined for the OnClick event associated with the button.
The system initiates the user's previously failed subscription payment again through Iyzico.
If the payment is successful, the user sees a “Payment Successful” message and the subscription continues.
If it fails again, an error message is displayed to the user and support is recommended.
Retry Subscription Action Advanced Customizations
Dynamic User Data: User Name can be automatically filled in with the logged-in user's information.
Conditional Retry: This action should be called if the previous payment attempt was actually unsuccessful. The previous payment status can be checked (with Retrieve Subscription).
Post-Successful Transaction Actions: If the payment is successful, subscription access can be enabled, a role can be assigned, or a notification email can be sent.
Technical Risks
Invalid User Name: If an incorrect User Name value is entered, the transaction will fail. User data must be verified.
Repeated Attempts: If the payment has already been successful, there is no need to try again. The subscription status should be checked to prevent unnecessary attempts.
Invalid Card Information: If the user's card is not registered in the system or has expired, the transaction may fail again.
Incorrect Action Chain: If the successful transaction flow (e.g., course access, message display, etc.) after Retry Subscription is not defined, the user cannot proceed in the system.
Retry Subscription is an action that improves the user experience for failed payments and makes payment processes flexible and sustainable. When configured correctly on Kuika, it supports the continuity of your subscription-based revenue model.
