DOC-1461/add-that-rejection-reasons-merchant-should-not-be-displayed

docs/topics/merchants/index.mdx

@@ -117,7 +117,7 @@ Updating a merchant profile produces the following events:
 1. If Swan rejects the update request, the merchant profile remains `Enabled` by default, unless Swan decides otherwise. 
 The merchant profile status doesn't change.
 
-When a merchant payment method is requested, Swan may ask for additional information even if the merchant profile is already `Enabled`.
+When a merchant payment method is requested, Swan may need to request additional information even if the merchant profile is already `Enabled`.
 Swan will contact you or your user directly, based on your communication preferences.
 
 If you requested an update and your update status is `PendingReview`, but you need to **make another change**, submit a new update request.
@@ -143,6 +143,10 @@ A merchant profile can be rejected for the following reasons:
 | `GenericRejection` | The profile was rejected for a general reason not covered by other categories. |
 | `SuspiciousBehavior` | The profile was rejected due to alerts related to suspicious processing behavior. |
 
+:::info For Partners only
+These rejection reasons are intended for Partners and shouldn't be displayed to end users.
+If you need more details about a specific rejection, please contact Swan.
+:::
 
 ## Payment methods {#methods}
 
@@ -214,6 +218,11 @@ A merchant payment method can be rejected for the following reasons:
 | `ContractualCriteriaNotFulfilled` | The request doesn't meet the contractual criterion agreed upon with the Partner. |
 | `GenericRejection` | The request was rejected for a reason not covered by other categories. |
 
+:::info For Partners only
+These rejection reasons are intended for Partners and shouldn't be displayed to end users.
+If you need more details about a specific rejection, please contact Swan.
+:::
+
 ### Rolling reserve {#rolling-reserve}
 
 import RollingReserve from './partials/_rolling-reserve.mdx';