Skip to main content

Authorisation

POST 
/direct/auth

Authorise against a card

info

If the deferredCapture element of the request is false, then the authorisation will be captured immediately. If the deferredCapture element is true then the capture will take place at a later time.

This could be either:

  1. When a Capture request referencing the auth request is received.
  2. If a merchant account is configured to do so, the Platform will automatically capture the auth after a configurable fixed time. e.g. 2 days. This is known as ‘deferred capture’. Please contact your integration manager to discuss this requirement.

The default value for deferredCapture is false, meaning that authorisations are automatically captured at the end of the authorisation request. Also, a deferred capture authorisation, if not being captured, must be reversed. Failure to do so could ring fence funds on the customer’s payment method preventing them from using those funds until a later date, where the funds have been released by the issuer.

Accounts may be configured to require 3D Secure authentication. Auth requests targeted at accounts will be required to include extra information to enable the authentication. See 3D Secure section for details.

Request​

Responses​

Success