{"title":"Transaction description","category":"default","creationDate":1674660120,"content":"<p>When shoppers check their bank statements, they need to be able to easily identify the charges they see. The text that describes charges is known as a <em>transaction &nbsp;description<\/em>, <em>statement&nbsp;descriptor<\/em>, <em>shopper&nbsp;statement<\/em>, or <em>billing&nbsp;descriptor<\/em>. If shoppers do not recognize a transaction by its description:<\/p>\n<ul>\n<li>There is a higher chance your shopper issues a chargeback.<\/li>\n<li>You can get a fine from the relevant card scheme related to your chargeback rate.<\/li>\n<\/ul>\n<p>To prevent these issues, ensure that your transaction description contains your brand or the (chain) merchant name that is most recognizable to the cardholder (as required by the card schemes), and optionally customize your transaction description.<\/p>\n<h2>Requirements<\/h2>\n<p>Before you begin, take into account the following requirements, limitations, and preparations.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Requirement<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Integration type<\/strong><\/td>\n<td style=\"text-align: left;\">Any payments integration with Adyen.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/development-resources\/api-credentials\/roles\/\">API credential roles<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">To customize transaction descriptions using the Management API, make sure that you have the following role: <ul><li markdown=\"1\"><strong>Management API \u2014 Payment methods read and write<\/strong><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/account\/user-roles\">Customer Area roles<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">To customize transaction descriptions using the Customer Area, make sure that you have one of the following roles: <ul><li markdown=\"1\"><strong>Merchant admin<\/strong><\/li> <li markdown=\"1\"><strong>Change payment methods<\/strong><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Limitations<\/strong><\/td>\n<td style=\"text-align: left;\">Take into account the following: <ul><li markdown=\"1\">You can only customize your transaction description in the live environment.<\/li> <li markdown=\"1\">If you want to define <a href=\"#multiple-in-ca\">multiple different descriptions<\/a> by uploading a CSV file, note that the maximum file size is 10 MB.<\/li> <li markdown=\"1\">Not all payment methods allow customization of the transaction description. See the <a href=\"#payment-methods\">supported payment methods<\/a>.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Without customization<\/h2>\n<p>Without customization, the transaction description consists of the <strong>Name<\/strong> set in your <a href=\"https:\/\/ca-live.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">live Customer Area<\/a> under <strong>Settings<\/strong> &gt; <strong>Account<\/strong>, combined with the <strong>City<\/strong> and the <strong>Country\/Region<\/strong> from your merchant account address.<\/p>\n<p>The city and country\/region are always added to transaction descriptions, even if you customize the description.<\/p>\n<h2>Customization options<\/h2>\n<p>To help your shoppers easily identify the payments made to your business, you can customize the transaction description by adding information. You can add either of the following:<\/p>\n<ul>\n<li>A <a href=\"#dba\">Doing Business As (DBA) name<\/a>: a static value that represents your business.<\/li>\n<li>A <a href=\"#dynamic-values\">dynamic value<\/a>: the transaction-specific shopper statement that is specified in the payment request.<\/li>\n<li>A <a href=\"#combination\">combination<\/a> of your DBA name followed by the shopper statement from the payment request.<\/li>\n<\/ul>\n<p>If you do business in Japan, we highly recommend that you <a href=\"#japanese-characters\">add localized shopper statements in Japanese characters<\/a>.<\/p>\n<h3 id=\"dba\">Doing Business As (DBA) name<\/h3>\n<p>Your DBA name is a static value that represents your business. To add your DBA name to your transaction descriptions, you need to turn on this setting, and specify the text to use.<\/p>\n<p>We recommend that you set your DBA name to the name by which your shoppers know your business.<\/p>\n<h3 id=\"dynamic-values\">Dynamic values<\/h3>\n<p>Using dynamic values, you can customize the transaction description for each of your shoppers. For example, you can add the order reference number corresponding to the payment.<\/p>\n<p>To add a dynamic, transaction-specific shopper statement to your transaction descriptions, you need to turn on this setting, and <a href=\"#shopper-statement\">specify a shopper statement<\/a> in each individual payment request.<\/p>\n<p>Be aware of the following:<\/p>\n<ul>\n<li>If you do not turn on dynamic values, the shopper statement from the payment request will <em>not<\/em> appear in your shoppers' bank statements.<\/li>\n<li>If you turn on dynamic values but do not send a shopper statement in the payment request, your DBA name will be used instead.<\/li>\n<\/ul>\n<h3 id=\"combination\">Combination<\/h3>\n<p>To add both your DBA name and a transaction-specific shopper statement to your transaction descriptions, you need to turn on this setting, specify a DBA name, and <a href=\"#shopper-statement\">specify a shopper statement<\/a> in each payment request.<\/p>\n<p>With this setting, your DBA name is used as a base for the transaction description. The shopper statement defined in the payment request is appended to this description.<\/p>\n<h2>Customer Area or Management API<\/h2>\n<p>To add information to the transaction description, you can use the live Customer Area or the live Management API.<\/p>\n<ul>\n<li>\n<p>Using the <strong>live Customer Area<\/strong>, you have two options:<\/p>\n<ul>\n<li>You can define the <em>same transaction description<\/em> for an individual merchant account or store or for multiple accounts or stores in one go.<\/li>\n<li>Or you can upload a CSV file to define <em>various different transaction descriptions<\/em> for multiple merchant accounts and stores.<\/li>\n<\/ul>\n<p>In both cases the customized transaction description is applied to transactions made using <strong>all the payment methods<\/strong> that support customization and that have been added to the merchant account or store.<\/p>\n<\/li>\n<li>\n<p>Using a <strong>live Management API<\/strong> endpoint, you can customize the transaction description <strong>per payment method<\/strong>. In this way you can use different descriptions for different payment methods. Not all payment methods that are available through the Management API support customization.<\/p>\n<\/li>\n<\/ul>\n<p>A payment method-specific customization overrules the general transaction description settings from the Customer Area.<\/p>\n<h2>Check the transaction description<\/h2>\n<p>In your live Customer Area you can check the transaction description that applies to your merchant account or store. Using the live Management API you can check the transaction description that applies to specific payment methods.<\/p>\n\n<div id=\"tab0jGwu\">\n    <div data-component-wrapper=\"tabs\">\n        <tabs\n                        :items=\"[{&quot;title&quot;:&quot;Customer Area&quot;,&quot;content&quot;:&quot;\\n&lt;p&gt;When using your Customer Area to find out how your business appears on your shoppers&#039; bank statements, you need to have one of the following &lt;a href=\\&quot;\\\/pt\\\/account\\\/user-roles\\&quot;&gt;roles&lt;\\\/a&gt;:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;strong&gt;Merchant admin&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;Change payment methods&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;p&gt;To check the transaction description for a merchant account or store:&lt;\\\/p&gt;\\n&lt;ol&gt;\\n&lt;li&gt;Log in to your &lt;a href=\\&quot;https:\\\/\\\/ca-live.adyen.com\\\/\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot; class=\\&quot;external-link no-image\\&quot;&gt;live Customer Area&lt;\\\/a&gt;.&lt;\\\/li&gt;\\n&lt;li&gt;Go to the merchant account or store that you want to check the transaction description for.&lt;\\\/li&gt;\\n&lt;li&gt;Go to &lt;strong&gt;Settings&lt;\\\/strong&gt; &amp;gt; &lt;strong&gt;Transaction description&lt;\\\/strong&gt;.&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Under &lt;strong&gt;Show on bank statements&lt;\\\/strong&gt;, check the settings:&lt;\\\/p&gt;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Selected setting&lt;\\\/th&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Transaction descriptions include&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;A dynamic value&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The shopper statement from the payment request. Or, if the payment request does not contain a shopper statement, the DBA name shown in the box.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;A static business name&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The DBA name shown in the box.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;Static name and dynamic value&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;A combination of the DBA name shown in the box, followed by the shopper statement from the payment request (if present).&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&lt;p&gt;These settings apply to &lt;a href=\\&quot;#payment-methods\\&quot;&gt;most card payments and some other payment methods&lt;\\\/a&gt;.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:&quot;ca&quot;,&quot;oldTabId&quot;:&quot;ca-1_1&quot;,&quot;relation&quot;:&quot;ca&quot;},{&quot;title&quot;:&quot;Management API&quot;,&quot;content&quot;:&quot;\\n&lt;p&gt;To check your transaction descriptions using the Management API, you need to have one of the following &lt;a href=\\&quot;\\\/pt\\\/account\\\/user-roles\\&quot;&gt;roles&lt;\\\/a&gt;:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;strong&gt;Management API \\u2014 Payment methods read and write&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;Management API \\u2014 Payment methods read&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;p&gt;To find out how your business appears on your shopper&#039;s bank statements:&lt;\\\/p&gt;\\n&lt;ol&gt;\\n&lt;li&gt;Make a GET  &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/Management\\\/latest\\\/get\\\/merchants\\\/(merchantId)\\\/paymentMethodSettings\\&quot; class=\\&quot;codeLabel  external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/merchants\\\/{merchantId}\\\/paymentMethodSettings&lt;\\\/a&gt; request to the live endpoint.&lt;\\\/li&gt;\\n&lt;li&gt;In the response, find the relevant payment method and inspect the &lt;code&gt;transactionDescription&lt;\\\/code&gt; object of that payment method.\\n&lt;ul&gt;\\n&lt;li&gt;&lt;code&gt;doingBusinessAsName&lt;\\\/code&gt;: the DBA name defined for this payment method.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;code&gt;type&lt;\\\/code&gt;: determines what information is added to the transaction description. The possible values are:\\n&lt;ul&gt;\\n&lt;li&gt;&lt;strong&gt;fixed&lt;\\\/strong&gt;: the &lt;code&gt;doingBusinessAsName&lt;\\\/code&gt; value.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;dynamic&lt;\\\/strong&gt;: the shopper statement from the payment request, or the &lt;code&gt;doingBusinessAsName&lt;\\\/code&gt; value if the payment request does not contain a shopper statement.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;append&lt;\\\/strong&gt;: a combination of the &lt;code&gt;doingBusinessAsName&lt;\\\/code&gt; value, followed by the shopper statement from the payment request (if present).&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&quot;,&quot;altTitle&quot;:&quot;api&quot;,&quot;oldTabId&quot;:&quot;api-1_2&quot;,&quot;relation&quot;:&quot;api&quot;}]\"\n            :should-update-when-url-changes='true'>\n        <\/tabs>\n    <\/div>\n<\/div>\n\n<h2 id=\"customize-the-transaction-description\">Customize the transaction description<\/h2>\n<p>When you configure the transaction description, take into account that the description can be a maximum of <strong>22 characters<\/strong> including spaces for the DBA name, dynamic value, or combination. Anything exceeding that is truncated and left out. What remains is then sent along with the city and country\/region.<\/p>\n<p>Allowed characters:<\/p>\n<ul>\n<li>Lowercase and uppercase characters: <code>[a-z]<\/code> <code>[A-Z]<\/code><\/li>\n<li>Numbers: <code>[0-9]<\/code><\/li>\n<li>Special characters: <code>.<\/code>, <code>,<\/code>, <code>'<\/code>, <code>_<\/code>, <code>-<\/code>, <code>?<\/code>, <code>+<\/code>, <code>*<\/code>, and space.<\/li>\n<\/ul>\n\n<div id=\"tab2FdmI\">\n    <div data-component-wrapper=\"tabs\">\n        <tabs\n                        :items=\"[{&quot;title&quot;:&quot;Customer Area&quot;,&quot;content&quot;:&quot;\\n&lt;div class=\\&quot;sc-notice info\\&quot;&gt;&lt;div&gt;\\n&lt;p&gt;When you change the transaction description in the &lt;a href=\\&quot;https:\\\/\\\/ca-live.adyen.com\\\/\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot; class=\\&quot;external-link no-image\\&quot;&gt;live Customer Area&lt;\\\/a&gt;, the changes affect only your current payment methods. If you add a new payment method, its transaction description defaults to your DBA name. We recommend you reconfigure your transaction description after adding a new payment method to ensure your transaction description is consistent across all payment methods.&lt;\\\/p&gt;\\n&lt;\\\/div&gt;&lt;\\\/div&gt;\\n&lt;p&gt;There are two methods to change the transaction description in your live Customer Area:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;\\n&lt;p&gt;Define a &lt;a href=\\&quot;#single-in-ca\\&quot;&gt;single transaction description&lt;\\\/a&gt; and select one or more merchant accounts or stores to apply the description to. In this way you can apply the same description to many accounts or stores in one go.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Upload a CSV file with &lt;a href=\\&quot;#multiple-in-ca\\&quot;&gt;various transaction descriptions&lt;\\\/a&gt; for various merchant accounts and stores. In this way you can supply all the different descriptions for all your merchant accounts and stores in one go. The maximum file size of the CSV file is 10 MB.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;p&gt;For these tasks, you need to have one of the following &lt;a href=\\&quot;\\\/pt\\\/account\\\/user-roles\\&quot;&gt;roles&lt;\\\/a&gt;:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;strong&gt;Merchant admin&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;Change payment methods&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;h3 id=\\&quot;single-in-ca\\&quot;&gt;Define a single description&lt;\\\/h3&gt;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;Log in to your &lt;a href=\\&quot;https:\\\/\\\/ca-live.adyen.com\\\/\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot; class=\\&quot;external-link no-image\\&quot;&gt;live Customer Area&lt;\\\/a&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Go to &lt;strong&gt;Settings&lt;\\\/strong&gt; &amp;gt; &lt;strong&gt;Transaction description&lt;\\\/strong&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Select the tab &lt;strong&gt;Set a single description&lt;\\\/strong&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Select the merchant accounts or the stores that you want the transaction description to apply to.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Configure the transaction description you want.&lt;\\\/p&gt;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Effect&lt;\\\/th&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Action&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Add DBA name&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Select &lt;strong&gt;A static business name&lt;\\\/strong&gt;, and in the box type your DBA name.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Add shopper statement&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Select &lt;strong&gt;A dynamic value&lt;\\\/strong&gt;, and in the box type your DBA name.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Combination of DBA name and shopper statement&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Select &lt;strong&gt;Static name and dynamic value&lt;\\\/strong&gt;, and in the box type your DBA name.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Select &lt;strong&gt;Save&lt;\\\/strong&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&lt;p&gt;Your changes are applied immediately to all transactions processed through the selected merchant accounts or stores.&lt;\\\/p&gt;\\n&lt;h3 id=\\&quot;multiple-in-ca\\&quot;&gt;Define multiple different descriptions&lt;\\\/h3&gt;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;Log in to your &lt;a href=\\&quot;https:\\\/\\\/ca-live.adyen.com\\\/\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot; class=\\&quot;external-link no-image\\&quot;&gt;live Customer Area&lt;\\\/a&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Go to &lt;strong&gt;Settings&lt;\\\/strong&gt; &amp;gt; &lt;strong&gt;Transaction description&lt;\\\/strong&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Select the tab &lt;strong&gt;Set multiple descriptions&lt;\\\/strong&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;To download the template CSV file, in the text select the words \\&quot;&lt;strong&gt;this template&lt;\\\/strong&gt;\\&quot;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Fill out the CSV file as described below, and save it under a new name.&lt;\\\/p&gt;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Column&lt;\\\/th&gt;\\n&lt;th&gt;Explanation&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;merchantAccountCode&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td&gt;The unique ID of the merchant account.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;storeCode&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td&gt;The unique store ID, if the transaction description should apply to a specific store under the specified merchant account. Leave empty if not applicable.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;type&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td&gt;One of the following values, to indicate what to add to the transaction description: &lt;ul&gt;&lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;fixed&lt;\\\/strong&gt;: adds the DBA name.&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;dynamic&lt;\\\/strong&gt;: adds the shopper statement from the payment request.&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;append&lt;\\\/strong&gt;: adds the DBA name followed by the shopper statement from the payment request (if present).&lt;\\\/li&gt;&lt;\\\/ul&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;doingBusinessAsName&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;td&gt;Your DBA name.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;In the Customer Area, click on the upload box and upload your saved CSV file.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Select &lt;strong&gt;Save&lt;\\\/strong&gt;.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&lt;p&gt;Your changes will be applied within one calendar day.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:&quot;ca&quot;,&quot;oldTabId&quot;:&quot;ca-2_1&quot;,&quot;relation&quot;:&quot;ca&quot;},{&quot;title&quot;:&quot;Management API&quot;,&quot;content&quot;:&quot;\\n&lt;p&gt;To configure the transaction description for a specific payment method using the Management API, you need to have the following &lt;a href=\\&quot;\\\/pt\\\/account\\\/user-roles\\&quot;&gt;role&lt;\\\/a&gt;:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;strong&gt;Management API \\u2014 Payment methods read and write&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;p&gt;You can configure the transaction description while requesting a payment method, or later, when updating a payment method.&lt;\\\/p&gt;\\n&lt;p&gt;To configure the transaction description:&lt;\\\/p&gt;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;If you are requesting a new payment method, make a POST  &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/Management\\\/latest\\\/post\\\/merchants\\\/(merchantId)\\\/paymentMethodSettings\\&quot; class=\\&quot;codeLabel  external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/merchants\\\/{merchantId}\\\/paymentMethodSettings&lt;\\\/a&gt; request to the live endpoint.&lt;br \\\/&gt;\\nOr if you are updating an existing payment method, make a PATCH  &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/Management\\\/latest\\\/patch\\\/merchants\\\/(merchantId)\\\/paymentMethodSettings\\\/(paymentMethodId)\\&quot; class=\\&quot;codeLabel  external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/merchants\\\/{merchantId}\\\/paymentMethodSettings\\\/{paymentMethodId}&lt;\\\/a&gt; request to the live endpoint.&lt;\\\/p&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;In the request body, for the relevant payment method specify a &lt;code&gt;transactionDescription&lt;\\\/code&gt; object containing:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;code&gt;doingBusinessAsName&lt;\\\/code&gt;: the DBA name for this payment method.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;code&gt;type&lt;\\\/code&gt;: determines what the transaction description consists of. The possible values are:\\n&lt;ul&gt;\\n&lt;li&gt;&lt;strong&gt;fixed&lt;\\\/strong&gt;: transaction descriptions consist of the &lt;code&gt;doingBusinessAsName&lt;\\\/code&gt; value.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;dynamic&lt;\\\/strong&gt;: transaction descriptions consist of the shopper statement from the payment request, or of the &lt;code&gt;doingBusinessAsName&lt;\\\/code&gt; value if the payment request doesn&#039;t contain a shopper statement.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;strong&gt;append&lt;\\\/strong&gt;: transaction descriptions consist of a combination of the &lt;code&gt;doingBusinessAsName&lt;\\\/code&gt; value, followed by the shopper statement from the payment request (if present).&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;\\\/li&gt;\\n&lt;\\\/ol&gt;\\n&lt;p&gt;Your changes are applied immediately to all the transactions processed with that payment method on your merchant account.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:&quot;api&quot;,&quot;oldTabId&quot;:&quot;api-2_2&quot;,&quot;relation&quot;:&quot;api&quot;}]\"\n            :should-update-when-url-changes='true'>\n        <\/tabs>\n    <\/div>\n<\/div>\n\n<h2 id=\"shopper-statement\">Specify a shopper statement<\/h2>\n<p>If you want your transaction descriptions to contain a dynamic shopper statement, it is not enough to configure the dynamic value option or the combination option as described under <a href=\"#customize-the-transaction-description\">Customize the transaction description<\/a>. You also need to add a <code>shopperStatement<\/code> parameter to each payment request.<\/p>\n<ul>\n<li>For ecommerce transactions, add a <code>shopperStatement<\/code> parameter to your  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/sessions\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/sessions<\/a> or  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request.<\/li>\n<li>For point-of-sale transactions, pass the <code>shopperStatement<\/code> inside the <a href=\"\/pt\/point-of-sale\/add-data\">\n  <code>SaleToAcquirerData<\/code>\n<\/a> parameter of your Terminal API request.<\/li>\n<\/ul>\n<h3>(Optional) Add a localized transaction description<\/h3>\n<p>If you are in Japan, go to the <a href=\"#japanese-characters\">Japan-specific section<\/a> for instructions.<\/p>\n<p>If you are active in a local market that uses a different character set, you can add a localized shopper statement. This is supported for ecommerce transactions using the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> endpoint.<\/p>\n<p>Do the following:<\/p>\n<ul>\n<li>Configure the dynamic value option or the combination option as described under <a href=\"#customize-the-transaction-description\">Customize the transaction description<\/a>.<\/li>\n<li>In your API request, include both the <code>shopperStatement<\/code> parameter and the <code>localizedShopperStatement<\/code> parameter.<br \/>\nIf you do not include a <code>localizedShopperStatement<\/code> or leave it empty, <code>shopperStatement<\/code> is used.<br \/>\nFor cross-border transactions, <code>shopperStatement<\/code> is used.<\/li>\n<\/ul>\n<h2 id=\"japan\">Localized shopper statements in Japan<\/h2>\n<p>If you do business in Japan, we support the following character sets, in combination with the <a href=\"#customize-the-transaction-description\">other allowed values for transaction descriptions<\/a>:<\/p>\n<ul>\n<li>ja-Hani (Kanji)<\/li>\n<li>ja-Kana (Katakana)<\/li>\n<\/ul>\n<p>You have various options to set a transaction description in Japanese characters:<\/p>\n<ul>\n<li>\n<p>For in-person payments, when you create a Japanese store using the Management API, you must provide Kanji and Katakana shopper statements. These statements will then be used for all in-person payments processed for that store. See <a href=\"\/pt\/point-of-sale\/design-your-integration\/determine-account-structure\/automate-store-management?tab=create_a_store_-_japan_1_2\">Create a store - Japan<\/a>.<\/p>\n<\/li>\n<li>\n<p>For online payments, you can set what appears in the shopper statement in the following ways:<\/p>\n<ul>\n<li>Contact our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a> with the Kanji and Katakana values that you want to set for your account.<\/li>\n<li><a href=\"#japanese-characters\">Add shopper statements in Japanese characters to your <code>\/payments<\/code> request<\/a>.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3 id=\"japanese-characters\">Japanese shopper statement in online payments request<\/h3>\n<p>In the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request, include the <code>localizedShopperStatement<\/code> parameter. Including this parameter overrides any values that are set for your account.<\/p>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example of localized shopper statement with Kanji and Katakana values'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n  \\\"localizedShopperStatement\\\": {\\n    \\\"ja-Hani\\\": \\\"\\u30a2\\u30c7\\u30a3\\u30a8\\u30f3\\u682a\\u5f0f\\u4f1a\\u793e\\\",\\n    \\\"ja-Kana\\\": \\\"\\uff71\\uff83\\uff9e\\uff68\\uff74\\uff9d\\uff7c\\uff9e\\uff6c\\uff8a\\uff9f\\uff9d\\\"\\n  }\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h3>Character width<\/h3>\n<p>The width of the characters that show up on the shopper's bank statement depends on the card brand and character set:<\/p>\n<table>\n<thead>\n<tr>\n<th>Brand<\/th>\n<th>Kanji characters<\/th>\n<th>Katakana characters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Visa<\/td>\n<td>Full-width<\/td>\n<td>Half-width<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>Full-width<\/td>\n<td>Half-width<\/td>\n<\/tr>\n<tr>\n<td>JCB <br> Includes Diners and Discover, which process through JCB.<\/td>\n<td>Full-width<\/td>\n<td>Full-width<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"payment-methods\">Supported payment methods<\/h2>\n<p>The following sections list the payment methods that support customized transaction descriptions. If defined in the Customer Area, the customized transaction description applies to all listed payment methods. This description can be overwritten by a transaction description that has been defined using the Management API for the individual payment method.<\/p>\n<h3>Cards<\/h3>\n<ul>\n<li>Cartes Bancaires<\/li>\n<li>China Union Pay (CUP)<\/li>\n<li>Diners<\/li>\n<li>Discover<\/li>\n<li>Eftpos<\/li>\n<li>Girocard<\/li>\n<li>Interac<\/li>\n<li>JCB<\/li>\n<li>Maestro<\/li>\n<li>Mastercard<\/li>\n<li>NYCE<\/li>\n<li>Pulse<\/li>\n<li>Star<\/li>\n<li>Visa<\/li>\n<\/ul>\n<h3>Wallets<\/h3>\n<p>Your transaction description configuration also applies if the shopper paid using a wallet payment method that contains one of the card brands above.<\/p>\n<p>For example, if a shopper pays with Apple Pay using their Visa card, the transaction description you configured in the Customer Area will be used. Or if you used the Management API to configure a specific transaction description for Visa, that description will be used.<\/p>\n<h3>Other payment methods<\/h3>\n<ul>\n<li>Bancontact (BCMC) - both card and mobile integrations<\/li>\n<li>iDEAL<\/li>\n<\/ul>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/account\/manage-payments\/\"\n                        target=\"_self\"\n                        >\n                    Manage payments\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/account\/transaction-description","articleFields":{"description":"Find out what shoppers see on their bank statement and how you can change it.","search_tags":["statement descriptor","shopper statement","billing descriptor","account statement","payment description","payment descriptor"],"feedback_component":true,"last_edit_on":"17-01-2024 16:57","filters_component":false,"page_id":"e470e27e-57af-468e-817d-d1bf1a5660a6","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/account\/transaction-description","title":"Transaction description","content":"When shoppers check their bank statements, they need to be able to easily identify the charges they see. The text that describes charges is known as a transaction &nbsp;description, statement&nbsp;descriptor, shopper&nbsp;statement, or billing&nbsp;descriptor. If shoppers do not recognize a transaction by its description:\n\nThere is a higher chance your shopper issues a chargeback.\nYou can get a fine from the relevant card scheme related to your chargeback rate.\n\nTo prevent these issues, ensure that your transaction description contains your brand or the (chain) merchant name that is most recognizable to the cardholder (as required by the card schemes), and optionally customize your transaction description.\nRequirements\nBefore you begin, take into account the following requirements, limitations, and preparations.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nAny payments integration with Adyen.\n\n\nAPI credential roles\nTo customize transaction descriptions using the Management API, make sure that you have the following role: Management API \u2014 Payment methods read and write\n\n\nCustomer Area roles\nTo customize transaction descriptions using the Customer Area, make sure that you have one of the following roles: Merchant admin Change payment methods\n\n\nLimitations\nTake into account the following: You can only customize your transaction description in the live environment. If you want to define multiple different descriptions by uploading a CSV file, note that the maximum file size is 10 MB. Not all payment methods allow customization of the transaction description. See the supported payment methods.\n\n\n\nWithout customization\nWithout customization, the transaction description consists of the Name set in your live Customer Area under Settings &gt; Account, combined with the City and the Country\/Region from your merchant account address.\nThe city and country\/region are always added to transaction descriptions, even if you customize the description.\nCustomization options\nTo help your shoppers easily identify the payments made to your business, you can customize the transaction description by adding information. You can add either of the following:\n\nA Doing Business As (DBA) name: a static value that represents your business.\nA dynamic value: the transaction-specific shopper statement that is specified in the payment request.\nA combination of your DBA name followed by the shopper statement from the payment request.\n\nIf you do business in Japan, we highly recommend that you add localized shopper statements in Japanese characters.\nDoing Business As (DBA) name\nYour DBA name is a static value that represents your business. To add your DBA name to your transaction descriptions, you need to turn on this setting, and specify the text to use.\nWe recommend that you set your DBA name to the name by which your shoppers know your business.\nDynamic values\nUsing dynamic values, you can customize the transaction description for each of your shoppers. For example, you can add the order reference number corresponding to the payment.\nTo add a dynamic, transaction-specific shopper statement to your transaction descriptions, you need to turn on this setting, and specify a shopper statement in each individual payment request.\nBe aware of the following:\n\nIf you do not turn on dynamic values, the shopper statement from the payment request will not appear in your shoppers' bank statements.\nIf you turn on dynamic values but do not send a shopper statement in the payment request, your DBA name will be used instead.\n\nCombination\nTo add both your DBA name and a transaction-specific shopper statement to your transaction descriptions, you need to turn on this setting, specify a DBA name, and specify a shopper statement in each payment request.\nWith this setting, your DBA name is used as a base for the transaction description. The shopper statement defined in the payment request is appended to this description.\nCustomer Area or Management API\nTo add information to the transaction description, you can use the live Customer Area or the live Management API.\n\n\nUsing the live Customer Area, you have two options:\n\nYou can define the same transaction description for an individual merchant account or store or for multiple accounts or stores in one go.\nOr you can upload a CSV file to define various different transaction descriptions for multiple merchant accounts and stores.\n\nIn both cases the customized transaction description is applied to transactions made using all the payment methods that support customization and that have been added to the merchant account or store.\n\n\nUsing a live Management API endpoint, you can customize the transaction description per payment method. In this way you can use different descriptions for different payment methods. Not all payment methods that are available through the Management API support customization.\n\n\nA payment method-specific customization overrules the general transaction description settings from the Customer Area.\nCheck the transaction description\nIn your live Customer Area you can check the transaction description that applies to your merchant account or store. Using the live Management API you can check the transaction description that applies to specific payment methods.\n\n\n    \n        \n        \n    \n\n\nCustomize the transaction description\nWhen you configure the transaction description, take into account that the description can be a maximum of 22 characters including spaces for the DBA name, dynamic value, or combination. Anything exceeding that is truncated and left out. What remains is then sent along with the city and country\/region.\nAllowed characters:\n\nLowercase and uppercase characters: [a-z] [A-Z]\nNumbers: [0-9]\nSpecial characters: ., ,, ', _, -, ?, +, *, and space.\n\n\n\n    \n        \n        \n    \n\n\nSpecify a shopper statement\nIf you want your transaction descriptions to contain a dynamic shopper statement, it is not enough to configure the dynamic value option or the combination option as described under Customize the transaction description. You also need to add a shopperStatement parameter to each payment request.\n\nFor ecommerce transactions, add a shopperStatement parameter to your  \/sessions or  \/payments request.\nFor point-of-sale transactions, pass the shopperStatement inside the \n  SaleToAcquirerData\n parameter of your Terminal API request.\n\n(Optional) Add a localized transaction description\nIf you are in Japan, go to the Japan-specific section for instructions.\nIf you are active in a local market that uses a different character set, you can add a localized shopper statement. This is supported for ecommerce transactions using the  \/payments endpoint.\nDo the following:\n\nConfigure the dynamic value option or the combination option as described under Customize the transaction description.\nIn your API request, include both the shopperStatement parameter and the localizedShopperStatement parameter.\nIf you do not include a localizedShopperStatement or leave it empty, shopperStatement is used.\nFor cross-border transactions, shopperStatement is used.\n\nLocalized shopper statements in Japan\nIf you do business in Japan, we support the following character sets, in combination with the other allowed values for transaction descriptions:\n\nja-Hani (Kanji)\nja-Kana (Katakana)\n\nYou have various options to set a transaction description in Japanese characters:\n\n\nFor in-person payments, when you create a Japanese store using the Management API, you must provide Kanji and Katakana shopper statements. These statements will then be used for all in-person payments processed for that store. See Create a store - Japan.\n\n\nFor online payments, you can set what appears in the shopper statement in the following ways:\n\nContact our Support Team with the Kanji and Katakana values that you want to set for your account.\nAdd shopper statements in Japanese characters to your \/payments request.\n\n\n\nJapanese shopper statement in online payments request\nIn the  \/payments request, include the localizedShopperStatement parameter. Including this parameter overrides any values that are set for your account.\n\n    \n\nCharacter width\nThe width of the characters that show up on the shopper's bank statement depends on the card brand and character set:\n\n\n\nBrand\nKanji characters\nKatakana characters\n\n\n\n\nVisa\nFull-width\nHalf-width\n\n\nMastercard\nFull-width\nHalf-width\n\n\nJCB  Includes Diners and Discover, which process through JCB.\nFull-width\nFull-width\n\n\n\nSupported payment methods\nThe following sections list the payment methods that support customized transaction descriptions. If defined in the Customer Area, the customized transaction description applies to all listed payment methods. This description can be overwritten by a transaction description that has been defined using the Management API for the individual payment method.\nCards\n\nCartes Bancaires\nChina Union Pay (CUP)\nDiners\nDiscover\nEftpos\nGirocard\nInterac\nJCB\nMaestro\nMastercard\nNYCE\nPulse\nStar\nVisa\n\nWallets\nYour transaction description configuration also applies if the shopper paid using a wallet payment method that contains one of the card brands above.\nFor example, if a shopper pays with Apple Pay using their Visa card, the transaction description you configured in the Customer Area will be used. Or if you used the Management API to configure a specific transaction description for Visa, that description will be used.\nOther payment methods\n\nBancontact (BCMC) - both card and mobile integrations\niDEAL\n\nSee also\n\n\n                    Manage payments\n                \n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Account","lvl2":"Transaction description"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/account","lvl2":"\/pt\/account\/transaction-description"},"levels":3,"category":"Account","category_color":"green","tags":["statement descriptor","shopper statement","billing descriptor","account statement","payment description","payment descriptor"]}}