You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/topics/merchants/index.mdx
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,23 +71,27 @@ flowchart LR
71
71
72
72
## Merchant profiles {#profiles}
73
73
74
-
A **merchant profile** is a collection of business, risk, and support information that fulfills two primary requirements: **approve the account holder** as a merchant, and **facilitate accepting payments** with Swan.
74
+
A **merchant profile** is a collection of business, risk, and support information that fulfills two primary requirements:
75
+
76
+
1.**Approve the account holder** as a merchant.
77
+
1.**Facilitate accepting payments** with Swan.
78
+
75
79
If a Swan account holder wants to accept payments from customers, they must have at least one merchant profile.
76
80
77
-
Users can create merchant profiles during onboarding, but only if you've requested the feature for them.
81
+
Your users can create merchant profiles during onboarding, but only if you've requested the feature for them.
78
82
Since merchants are considered high risk, merchant profiles should only be requested for users who qualify and will accept payments.
79
83
Requesting merchant profiles for users that don't qualify may create false expectations about available features.
80
84
81
-
The merchant profile contains the following information:
85
+
A merchant profile contains the following information:
82
86
83
87
1. Business details
84
-
2. Description of the business activity
85
-
3. Link to the merchant's website or social network
86
-
4. Projected volumes
87
-
5. Payment frequency
88
-
6. Logo (optional), in `.png` format and less than 1 MB. It's shown online and on the PDF of the payment mandate.
89
-
7. Accent color
90
-
8. Customer region
88
+
1. Description of the business activity
89
+
1. Link to the merchant's website or social network
90
+
1. Projected volumes
91
+
1. Payment frequency
92
+
1. Logo (optional), in `.png` format and less than 1 MB. It's shown online and on the PDF of the payment mandate.
93
+
1. Accent color
94
+
1. Customer region
91
95
92
96
Complete as many information fields as possible to decrease the turnaround time for enabling the merchant profile.
93
97
@@ -108,7 +112,7 @@ Updating a merchant profile produces the following events:
108
112
The merchant profile status doesn't change.
109
113
110
114
When a merchant payment method is requested, Swan may ask for additional information even if the merchant profile is already `Enabled`.
111
-
Swan will contact you or the user directly, based on your communication preferences.
115
+
Swan will contact you or your user directly, based on your communication preferences.
112
116
113
117
If you requested an update and your update status is `PendingReview`, but you need to **make another change**, submit a new update request.
114
118
Swan reviews both requests, but only the most recent is made public.
0 commit comments