Guides
Start typing to search…

Descriptor Guide

Descriptor allows the merchant to define a static or dynamic descriptor, which appears in the payment statement.

🚧

Please note that....

  • Special configuration is required to use static or dynamic descriptor. For more information, please contact Revolv3 Support Team.

Static Descriptor

Static descriptor is easy to set up and maintain, requiring no dynamic updates or customizations for each transaction. Ideal for merchants offering a single product or service with no need for varied descriptions.


Processors supporting Static Descriptor

📘

Important clarification

Actually every payment processor supports a static descriptor, since we can't leave it empty or unfilled for real transactions, it should at least contain legal or DBA names. Usually this functionality can be provided by the payment processor itself.

Despite this Revolv3 also provides the ability to configure a static descriptor on our side, but only for some processors.

Static Descriptor currently can be configured in Revolv3 Portal for the following processors:

  • WorldPay
  • Nuvei
  • Adyen

Dynamic Descriptor

The primary purpose of a dynamic descriptor, like a static descriptor, is to provide clear and specific transaction details to cardholders on their bank statements, improving transparency and reducing chargebacks.

However, a dynamic descriptor allows merchants to customize the information that appears on a cardholder's statement for each transaction, dynamically tailoring it to reflect the specific purchase.

The following object is used to specify the dynamic descriptor:

"DynamicDescriptor":{
     "SubMerchantId": "98765",
     "SubMerchantName": "Test",
     "SubMerchantPhone": "408-555-1212",
     "CountryCode": "US",
     "City": "Oakland"
},

There several parameters, each of which is optional, as is the parent DynamicDescriptor object.

The following table provides a description of each parameter:

Name

Description

SubMerchantId

The internal merchant’s ID, which is sent to the relevant card scheme

SubMerchantName

The merchant name, as is displayed for the transaction on the consumer’s card statement.

For payment facilitator only, the maximum length of the parameter is 22, and might consist of the following structure: Prefix*<subMerchant name>** where:

  • Prefix – The PayFac prefix, approved by processor.
  • * – A fixed character.
  • <subMerchant name> – Sub-merchant name.

SubMerchantPhone

The merchant (sub-merchant for payment facilitators) contact information, as is displayed for the transaction on the consumer’s card statement. It can also be an email address.

CountryCode

The merchant (sub-merchant for payment facilitators) contact information, as is displayed for the transaction on the consumer’s card statement. It can also be an email address.

City

The payment facilitator’s sub-merchant’s city name


Endpoints supporting Dynamic Descriptor

Not all endpoints include the ability to define the DynamicDescriptor object, so the following list will help you when you are planning an integration or to understand if you can use this feature in your current integration.


Processors supporting Dynamic Descriptor

Dynamic Descriptor currently can be configured for the following processors:

  • WorldPay
  • Nuvei

This means that if the request contains a DynamicDescriptor object, this data will be passed to the corresponding processor, otherwise it will not.

Updated 8 days ago