Statement Descriptor

BlueSnap is required to send the shopper's bank your statement descriptor text, along with your business's URL, phone number, and address. The shopper's card or bank statement will show your statement descriptor text, along with some or all of the other information, depending on the bank.


BlueSnap information may appear for pending transactions

Depending on the bank processing your card transactions and the shopper’s issuing bank, there are instances where the BlueSnap company name and information appear on the pending authorization transaction. Your own selected descriptor should be displayed on the settled transaction your shoppers see on their statements. If you are not using the default invoice and receipt offered by BlueSnap, we recommend adding the following note to your shoppers on the invoice and receipt you create:

This transaction is being processed by BlueSnap. It may appear as BlueSnap, Payment Processed by BlueSnap or Online Payment”.

Statement descriptor format and content

You'll need to customize the statement descriptor to show your "Doing Business As" name. It should be a name that your shoppers closely associate with you. Showing this information on the billing statement helps shoppers identify the purchase, therefore reducing both returns and chargebacks.

The descriptor is shown with BlueSnap prefix and your support phone number, as follows:
[Descriptor][Support phone number]

For example: MerchantName8001234567

Descriptor: This is the descriptor text that you define. The descriptor field supports up to 20 alphanumeric characters, spaces, and these special characters: & , . - #. We recommend you include your DBA (Doing Business As) name in the descriptor. You may also include your address, product name or website URL in the descriptor.

Support phone number: The support phone number portion of the descriptor can be defined at the account level and is automatically included in the descriptor. This field can contain up to 12 numeric characters. To set the support phone number at the account level, go to Account Settings > General Settings in the Merchant Portal. This phone number can only be overridden if you are using one of the BlueSnap APIs. Refer to the API documentation to learn how.

Account-level descriptor, per-product descriptor, and per-transaction descriptor

  • Account level: You must configure an account level statement descriptor, which serves as the default descriptor for all transactions. Refer to Defining the account-level statement descriptor.
  • Per product (only with BuyNow hosted checkout): If you are using our BuyNow hosted checkout pages, you can set up a separate statement descriptor per product on the Product Information page.
    Note: If a shopper purchases two or more items (with different product-level descriptors) in the same transaction, the account level descriptor will override.
  • Per transaction and per subscription (only with the API): If you are using our Payment API or Extended Payment API, you can also define a descriptor dynamically per transaction and/or per subscription by including the soft-descriptor property in your request. You can define the support phone number dynamically by including the descriptor-phone-number property in the request. Refer to the API documentation.

Defining the account-level statement descriptor

To set up a statement descriptor for your BlueSnap account, go to Settings > General Settings.

In the Branding settings section, define the Default Statement (Soft) Descriptor and the Support phone number.


Note: This is not supported for Pre-Authorized Debit. The soft descriptor set in the portal will be displayed on the shopper's bank statement.