Page History

The MID

By subscribing Once you have subscribed to Axepta, you will have access to one or several MID. A MID or Merchant ID allows you to identify an online storeID is the ID of the merchant on Axepta.

It's used in every requests sent to Axepta.

There are 3 types of MIDs:

• MasterMID: Allows you Used to have a global view of the activity of the merchant on the different shops he owns. The masterMID cannot be used to perform transactions but is mainly used to connect to the backoffice and visualize its entire activity.
• Test MID: Allows you Used to perform test transactions (without having to bank).
• Production MID: Allows transactions to be carried out in a production environment (LIVE environment, with banking).Used to make real payments
  

The URLs

Client redirection : URLSucess & URLFailure

Axepta redirects the buyer customer to a the merchant page webstie based on the payment result :

• URLSuccess: "Successful payment" page of on the merchant's website if the payment is successful
• URLFailure: Merchant "Payment FailureFailed payment" page on the merchant's website if the if payment failed

When payment is made, the The customer is redirected to redirected to the merchant’s store website via HTTP GET.

Axepta then returns a HTTP status 302 (moved object) and attaches the payment status is sent as a Blowfish encryption parameter to URLSuccess or URLFailure.

Notification to Merchant Information System: URLNotify

After execution of the payment, the payment solution Axepta notifies the shop of the payment result.

How ? :

The payment solution Axepta calls URLNotify via HTTP POST. This is a completely separate communication from the original connection between the store, the buyer customer and the payment solutionAxepta.

Notify is only allowed via Port 443 (TLS) for security reasons.

If the store’s URLNotify is not accessible (e.g. HTTP status 500/404), the notification is repeated 8 times in 24 hours.

The key data

for reconciliation

Certain Some key data allow the merchant to make follow the link between payment from the initialization of a payment and the actual paymentto the reporting :

Reference number (RefNr) or archive reference:

The archival reference Reference Number or "RefNr" is a field mandatory parameter that must be conveyed sent in all your requests . It's present and is available in all Axepta reports.

This is a mandatory parameter of 12 alpha-numeric characters (only digits & letters).

Transaction ID (TransID)

This field represents the reference parameter is the unique ID of the single transaction in the form of a mandatory parameter of transaction, it's a 64 alpha-numeric characters that may contain parameter allowing special characters.

This data is present avaiable in all Axepta reports.

Basket Order Description (orderDesc)

This field parameter is used to set sent data (descriptions of items/products purchased) that will be returned to the merchant as is and avaialble in the reporting.

It can also be displayed on the payment page (customField) and is transmitted avaialble from the payment request to the reconciliation file.

This data is present avaiable in all Axepta reports.

Response codes

The return codes are in the form of an 8-character code divided into 3 blocks: N8, ( N NNNNNNN)

• N (status)
• NNN (Category)
• NNNN (details)

Example of a return code:

2 206 0203

• 2 Error
• 206 3DS credit card adapater for authorization GICC protocol
  
• 0203 Card brand does not support 3DS

Link to full list of return codes: A4 Response codes - old

Link to 3DSv2 return code list: 3DS Response Codes