Dynamic Descriptors

📘

Dynamic Descriptors applicability

Dynamic Descriptors can be applied to Card Deposits, Card Withdrawals and Card Refunds, as well as Card Verifications and Card Pre-Authorisations where PXP Financial is the Acquirer.

Descriptors for Cardholder's Statement

A merchant descriptor is what appears on a cardholder’s statement after they make a purchase - it’s goal is to identify the transaction to the cardholder.

PXP Financial sends by default the merchant name and location information for each transaction to the issuing bank. The issuing bank will use this information for the descriptor, but the final descriptor shown to customers depends on their setup.

Descriptors consist of two lines of information:

• Line 1: usually the merchant name (must contain the “doing business as”(DBA) name of the merchant or a name more recognizable to Cardholders.")
• Line 2: usually the city (but could also contain contact information like phone number or URL)

Static Descriptors

By default the PXP Financial system uses static descriptors. Those are configured individually for each merchant and are used when card transactions are authorised and captured.
If not requested differently by the merchant the descriptors use this setup:

• Line 1: merchant name
• Line 2: city

Please contact PXP Financial Support in order to set this up.

Dynamic Descriptors

Card payments can also be configured to support Dynamic Descriptors in order to display transaction/payment specific information on the cardholder's statement.

If dynamic descriptors are configured, the following information will be used:

• Line 1: "dynamic part" (taken from payment description, more information below)
• Line 2: usually the city (but could also contain contact information like phone number or URL)

Please contact PXP Financial Support in order to set this up.

Once this has been configured, the payment description which was provided in the payment request will be used as "dynamic part" for the descriptors.

Backend2Backend

The key-value PaymentDescription must be provided in the intiatePayment.specificPaymentData collection (for deposits and withdrawals) or in the initiatePaymentFromReference.specificPaymentData collection (for card refunds) up to a length of no more than 25 characters.

<specificPaymentData>
    <data xsi:type="keyStringValuePair">
    <key>PaymentDescription</key>
    <value>dynamic part of billing descriptor</value>
    </data>
    <data xsi:type="keyStringValuePair">
    <key>PaymentDescriptionLanguageCode</key>
    <value>en</value>
    </data>
</specificPaymentData>

Redirect

The key-value Description must be provided in the getRedirectData.additionalDetail section up to a length of no more than 25 characters.

🚧

Checkout Payment Description Usage

It is important to know that if a Description is provided in the getRedirectData request, this will not only be used as "dynamic part" for the billing descriptors, but also to overwrite the (default) label of the transaction description in the Amount header of the checkout selection and detail page. See Design a Merchant Custom Skin for more information.

<additionalDetails>
  <detail xsi:type="keyStringValuePair">
    <key>Description</key>
    <value>Description which is displayed to customer in checkout = dynamic part of billing descriptor</value>
  </detail>
</additionalDetails>

Payment Facilitators

As required by the schemes (Visa and Mastercard) it is mandatory to show the Payment Facilitator Name as first part of Line 1.
Once this is configured, the PXP Financial system will ensure this is pre-fixed to the static or dynamic part of the billing descriptors (for card transactions of merchants which belong to this payment facilitator).