Skip to content
Fruhmann edited this page Mar 27, 2019 · 3 revisions

Paylib is a French mobile wallet initiated by a collaboration of major French banks. By linking a credit card to their account, Paylib allows consumers to make purchases without having to re-enter their card details. To pay, consumers have to enter their username, password and a code generated by the Paylib app.

Paylib Configuration

To configure your Paylib payments, please contact Wirecard Support. Available Paylib-specific settings are listed below.

Payment Action

Paylib payment can be performed using two different payment actions:

1. Authorization: Payments for orders are not captured/invoiced but only authorized by the consumer, and thus only reserved. For debit, you have to confirm/capture the amount manually.

  • This payment action triggers the transaction type authorization for payment method Paylib.
  • The order created will be labeled as Authorized.

2. Purchase: Set payment action to Purchase to capture/invoice payments of orders automatically.

  • This payment action triggers the transaction type purchase for payment method Paylib.
  • The order created will be labeled as Processing.


The descriptor is the text representing an order on the consumer's bank statement issued by their credit card company. It provides information for the consumer, as it associates a specific debit on the consumer's account with the respective purchase in your shop.

  • If the descriptor is Disabled, the issuer/acquirer generates a default entry for each purchase.

  • If the descriptor is Enabled, the default descriptor text consists of the first 9 characters of the shop name and the order number. To modify the descriptor, contact Wirecard Support.

    Data and Structure:

    • Your merchant name and merchant location are usually displayed on the cardholder's bank statement (static data). These fields, or parts of them, are used for presenting the dynamic data on the cardholder's statement.
      Apart from such static data, you can add transaction information to better reference your sales. For example, you can use invoice number, booking ID or transaction ID. This data is typically passed along to you (the merchant). As the field has a fixed length, the longer the merchant name, the smaller the number of digits allocated to dynamic information, e.g.:

      • VISA: Name: 25 digits, location: 13 digits
      • Mastercard: Name: 22 digits, location: 13 digits
      • JBC: Name: 25 digits, location: 13 digits
    • Consider all these parameters before setting a dynamic descriptor because any text exceeding the permissible length is cut off and discarded.

    • Be aware that industry-specific restrictions apply depending on card schemes.

    • Note: It is up to the issuer to decide which data provided in the dynamic descriptor is printed on the cardholder's statement. Therefore, Wirecard cannot guarantee that the dynamic descriptor data is fully printed on the cardholder's statement.

    • Wirecard Bank (WDB) receives the transaction data from the Wirecard processing platform, looks up the merchant address, consolidates static address details and dynamic sales data (including merchant name and merchant location) and routes the information and the settlement request to the issuer. The amount of information that will later appear on the customer’s card statement may vary from issuer to issuer.

Enable this feature to send the descriptor with each request/response.

Post-Processing Operations

Post-processing operations, such as refund, are currently not supported by the Wirecard Shopify App. Use the Wirecard Enterprise Portal (WEP) to execute post-processing operations.

You can’t perform that action at this time.