Dynamic Statement Descriptors & MCCs


Limited Support

This functionality may not be available for all payment methods. We are working on extending support to additional payment methods. Please contact us if you have questions.


PCI-DSS Warning

If you use this guide to process credit cards, we will likely ask you to submit proof of PCI-DSS compliance. You may be able to lessen the requirement by collecting token information client-side and using Tokens. Have a chat with your Customer Success representative for more details.

The simplest way around this is to integrate with Hosted Page or Hosted Fields.

By default all payments use a single statement descriptor and merchant category code (MCC) for all their payments. Merchants with brands that differ from their merchant name, or multiple distinct brands, can set a per-payment or per-session MCC at their respective creation time to help their customer identify charges.

This guide extends Creating Payments with additional information. Please refer to the original Creating Payments guide for how to generate a session or payment.


Please see the table below for a list of supported parameters:

mccstring, 4 characters"5799"
statement_descriptor[statement_descriptor_alpha]string, alphanumeric"Degica"

Which data gets passed on to the payment gateway and ultimately the customer depends on the payment method and the gateway.


To add an MCC and/or a dynamic statement descriptor, supply the additional keys as show in this recipe:

If you supply an MCC or statement descriptor when creating a session, they will be passed on to the resulting payment as well.


You can also create a payment directly with a custom MCC and/or dynamic statement descriptor:

What’s Next