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

Update a merchant profile

You can request an update to a merchant profile with the API. If you use Swan's Web Banking interface, merchants can request an update through their app.

Request an update for the merchant's name, website, product type, expected monthly payment volume, expected average basket, and logo. All updates are reviewed by Swan.

Guide​

  1. Call the requestMerchantProfileUpdate mutation. You don't need consent.
  2. Include only the information you wish to update.
    • Possible fields: merchantName, productType, expectedMonthlyPaymentVolume, expectedAverageBasket.
  3. Configure the success payload to display the updated information in case you need to verify it.
  4. Add relevant payload and rejection details (not shown) to your mutation.
    • In the following example, the expectedAverageBasket, or expected average transaction, changed from €50 to €75 (line 8). Therefore, request the updated basket in the success payload (lines 12-14).

Mutation​

Open in API Explorer
mutation ProfileUpdate {
requestMerchantProfileUpdate(
input: {
merchantProfileId: "$MERCHANT_PROFILE_ID"
expectedAverageBasket: { value: "75", currency: "EUR" }
}
) {
... on RequestMerchantProfileUpdateSuccessPayload {
__typename
requestMerchantProfileUpdate {
status
expectedAverageBasket {
currency
value
}
}
}
}
}

Payload​

The payload confirms your update request to an average basket of €75 with the status PendingReview.

{
"data": {
"requestMerchantProfileUpdate": {
"__typename": "RequestMerchantProfileUpdateSuccessPayload",
"requestMerchantProfileUpdate": {
"status": "PendingReview",
"expectedAverageBasket": {
"currency": "EUR",
"value": "75"
}
}
}
}
}