Eine Transaktion erneut autorisieren

  Zuletzt aktualisiert: 

  Leider ist das hier dokumentierte Produkt derzeit nur in englischer Sprache erhältlich.


A Re-Auth is a process where a new Authorisation can be performed using the same credit/debit card as a previous transaction.



  This functionality is only available to those with the following user roles:
Admin, TransactionUser

If re-using previously stored credentials, Visa and Mastercard have mandated that you set the Credentials on file field to “2 – Scheduled payment using stored credentials”.

If this transaction is to be a Merchant Initiated Transaction (MIT) (opposed to a Customer Initiated Transaction or CIT), Visa has mandated that you specify the reason for the payment, by selecting a value in the Initiation reason field.

You must ensure the initiation reason selected correctly represents the reason for the new payment. Visa may introduce new values to this list in the future.

  Click here for further information on this mandate.


How to perform a Re-auth

1. Select transaction(s) for re-authorisation

Select “Transactions” from the left. Perform a search and then click a transaction reference displayed in the results table to view further details.

2. Select the action

Click the “Re-auth” button displayed near the bottom of the page.

If there is not enough space to display all options, these will be combined into a single “Actions” button. Click to expand to view all options.

3. Allowed and Disallowed transactions

If successful, the page displayed will be pre-filled with details inherited from the selected transaction(s).


You should check the “Summary” table at the top of the page, which displays the number of selected transactions that are “Allowed” and “Disallowed”. Disallowed transactions are not suitable for the desired action and are not displayed on the page.

Why have some of the selected transactions been disallowed?

This can occur for a number of reasons, including:

  • You may have selected a transaction where the payment method doesn’t support re-authorisation, e.g. an Alternative Payment Method (APM). Please refer to our documentation for Payment Pages or our API for further information about a given APM.
  • You may have selected a request type that does not support re-authorisation, e.g. THREEDQUERY.

4. Fill out the form

Check the values displayed on-screen and make any necessary adjustments. By default, a re-authorisation of the same amount will be processed. You can opt to change the amount by changing the value on the form for a given transaction.


You click the “+” icon on the left to expand the form and display additional fields that can be changed prior to re-authorisation. Of particular importance, you may wish to check the following:

  • Check the expiry date is still valid on the customer’s card. If the customer has renewed their card and has a new expiry date, you can enter the new value on the form to proceed.
  • We do not store the security code associated with the customer’s card on our severs. You can prompt the customer for their security code and enter this on the form. This allows security code checks to be performed.


  • Credentials on File and Initiation Reason
    • If you are processing a re-authorisation using previously-stored credentials, set Credentials on file to “2”. You should also specify an Initiation reason (click here to learn more about the different values).
    • If the credentials are to be stored for future payments, set this field to value “1” to indicate you have sought permission from the customer.

When you are ready to process the request, click “Re-Auth” at the bottom of the page.

  Rules cannot be inherited by child authorisations. They will only be performed on Re-Auth transactions if active in the Rule Manager.


Handling the response

If the action was processed successfully, you should see a green success message at the top of the page. For each row under the “Successfully Processed Transactions” header, you can click the “+” icon to view the full response for each action processed.


A summary table will also be displayed at the top of the page, counting Success and Error cases.


Troubleshooting errors

If errors have occurred, the transactions you attempted to action should remain on screen. Check the error code and message for further information on the nature of the problem. In some cases (e.g. a field error), you can correct a mistake on the form and resubmit. Invalid fields are highlighted in red. Ensure you click the “+” icon on the left as the field that is causing the error may be hidden.

War dieser Artikel hilfreich?
0 von 0 Personen fanden dies hilfreich