Functional coverage

• Card payment with 3DSV2
• Alternative payments (ALI, WEC, UPI, BAN, PAL)
• Choice of integration in remote page or via an iframe
• Refund management
• Personalization via template
• Personalization via 'custom' fields

Requirements

• Proximis version 5.13 or higher.
• Php version 7.4 or higher.

Installation

The Module is now moved to a composer third-party Plugin.

If you installed the module with an archive, you need to uninstall it with the following command. php bin/change.phar proximis:plugins -v disable module_Project_Axepta

Add the third-party Clever Age repository by adding the following to your composer.json

        {          "type": "composer",          "url": "https://nexus-production.tools-services-1.omn.proximis.com/repository/cleverage-axepta/"        }

Add the module in the require part of your composer.json

{"require": {        "cleverage/axepta": "^1"    }}

Then run your update.bash script.

Install the plugin. php bin/change.phar proximis:plugins -v enable CleverAge_Axepta

In your project configuration, make sure to have the logger by service to see this module logs in log/proximis.axepta.log

"Logger": {      "Writer": {        "fileByService": true      }    },

Configuration

Create the connector from the back office. /admin.php/Rbs/Commerce/Connector/

General properties tab.

The field titre sur le site will be visible by the customer, the label, only in the backoffice.

The field code is used to identify the connector in the code base.

The field description can contain formatted text, images and links.

The field visuel allows the display of an image next to the titre sur le site.

The field critère d’application allows setting specific rules to display the connector.

The field instruction de paiement can contain formatted text, images and links.

Technical properties tab.

Select for the connector type : Connecteur de paiement Axepta

Some information about your current environnement is displayed. Make sure to use the appropriate configuration keys.

• Configuration keys : This information is provided by BNP.

• Connector Options : Select your options for this connector.

• Template personnalisé

Allow to use Axepta custom page, see : https://docs.axepta.bnpparibas/pages/viewpage.action?pageId=6914816#Pagedepaiement-Pagedepaiementducommer%C3%A7ant

“Template”, “CCTemplate” et SDDTemplate” parameters are available.

• Currencies : Select allowed currencies for this connector.
• Payment modes : Select allowed payment modes for this connector.

To have this payment mode available in the checkout, you need to add it to the checkout process. /admin.php/Rbs/Commerce/Process/

You can create multiple connectors with a different configuration. You can have a connector dedicated to one payment mode for example.

You can create multiple connectors with a different configuration. You can have a connector dedicated to one payment mode for example.

Transactions monitoring

From the url admin.php/Rbs/Order/Transaction/ select a transaction to see it’s technical details.

Refunds management 

When an order is cancelled, it is eligible for a refund.

From the url ua.php/financial/ in the refund detail page, select the action ‘traiter’ and confirm.

The query is sent to Axepta and the operation result can be found in the timeline section.

If an error occurs, a message will be displayed.

If the refund is accepted, you can validate it by selecting ‘traitement manuel’

Developer Documentation :

Added a new payment method.

The documentation of alternative payment modes are available in the following page.

https://docs.axepta.bnpparibas/display/DOCBNP/Alternative+payment+methods+Integration

You should take exemple on already implemented payment mode.

1. Add a new class for each payment mode you want to add in App/Modules/Project/Axepta/PaymentModes.

This class will need to extend the PaymentModeBase and declare the buildDeportedPageQuery method.

