This functionality is available via API and select client libraries. The 3 related API endpoints are:
To capture or cancel an authorize transaction, use /capture or /cancel endpoints and include the transaction UUID from the original authorize transaction:
- Authorize: When you authorize a subscriber's credit card, we check with the subscriber's bank to see if the credit card is legitimate and has sufficient funds for the amount you authorized. If the subscriber's bank approves, a hold is placed on the funds in the subscriber's account but no money has moved, yet.
- Capture: In order to actually move money from the subscriber's account, you have to issue a capture request on the original authorization to collect ("capture") the funds.
- Cancel: If you choose not to capture the funds from the subscriber's account, you can explicitly cancel the authorization to release the hold on those funds.
- Authorize the amount first but only capture the funds once you've shipped the physical goods.
- Perform a manual fraud review before capturing the funds and fulfilling the order.
- Authorize the amount at the start of a free trial and then capture the funds at start of the subscription.
- You can only capture an authorization once.
- You must capture all the line items on an invoice, and for the full amount of the authorization.
- Gift cards and coupons will be redeemed and marked as used at the time of authorization.
- Authorizations automatically expire after a period of time if they are not captured. The length of time varies by card brand and gateway, but usually it is within 7-10 days. If you wait too long to capture an authorization, the gateway may have already canceled the authorization.
- If an authorization has already been captured, Recurly will return an error message via the API.
- If an authorization has already been canceled, Recurly will return an error message via the API. In this case, you can either: submit a new authorization, or initiate a transaction request.
- Other gateways will be added according to merchant demand.
There are no per transaction fees for authorizations. Merchants will only be charged for captures.
- "Partial captures": partially capturing an authorization (e.g. only capturing $5 of a $10 authorization).
- "Multiple captures": partially capturing an authorization multiple times (e.g. capturing $2 first, then $8, of a $10 authorization). Capture requests must capture all line items on an invoice.
- Capturing more than the amount authorized (e.g. capturing $11.50 of a $10 authorization).
- Also note: Recurly does not automatically authorize your subscribers' cards in advance of recurring subscription renewals.
- Merchants can capture the full authorization amount, and then refund individual line items in separate refund transaction requests.
- Merchants can cancel the initial authorization, and then initiate transaction requests for individual line items as separate transactions.
- Recurly will not automatically cancel authorizations. You will need to explicitly cancel authorizations so that there are not long holds on customers' accounts. Note: it is best industry practice for merchants to explicitly cancel authorizations and not rely on authorizations to be expired by the gateways.
- Recurly will not inform merchants when authorizations have been canceled or expired upstream, i.e. by the gateway. This information is not always available from the gateway.
- Authorization, cancel, and capture transactions do not look at account credits (or credit invoices), and will only authorize, cancel, or capture the original, requested transaction amount. If an account has a credit, a merchant can identify that prior to requesting the authorization transaction, and requesting an auth for the discounted amount, and subsequently canceling, or capturing the discounted amount.
- Delayed capture: Recurly does not support delaying or customizing the timing of captures, i.e. captures are immediately initiated when the API request is received.
- Captures cannot be canceled or voided. The transaction would have to be refunded upon success.
- Subscriptions with a future start date (free trial) longer than 7 days is not supported on Stripe.
- Auth and Capture is only supported via Recurly’s API and select client libraries.
- Auth and Capture does not fully support 3rd party integrations such as Xero or QB (coming soon).
To enable this feature, please contact Recurly Support.