Contents

Document history

Payment Page global overwiew

The first step of a payment process is offering the user the possibility to select a payment method. To do so, the merchant can choose between 2 different options:

• Using the BNP Paribas payment page with different option to display the payment means on the page.
• Creating his own payment page.

BNP Paribas Payment Page

Language of the payment page

The standard BNP Paribas payment page is available in 7 languages : french, english, german, spanish, portuguese, italian and dutch. 

By default, the language of the payment page will match the language used previously by the user, on the merchant's website. However, the user will have the possibility to change the language once he arrives on the payment page thanks to a scrolling menu, on the top right of the page (see below) :

Payment methods selection page

There are 3 different options to display the payment methods on the Axepta Online payment page:

• Payment page offering cards only
• Payment page highlighting cards payment
• Payment page offering cards payment and alternative payment methods

Payment by cards only

This page shows card payment checkout only and is useful for a merchant who wants to offer payment by cards only (CB, Visa, MasterCard, Amex…).

To make card payments via the payment platform form, please use the following URL:

https://paymentpage.axepta.bnpparibas/payssl.aspx?...

The general parameters of a payment request by card are available in a dedicated document (Please refer to the “card processing” document).

Payment by cards is highlighted

This page is enriched with a drop-down menu showing alternative payment methods (PayPal, iDEAL, Sofort, Wechat…) for a merchant who wants to highlight card payments but also offers other payment methods.

As this page offers many payment methods at the same time, proceeding to payment should be done using the following URL:

https://paymentpage.axepta.bnpparibas/paymentPage.aspx?...

• When the user chooses to pay by card, he will be automatically redirected to the specific URL for card payments (payssl.aspx)
• When the user chooses to pay with another payment method from the drop-down list, he will be redirected to the specific URL (Please refer to the manual of each available payment method).

To activate this display, the merchant must contact the BNP Paribas Helpdesk:

• Phone : 0 800 25 62 25
• Mail : bnpparibas@computop.com

Payment by cards and alternative payment methods

This page shows all the logos of the available payment methods, so the merchant is not highlighting any payment method. 

As this page offers many payment methods at the same time, proceeding to payment should be done using the following URL:

https://paymentpage.axepta.bnpparibas/paymentPage.aspx?...

The user will be automatically redirected to the specific URL of the chosen payment method (please refer to each payment method guide).

This page is displayed to the merchant by default. If the merchant wants to reorganize the payment methods’ order, he must configure the payment methods in the “PayTypes” parameter according to his preferred order. (More information about this parameter in the Definition of parameters values section)

How to call the payment methods selection page?

To make payment requests via the payment methods selection page, the merchant should send a request to the following URL with HTTPS GET or HTTPS POST:

https://paymentpage.axepta.bnpparibas/paymentPage.aspx?...

All details required for payment processing are forwarded as parameters.

Calling this page starts with the correct composition of the parameters which consist of a key and a value pair (NVP) and which are separated by an “equals” sign (=):

MerchantID=Test

All parameters are gathered in a character string and separated by the character &:

Amount=100&Currency=EUR&TransID=12345

Notice: Since the characters "=" and "&" are used as separating characters, these characters cannot be transmitted as values. All values which you transmit without BlowFish-encryption must be URL-Encoded.

A correct parameter character string for the Payment platform contains three basic parameters: MerchantID, Len and Data. The parameters MerchantID and Len are unencrypted. Only the Data parameter is Blowfish-encrypted:

MerchantID=Test&Len=67&Data=0A67FE96a65d384350F50FF1

The Data parameter contains the sensitive payment details such as amount and currency. The encrypted bytes are Hex-encoded and completed to two characters from the left with a zero. Encryption is via Blowfish ECB and is available to you as source-code and components.

The Len parameter is very important for encryption because it contains the length of the unencrypted character string in the Data parameter. Since the data quantity to be encrypted is increased by a multiple of 8 in the case of the Blowfish encryption, the correct length of the character string must be known for decryption. Otherwise accidental characters emerge at the end of the character string.

The parameters are transmitted via HTTPS POST or HTTPS GET.

