Summary

Context

AXEPTA provides merchants with the templates of the payment pages. These can be customized by adding graphic elements or texts.

Once the custom Template is created, it must be uploaded via the Back-Office in the Template Manager tab.

At the end of this step, the merchant can specify, in the payment request ("Template" parameter), the custom Template he wants to display to his customer.

On each payment page, a template

There are 2 types of AXEPTA payment pages

Name	Endpoints	Expectation	Templates Standard AXEPTA	Custom merchant templates (e.g. BNP_DEMO_AXEPTA)
Form for choosing payment methods	paymentpage.aspx		PaymentPageLogos_BNP_v1	In coming
			PaymentPageDropDown_BNP_v1	In coming
Card payment form	payssl.aspx		Cards_BNP_V1	In coming

Templates for merchants (archive)

The following Templates can be downloaded and will serve as a customization base for merchants.

In coming

Contents Template archive

Composition at the root

File organization and naming are the same for PaymentPage and PaySSL.

Composing the Pictures folder

The image folder must contain the following directories & files:

• css: Contains the project's CSS file
• data: this contains the files:
• coBadgedCards.json file: contains information for the proper functioning of the card payment form.
• File: translations.json: Contains all translations
• fonts: Contains font files
• images: Contains images
• js: Contains JS files

Update MerchandID (MID)

In order to modify the MerchandID and TemplateName, it is necessary to rename the files/folders as follows:

• XML : {MerchantID}_{TemplateName}_{TemplateType}

• XLS : {MerchantID}_{TemplateName}_{TemplateType}

• Image : images_{TemplateName}_{MerchantID}

Once the file names have been changed, it is necessary to modify the links using these files.

They are present in the files :

• XML

• XLS

• Image/js/main.js

The easiest way to update the paths present in these files is to search/replace in a text editor.

Create a Template Archive

In order to upload the template via the Template Manager, it is necessary to create an archive containing the three elements (XML, XLS and image folder) at the root.

Be careful, you must archive the three elements by selecting them when creating the archive and not archive the parent folder.

This archive should be named as follows: TemplateYYYYMMDD001MerchandID:

• Template: Allows you to indicate that it is a template

• YYYYMMDD: The date of the day of upload

• 001: The version number. This must be incremented with each new upload for a given day

• MerchandID: The merchant's ID.

Exemple : Template20220624003BNP_DEMO_AXEPTA.zip

Testing template

Once the archive is created, the merchant can test the display of the Template:

• Upload of the Template archive in the Template Manager of the Axepta Back-Office - cf. Template Manager.
• Calling the Template in payment requests via paymentpage.aspx or payssl.aspx
  • Using the Template parameter: Template={MerchantID}_{TemplateName}

Customization steps

Customization is done in several steps:

• Creating customization add-on files:
  • Design & Features: CSS & javascript
  • Images, fonts...
• Adding files to the 'images' directory
• Adding references (paths) to the XML file in the Template folder
• Update of the MID and the name of the template that will be used when calling the payment page
• Creating the Template archive
• Test the Template
• Use the Template in payment requests

Questions