Authorise Only or Capture Automatically

The auto_capture flag allows to save the additional API call to start the Smart Transaction, and capture the payment. Whether you can use this depends on the exact scenario.

The flag can be passed when you create a Smart Transaction:

Request
POST /api/v2/Smart/Transactions HTTP/1.1
Host: connect-testing.secupay-ag.de
Authorization: Bearer qb56tjj1bcvo9n2nj4u38k84lo
Content-Type: application/json
Accept: application/json
 
{
// ...
"payment_context": {
"auto_capture": true
}
// ...
}

The default value is false.

Scenario

Details

Final confirmation after authorisation

  1. Your shop creates a Smart Transaction without auto_capture or with "auto_capture": false.

  2. Your shop starts the authorisation process (/prepare) before the final confirmation of your customer. This process may involve an external authorisation (3-D Secure check, PayPal). At the end the payment is authorised, and the Smart Transaction has status approved.

  3. Your shop asks the customer for his final confirmation with the Buy now! button. Having his confimation, the shop calls our API to capture the payment (/start). The Smart Transaction has now status pending if you must wait, or ok, received or collection if you can deliver.

Final confirmation before authorisation

  1. Your shop creates a Smart Transaction with "auto_capture": true.

  2. Your shop starts the authorisation process (/prepare). This process may involve an external authorisation (3-D Secure check, PayPal). At the end the payment is authorised and also captured. The Smart Transaction has now status pending if you must wait, or ok, received or collection if you can deliver.

The button for the final confirmation could also be labelled Pay now! or Subscribe now!, for instance. Please consider the legal requirements for the conclosure of contract.

The exact flows are described in the Reference sections for authorisation and capture using the respective payment methods.