Skip to main content
When authorizing a payment, you can choose to do it in two ways depending on your case:
  • One-step: Authorize and Capture in the same step.
  • Two-Step: Authorize first, and then capture in a different step.
Both options have pros and cons, and which one you use will depend on your type of business, use case, and factors like how often you change the authorized amount before actually capturing it. The availability of each flow will depend on the providers you choose for processing the payment and other factors (payment method, type of card, country, etc.). Good news! Payrails supports both modes, and it’s easy to configure your workflows to choose one or the other by default. Also, if for a specific workflow execution you need to override the default behavior, you can also do it.

Capture Mode

Cancel Mode

Cancel vs. Refund vs. VoidIn this case, we use the term “Cancel” to refer to canceling an authorization of a payment that has not been captured yet.A Refund can only be performed after a payment is Captured.
Delays in both are not allowedPlease note that there could be a possible conflict if you set the value Delayed to both captureMode and cancelMode. We will reject that configuration because it can lead to unexpected behaviours.

Delay defaults and formats

For both captureDelay and cancelDelay, we use the ISO 8601 standard. If it’s your first time using it, you may find it a bit strange, but it’s super powerful! If you choose a captureMode or cancelDelay of type Delayed but you don’t indicate a delay time in their respective fields, our default is 5 minutes.

Multiple captures

By default, all our captures are final in the payment processor. If you want a different behaviour, please indicate it to your integration team. This means, for example, that if you authorized 10 EUR, and then capture 7 EUR, the remaining 3 EUR are immediately released.
Last modified on September 28, 2026