Notice: Please note that the maximum length of a payment request is limited to 5120 characters. If you require longer strings, please contact The BNPP Support.

To illustrate a payment request, find below the unencrypted parameter character string:

MerchantID=Test&TransID=100000001&Amount=11&Currency=EUR&URLSuccess=https://www.shop.com/ok.html&URLFailure=https://www.shop.com/failed.html&URLNotify=https://www.shop.com/notify.cgi&OrderDesc=My order   

This character string is encrypted and transmitted as the “Data” parameter, as shown below:

https://paymentpage.axepta.bnpparibas/paymentPage.aspx?MerchantID=Test&Len=162&Data=E98D40FFFD622C5FE7414F73539A1852C2CE7C8B09D34DF217E27FA2E194B9968DE9ABAE3B1F44B5485EFE3EF2597C7395BADBAD4340CDFD000DD57129EEFAA0BE904A7E2339DCF9363DA6ACDBE5EF98E169FC3092B160252A037135421FD0CE092C174A7D1D63517BD45099AC2B682F5E3CD2C942A6F0E741A833C0

Notice: Please note that a value is to be assigned to each parameter. Do not transmit empty parameters, as this can cause the payment to fail.

The following parameters are mandatory for all payment methods and have to be submitted Blowfish-encrypted within the Data parameter to the payment methods selection page.

These parameters are mandatory for all payment means and must be transmitted and Blowfish-encrypted in the “Data” parameter.

Notice: Please take all further parameters specifically for a payment method from the manual of the respective payment method.

Which are the integration options of the payment page?

The choice of displaying the payment page as a redirect, pop-up or iFrame is up to the merchant.

Redirection to the payment page

This option redirects the buyer to the secure payment page. This is a simple and secure option. The page is responsive and can be customized to the colors and image of the site, which blurs the effect of breakage. Adding the merchant’s logo, colors and fonts gives the buyer the impression of remaining in the same environment.

iFrame payment page

This option allows the buyer to stay in a known and trusted environment. The payment tunnel is fluid and dropouts are less common. However, there are some disadvantages that must be taken into account before integrating the iFrame mode on your website. Indeed, unlike the redirection option, if a visitor refreshes the website site's page, the payment data is lost. The payment process must be restarted from the beginning. Especially since the implementation of an iFrame requires a significant amount of development by the e-merchant to integrate it harmoniously into his e-commerce site.

The iFrame request that should be integrated in the HTML payment page may look like the following:

…

<body>

<iframe id="idFrame" name="nameFrame" src="https://paymentpage.axepta.bnpparibas/payssl.aspx?MerchantID=YourMID&Len=123&Data=AGSDJ…ASDF&template=YourMerchantID" height=”600” width=”400” />

</body>

…

Then, the merchant can integrate the following script into his URLSuccess / URLFailure HTML source code to leave the iFrame:

<head>
<script>

function breakout() {

  if (window.top != window.self) {

    window.top.location = "LINK TO URLSUCCESS/FAILURE";

  }

}

</script>
</head>
…

Pop-up payment page

This option, also called "lightbox", is a secondary window that appears in front of the main navigation window. The buyer does not feel as if they are leaving the merchant's website and ends up on a superimposed page. This page will be automatically closed once payment has been made.

Mobile device payment page

This option offers a fully integrated route that is perfectly adapted to the smartphone/tablet environment. The payment solution is compatible with iOS and Android environments.

How to customize the payment page?

When the merchant decides to use the standard payment page of BNP Paribas, he has the possibility to insert his logo and customize up to 9 specific fields (also called customfields) of the payment form. By default, BNP Paribas recommends the use of these fields to value the following data:

Notice: The Customfield[n] parameters are configurable in the request only when using HTTP GET.

When the customer will customize the payment methods selection page, all the customized fields will be displayed on the left side of the window, as shown below: 

When the merchant chooses to display only the amount and the currency of an order on the "Pay" button (see the following display) only the customfield1 parameter must be sent :

Merchant's payment page

How to integrate the payment page?

The merchant can also use his own payment page layout.

