Skip to content

DOC-1024 Merchant doc updates #316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ntombing
Copy link
Contributor

Merchant overview page ready for review. Still need to update the guides.

@ntombing ntombing requested a review from racene-swan May 28, 2025 13:59
Copy link

linear bot commented May 28, 2025

Copy link

netlify bot commented May 28, 2025

Deploy Preview for incomparable-tiramisu-91a96a ready!

Name Link
🔨 Latest commit 7f26e0e
🔍 Latest deploy log https://app.netlify.com/projects/incomparable-tiramisu-91a96a/deploys/683716ace9f9300008306c65
😎 Deploy Preview https://deploy-preview-316--incomparable-tiramisu-91a96a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

| `Suspended` | Status **assigned by Swan** when the merchant's use of their profile or payment method needs to be reviewed. The status can't return to `Enabled` without a review. |
| `Rejected` | Final status **assigned by Swan** when Swan decides the risk of this profile or the risk of this payment method for the associated merchant is too high, or for some other risk-related reason. |
| `Disabled` | Final status **set by you** using the `requestMerchantPaymentMethods` mutation. |

## Merchant profiles {#profiles}

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.
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be in a numbered list.

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.
If a Swan account holder wants to accept payments from customers, they must have at least one merchant profile.

Merchant profiles can be created at the same time as onboarding.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same time as an onboarding? Or simultaneously with onboarding?

If a Swan account holder wants to accept payments from customers, they must have at least one merchant profile.

Merchant profiles can be created at the same time as onboarding.
Since merchants are considered high risk, profiles should only be created for users who need merchant features.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high-risk - what do we mean by "users who need merchant features" - this is unclear since this whole section is about Merchant profiles.


Merchant profiles can be created at the same time as onboarding.
Since merchants are considered high risk, profiles should only be created for users who need merchant features.
Requesting profiles for all users may lead to unmet expectations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do we mean by this? will it be rejected? what's the user impact here?

- Projected volumes
- Logo (optional), displayed online and on mandate PDFs
- Payment frequency
- Logo (optional), in `.png` format and less than 1 mb, displayed online and on mandate PDFs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we mean 1Mb or MB?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's a mandate PDF?


A merchant profile is required of all Swan account holders wanting to accept payments from customers.
If you want to accept payments from customers, you must have at least one merchant profile.
To speed up enabling your merchant profile, complete as many information fields as possible.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rework this sentence - it's clunky.

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`.
Swan will contact the you or the user directly, based on your communication preferences.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Swan will contact you or the user directly

Copy link
Contributor

@racene-swan racene-swan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left comments directly here :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants