sumup · matoous · Aug 2, 2026 · Aug 2, 2026
diff --git a/src/content/docs/tools/glossary/countries-and-currencies.mdx b/src/content/docs/tools/glossary/countries-and-currencies.mdx
@@ -0,0 +1,282 @@
+---
+title: Countries and Currencies
+description: Default merchant-account currencies for countries where SumUp operates.
+sidebar:
+  order: 30
+---
+
+import Callout from "@components/content/Callout";
+import SearchableTable from "@components/content/SearchableTable";
+
+A SumUp merchant account has a default currency based on the country where the
+merchant is registered. When an API request requires a currency, use the
+merchant account's `default_currency` in the format defined by
+[ISO 4217](https://www.iso.org/iso-4217-currency-codes.html).
+
+<Callout type="caution">
+  This table describes merchant-account markets and currencies, not universal
+  product availability. An API, SDK, payment method, or card reader might
+  support fewer countries or currencies. Check the relevant product guide and
+  API schema before building an integration.
+</Callout>
+
+## Supported countries and currencies
+
+The country coverage follows SumUp's current
+[list of markets](https://www.sumup.com/en-us/press/). Search by country name,
+country code, currency, or currency code.
+
+<SearchableTable
+  client:load
+  searchPlaceholder="Search countries or currencies"
+  columns={[
+    { key: "icon", label: "" },
+    { key: "country", label: "Country", nowrap: true },
+    { key: "currency", label: "Currency", nowrap: true },
+    { key: "currencyCode", label: "Code", as: "code", nowrap: true },
+  ]}
+  rows={[
+    {
+      icon: "flag_au",
+      country: "Australia (AU)",
+      currency: "Australian dollar",
+      currencyCode: "AUD",
+    },
+    {
+      icon: "flag_at",
+      country: "Austria (AT)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_be",
+      country: "Belgium (BE)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_br",
+      country: "Brazil (BR)",
+      currency: "Brazilian real",
+      currencyCode: "BRL",
+    },
+    {
+      icon: "flag_bg",
+      country: "Bulgaria (BG)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_ca",
+      country: "Canada (CA)",
+      currency: "Canadian dollar",
+      currencyCode: "CAD",
+    },
+    {
+      icon: "flag_cl",
+      country: "Chile (CL)",
+      currency: "Chilean peso",
+      currencyCode: "CLP",
+    },
+    {
+      icon: "flag_co",
+      country: "Colombia (CO)",
+      currency: "Colombian peso",
+      currencyCode: "COP",
+    },
+    {
+      icon: "flag_hr",
+      country: "Croatia (HR)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_cy",
+      country: "Cyprus (CY)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_cz",
+      country: "Czech Republic (CZ)",
+      currency: "Czech koruna",
+      currencyCode: "CZK",
+    },
+    {
+      icon: "flag_dk",
+      country: "Denmark (DK)",
+      currency: "Danish krone",
+      currencyCode: "DKK",
+    },
+    {
+      icon: "flag_ee",
+      country: "Estonia (EE)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_fi",
+      country: "Finland (FI)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_fr",
+      country: "France (FR)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_de",
+      country: "Germany (DE)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_gr",
+      country: "Greece (GR)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_hu",
+      country: "Hungary (HU)",
+      currency: "Hungarian forint",
+      currencyCode: "HUF",
+    },
+    {
+      icon: "flag_ie",
+      country: "Ireland (IE)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_it",
+      country: "Italy (IT)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_lv",
+      country: "Latvia (LV)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_lt",
+      country: "Lithuania (LT)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_lu",
+      country: "Luxembourg (LU)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_mt",
+      country: "Malta (MT)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_mx",
+      country: "Mexico (MX)",
+      currency: "Mexican peso",
+      currencyCode: "MXN",
+    },
+    {
+      icon: "flag_nl",
+      country: "Netherlands (NL)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_no",
+      country: "Norway (NO)",
+      currency: "Norwegian krone",
+      currencyCode: "NOK",
+    },
+    {
+      icon: "flag_pe",
+      country: "Peru (PE)",
+      currency: "Peruvian sol",
+      currencyCode: "PEN",
+    },
+    {
+      icon: "flag_pl",
+      country: "Poland (PL)",
+      currency: "Polish zloty",
+      currencyCode: "PLN",
+    },
+    {
+      icon: "flag_pt",
+      country: "Portugal (PT)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_ro",
+      country: "Romania (RO)",
+      currency: "Romanian leu",
+      currencyCode: "RON",
+    },
+    {
+      icon: "flag_sk",
+      country: "Slovakia (SK)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_si",
+      country: "Slovenia (SI)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_es",
+      country: "Spain (ES)",
+      currency: "Euro",
+      currencyCode: "EUR",
+    },
+    {
+      icon: "flag_se",
+      country: "Sweden (SE)",
+      currency: "Swedish krona",
+      currencyCode: "SEK",
+    },
+    {
+      icon: "flag_ch",
+      country: "Switzerland (CH)",
+      currency: "Swiss franc",
+      currencyCode: "CHF",
+    },
+    {
+      icon: "flag_gb",
+      country: "United Kingdom (GB)",
+      currency: "Pound sterling",
+      currencyCode: "GBP",
+    },
+    {
+      icon: "flag_us",
+      country: "United States (US)",
+      currency: "US dollar",
+      currencyCode: "USD",
+    },
+  ]}
+  tableLayout="auto"
+/>
+
+## Use the correct currency in an integration
+
+1. Retrieve the merchant account and read its `default_currency` from the
+   [Retrieve a Merchant endpoint](/api/merchants/get/).
+2. Send that value in payment requests that require a currency, such as
+   [Create a Checkout](/api/checkouts/create/).
+3. Confirm that the value is accepted by the endpoint's current API schema and
+   that the product is available for the merchant's country.
+
+For online payments, also use the payment methods returned for the checkout
+rather than assuming that every method is available for a country or currency.
+See [Payment methods](/online-payments/payment-methods/).
diff --git a/src/content/help/affiliate-key.mdx b/src/content/help/affiliate-key.mdx
@@ -1,5 +1,7 @@
 ---
-title: How do I retrieve an affiliate key?
+title: How do I create an Affiliate Key?
 ---
 
-You need to create your key by logging in to the Developer page of the [SumUp Dashboard](https://me.sumup.com/developers). Details on its implementation can be found in our [step-by-step guide](/terminal-payments).
+Open [Developer Settings](https://me.sumup.com/settings/developer) in the SumUp Dashboard, then go to **For Developers** > **Toolkit** > **Affiliate Keys**. Enter an application identifier that matches your app ID or bundle ID, then select **Add**.
+
+An Affiliate Key identifies your card-present integration; it does not authorize API requests. Follow the [Affiliate Keys guide](/tools/authorization/affiliate-keys/) for creation steps, credential requirements, and request examples.
diff --git a/src/content/help/oauth-credentials.mdx b/src/content/help/oauth-credentials.mdx
@@ -2,4 +2,6 @@
 title: How do I set up OAuth credentials?
 ---
 
-You can create credentials by logging in on the [SumUp Developer](https://me.sumup.com/developers) page and navigating to the "Create Client Credentials" section. Detailed information on how to authenticate further can be found in our [step-by-step guide](/tools/authorization/oauth/#steps) or in this [video](https://www.youtube.com/watch?v=0ALwF_tm8wII).
+Open the [OAuth apps page](https://me.sumup.com/settings/oauth2-applications) in the SumUp Dashboard and select **Create application**. After registering the application, open it and select **Create client secret**.
+
+Follow the [OAuth application registration guide](/tools/authorization/oauth/#register-an-oauth-application) for redirect URI, scope, and credential-storage requirements.
diff --git a/src/content/help/support-libraries.mdx b/src/content/help/support-libraries.mdx
@@ -9,13 +9,13 @@ SumUp maintains multiple SDKs and APIs to simplify your integration work across
 - [JavaScript / TypeScript, Go, Python, Java, PHP, .NET, and Rust SDK guides](/tools/sdks/) cover server-to-SumUp API calls for online payments and remote Solo reader management through the Cloud API.
 - Use these when you’re building checkout pages, recurring billing, or card-present integrations from a backend or platform that can make API requests.
 
-## Card-present SDKs
+## Card-Present Integrations
 
 - [Android SDK](https://github.com/sumup/sumup-android-sdk) and [iOS SDK](https://github.com/sumup/sumup-ios-sdk) let you embed our reader experience inside native apps.
-- [Android URL scheme](https://github.com/sumup/sumup-android-url-scheme) and [iOS URL scheme](https://github.com/sumup/sumup-ios-url-scheme) are lightweight options for launching the SumUp app to take a payment.
-- See the [terminal payments docs](/terminal-payments/) for installation and certification requirements.
+- [Payment Switch](/terminal-payments/payment-switch/) provides Android and iOS URL schemes for launching the SumUp app. It is a legacy fallback for integrations that cannot use the native SDKs or Cloud API.
+- See the [terminal payments comparison](/terminal-payments/#choose-your-integration) before choosing an integration, then follow its canonical implementation guide.
 
-## Cloud API for Solo readers
+## Cloud API for Supported Readers
 
-- The [Cloud API](/terminal-payments/cloud-api/) triggers card-present transactions on Solo readers from any backend or platform that can make HTTPS calls.
+- The [Cloud API](/terminal-payments/cloud-api/) triggers card-present transactions on supported readers from any backend or platform that can make HTTPS calls.
 - Use it when your POS runs on web, desktop, or another environment that can’t embed the native Android/iOS SDKs but still needs in-person payments.
diff --git a/src/content/help/supported-currencies.mdx b/src/content/help/supported-currencies.mdx
@@ -1,19 +1,9 @@
 ---
-title: Which currencies are supported by SumUp?
+title: Which currency should I use for a payment?
 ---
 
-We provide support coverage on three continents and in the following currencies:
+Use the default currency of the merchant account receiving the payment. The currency in a checkout or reader-payment request must match that merchant account; it is not a per-transaction settlement-currency choice.
 
-- EUR
-- GBP
-- USD
-- BRL
-- CLP
-- PLN
-- CHF
-- SEK
-- CZK
-- NOK
-- DKK
-- HUF
-- BGN
+Currency availability depends on the merchant's registered country and the product or payment method being used. For online payments, use a value accepted by the [`currency` field in Create a Checkout](/api/checkouts/create/) and check [payment-method availability](/online-payments/payment-methods/) for the merchant and checkout. For in-person payments, use the merchant account currency and confirm that the selected reader and integration are available in that market.
+
+For a country-by-country reference, see [Countries and Currencies](/tools/glossary/countries-and-currencies/). When building a payment request, do not derive the value from that table. Read the merchant account's `default_currency` through the [Retrieve a Merchant endpoint](/api/merchants/get/) or from the SumUp Dashboard, and use that value.
diff --git a/src/content/help/supported-os.mdx b/src/content/help/supported-os.mdx
@@ -1,5 +1,11 @@
 ---
-title: Which operating systems are supported by SumUp card readers?
+title: Which operating systems support SumUp in-person integrations?
 ---
 
-The SumUp card readers support iOS & Android.
+Platform support depends on the integration you choose:
+
+- [Cloud API](/terminal-payments/cloud-api/) works with web, desktop, and other server-capable platforms that can make HTTPS requests. The payment is completed on a supported reader.
+- [Terminal SDKs](/terminal-payments/sdks/) are available for native Android and iOS applications.
+- [Payment Switch](/terminal-payments/payment-switch/) supports Android and iOS app handoff as a legacy fallback.
+
+Reader compatibility and market availability also vary. Use the [in-person payments comparison](/terminal-payments/#choose-your-integration) and [reader compatibility table](/terminal-payments/#reader-compatibility) before choosing a platform and reader.
diff --git a/src/content/help/terminal-standalone-setup.mdx b/src/content/help/terminal-standalone-setup.mdx
@@ -2,4 +2,6 @@
 title: Do SumUp card readers work in a standalone setup?
 ---
 
-Our devices are designed to follow a payment flow that doesn’t allow them to operate unattended.
+Some do. [Solo](/terminal-payments/readers/solo/) has its own touchscreen and connectivity, so merchants can take payments without a paired phone or tablet. Other readers, such as [Solo Lite](/terminal-payments/readers/solo-lite/), require a compatible companion device.
+
+For a web-based, desktop, kiosk, or server-driven integration, use the [Cloud API](/terminal-payments/cloud-api/) with a supported reader. If by "standalone" you mean an unattended or self-service deployment, confirm the requirements for your reader, market, and commercial setup with SumUp before implementation; standalone operation does not by itself establish suitability for unattended use.
diff --git a/src/content/help/web-app-terminal-communication.mdx b/src/content/help/web-app-terminal-communication.mdx
@@ -2,4 +2,6 @@
 title: Can my web app communicate with SumUp devices?
 ---
 
-Yes. For web applications running on mobile devices where the SumUp app is installed, you can call the SumUp app via URL. Read more on this preferred merchant approach in our [API Payment Switch](/terminal-payments/payment-switch/) guide.
+Yes. For a web-based or server-driven point of sale, use the [Cloud API](/terminal-payments/cloud-api/). Your backend makes authenticated HTTPS requests to start a payment on a supported reader, so the integration can run on any server-capable platform. Keep secret API keys out of browser code.
+
+If a mobile web application must hand off the payment to the installed SumUp app, [Payment Switch](/terminal-payments/payment-switch/) remains available as a legacy fallback. It is not the preferred path for new web integrations.