To do so, the merchant can design a template (with HTML and based on XSLT - Extensible Stylesheet Language Transformation) and send it to the Axepta BNPP Support which copies this template to its Payment platform Server.

For more information about XSLT see www.w3.org.

The merchant will only have to enter the name of his XSLT-file in the “Template” parameter and the checkout form will appear in his layout.

Following parameters are optional and can be submitted unencrypted by the merchant when he wants to design his own payment methods selection page.

Which are the conventions to follow?

The merchant who is willing to integrate his own payment page will have to respect certain conventions.

Conventions related to all payment methods

• Files names

An XSL file designed by the merchant defines his individual layout. The associated XML file contains the texts that should be displayed on the form. Hence, multilingualism is easy. The merchant must always use his MerchantID in the names of the files.

• XSL template:             xsl
• XML text file:              xml
• Sub folder for pictures, CSS- and JS-files:       Templates/imagesMerchantID_PaymentPage

In order not to receive safety notices, please ensure that external image sources are retrieved via SSL.

In order to call the individual layout, the merchant must use the ‘Template’ parameter with his MerchantID and attach it unencrypted to the call of the form of payment methods selection page, for example:

https://paymentpage.axepta.bnpparibas/paymentPage.aspx?MerchantID=IhreMID&Len=123&Data=AGSDJ…ASDF&template=IhreMerchantID

• Hidden Fields

The following hidden fields must be implemented so that the values can be passed on when sending the form:

MerchantID:                    “MerchantID“
Request length:               “Len“
Request data:                  “Data“
Template:                        “Template“
Language:                       “Language“
URL for back button:       “URLBack“
Payment method:           “PaymentMethod“
Credit card brand:           “CreditCardBrand“

• Language selection

The language selection on the payment methods selection page form occurs automatically depending on the parameter Language. Other language areas are filtered out.

If the merchant wishes to access the field of another language area e.g. with JavaScript, you can do so via the following path: Payment platform/language/@name.

• XML structure

The ‘Language’ parameter controls which section of the XML text file is read out. German ‘de’ is always used as standard.

The XML file should have the following basic structure:

‘UTF-8’ is also possible for the coding.

With <xsl:variablename=““ select=“Payment platform/language/@name”/> you can directly address an XML language section from the XSL file.

For an overview of which parameters are rendered by page, please examine the following structure (XSL file is rendered against the following XML string):

In your XSL file you can access each single value within this XML structure which is rendered in the backend based on the XML language file and additional values.

• JavaScript

Individual JavaScript methods are available either in the HEAD section of your XSL file or within the file main.js that can be found in the images folder at

Notice: No external links to the JavaScript must be user.

Conventions related to card payments

• Link to BNP Paribas logo

It’s important to provide the cardholders with information about the server they are on during the payment process. To do so, we ask the merchant to implement a logo (like it is implemented on the BNP Paribas form) or to display a small imprint link. Logos are part of the programming examples.

Both items of information must refer to the BNP page impressum.aspx. The ‘Data’ parameter, which is appended to the URL as in the following example, must be configured.

• Link to Verified by Visa and MasterCard Secure Code

Visa and MasterCard regulations require that the payment page displays the Verified and SecureCode logos. Please link the Verified logo to vbv.aspx and the SecureCode logo to:

https://brand.mastercard.com/brandcenter/mastercard-brand-mark/downloads.html

• Error mapping

In case of error, Axepta returns the form in order to enable the card data to be entered again. The merchant can only evaluate the ‘error code’ parameter and display the desired text from the XML file.

At this point the ‘error code’ template is called:

It can alternatively be implemented with ‘if’

It is also possible to integrate the error messages directly into the “main” template:

Definitions of parameters values

« PayTypes » Parameter

The different payment methods available and the specific values to write in « Paytypes » parameter.

« CCBrand » Parameter

The following table lists all card brands that can be used via the method selection payment page. When submitting the “CC” value in the parameter “PayTypes” the brands displayed are configured by submitting a string of the desired brand names separated by pipe signs.

Notice: Please note that the names of parameters can be returned in upper or lower case.