Defining the Action in UI Design

• Open your project on the Kuika platform.
• Go to the UI Design module and select the relevant screen.
• Create a button (e.g., “Send”).

• Select the button and add the Verification → Verify Recaptcha Token action from the + ADD ACTION menu according to the event to be performed (Initial Actions, OnClick, OnBlur, etc.).

Configuring Action Parameters

• Token (String - required): The token value generated as a result of the reCAPTCHA process completed by the user on the client side. It is usually linked to one of the following data sources via the Symbol Picker:
  
  • Action Result
  • Current
  • Form Component
  • Screen Input
  • Fixed (fixed value)

A user filling out a registration form is asked to complete a reCAPTCHA verification. When the user clicks the “Sign Up” button, the Verify Recaptcha Token action is executed first. If the token is verified, the registration process continues; otherwise, an error message is displayed.

Adding a reCAPTCHA Verification Action Before User Registration

• Enter the UI Design module and drag and drop a Button element from the Elements panel on the left side.
• In the Properties panel, enter a label such as “Sign Up” in the Label section of the button.
• Select the relevant button and add the OnClick → Verification → Verify Recaptcha Token action from the + ADD ACTION menu.

Configuring the Verify Recaptcha Token Action

• Token: This value can be dynamically retrieved from the reCAPTCHA component.

With this configuration, reCAPTCHA verification is automatically performed when the user clicks the button. If the verification is successful, the process continues; otherwise, it is stopped.

• Security Check with Conditional Flow:

Depending on the verification result

• If unsuccessful → an error message can be displayed to the user.

• reCAPTCHA Version Compatibility:

Token values can be used appropriately with Google reCAPTCHA v2 and v3 support. Verification strategies can be applied as visible (v2) or invisible (v3) according to the form structure.

• Dynamic Determination of Token Source:

The token can be obtained in the following ways:

• From a form element (e.g., a reCAPTCHA widget)
• From an external API
• From the Action Result
• By manually entering it in the Fixed field and running the test scenario

Technical Risks

• Invalid Token Usage: The token may have expired or be fake; verification will fail.
• Client-Server Incompatibility: The application environment must be compatible with the reCAPTCHA version (e.g., if v3 is supported, v3 tokens must be obtained).
• Out-of-Scope Verification: The action should only work in the required fields; it does not need to be added to every button or action.

The Verify Recaptcha Token action enhances security in your application by integrating reCAPTCHA verification. It provides a strong defense against spam and bots, allowing only real users to perform actions. With support for both web and mobile applications, it can be easily implemented in any user interaction and adapted to advanced security scenarios.