Capture Reserved Funds is an action used within Kuika's Stripe integration. It enables the collection of a previously reserved amount, i.e., a “pre-authorized” payment, on Stripe. This process is typically used in two-step payment workflows: in the first step, the payment is authorized; in the second step, it is captured.
Technical Features
Flexible Amount Collection: The entire authorized amount or a portion of it can be collected.
Web and Mobile App Support: Supported on web and mobile apps.
Secure and Direct Transactions: The collection process is carried out securely by communicating directly with the Stripe API.
Capture Reserved Funds Action Application Steps
Log in to the Kuika platform.
Select the project you want to work on from the Apps screen.
Go to the UI Design module.
Select the UI element that will trigger the collection process (e.g., “Collect Payment” button).
Click on the +ADD ACTION option in the Properties panel on the right side.
Select the button and add the Payment Stripe >Capture Reserved Funds action from the + ADD ACTION menu according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).
Define the following parameters in the settings that appear:
Payment Intent: A unique ID for the payment transaction that has been previously authorized on Stripe. For example: pi_3NsG9sLz3fD9oQvX2t7q...
Amount: The amount to be collected. Enter the full amount authorized by Stripe or a specified portion here.
Complete the process by clicking the Close button.
Use Case: Pre-Authorization Charge in Hotel Reservations
A user makes a hotel reservation and an initial amount of ₺1,000 is authorized (not charged) from their credit card via Stripe. This amount must be collected after the customer checks in at the hotel.
Scenario Flow:
The user makes a reservation. A Payment Intent is created and reserved.
On the day of check-in, the receptionist clicks the “Collect” button.
The Capture Reserved Funds action associated with this button is triggered.
The Payment Intent ID and the amount to be collected are sent to the system.
The collection is made via Stripe.
A successful transaction message is displayed to the user, and the invoice is automatically sent by email.
Partial Collection: Only a portion of the amount authorized by the Amount parameter can be collected (e.g., 800₺ instead of 1,000₺).
Payment Delay: Instead of receiving payment immediately, the capture process can be performed hours or days after the user completes the transaction. This is particularly useful in scenarios such as rentals and pre-orders.
Post-Payment Workflows: After payment, a notification can be displayed to the user, an email can be sent, or the user can be redirected to a confirmation page.
Technical Risks
Unauthorized Payment Intent: The capture process is only valid for authorized but not yet collected Payment Intent objects.
This action will fail for a previously collected transaction.
Timeout Risk: Stripe expects authorization transactions to be collected within 7 days. Once this period has passed, capture cannot be performed.
Overcharge: If the Amount parameter is entered as more than the authorized amount, the transaction will be declined. Input data must be validated.
Repeated Transactions with the Same Payment Intent: Each PaymentIntent can only be charged once. It should not be reused.
Capture Reserved Funds is an ideal solution for controlling pre-authorized payments with Stripe. It provides flexibility in two-step payment processes, improves the user experience, and offers financial control for businesses. It can be easily integrated with Kuika's action architecture and supported by robust data flows.