public static function buildDeportedPageQuery(\Rbs\Payment\Documents\Transaction $transaction, $connectorId, \Rbs\Website\Documents\Website $website, \Project\Axepta\Events\Documents\AxeptaEngine $engine): string {    $paymentRequest = parent::prepareDefaultPaymentRequest($transaction, $connectorId, $website, $engine);     // PAYMENT_URL is specific to the payment mode and available in the documentation.    $paymentRequest->setUrl(self::PAYMENT_URL);     return parent::validateAndBuildQueryString($paymentRequest, $engine, $transaction, $website);  }

Depending on the payment mode required parameters you will need to add them to the $paymentRequest. (ie $paymentRequest→setAccOwner($accountOwner);)

     2. Add your payment trigram inside showPaymentModes() in the file App/Modules/Project/Axepta/Assets/Admin/directives.js

     3. Add your payment trigram inside getEnabledPaymentModes() in the file App/Modules/Project/Axepta/Events/Documents/AxeptaEngine.php

and to getDeportedPageQuery() in the file App/Modules/Project/Axepta/Http/Ajax/DeportedPageQuery.php

     4. Add the logo of the payment mode in the folder App/Modules/Project/Axepta/Assets/Theme/img/logos

The logo must be named after the trigram and the extension must be .png

Add of the FLOA Pay payment method

• Add the connector 
  

To make FLOA payment methods (Deferred/ 3X/ 4X) available to your customers, you must configure a new connector from your BO at/admin.php/Rbs/Commerce/Connector/ and add it to the payment methods available in your payment process.

In the activation key section use the following key :

• Connector configuration

 Here is an example configuration with the test values provided by Floa : 

• Connector display with compatible modes

Once configured, the connector will display with the others.  FLOA buttons will display based on the min/max thresholds configured.

  When clicking on a Floa logo, the user is redirected to a remote page. Fill in the information for an eligibility result (display page) then in the second step, the card information n(payment page) 

• File page

• Payment page

Test cards are available at : https://floapay.readme.io/reference/test-card-numbers 

Add of the Apple Pay payment method

• Apple Pay configuration 

Apple Pay is not supported by all devices and browsers, the list of supports is available here https://developer.apple.com/documentation/apple_pay_on_the_web/#2978468 (use of Apple Pay JS). 

Here is what is implemented for the Axepta - Proximis connector : 

• Connector configuration 

To integrate with Apple Pay, two certificates are required, the merchant identification certificate and the payment processing certificate.

Apple Pay side

Merchant identifier

Create an Apple Pay merchant ID by following the Apple documentation https://developer.apple.com/help/account/configure-app-capabilities/configure-apple-pay-on-the-web 

Payment Processing Certificate

• Axepta BNP Paribas support generates the . csr for the merchant
• Using this . csr, generate the file apple-developer-merchantid-domain-association.txt which will identify the merchant on the site
• Send your integrator the file apple-developer-merchantid-domain-association.txt obtained during the generation of your merchant ID so that it deposits it in the App/Config/.well-known . This will allow in your next deployment to place this file at the root of your site in order to have it verified by Apple.

Merchant Identification Certificate

• Generate on a Mac a file a file. csr
• From your Apple Developer Admin account generate a . cer certificate from the . csr file.
• Retrieve this certificate. cer on the Mac and group it with the key to the . csr file in your keychain.
• From this  grouping in your keychain create a file. p12
• Then use this file. p12 to generate an ApplePay.crt.pem certificate file and a second file for the associated ApplePay.key.pem key (the file nomenclature must be respected).
• Open the terminal and run the commands below to split the. p12 in key and certificate, where ApplePayMerchantID_and_privatekey.p12 is the name of your file. p12

•  Drop these two . pem files in the App/Config/ApplePay directory of your project.

 We recommend using a passphrase when generating the file pair. pem, it will have to be entered in the connector configuration in the Proximis Back-Office.

Proximis side

Payment connector

To allow your customers to pay via Apple Pay, you must activate the payment method in the connector configuration in Proximis :

You can then specify the different settings associated with Apple Pay: 

Apple Pay SDK Statement

In the Proximis BO go to “Settings > Common > HTML Code” and click on the “Add HTML code” button :

Then declare the Apple Pay SDK in your document : https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js

Save your document: 

Then go to the configuration of your payment page in the Proximis BO and declare a new block of type “HTML code” then fill in the previously created document containing the SDK as a parameter.

Payment front

Payment via Apple Pay is then available on your front connector :

When the Apple Pay button is clicked, the payment sheet will open :

How to customize the front template.

You can edit the twig file App/Modules/Project/Axepta/Assets/Theme/ng-template/project-axepta-payment.twig to remove the inline style and declare your own CSS rules.

How to declare new translations.

Right now the module is shipped with the fr_FR locale. But you can create a new folder for any locale. Take exemple on the files inside te folder App/Modules/Project/Axepta/Assets/I18n

You can always edit the translated strings from the translation manager.ua.php/lmsManager/Plugin/m.project.axepta

PayPal testing 

If you would like to test PayPal in a test environnent, please follow the instructions in order to activate the Sandbox. 

Description of available methods of payment