Letzte Aktualisierung 28/04/2015

1. What is Paylib?

Paylib is a French e-wallet that contains cards supported by Carte Bancaire in France.

A customer can pay with Paylib in two ways:

  • via the Paylib mobile app
  • via an SMS code

As no card details are required, the customer does not need to have his card at hand or have to pass sensitive card details.

Paylib is supported by the following acquiring banks in France:

  • BNP Paribas
  • Société Générale
  • La Banque Postale

Paylib via Ingenico ePayments must be used with our e-Commerce hosted payment page solution. Only minimal integration is required.

2. Activation and configuration

In order to add Paylib, you need to have at least one credit or debit card (supported by Carte Bancaire in France) activated in your Ingenico ePayments account. The acquirer of this card needs to be one of the acquirers supported by Paylib at Ingenico ePayments.

Once you've added the payment method accordingly, you can request the enrollment of the payment method. The enrollment request will be sent to unsere Kundendienst team, which will complete the rest of the activation.

In our test environment the activation process is similar, with the exception that a sandbox environment of Paylib is used and there's no acquirer connection.

3. Integration with e-Commerce

If you let your customers choose their preferred payment method directly on our e-commerce hosted payment page (as opposed to a selection page of your own), no further integration is required; the payment method (once activated) will be visible on the payment page.

In the event you've created a payment method selection page of your own, by which your customers are redirected from your page directly to the payment page with the payment method preselected, you're making use of the PM and BRAND parameters.

To call the Paylib payment page directly, the following PM and BRAND values must be used:

Parameter Value
PM Paylib
BRAND Paylib

The same values are returned in the redirection and post-sale feedback.

4. Testing

Once you've activated Paylib in your test account, you can perform tests between the Ingenico ePayments and the Paylib platform.

Testing Paylib however is focussed mainly on testing the various possibilities on the Paylib platform. As there's no connection with any acquirer, it's not possible to make any authorisations or captures; A transaction will always be refused.

Below are all the tests that are possible with Paylib, using login en password:

Login Password Description
sb.visa.ok@paylib.fr
P@ssword1!
Successful authentication and VISA card details available
sb.mc.ok@paylib.fr
P@ssword1!
Successful authentication and MasterCard card details available
sb.multi.ok@paylib.fr
P@ssword1!
Successful authentication and choice of cards: 1 VISA and 1 MasterCard
sb.multi.ok.sms@paylib.fr
P@ssword1!
Successful authentication and choice of cards: 1 VISA and 1 MasterCard.
Hard authentication required: OTP SMS (One-Time password).
SMS not available in TEST, ‘123456’ to be used.
sb.ko@paylib.fr
P@ssword1!
Refused authentication
sb.multi.ok.nocard@paylib.fr
P@ssword1!
Successful authentication and no cards available.
sb.multi.ok.te@paylib.fr
P@ssword1!
Successful authentication and choice of cards: 1 VISA and 1 MasterCard, but will result in a technical error.
sb.multi.ok.badtoken@paylib.fr
P@ssword1!
Successful authentication, but invalid token when getting card details.

5. Reporting

5.1 Online

As Paylib only acts as a container for the actual cards, at the beginning of a transaction the payment method will be “Paylib” but later change to "Visa", "Mastercard", etc., once the card data is collected. Nevertheless, a "Wallet" field is also available and will contain the “Paylib” value. 

Via "View transactions" in your Ingenico ePayments account, your Paylib transactions would look like this (click image to enlarge):

Paylib transactions

Note that the transaction in status 0, in which case no card details have been collected, still shows "Paylib" as the payment method, whereas for the declined transaction a Visa card was used. For both transactions the Wallet column shows "Paylib".

5.2 Download

In the files that you download via "View transactions" and/or "Financial history", the "METHOD" and "BRAND" columns show the values of the payment method that the customer used. In case of Paylib, these values will be no different than those of normal credit card transactions.

Therefore, in order to distinguish which credit card transactions were actually initiated with Paylib, you can add an extra field/column to your reports: "TO_WALLET". To have this field added, go to "Operations" > "Electronic reporting" and under the "Dynamic" structure" add the "[TO_WALLET]" field to the "Optional fields":

Paylib Reporting
 

6. Transaction maintenance

Paylib is only applied as such in the beginning of a transaction. Once the card details have been processed, the payment method changes to the card brand used (e.g. Visa or MasterCard). As from that point, Paylib will only be used as the wallet indicator.

Consequently, all usual maintenance operations for credit cards also apply here.

Diese Website verwendet Cookies, um Ihnen die beste Nutzer-Erfahrung zu geben. Wenn Sie Cookies nicht akzeptieren möchten, empfehlen wir Ihnen, Ihre Cookie-Einstellungen zu ändern. Klicken Sie auf "Akzeptieren", um alle Cookies von dieser Website zu ermöglichen.

Cookie-einstellungen

Cookies werden verwendet, um die Webseite zu verbessern und Informationen anzubieten, die für Sie von Interesse sind.

Funktionsbezogene Cookies

Funktionsbezogene Cookies sind für das ordnungsgemäße Funktionieren der Webseite nötig. Diese Cookies können nicht deaktiviert werden.

Optimierte

Optimierungscookies ermöglichen es uns, die Nutzung der Webseite zu analysieren, damit wir unsere Webseite bewerten und verbessern können.
Dies ist der Standardwert.

Personalisierte

Personalisierte Cookies werden für Soziale Medien und die erweiterte Personalisierung verwendet. Sie ermöglichen es uns, Ihnen Informationen bezüglich Ihres Unternehmens zu zeigen.


Beispiel für unterstützte Funktionen

  • Ländereinstellung speichern
  • Spracheinstellung speichern

Beispiel für eine unerlaubte Funktion

  • Personenbezogene Daten über Ihren Besuch speichern
  • anonymes Tracking über Google Analytics
  • Tracking zum Zweck der Weitervermarktung

Beispiel für unterstützte Funktionen

  • Ländereinstellung speichern
  • Spracheinstellung speichern
  • Anonymes Tracking über Google Analytics

Beispiel für eine unerlaubte Funktion

  • Personenbezogene Daten über Ihren Besuch speichern
  • Tracking zum Zweck der Weitervermarktung

Beispiel für unterstützte Funktionen

  • Ländereinstellung speichern
  • Spracheinstellung speichern
  • Anonymes Tracking über Google Analytics
  • Auf Ihre Interessen abgestimmte Inhalte bereitstellen
  • Auf Ihre Interessen abgestimmte Inserate bereitstellen
  • Tracking zum Zweck der Weitervermarktung

Beispiel für unerlaubte Funktionen

  • Personenbezogene Daten speichern