Welcome to Zuora Product Documentation

Explore our rich library of product information

Configure dynamic soft descriptors

Learn how to configure dynamic soft descriptors to enhance transaction visibility and reduce chargebacks by mapping descriptor fields to standard or custom fields.

You can configure dynamic soft descriptors, which will take precedence over any static soft descriptors you have configured on the gateway instance page. Dynamic soft descriptors enable you to utilize values from standard or custom fields, providing more detailed and relevant information on your customers' billing statements. The descriptor containing the retrieved text will be displayed on your customers' cards or account statements and help them identify transactions. This will help reduce chargebacks by providing enhanced visibility of transaction references to the cardholders.

To enable and configure dynamic soft descriptors for your Checkout.com gateway instance:

  1. Navigate to Settings > Payments > Define Payment Rules.
  2. In the Select the source field for Soft Descriptors to appear on statements section, you can map the soft descriptor fields to specific Zuora fields.
    1. Description: Select a field from the dropdown list. For example, you can map this to a standard field, like Account.Name or a custom field you have created on the Account object.
    2. Merchant City: This field will automatically be sourced from the Payment Method address, otherwise it will fall back to the value in the BillTo Contact address.
  3. Click Save to apply the configuration.

After you have configured these rules, subsequent payment requests will use the values from the mapped fields.

  • If both the static

    descriptor in the Checkout.com gateway instance

    and a dynamic soft descriptor are configured, the dynamic soft descriptor values will override the static value in the payment request.
  • You can map soft descriptor fields to custom fields. For instance, if you create a custom field on the Account object and assign it a value, you can select that custom field from the dropdown to be sent in the payment request.
  • After creating a payment, you can verify which values were sent by checking the request and response logs for the payment. The logs will show the values that were dynamically pulled from the configured fields and appended to the request body of the payment request.