Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Skip to main content

Request a merchant profile

Before your merchant can use Swan to accept payments from customers, request a merchant profile with the API.

All new merchant profiles are reviewed by Swan. Swan might contact you for more information before accepting or rejecting the merchant profile.

Prerequisites
  • The merchant's account holder type is Company.
  • You have a project access token, or, if you're an account member, a user access token with CanManageAccountMembership membership permission.

Guide​

  1. Call the requestMerchantProfile mutation.
  2. Include all mandatory information: accountId, merchantName, productType, expectedMonthlyPaymentVolume, and expectedAverageBasket.
  3. Add relevant payload and rejection details to your mutation.
  4. (Optional) Use merchantLogo to include a logo for your merchant. The image must be converted to a base64 encoded string.
  5. The new merchant is created with the status PendingReview.
  6. Swan reviews the new merchant profile and updates the status.
tip

Provide your customerRegion, paymentFrequency, and at least one socialNetwork or merchantWebsite to speed up merchant profile enablement.

Mutation​

Open in API Explorer
mutation MerchantProfile {
requestMerchantProfile(
input: {
accountId: "$YOUR_ACCOUNT_ID"
merchantName: "Merchant Company Name"
productType: Goods
expectedMonthlyPaymentVolume: {
value: "3000"
currency: "EUR"
}
expectedAverageBasket: {
value: "50"
currency: "EUR"
}
}
) {
... on RequestMerchantProfileSuccessPayload {
__typename
merchantProfile {
accountId
id
statusInfo {
status
... on EnabledMerchantProfileStatusInfo {
__typename
enabledAt
status
}
}
productType
}
}
... on ForbiddenRejection {
__typename
message
}
... on AccountNotFoundRejection {
id
message
}
... on InternalErrorRejection {
__typename
message
}
}
}

Payload​

The payload confirms your new merchant profile with the status PendingReview.

{
"data": {
"requestMerchantProfile": {
"__typename": "RequestMerchantProfileSuccessPayload",
"merchantProfile": {
"accountId": "$YOUR_ACCOUNT_ID",
"id": "$YOUR_MERCHANT_PROFILE_ID",
"statusInfo": {
"status": "PendingReview"
},
"productType": "Goods"
}
}
}
}