Capturing your transaction in tandem with your authorization is a pretty standard payments configuration, however by separating the two events, your business can unlock cost savings and agility.
By decoupling auth and capture, it allows you to confirm and lock in the available funds at the time of purchase, but only capture once you're confident you can fulfill the transaction. Merchants can use this Automation to do things like check on inventory, wait for customer signatures, or wait for the delivery of goods and services before closing the transaction.
Why would a merchant do this? Payment Service Providers charge a refund fee to reverse transactions after the transaction has been closed or captured. Separating authorization and capture affords you the option to void or cancel the authorization instead of processing a refund if your customer changes their mind. For merchants at scale, these refund fees which aren't always transparent in your invoice can really add up.
By triggering a WhenThen API to capture the transaction, you can help minimize your refund fees. Further, you can see the status of each of your payments in our Insights feature, allowing you to have full transparency of your payment operations.
Try this recipe for free and see it in action!