Capture Payment
The Capture Payment block finalizes a payment that has already been authorized within a MindStudio workflow.
Capture an authorized payment in your workflow
The Capture Payment block finalizes a payment that has already been authorized within a MindStudio workflow. Authorization and capture are two distinct steps in many payment flows — authorization reserves funds on a customer's payment method, while capture is the action that actually collects those funds. This block handles that second step.
The block's configuration interface is minimal: it requires a block ID, a default transition ID, and an optional display name. There are no additional input parameters exposed in the interface, which means the block operates on the payment context that has already been established earlier in the workflow — typically by a preceding authorization step.
This block produces no explicit output fields, so it functions as an action step rather than a data-retrieval step. It fits into checkout and order-processing workflows where a payment has been pre-authorized and a downstream condition — such as inventory confirmation or user approval — determines when the funds should actually be collected.
What you can build
Real-world workflows powered by the Capture Payment block.
Confirm Order Then Charge
Authorize payment at checkout, verify inventory availability, then capture funds only after stock is confirmed.
Human Approval Before Capture
Hold an authorized payment until a staff member reviews and approves the order before funds are collected.
Subscription Renewal Flow
Authorize a renewal charge at the start of a billing cycle and capture it once the service period is activated.
Fraud Review Gate
Route authorized payments through a fraud-check step and capture only those that pass the review criteria.
Event Ticket Fulfillment
Authorize payment when a ticket is reserved and capture it once the ticket is successfully issued to the buyer.
Multi-Step Service Booking
Authorize a deposit when a service is booked and capture the payment after the appointment is confirmed by the provider.
Ready to add Capture Payment to your workflow?
Get Started FreeCommon questions about Capture Payment
What parameters does the Capture Payment block require?
The block requires an id (a string identifying the block) and a defaultTransitionId (a string controlling workflow routing). A displayName is optional. No additional payment-specific parameters are exposed in the interface.
What does the Capture Payment block return?
The block does not define any output fields. It functions as an action step that executes the capture and then transitions to the next block in the workflow.
Does this block also handle payment authorization?
No. The block is specifically for capturing an already-authorized payment. Authorization must be established earlier in the workflow before this block is reached.
What kinds of workflows commonly use this block?
It is used in checkout, order fulfillment, subscription billing, and booking workflows where payment authorization and capture are intentionally separated by a conditional or approval step.
Can the block be skipped conditionally in a workflow?
Yes. Because the block uses a defaultTransitionId for routing, workflow logic upstream can branch around it, allowing capture to occur only when specific conditions are met.
Related capabilities
Detect PII
Scan text for personally identifiable information using Microsoft Presidio.
Redact PII
Replace personally identifiable information in text with placeholders using Microsoft Presidio.
Authorize Payment
In managed payment mode, create a payment authorization. All billing events after the authorization and under the total cap will be billed to the user.
Add Capture Payment to your workflow
Build powerful AI workflows with drag-and-drop blocks. No coding required.