Dynamic Billing Descriptor

Learn how dynamic billing descriptors work

The billing descriptor is the text that is displayed on the customer's credit card statement identifying a purchase from a merchant’s website.
Using clear and accurate statement descriptors can reduce chargebacks and disputes. Banks and card networks require the inclusion of certain types of information that help customers understand their statements, and statement descriptors provide this information.
This descriptor can be set dynamically in a payment request.

📘

If you would like to enable this functionality, please contact payabl Risk Team.

Difference between Dynamic and Static descriptors

Static Descriptor: The descriptor for all transactions processed through one MID remains the same. Multiple descriptors are not possible.
Dynamic Descriptor: The descriptor for all transactions is processed for different products. You can have multiple descriptors.

Why you need Dynamic Descriptor?

If a descriptor does not fit with the business, chances are that the customer will dispute the transaction - simply because he doesn’t recall having made the purchase. The more informative the descriptor, the lower the risk for receiving a dispute.

📘

If you have one MID and different accounts/URLs, then you can use Dynamic Descriptor for those different URLs.

How to use Dynamic Descriptor

A Dynamic Descriptor can be sent with each transaction via the API request. So for this, you can send the parameter in your request:
custom2: Dynamic descriptor.

Make sure that the total length of the concatenated descriptor is no less than 38 characters, if it is shorter then rest can be filled with empty space.

The DBa (doing business as) should contain a maximum of 25 characters with only letters and numbers. The city field should contain a maximum of 13 characters.

Dynamic Descriptor Example

custom2 = My Company Name/Phone Number/City.

Did this page help you?