reauth.cgi
Please note, that reauth.cgi does not work for the Danish cards Dankort and VISA-Dankort.
Description
An authorised transaction is legally binding for a fixed number of days (e.g., the standard for PBS is 7 days). Technically, however, an authorisation is available for up to two months. If the goods cannot be shipped to the customer within the fixed number of days (the goods may be out of stock), the transaction needs to be re-authorised before it can be captured. Please note, that it is important to re-authorise the transaction before shipping the goods, since the credit card may have been stolen or expired in the meantime. Under normal circumstances the re-authorisation process is handled through the DIBS administration interface. However, the function reauth.cgi offers another way to re-authorise transactions.
Usage
The standard work flow for reauth.cgi is:
- A set of parameters are posted to: https://payment.architrade.com/cgi-bin/reauth.cgi
- The DIBS server processes the information
- A response is sent to the script that originally posted the request to the DIBS servers
Function call
https://payment.architrade.com/cgi-bin/reauth.cgi
Input parameters
The function reauth.cgi accepts the following input parameters:
Parameter | Description |
merchant | The merchant parameter is the shops DIBS identification number. The merchant number is available in the order confirmation email and is a 7-digit integer. |
transact | The unique DIBS identification number for the transaction you want to capture. The transact is returned from a successful authorisation, and is a as minimum 6-digit integer , e.g. transact=123456. |
textreply | If this variable is set (e.g. textreply=true) the DIBS server returns its answer in simple text format. If you are not using the standard DIBS payment window, e.g. using server-to-server requests, this significantly simplifies parsing the answer and is recommended. |
[account] | If several departments in a company use the same acquirer contract it may be beneficial to keep track of the transactions by department. Including the account parameter enables separation of the transaction by department. |
Return parameters
The return parameters depend on the result of the reauthorisation. If the transaction was accepted, then the return parameters are:
Parameter | Type | Description |
transact | integer | All transactions are given a unique DIBS identification number. It is at minimum a 6-digit integer, e.g. transact=123456. |
status | string | ACCEPTED |
[?x=<x>&y=<y>...] | optional | Parameters sent to reauth.cgi as part of the accepturl are returned. |
All values | not a parameter | In the DIBS administration interface it is possible to enable the return of all parameters sent to reauth.cgi, except credit card details. |
If the reauthorisation was not accepted, the return parameteres are:
Parameter | Type | Description |
status | string | DECLINED |
reason | integer | If the transaction is rejected, it returns with a reason for the rejection. Please refer to error codes for a list of possible values. |
[?x=<x>&y=<y>...] | optional | All parameters sent to the DIBS server, as part of the cancelurl, are returned. |
All values | not a parameter | In the DIBS administration interface it is possible to enable the return of all parameters sent to reauth.cgi, except credit card details. |
Example
<form method="post" action="https://payment.architrade.com/cgi-bin/reauth.cgi"> <input name="merchant" value="12345678" type="hidden" /> <input name="transact" value="400111" type="hidden" /> <input name="textreply" value="yes" type="hidden" /> </form> |
