You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

The MID

Once you have subscribed to Axepta, you will have access to one or several MID. A MID or Merchant ID is the ID of the merchant on Axepta.

It's used in every requests sent to Axepta.

There are 3 types of MIDs:

  • MasterMID: 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: Used to perform test transactions (without having to bank).
  • Production MID: Used to make real payments


From test to production environnement ?

The merchant switchs from test environement to LIVE environement simply by switching from test MID to Production MID.


The URLs

Client redirection : URLSucess & URLFailure

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

  • URLSuccess: "Successful payment" page on the merchant's website if the payment is successful
  • URLFailure: "Failed payment" page on the merchant's website if the if payment failed

The customer is redirected to the merchant’s website via HTTP GET.

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


Notification to Merchant Information System: URLNotify

Axepta notifies the shop of the payment result.

How ?

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

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


Some key data allow the merchant to follow the payment from the initialization to the reporting :


Reference number (RefNr)

The Reference Number or "RefNr" is a mandatory parameter that must be sent in all your requests and is available in all Axepta reports.

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


We recommend to use the most restrictive format for this parameter (AN12 - M) and create unique RefNr.


Transaction ID (TransID)

This parameter is the unique ID of the transaction, it's a 64 alpha-numeric characters parameter allowing special characters.

This data is avaiable in all Axepta reports.


Order Description (orderDesc)

This parameter is used to 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 avaialble from the payment request to the reconciliation file.

This data is avaiable in all Axepta reports.


The format depends on the available paymethods for your MerchantId. Please choose your format in that way that all paymethods are covered.

If you offer only card payments with credit card form, we recommend : ANS..768 - M

If you offer several payment methods through Hosted Payment page, we recommend : ANS..354 - M

For more details: Data reconciliation : Key Data


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

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

  • No labels