The table below gathers the 3 key data for data reconciliation: data in the request, in the response or in Axepta reports.Key Data | |||
TransID | RefNr | OrderDesc | |
| Description | Unique transaction identifier | Reference Number - this data is used to follow up the transaction from the request to the reporting | Order Description |
Mandatory / Optionnal | M | M* | M |
Format | ans64 | an12 | ans768 |
REQUEST - msgVer=2.0 | |||
paymentpage.aspx | Yes | Yes | Yes |
paySSL.aspx | Yes | Yes | Yes |
payNow.aspx | Yes | Yes | Yes |
direct.aspx | Yes | Yes | Yes |
capture.aspx | Yes | Yes | Yes |
RESPONSE | |||
paymentpage.aspx | Yes | Yes | No |
paySSL.aspx | Yes | Yes | No |
payNow.aspx | Yes | Yes | No |
direct.aspx | Yes | Yes | No |
capture.aspx | Yes | Yes | No |
NOTIFICATION - URL Notify | Yes | Yes | No |
REPORTING | |||
BO | |||
Table | Yes | Yes | Yes |
Detail of a transaction or an operation | Yes | Yes | Yes |
CSV Export | Yes | Yes | Yes |
Search | Yes | Yes | No |
SETTLEMENT FILE | Yes | Yes | Yes |
SMARTDATA | Yes | Yes | Yes |
*RefNR' parameter specificity
The format and conditions of use of the RefNr parameter depend on the payment method and the integration mode chosen.
This parameter is mandatory for card payments reconciliation.
The table below summarizes all the possible formats for this field.
| Format | Condition | Description |
|---|---|---|
AN12 | O | CB, VISA, Mastercard |
AN12 | M | AMEX |
ANS30 | O | Payment way with Limonetik |
ANS40 | O | PPRO integration |
AN12 | M | Direct integration |
O : Optional
M : Mandatory
We recommend using the most restrictive format for this parameter (AN12 - M).