{"_id":"59dfa8f45c0bae001c2e8b08","category":{"_id":"59dfa8f45c0bae001c2e8af0","version":"59dfa8f45c0bae001c2e8ae8","project":"57336fd5a6a9c40e00e13a0b","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-11-03T20:45:01.593Z","from_sync":false,"order":7,"slug":"topics","title":"Guides"},"parentDoc":null,"project":"57336fd5a6a9c40e00e13a0b","user":"560d5913af97231900938124","version":{"_id":"59dfa8f45c0bae001c2e8ae8","project":"57336fd5a6a9c40e00e13a0b","__v":1,"createdAt":"2017-10-12T17:40:04.535Z","releaseDate":"2017-10-12T17:40:04.535Z","categories":["59dfa8f45c0bae001c2e8ae9","59dfa8f45c0bae001c2e8aea","59dfa8f45c0bae001c2e8aeb","59dfa8f45c0bae001c2e8aec","59dfa8f45c0bae001c2e8aed","59dfa8f45c0bae001c2e8aee","59dfa8f45c0bae001c2e8aef","59dfa8f45c0bae001c2e8af0"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"3.23. Release","version_clean":"8976.0.0-Basics","version":"8976-Basics"},"__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-21T15:29:17.359Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":14,"body":"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.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Depending on the processor 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 show in the settled transaction your shoppers see on their statements. We are doing everything we can to make sure pending authorization messages reflect the same information. If you are not using the default invoice and receipt offered by BlueSnap, we recommend adding the following note to your shoppers: “This transaction is being processed by BlueSnap”.\",\n  \"title\": \"BlueSnap information may appear for pending transactions\"\n}\n[/block]\n##Statement descriptor format and content\nYou'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.\n\nThe descriptor is shown with BlueSnap prefix and your support phone number, as follows:\n**<span style=\"color:MediumSeaGreen\">[BlueSnap prefix]</span><span style=\"color:SlateBlue\">[Descriptor]</span><span style=\"color:Tomato\">[Support phone number]</span>**\n\nFor example: <span style=\"color:MediumSeaGreen\">BLS*</span><span style=\"color:SlateBlue\">MerchantName</span><span style=\"color:Tomato\">8001234567</span>\n\n <span style=\"color:MediumSeaGreen\">BlueSnap prefix</span>: The prefix **BLS*** appears on all transactions.\n  \n<span style=\"color:SlateBlue\">Descriptor</span>: 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.\n\n<span style=\"color:Tomato\">Support phone number</span>: The support phone number portion of the descriptor is either defined at the account level and is automatically included in the descriptor or it is dynamically changed per transaction. To set the support phone number at the account-level, go to **Settings > General Settings > Branding Settings** in the BlueSnap merchant console. To see how to change the support phone number per transaction, see below.\n\n## Account-level descriptor and per-transaction or per-subscription descriptors\nYou must define an account-level statement descriptor text, which will serve as the default descriptor for all transactions. For instructions on setting this up for your account, [go here](http://support.bluesnap.com/docs/statement-descriptor#defining-the-account-level-statement-descriptor).\n\nWhen using the **Payment API**, you can also define descriptor text dynamically per transaction by including the `softDescriptor` property in the [cardTransaction](/v2.1/docs/card-transaction), [altTransaction](/v2.0/docs/alt-transaction), or [subscription](/v2.1/docs/recurring-subscription) resources. You can also define the support phone number dynamically per transaction by including `descriptorPhoneNumber` in [cardTransaction](/v2.1/docs/card-transaction) or [subscription](/v2.1/docs/recurring-subscription).\n\nWhen using the **Extended Payment API**, you can dynamically define descriptor text or support phone number per transaction by including the `soft-descriptor` property or the `descriptor-phone-number` property in the [order](/v3.0/docs/order) resource.","excerpt":"","slug":"statement-descriptor","type":"basic","title":"Statement Descriptor"}

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 processor 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 show in the settled transaction your shoppers see on their statements. We are doing everything we can to make sure pending authorization messages reflect the same information. If you are not using the default invoice and receipt offered by BlueSnap, we recommend adding the following note to your shoppers: “This transaction is being processed by BlueSnap”.

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:
[BlueSnap prefix][Descriptor][Support phone number]

For example: BLS*MerchantName8001234567

BlueSnap prefix: The prefix BLS* appears on all transactions.

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 is either defined at the account level and is automatically included in the descriptor or it is dynamically changed per transaction. To set the support phone number at the account-level, go to Settings > General Settings > Branding Settings in the BlueSnap merchant console. To see how to change the support phone number per transaction, see below.

Account-level descriptor and per-transaction or per-subscription descriptors

You must define an account-level statement descriptor text, which will serve as the default descriptor for all transactions. For instructions on setting this up for your account, go here.

When using the Payment API, you can also define descriptor text dynamically per transaction by including the softDescriptor property in the cardTransaction, altTransaction, or subscription resources. You can also define the support phone number dynamically per transaction by including descriptorPhoneNumber in cardTransaction or subscription.

When using the Extended Payment API, you can dynamically define descriptor text or support phone number per transaction by including the soft-descriptor property or the descriptor-phone-number property in the order resource.