Payment Fail Page (callback_fail)
When a payment request is processed by the gateway, the result is either Success, Failure, or Open:
- Sucess. The payment request was successfully processed. The result is posted to the OK page (callback_ok).
For more information, see Settings for the Payment OK page (callback_ok) .
- Failure. The payment request failed. The result is posted to the fail page (callback_fail).
- Open. If a payment request cannot be completely processed now, the result is posted to the open page (callback_open). When the request is later processed, a notification is sent to the notification page (callback_notification). For more information, see
Payment Open Page (callback_open) andPayment Notification (callback_notification).
The following parameters are used in the callback_fail page.
All of the POST/GET parameters (except checksum) are available as XML in the xml parameter, and you are recommended to rely on the xml parameter for processing business logic.
The status of the transactions:
|error_message||A fallback error message that is safe to display to your customers. You are recommended to always display your own, custom error message, providing your customer with more details about the error, and only use this error message as a fallback mechanism. You must include the message for Klarna payments , or if the cardholder_message_must_be_shown return parameter is true.||String|
|merchant_error_message||An error message for the merchant's eyes only, but provides more detail as to what went wrong (This is only sent to the FAIL-callback page).||String|
|cardholder_message_must_be_shown||An indicator on whether the card holder error message must be shown to your customer.||boolean|
This is the internal ID of the order in your webshop.
In most integrations, you can use the same order ID for up to four orders.
The authorisation type of the payment, for example, "payment"/"paymentAndCapture"/"subscription"
The status of the transaction, depending on the payment method, for example, preauth,recurring_confirmed, captured, etc.
A unique token you can use for blacklisting a credit card. This token can be used to build up a black list of credit cards. The token is only returned if this is a credit card payment.
This is the unique credit card token value that identifies a credit card within the AltaPay Payment Gateway. This token can be used later with the Merchant API or with creditcard token ordering so that the customer does not need to enter credit card details in their next order. The token is only returned for credit card payments.
The payment method:
Indicates whether a transaction was just reserved, and subsequently needs to be captured. For example, if a credit card payment has the authorisation type "payment", this value is true, but if the authorisation type is paymentAndCapture, this value is false, because the transaction has already been captured.
Contains the XML response of the API call. This is the parameter from which to design the business logic. For detailed information about the XML response from API calls, see API Response structure (XML).
If the Customer Information Shared Secret field is set under Home > Terminal Settings in the Merchant Information Interface, the checksum can be used to authenticate the origin of a request, to counter "man in the middle" attacks.
The checksum is calculated based on these parameters:
For more information, see Checksum Calculation.
If fraud detection is available for the payment we also post back the following parameters.
This is the probability that the transaction is a fraud attempt, and should be read in context of the FraudExplanation and the FraudRecommendation. For example a fraud risk score of 13.37 means there is a 13.37% chance of this order being fraud. Only MaxMind utilizes the fraud score. For ReD, the value is always -1.
|fraud_explanation||Contains a detailed explanation of the fraud risk evaluation. Only relevant for MaxMind. For ReD it contains the value of the recommendation.||string|
The recommendation from the fraud detection service provider. For example:
Unknown is also returned for declined transaction.
If address verification is enabled for the payment, the following parameters are also posted to the callback page:
|avs_code||The address verification result code. For more information, see Address verification parameters.||A-Z|
|avs_text||The description of the address verification result code. For more information, see Address verification parameters.||String|
For more information, see Settings for the fail page (callback_fail).