What does this Action do?
The “Continue payment flow” Action is used to determine when to respond to the payment authorization request. Rather than only using the authorization request result to determine the outcome of a payment request, this Action allows you to choose when to respond to the payment request. The payment request is returned the status of the payment at the time of this Action running. There are several use cases where you may want this flexibility, such as your post-authorization fraud check fails and so you want to reject the payment and show a failure screen to your customer. For customer-initiated transactions (CITs), this Action is ultimately responsible for telling Universal Checkout to display the success or failure screen to the customer.
Workflow example
How to use the Action
- Determine when you want to respond to the payment authorization request. This will usually be after the “Authorize payment” Action but could be after post-authorization business rules, such as fraud checks.
- Assign a
payment ID- this will usually be the “Payment ID” from the “Payment created” Trigger output or “Payment status updated” Trigger output
Use cases
Based on your needs, you can utilize this Action in a few ways. Below are some examples for inspiration:
Use Case 1
Use Case 2
Use Case 3
Control the checkout result with Checkout outcome
You can control how the checkout resolves using theCheckout outcome setting in the Continue payment flow Action.
By default, checkout resolution is based on the payment status. However, you can explicitly choose to return a Checkout complete or Checkout failure result to the customer.
This is useful if you want to show a success screen even when the payment is still pending - for example, after a successful 3DS check and before the authorisation.
To use this feature, you can add a condition before the Continue payment flow Action and select the outcome you want. This gives you full control over the final checkout experience.
Use Case – Override checkout result