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: There are no per transaction fees for authorizations. Merchants will only be charged for captures. Note, this is separate from verifications, which will still incur standard Recurly transaction fees. To enable this feature, please contact Recurly Support.
Learn about the reasons why a payment authorisation can be refused.
When your payment authorisation request is not successful, the response returns HTTP status code 200/OK and includes a resultCode set to either Refused, Error, or Cancelled. In addition, the response contains a refusalReason field with a short message explaining why a payment was refused, as well as the refusalReasonCode (in Checkout API only). The possible refusalReason values are listed below.
See also
|