 is the text that appears for each transaction listed on the monthly statement sent to your customer. The statement descriptor gives the cardholder information to identify each transaction.

You can configure the text of a statement descriptor for your organization.

Statement descriptions are important because:

Cross River supports 2 kinds of statement descriptors: 

When you onboard to CR you supply your merchant name and abbreviated name. Tell your payments implementation manager whether you prefer a static or dynamic descriptor. If you're configured for dynamic descriptors you enter your additional text as part of the API request for each transaction.

This text is always the same and also appears as part of the dynamic descriptor. Tell your implementation manager which types of static descriptor you prefer:

, the descriptor could appear in these ways:

Some processors append city and state to the descriptor:

If you're configured for dynamic statement descriptors, you first choose whether to include the abbreviated name or not. Like with static descriptors, this text always appears for every transaction and does not change. In effect, the dynamic descriptor is in addition to the static descriptor.

You add additional text using a specific field in the transaction API POST request. The descriptor will look like this:

, the descriptor would look like one of these:

OFAC screening overview

Statement descriptor

Bank Identification Number. A unique identifier used in payment card transactions.

COS_Explorer

relationshipmanager

Cross River guides provide details about our products

guide

var_miha

new_var_2

new_mih_var

mih_var

This is a plain text that will be inserted in an expandable heading for using this raw as an exampl

testheight

available

testulet

testvar

altscenario

This is a plain text that will be inserted in an expandable heading for using this raw as an example

scenario

exemplu