Integration of Axepta Online payment platform
Axepta Online interfaces
Hosted by Axepta Online
| List of payment methods | Credit card forms |
|---|---|---|
| Screenshots |
|
|
| Endpoint Axepta | paymentpage.aspx | payssl.aspx |
| Hosting and Data Storage | Axepta BNP Paribas Server | Axepta BNP Paribas Server |
Data Format | URL parameters (NVP Format: Name-value-pairs) | Input parameters (NVP Format: Name-value-pairs) |
Data Transfer | Via HTTP GET or POST | Via HTTP POST |
Hosted by the merchant
One-shot payment
Merchants can create ans host their own payment page. They will use the paynow.aspx endpoint in order to send the data.
Merchants processing card transactions using the Silent Post model must submit the PCI DSS Self-Assessment Questionnaire (SAQ) A-EP. This SAQ is more comprehensive and thus might require more time and resources in comparison to SAQ A applicable to merchants that use hosted payment pages. However, merchants should always consult with their acquirer to evaluate the level of compliance required and refer to the PCI DSS guidelines. This does not affect the use of pseudo card numbers which is possible without submitting the SAQ questionaire.
One-click payment
Merchants can create a form for One-click payment, using the PCNr (Pseudo Card Number / Token) in the card JSON Object and paynow.aspx.
In that case, the merchant is exempt from submitting the PCI DSS Self-Assessment Questionnaire (SAQ) A-EP.
User experiences
Axepta Online offers 4 kind of customer experiences allowing merchants to choose the one that suits the best the customer experience they create.
Option | Redirection | iFrame | Lightbox/Pop-up | Mobile device |
|---|---|---|---|---|
Overview |
|
|
|
|
Advantages | -Easy integration -Less development resources from the merchant’s side | -The buyer remains on the merchant’s website: Known and trusted environment -The payment tunnel is fluid and dropouts are rare. | -A superimposed window will be displayed on the merchant’s website containing the payment form. | -Fully integrated to the merchant’s mobile app depending on the payment method. |
To consider | - Leaving the payment tunnel | - If the user refreshes the website page, the written data will be lost, and the payment process should be made from the beginning. | -Some browsers may block pop-up windows. | - Payment can be made via browser |
All details and customization capabilities available here : Integration and customization capabilities