diff --git a/AGENTS.md b/AGENTS.md
index 131bc421..dc8687b2 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -4,6 +4,10 @@
 
 The portal uses Astro with the Starlight theme. Application source sits in `src/`, with `pages/` for route entry points, `content/` for MDX docs, `components/` for reusable UI (React, Astro, and Circuit UI), and `utils/`/`lib/` for shared logic. Assets live in `src/assets` and `public/`. Build outputs go to `dist/`. Configuration resides in `astro.config.ts`, `ec.config.mjs`, and `wrangler.jsonc`; adjust them when adding new content types or deployment targets. API documentation is based on `openapi.yaml`, this file is synchronized from outside this repository, do not edit it.
 
+## Content
+
+Content (`content/`) of the developer portal uses United States English spelling and grammar. The articles shall be clear and concise and refer to external documentation for established standards and RFCs. We don't use emojis.
+
 ## Build, Test, and Development Commands
 
 - `npm run dev` — watch mode with Hot Module Reloading; use when authoring docs or components.
diff --git a/public/_redirects b/public/_redirects
index 48186316..3cdd4ec3 100644
--- a/public/_redirects
+++ b/public/_redirects
@@ -10,9 +10,9 @@
 /online-payments/tools/hosted-checkout                                      /online-payments/checkouts/hosted-checkout/
 /online-payments/introduction/webhooks                                      /online-payments/webhooks/
 /online-payments/introduction/response-handling                             /online-payments/guides/response-handling/
-/online-payments/introduction/register-app                                  /tools/authorization/register-app
+/online-payments/introduction/register-app                                  /tools/authorization/oauth/
 /online-payments/introduction/get-started                                   /online-payments/
-/online-payments/introduction/authorization                                 /tools/authorization/authorization/
+/online-payments/introduction/authorization                                 /tools/authorization/
 /online-payments/introduction/3ds                                           /online-payments/3ds/
 /online-payments/apm/introduction                                           /online-payments/apm
 /extdev                                                                     /quickstart
@@ -23,7 +23,7 @@
 /docs/sumup-woocommerce-plugin                                              /online-payments/plugins/woocommerce
 /docs/sumup-prestashop-plugin                                               /online-payments/plugins/prestashop
 /docs/single-payment                                                        /online-payments/guides/single-payment
-/docs/register-app                                                          /tools/authorization/register-app
+/docs/register-app                                                          /tools/authorization/oauth/
 /docs/refund                                                                /online-payments/guides/refund
 /docs/recurring-payments                                                    /online-payments/guides/recurring-payments
 /docs/php-sdk                                                               /online-payments/sdks/php-sdk
diff --git a/src/content/docs/online-payments/checkouts/card-widget.mdx b/src/content/docs/online-payments/checkouts/card-widget.mdx
index cbc16527..638cff7f 100644
--- a/src/content/docs/online-payments/checkouts/card-widget.mdx
+++ b/src/content/docs/online-payments/checkouts/card-widget.mdx
@@ -19,7 +19,7 @@ A secure HTTPS connection is used to submit the payment information. To ensure a
 
 Payment Widget is available to all SumUp merchants and getting started with it is really easy!
 
-The only requirement to use Payment Widget is the ability to create online checkouts [using SumUp checkout API](/api/checkouts/create). SumUp API requires authorization with an API Key or Access Token - see the [Authorization Guide](/tools/authorization/authorization/) for details.
+The only requirement to use Payment Widget is the ability to create online checkouts [using SumUp checkout API](/api/checkouts/create). SumUp API requires authorization with an API Key or Access Token - see the [Authorization guide](/tools/authorization/) for details.
 
 ## Compliance
 
diff --git a/src/content/docs/online-payments/checkouts/hosted-checkout.mdx b/src/content/docs/online-payments/checkouts/hosted-checkout.mdx
index ca7b7ae6..ac93a54d 100644
--- a/src/content/docs/online-payments/checkouts/hosted-checkout.mdx
+++ b/src/content/docs/online-payments/checkouts/hosted-checkout.mdx
@@ -20,7 +20,7 @@ All SumUp payment methods are available in Hosted Checkout, according to availab
 
 Hosted Checkouts is available to all SumUp merchants and getting started with it is really easy!
 
-The only requirement to access Hosted Checkout is the ability to create online checkouts [using SumUp checkout API](/api/checkouts/create), which returns the hosted checkout URL. SumUp API requires authorization with an API Key or Access Token - see the [Authorization Guide](/tools/authorization/authorization/) for details.
+The only requirement to access Hosted Checkout is the ability to create online checkouts [using SumUp checkout API](/api/checkouts/create), which returns the hosted checkout URL. SumUp API requires authorization with an API key or access token—see the [Authorization guide](/tools/authorization/) for details.
 
 ## Accessing Hosted Checkout
 
diff --git a/src/content/docs/online-payments/guides/refund.mdx b/src/content/docs/online-payments/guides/refund.mdx
index 5f2b9b0b..42a5685a 100644
--- a/src/content/docs/online-payments/guides/refund.mdx
+++ b/src/content/docs/online-payments/guides/refund.mdx
@@ -24,13 +24,13 @@ Here are the things that you need in order to complete the steps in this guide:
 
 - You have a merchant account with [SumUp](https://me.sumup.com/login) and have already filled in your [account details](https://me.sumup.com/account).
   - For a **test account** reach out to our support team through this [contact form](/contact).
-- You have [registered your client application](/tools/authorization/register-app/) with SumUp.
-- You have a valid access token obtained via the [Authorization code flow](/tools/authorization/authorization/#authorization-code-flow).
+- You have [registered your client application](/tools/authorization/oauth/#register-oauth-application) with SumUp.
+- You have a valid access token obtained via the [Authorization code flow](/tools/authorization/oauth/#authorization-code-flow).
 - You have processed successfully a payment checkout and you need to refund the transaction.
 
 <Aside type="note">
 
-Transactions are associated with active merchant user accounts. As a result, you _cannot_ use an access token obtained via the [Client credentials flow](/tools/authorization/authorization/#client-credentials-flow) to complete the steps in this guide.
+Transactions are associated with active merchant user accounts. As a result, you _cannot_ use an access token obtained via the [Client credentials flow](/tools/authorization/oauth/#client-credentials-flow) to complete the steps in this guide.
 
 </Aside>
 
diff --git a/src/content/docs/online-payments/guides/single-payment.mdx b/src/content/docs/online-payments/guides/single-payment.mdx
index 840b3378..62b5f2b6 100644
--- a/src/content/docs/online-payments/guides/single-payment.mdx
+++ b/src/content/docs/online-payments/guides/single-payment.mdx
@@ -23,12 +23,12 @@ Here are the things that you need in order to complete the steps in this guide:
 
 - You have a merchant account with [SumUp](https://me.sumup.com/login) and have already filled in your [account details](https://me.sumup.com/account).
   - For a **test account** reach out to our support team through this [contact form](/contact).
-- You have [registered your client application](/tools/authorization/register-app/) with SumUp.
-- You have a valid access token obtained via one of the supported OAuth2 authorization flow, the [Authorization code flow](/tools/authorization/authorization/#authorization-code-flow) or [Client credentials flow](/tools/authorization/authorization/#client-credentials-flow).
+- You have [registered your client application](/tools/authorization/oauth/#register-oauth-application) with SumUp.
+- You have a valid access token obtained via one of the supported OAuth2 authorization flow, the [Authorization code flow](/tools/authorization/oauth/#authorization-code-flow) or [Client credentials flow](/tools/authorization/oauth/#client-credentials-flow).
 
 <Aside type="note">
 
-You can create and complete a payment checkout for any valid SumUp merchant user's account. As a result, you _can_ use an access token obtained either via the [Client credentials flow](/tools/authorization/authorization/#client-credentials-flow) or via the [Authorization code flow](/tools/authorization/authorization/#authorization-code-flow).
+You can create and complete a payment checkout for any valid SumUp merchant user's account. As a result, you _can_ use an access token obtained either via the [Client credentials flow](/tools/authorization/oauth/#client-credentials-flow) or via the [Authorization code flow](/tools/authorization/oauth/#authorization-code-flow).
 
 </Aside>
 
diff --git a/src/content/docs/online-payments/guides/tokenization-with-payment-sdk.mdx b/src/content/docs/online-payments/guides/tokenization-with-payment-sdk.mdx
index 32e56421..1b3226b8 100644
--- a/src/content/docs/online-payments/guides/tokenization-with-payment-sdk.mdx
+++ b/src/content/docs/online-payments/guides/tokenization-with-payment-sdk.mdx
@@ -14,7 +14,7 @@ Here are the things that you need in order to complete the steps in this guide:
 
 - You have a merchant account with [SumUp](https://me.sumup.com/login) and have already filled in your [account details](https://me.sumup.com/account).
   - For a **test account** reach out to our support team through this [contact form](/contact).
-- You have [an api key](/api-keys/). For more details see [docs](/tools/authorization/authorization/#api-keys)
+- You have [an API key](/tools/authorization/api-keys/). For more details see the [API key guide](/tools/authorization/api-keys/#create-an-api-key).
 - You have control over the backend server to retrieve data in a secure manner.
 
 ## Summary
diff --git a/src/content/docs/online-payments/index.mdx b/src/content/docs/online-payments/index.mdx
index d964266c..6dafc57b 100644
--- a/src/content/docs/online-payments/index.mdx
+++ b/src/content/docs/online-payments/index.mdx
@@ -41,7 +41,7 @@ When you're done experimenting with the test account, switch back to a regular a
 
 ## Authorization
 
-All Online Payment products consume SumUp APIs, which requires a means of authorization - either an API Key or Access Token. Check the [Authorization Guide](/tools/authorization/authorization/) for details on the available authorization options in SumUp.
+All Online Payment products consume SumUp APIs, which requires a means of authorization—either an API key or access token. Check the [Authorization guide](/tools/authorization/) for details on the available authorization options in SumUp.
 
 ## Checkout Products
 
@@ -99,13 +99,13 @@ The API receives requests and communicates responses mostly in [JSON](http://www
 
 ### Receiving payments
 
-In order to receive payments, you need to [create a checkout](/online-payments/guides/single-payment/#1-create-a-checkout). Whether you would like to receive payments as a merchant directly, or initiate payments on a merchant's behalf depends on the type of [authorization](/tools/authorization/authorization/) provided.
+In order to receive payments, you need to [create a checkout](/online-payments/guides/single-payment/#1-create-a-checkout). Whether you would like to receive payments as a merchant directly, or initiate payments on a merchant's behalf depends on the type of [authorization](/tools/authorization/) provided.
 Checkouts are created in a server-to-server communication. This ensures that you can keep your access token and client credentials secret and guarantees that sensitive checkout details, e.g. amount or recipient, cannot be changed.
 
 [Completing checkouts](/online-payments/guides/single-payment/#2-complete-a-checkout) could be done via your web browser or mobile application, which guarantees you do not need to worry about sensitive data, like card data, ever hitting your servers and thus avoiding the need to be PCI DSS compliant.
 
 <Aside type="tip">
-A checkout can be completed in a browser only from a domain that is present as an authorized JavaScript origin when [creating your client credentials](/tools/authorization/register-app/#3-create-oauth-client-credentials).
+A checkout can be completed in a browser only from a domain that is present as an authorized JavaScript origin when [creating your client credentials](/tools/authorization/oauth/#3-create-oauth-client-credentials).
 </Aside>
 
 SumUp provides flexibility to complete a checkout by offering a couple of integration approaches:
diff --git a/src/content/docs/online-payments/plugins/prestashop.mdx b/src/content/docs/online-payments/plugins/prestashop.mdx
index 86c3cd00..8fe534c6 100644
--- a/src/content/docs/online-payments/plugins/prestashop.mdx
+++ b/src/content/docs/online-payments/plugins/prestashop.mdx
@@ -26,8 +26,8 @@ Currently the Alternative Payment Methods (APMs) are not available in SumUp plug
 
 ## Installation
 
-1. Follow the instructions described in [the register application guide](/tools/authorization/register-app) in order to obtain the client credentials for your app.
-2. Download the client credentials JSON as described in the [access client credentials section](/tools/authorization/register-app/#4-access-the-client-credentials)
+1. Follow the instructions described in [the register application guide](/tools/authorization/oauth/#register-oauth-application) in order to obtain the client credentials for your app.
+2. Download the client credentials JSON as described in the [access client credentials section](/tools/authorization/oauth/#4-access-the-client-credentials)
 3. Upload the JSON to the "Module Configuration" page in your PrestaShop Backoffice.
 4. Once your account is fully verified by SumUp, [contact us](/contact) to request enabling of the online payments scope for your PrestaShop online store.
 
diff --git a/src/content/docs/online-payments/plugins/wix.mdx b/src/content/docs/online-payments/plugins/wix.mdx
index 010c9171..1423de41 100644
--- a/src/content/docs/online-payments/plugins/wix.mdx
+++ b/src/content/docs/online-payments/plugins/wix.mdx
@@ -21,7 +21,7 @@ With this integration, the following Alternative Payment Methods (APMs) are avai
 
 Here's how you can connect SumUp to your WIX online store:
 
-1. First, create your secret API Key. [See this article](/tools/authorization/authorization/#integration-via-api-keys) for full information on how to do it. Copy your key before proceeding.
+1. First, create your secret API key. [See this article](/tools/authorization/api-keys/#create-an-api-key) for full information on how to do it. Copy your key before proceeding.
 2. Head over to your WIX dashboard.
 3. Go to **Settings** and click on **Accept payments**.
 4. Select **SumUp**, paste your secret API Key in the required field under **Account Information** and **Save**.
diff --git a/src/content/docs/online-payments/plugins/woocommerce.mdx b/src/content/docs/online-payments/plugins/woocommerce.mdx
index 5c0d92c4..da849f0f 100644
--- a/src/content/docs/online-payments/plugins/woocommerce.mdx
+++ b/src/content/docs/online-payments/plugins/woocommerce.mdx
@@ -72,7 +72,7 @@ You can now begin accepting payments through SumUp on your WordPress shop.
 ### Advanced Integration
 
 1. Once the plugin is activated, click on **Advanced version** option.
-2. [Create your API Key](/tools/authorization/authorization/#create-api-key)
+2. [Create your API key](/tools/authorization/api-keys/#create-an-api-key)
 3. Enter your credentials from your SumUp account (API Key, email and merchant code) and configure any settings as needed.
 
 ## Additional configuration
@@ -115,7 +115,7 @@ Create your credentials [here](https://developer.sumup.com/apps).
   Monday through Friday.
 </Aside>
 
-Once you ensure you've met the above requirements, you can proceed with our [Register application guide](/tools/authorization/register-app/) to set up your client credentials. In that page you find information on how to register an app and your client credentials which are necessary for setting up the plugin in your Wordpress account.
+Once you ensure you've met the above requirements, you can proceed with our [Register application guide](/tools/authorization/oauth/#register-oauth-application) to set up your client credentials. In that page you find information on how to register an app and your client credentials which are necessary for setting up the plugin in your Wordpress account.
 
 ## Plugin Configuration
 
diff --git a/src/content/docs/online-payments/sdks/react-native-sdk.mdx b/src/content/docs/online-payments/sdks/react-native-sdk.mdx
index 425132dd..b0fca163 100644
--- a/src/content/docs/online-payments/sdks/react-native-sdk.mdx
+++ b/src/content/docs/online-payments/sdks/react-native-sdk.mdx
@@ -21,8 +21,8 @@ SumUp's React Native Payment SDK provides a payment sheet that is displayed on t
 Here are the things that you need in order to complete the steps in this guide:
 - You have a merchant account with [SumUp](https://me.sumup.com/login) and have already filled in your [account details](https://me.sumup.com/account).
   - For a **test account** reach out to our support team through this [contact form](/contact).
-- You have [registered your client application](/tools/authorization/register-app/) with SumUp.
-- You have a valid access token obtained via the [Authorization code flow](/tools/authorization/authorization/#authorization-code-flow).
+- You have [registered your client application](/tools/authorization/oauth/#register-oauth-application) with SumUp.
+- You have a valid access token obtained via the [Authorization code flow](/tools/authorization/oauth/#authorization-code-flow).
 - The restricted `payment_instruments` scope is enabled for your client application. If it isn't enabled, [contact us](/contact) and request it.
 - Review how to create a single payment [here](https://developer.sumup.com/online-payments/guides/single-payment/#before-you-begin).
 
diff --git a/src/content/docs/terminal-payments/cloud-api.mdx b/src/content/docs/terminal-payments/cloud-api.mdx
index 8d20993a..8274bd24 100644
--- a/src/content/docs/terminal-payments/cloud-api.mdx
+++ b/src/content/docs/terminal-payments/cloud-api.mdx
@@ -32,7 +32,7 @@ The Cloud API integration supports:
 
 ## Prerequisites
 
-* Your device must be authorized to use the Cloud API. [Read the authorization guide](/tools/authorization/authorization/) and implement a method that best fits your use case. The API key should be sufficient if you do not intend to delegate access to third parties.
+* Your device must be authorized to use the Cloud API. [Read the authorization guide](/tools/authorization/) and implement a method that best fits your use case. The API key should be sufficient if you do not intend to delegate access to third parties.
 * You need to [create an Affiliate Key](/tools/authorization/affiliate-keys/) for your app. SumUp Cloud API requires the Affiliate Key to be present in checkout requests.
 * We strongly recommend keeping the Solo terminal plugged-in when using Cloud API.
 * If you want to use mobile data, make sure that you're not connected to a Wi-Fi network. Disconnect if you are -
diff --git a/src/content/docs/terminal-payments/index.mdx b/src/content/docs/terminal-payments/index.mdx
index 277695ba..338db398 100644
--- a/src/content/docs/terminal-payments/index.mdx
+++ b/src/content/docs/terminal-payments/index.mdx
@@ -16,7 +16,7 @@ You can accept card payments using SumUp’s platform accompanied by our proprie
 
 * Before you integrate either the [Native SDK](/terminal-payments/tools/sdk/) or the [Payment API Switch](/terminal-payments/payment-switch), you need to create a SumUp account in the [SumUp Dashboard](https://me.sumup.com). Alternatively, you can [create a test account](#getting-a-test-account).
 
-* Once you have an account, you need to [create an Affiliate Key](/tools/authorization/affiliate-keys/) for your app and [provide means of authorization](/tools/authorization/authorization/).
+* Once you have an account, you need to [create an Affiliate Key](/tools/authorization/affiliate-keys/) for your app and [provide means of authorization](/tools/authorization/).
 
 <Aside type="caution">
 
diff --git a/src/content/docs/terminal-payments/payment-switch.mdx b/src/content/docs/terminal-payments/payment-switch.mdx
index debe08d2..49cd3586 100644
--- a/src/content/docs/terminal-payments/payment-switch.mdx
+++ b/src/content/docs/terminal-payments/payment-switch.mdx
@@ -12,7 +12,7 @@ Your app initiates a request to charge a card, opens the SumUp app on the mercha
 
 The API integration also allows the possibility to pre-fill the checkout amount and card holder information, and to send a receipt via SMS or email. You can use the cash option, which is not available in our SDK version, for better reporting and management of your funds in the SumUp dashboard.
 
-Activate the [mandatory authorization scopes](/tools/authorization/authorization/#authorization-scopes) for a smooth performance. They will require obtaining an access token for your client application that will authenticate it with the SumUp REST API and authorize it to access server resources.
+Activate the [mandatory authorization scopes](/tools/authorization/oauth/#authorization-scopes) for a smooth performance. They will require obtaining an access token for your client application that will authenticate it with the SumUp REST API and authorize it to access server resources.
 
 ## API documentation
 
diff --git a/src/content/docs/terminal-payments/sdks/ios-sdk.mdx b/src/content/docs/terminal-payments/sdks/ios-sdk.mdx
index ef075045..d68b71c9 100644
--- a/src/content/docs/terminal-payments/sdks/ios-sdk.mdx
+++ b/src/content/docs/terminal-payments/sdks/ios-sdk.mdx
@@ -343,7 +343,7 @@ SumUp iOS SDK supports either the OAuth 2.0 Authorization Code Flow login with A
 
 ### Implementing Authentication with OAuth 2.0
 
-SumUp can issue Access Tokens in accordance with the OAuth 2.0 Authorization Code Flow, which is our recommended authorization approach (Client Credentials Flow is not supported by this SDK). See the [Authorization Documentation](/tools/authorization/authorization#integration-via-oauth-20) for more details.
+SumUp can issue Access Tokens in accordance with the OAuth 2.0 Authorization Code Flow, which is our recommended authorization approach (Client Credentials Flow is not supported by this SDK). See the [Authorization Documentation](/tools/authorization/oauth/#integration-via-oauth-20) for more details.
 
 ### Implementing Authentication with View Controller
 
diff --git a/src/content/docs/tools/authorization/affiliate-keys.mdx b/src/content/docs/tools/authorization/affiliate-keys.mdx
index 56b3eff4..ff733ddb 100644
--- a/src/content/docs/tools/authorization/affiliate-keys.mdx
+++ b/src/content/docs/tools/authorization/affiliate-keys.mdx
@@ -18,9 +18,7 @@ fees. For that reason, **Affiliate Keys are mandatory for card-present integrati
 * [API Payment Switch](/terminal-payments/payment-switch/)
 * [Solo API (Cloud API)](/terminal-payments/cloud-api/)
 
-Affiliate keys are NOT part of any authorization mechanism as such. They are used by SumUp in card-present integrations to attribute the payments to a specific integration.
-
-See [Authorization Guide](/tools/authorization/authorization/) for details on authorization.
+Affiliate keys are not an authorization mechanism. Use them together with either [API keys](/tools/authorization/api-keys/) or [OAuth 2.0](/tools/authorization/oauth/) depending on how your integration calls SumUp APIs.
 
 ## Create Affiliate Key
 
@@ -66,7 +64,7 @@ in their checkout requests.
 
 Check the following resources to build your integration:
 
-* [OAuth 2.0 App Registration Guide](/tools/authorization/register-app/)
+* [OAuth 2.0 App Registration Guide](/tools/authorization/oauth/#register-oauth-application)
 * [iOS SDK Guide](/terminal-payments/sdks/ios-sdk/)
 * [Android SDK Guide](https://github.com/sumup/sumup-android-sdk)
 * [PHP SDK Guide](/online-payments/sdks/php-sdk/)
diff --git a/src/content/docs/tools/authorization/api-keys.mdx b/src/content/docs/tools/authorization/api-keys.mdx
new file mode 100644
index 00000000..7a56f018
--- /dev/null
+++ b/src/content/docs/tools/authorization/api-keys.mdx
@@ -0,0 +1,58 @@
+---
+title: API Keys
+description: Learn how to use and protect SumUp API keys for direct integrations.
+sidebar:
+  order: 2
+---
+
+import { Aside, Steps } from '@astrojs/starlight/components';
+
+## Overview
+
+API keys are static credentials that let your application act on behalf of the merchant account that created the key.
+Use them when you control the merchant account and need direct access to SumUp APIs with the full set of permissions.
+
+## Authorize requests with an API key
+
+Include the API key in the `Authorization` header using the `Bearer` scheme when calling SumUp APIs.
+
+```bash
+curl https://api.sumup.com/v0.1/me -H "Authorization: Bearer $SUMUP_API_KEY"
+```
+
+<Aside type="caution">
+
+Do not expose secret API keys in publicly accessible places such as client-side code or repositories.
+API keys grant broad access to the merchant account, so treat them as sensitive credentials.
+
+</Aside>
+
+## Create an API key
+
+<Steps>
+
+1. Log in to [https://me.sumup.com](https://me.sumup.com).
+2. Expand your profile and open **Settings**.
+3. Go to **For Developers** > **Toolkit**.
+4. Select **API Keys**.
+
+   If this is your first key, the page only shows the SumUp Public Key.
+   Existing API keys are also listed here.
+
+   Do not use the public key in your integration.
+
+5. Select **Create** and name the key so you can identify it later.
+6. When prompted, copy or download the key. SumUp does not store the key, so you are responsible for keeping it secure.
+
+</Steps>
+
+## Handle API keys securely
+
+- Keep the key in a secure secret store and rotate it regularly.
+- Avoid sharing the key with third parties. If sharing is unavoidable, make sure they meet your security expectations.
+- Monitor how the key is used and revoke it promptly if you suspect misuse.
+
+## When to choose another method
+
+Use [OAuth 2.0](/tools/authorization/oauth/) when you build an integration that other merchants or their staff will authorize.
+For card-present scenarios, combine your chosen authorization method with an [Affiliate Key](/tools/authorization/affiliate-keys/).
diff --git a/src/content/docs/tools/authorization/authorization.mdx b/src/content/docs/tools/authorization/authorization.mdx
deleted file mode 100644
index f3988a78..00000000
--- a/src/content/docs/tools/authorization/authorization.mdx
+++ /dev/null
@@ -1,182 +0,0 @@
----
-title: Authorization
-description: Learn how to authenticate and authorize when calling the SumUp APIs.
-sidebar:
-  order: 2
----
-
-import { Aside, Steps } from '@astrojs/starlight/components';
-
-
-## Overview
-
-All requests to SumUp API must be made over [HTTPS](https://en.wikipedia.org/wiki/HTTPS) and must be authorized.
-
-SumUp supports two kinds of authorization. One is via [API keys](#api-keys) allowing the app to authenticate and authorize on behalf of the Merchant and access the SumUp API with full set of permissions.
-This is the easiest approach and accommodates most use cases.
-
-The other approach is via [OAuth 2.0](#integration-via-oauth-20), which allows the app to request access on behalf of third parties. This is useful for building advanced integrations to be used by multiple merchants.
-
-## Integration via API Keys
-
-SumUp uses API keys to authenticate and authorize the API requests. API Keys are short static tokens passed in the `Authorization` header.
-
-```bash
-curl https://api.sumup.com/v0.1/me -H "Authorization: Bearer $SUMUP_API_KEY"
-```
-
-The intended purpose of API keys is to authorize on behalf of a single merchant to whom the API key belongs.
-
-<Aside type="caution">
-
-Do not share your secret API keys in publicly accessible places such as GitHub repositories, client-side code, etc.
-Your API keys carry full permissions to the entire SumUp API, so make sure to keep them secure.
-Should you decide to integrate third-parties with the API key, you are responsible for ensuring the security of such integration.
-
-</Aside>
-
-### Create API Key
-
-<Steps>
-
-1. Log in to [https://me.sumup.com](https://me.sumup.com).
-2. Expand your profile and open **Settings**.
-3. Go to **For Developers** > **Toolkit**.
-4. Select **API Keys**.
-   
-   If you didn't create a key before, this page only shows the SumUp Public Key.
-   If you did, your existing API Keys can be found here.
-
-   Do not use the public key in your integration.
-
-5. Select **Create** and give the key a meaningful name. Your key is now created and granted permissions to access SumUp APIs.
-6. When prompted, copy the key (you can also download it). SumUp does not store the key for security reasons.
-   Integrators are responsible for handling the key securely in accordance with best industry practices.
-
-   * Ideally, do not share the key with third parties. If you do, ensure they handle it securely.
-   * Do not add the key to source-controlled repository or client-side code.
-   * Monitor key usage.
-   * Rotate the key on regular basis.
-
-</Steps>
-
-## Affiliate Keys
-
-Affiliate Keys are not part of authorization mechanisms as such, but they are required for card-present integrations. For more information, see [Affiliate Keys](/tools/authorization/affiliate-keys/).
-
-## Integration via OAuth 2.0
-
-OAuth 2.0 is the recommended approach for building advanced integrations, where multiple different merchants or their employees want to use SumUp.
-SumUp conforms to the [OAuth 2.0 protocol](https://oauth.net/2/), providing an authorization server and exposing the following endpoints as defined by the industry:
-
-- `https://api.sumup.com/authorize`
-- `https://api.sumup.com/token`
-
-
-[OAuth 2.0](https://oauth.net/2/) is an industry-standard authorization protocol that allows for control over an application’s scope, and authorization flows across multiple devices.
-OAuth 2.0 allows the app to request API access on behalf of other users after they grant you the permission.
-
-SumUp supports two standard OAuth 2.0 authorization flows:
-
-- The [authorization code flow](#authorization-code-flow) to request permissions from other users.
-- The [client credentials flow](#client-credentials-flow) to authenticate as yourself.
-
-<Aside type="caution">
-
-For security reasons, SumUp manually verifies the following scope grants:
-
-* `payments` - required to process payments.
-* `payment_instruments` - required to store customer data and tokenize cards.
-
-[Contact us](/contact) to request those scopes to be granted to your app.
-
-SumUp does not recommend direct OAuth 2.0 integration and does not expose detailed authorization endpoint documentation for that reason.
-Please use a library that handles OAuth 2.0 protocol. We highly recommend that you use one of the [existing reputable implementations](https://openid.net/developers/certified-openid-connect-implementations/).
-
-</Aside>
-
-### Authorization Code Flow
-
-This flow works [as specified by RFC 6749 Authorization Code Grant](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1), enabling applications to request permission from a SumUp merchant to act on their behalf. The [requested scopes](#authorization-scopes) define what your application is allowed to do.
-
-<Steps>
-
-1. To initiate the flow, your application redirects a user to the SumUp authorization server with the `https://api.sumup.com/authorize` endpoint.
-
-2. The request triggers an authorization prompt describing which application is requesting authorization from the user.
-
-    <Aside type="caution">
-    If the user denies and clicks the **Cancel** button on the request, the authorization server will not generate an authorization code and will instead return an `error` parameter with an `access_denied` value instead.
-    </Aside>
-
-3. Once the user accepts your authorization request, the authorization server redirects the user back to your application by using the registered URI you specified in the `redirect_uri` at the initial GET request. 
-  The response will return the `code` parameter, which is mandatory for retrieving an access token.
-
-4. To retrieve the access token, the app makes a request to the `https://api.sumup.com/token` endpoint with a `Content-Type: application/x-www-form-urlencoded` header.
-
-    The app receives the standard response, containing `access_token`, `refresh_token`, `token_type`, and `expires_in`.
-
-    ```json
-    {
-      "access_token": "565e2d19cef68203170ddadb952141326d14e03f4ccbd46daa079c26c910a864",
-      "refresh_token": "d180031bfe9bac36c336e5746637810272546865e9c9586012f462a56f3fe9af",
-      "token_type": "Bearer",
-      "expires_in": 3600
-    }
-    ```
-
-</Steps>
-
-The `access_token` can now be used in the `Authorization` header with `Bearer` scheme to authorize calls to SumUp services.
-The app can use the `refresh_token` to get a new `access_token` when it expires without the user’s interaction (see [Refresh token flow](#refresh-token-flow) below).
-
-### Refresh Token Flow
-
-To refresh the access token, send a request to the `https://api.sumup.com/token` endpoint with the refresh token you've received when completing the [Authorization code flow](#authorization-code-flow), as the OAuth 2.0 protocol dictates. Access tokens can expire for many reasons, such as if the user changes their password or revokes the app access.
-
-In the response, the app receives a new `access_token` that is valid for `expires_in` seconds and a new `refresh_token`. Make sure to store the new `refresh_token` for successive refreshes.
-
-<Aside type="caution">
-
-By default, refresh tokens are valid for a period of 6 months. After your `refresh_token` expires, the app must follow the [Authorization code flow](#authorization-code-flow) again to obtain a valid access token and a new refresh token. A new refresh token will also be issued when a valid refresh token is used within 30 days prior to its expiration. The new refresh token will be valid for another 6 months. The old refresh token remains valid until its expiration date, giving you a grace period to propagate the new token across your integration.
-
-Note that refresh tokens can be invalidated due to factors other than expiration, such as password change, scope changes, etc. Failed attempt to refresh a token should be handled gracefully by triggering a new login and obtaining fresh set of access and refresh token.
-
-</Aside>
-
-### Authorization Scopes
-
-Authorization scopes define what an application is allowed to do on a merchant's behalf. A required set of scopes may be passed as a space-separated list in the authorization request. When scopes are omitted, the default ones are granted. If additional scopes are required, a new `access_token` has to be collected via the [Authorization code flow](#authorization-code-flow).
-
-| Scope name                       | Default | Access Level | Description                                                                                                                                                                                                                                                             |
-| -------------------------------- | ------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| transactions.history             | yes     | merchant     | Allows to view the transactions and transaction history for a specific merchant user's account.                                                                                                                                                                     |
-| user.app-settings                | yes     | merchant     | Allows to view and modify the SumUp mobile application settings for a specific merchant user's account.                                                                                                                                                             |
-| user.profile_readonly            | yes     | merchant     | Allows to view the profile details for a specific merchant user's account.                                                                                                                                                                                          |
-| user.profile                     | no      | merchant     | Allows to modify the profile details of a specific merchant user's account.                                                                                                                                                                                         |
-| user.subaccounts                 | no      | merchant     | Allows to view and modify the profile details of a sub-account created for a specific merchant user's account. Sub-accounts are user accounts for employees of a merchant and can be granted different permissions by the holder of the main merchant user's account. |
-| user.payout-settings             | no      | merchant     | Allows to view and modify the payout settings for a specific merchant user's account.                                                                                                                                                                               |
-| products                         | no      | merchant     | Allows to view and modify the product store for a specific merchant user's account. This includes the products, shelves, prices, and VAT rates available in the merchant's product store.                                                                           |
-| `restricted` payments            | no      | feature      | Allows to make payments by creating and processing payment checkouts. Requires verification by SumUp before it can be granted.                                                                                                                                                                                               |
-| `restricted` payment_instruments | no      | feature      | Allows to save customers and tokenize their payment cards for a specific merchant user's account. Requires verification by SumUp before it can be granted.                                                                                                                                                         |
-
-Restricted scopes must be enabled by SumUp for your application. To do that, [contact us](/contact).
-
-### Client Credentials Flow
-
-This flow works [as specified by RFC 6749 Client Credentials Grant](https://datatracker.ietf.org/doc/html/rfc6749#section-4.4)
-
-In the Client Credentials flow, your application requests an access token without requesting authorization from a merchant user. As a result, when you use this flow, your application is not authorized to access any data that is associated with a merchant user's account, such as transactions or saved customers and tokenized payment cards. In other words, you can only process payments for merchant accounts with an access token obtained via this grant flow.
-
-To request an access token, the app needs to make a request to the `https://api.sumup.com/token` endpoint as defined in the OAuth 2.0 Client Credentials protocol. This flow does not grant a Refresh Token.
-
-## What's Next?
-
-Check the following resources to build your integration:
-
-* [OAuth 2.0 App Registration Guide](/tools/authorization/register-app/)
-* [iOS SDK Guide](/terminal-payments/sdks/ios-sdk/)
-* [Android SDK Guide](https://github.com/sumup/sumup-android-sdk)
-* [PHP SDK Guide](/online-payments/sdks/php-sdk/)
-* [React Native SDK](/terminal-payments/sdks/react-native-sdk/)
-* [Cloud API for the Solo Card Reader](/terminal-payments/cloud-api/)
diff --git a/src/content/docs/tools/authorization/index.mdx b/src/content/docs/tools/authorization/index.mdx
index afc21b68..06d01e33 100644
--- a/src/content/docs/tools/authorization/index.mdx
+++ b/src/content/docs/tools/authorization/index.mdx
@@ -5,17 +5,19 @@ sidebar:
   order: 1
 ---
 
-SumUp exposes a REST API that lets you manage checkouts, retrieve transactions
-and perform other operations programmatically. Before you can make requests you
-need to authenticate your application and, for card-present integrations,
-provide an [Affiliate Key](/docs/tools/authorization/affiliate-keys/).
+SumUp exposes REST APIs for managing checkouts, retrieving transactions, and more.
+Every integration needs a way to authorize API requests, and card-present solutions also need to identify the integration itself.
 
-Key topics in this section:
+## Choose the right option
 
-- **[Authorization](/docs/tools/authorization/authorization/)** – explains how to obtain
-  access tokens with API keys or OAuth 2.0.
-- **[Affiliate Keys](/docs/tools/authorization/affiliate-keys/)** – learn why affiliate
-  keys are required and how to generate one.
+- **[API keys](/tools/authorization/api-keys/)** – Static credentials owned by a single merchant.
+  Use them for direct server-to-server integrations when you control the merchant account and need full API access.
+- **[OAuth 2.0](/tools/authorization/oauth/)** – Standards-based authorization for multi-merchant solutions.
+  Use it when other merchants or their employees connect to your application and must explicitly grant access.
+- **[Affiliate Keys](/tools/authorization/affiliate-keys/)** – Required for card-present scenarios to attribute transactions to your integration.
+  Combine them with API keys or OAuth depending on how you authorize API calls.
 
-Once you are familiar with these concepts you can explore the detailed
-[API reference](/api/).
+## Next steps
+
+- Review the [API reference](/api/) once you have your credentials.
+- Follow product-specific guides such as [terminal integrations](/terminal-payments/) or [online payments](/online-payments/) with the appropriate authorization method in place.
diff --git a/src/content/docs/tools/authorization/oauth.mdx b/src/content/docs/tools/authorization/oauth.mdx
new file mode 100644
index 00000000..f5fb6c0f
--- /dev/null
+++ b/src/content/docs/tools/authorization/oauth.mdx
@@ -0,0 +1,220 @@
+---
+title: OAuth 2.0
+description: Learn how to request SumUp API access on behalf of other merchants.
+sidebar:
+  order: 3
+---
+
+import { Aside, Steps } from '@astrojs/starlight/components';
+import Image from '@components/content/Image.astro';
+
+## Integration via OAuth 2.0
+
+OAuth 2.0 lets your application request permission to act on behalf of other SumUp merchants or their employees.
+It follows the industry-standard [OAuth 2.0 protocol](https://oauth.net/2/) and is the right choice for multi-merchant integrations or when you cannot rely on a single merchant-owned API key.
+
+SumUp exposes two OAuth 2.0 endpoints:
+
+- `https://api.sumup.com/authorize`
+- `https://api.sumup.com/token`
+
+SumUp supports two OAuth 2.0 flows:
+
+- The [authorization code flow](#authorization-code-flow) when an end user grants your application access.
+- The [client credentials flow](#client-credentials-flow) when your application authenticates as itself.
+
+## Authorization flows
+
+Choose the flow that matches how your application obtains access while keeping scope verification requirements in mind.
+
+<Aside type="caution">
+
+SumUp manually verifies requests for the following scopes:
+
+* `payments` – required to create and process payments.
+* `payment_instruments` – required to store customer data and tokenize cards.
+
+[Contact us](/contact) to request those scopes for your application.
+
+Use a reputable OAuth 2.0 client implementation instead of handling the protocol manually.
+
+</Aside>
+
+## Authorization Code Flow
+
+This flow implements the [RFC 6749 Authorization Code Grant](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1). It lets a SumUp merchant review the permissions you request and authorize your application accordingly. The [requested scopes](#authorization-scopes) determine the allowed actions.
+
+<Steps>
+
+1. Redirect the user to `https://api.sumup.com/authorize` with the required parameters.
+2. SumUp shows an authorization prompt describing your application and the scopes requested.
+
+   <Aside type="caution">
+   If the user denies the request, SumUp sends an error response to your redirect URI and does not issue an authorization code.
+   </Aside>
+
+3. After the user approves, SumUp redirects to your **Redirect URI** with an authorization code and the original `state`.
+4. Your application exchanges the authorization code for tokens by calling the token endpoint described below.
+5. Use the `access_token` in the `Authorization: Bearer` header when calling SumUp APIs.
+
+</Steps>
+
+### Exchange the authorization code
+
+Send the following request to `https://api.sumup.com/token`:
+
+```bash
+curl https://api.sumup.com/token \
+  -X POST \
+  -H "Content-Type: application/x-www-form-urlencoded" \
+  -d "grant_type=authorization_code&code={AUTHORIZATION_CODE}&redirect_uri={REDIRECT_URI}" \
+  -u "{CLIENT_ID}:{CLIENT_SECRET}"
+```
+
+The response contains an access token, refresh token, and metadata such as token lifetime and granted scopes.
+
+```json
+{
+  "access_token": "{ACCESS_TOKEN}",
+  "token_type": "Bearer",
+  "expires_in": 3599,
+  "refresh_token": "{REFRESH_TOKEN}",
+  "scope": "payments customers payment_instruments"
+}
+```
+
+### Refresh the access token
+
+Access tokens expire, for example when a user changes their password or revokes access.
+Use the refresh token to request a new access token from `https://api.sumup.com/token` as defined by OAuth 2.0.
+
+Refresh tokens are valid for six months. If you use a refresh token within 30 days of its expiration, SumUp issues a new token that remains valid for another six months. The previous token keeps working until it expires, giving you time to rotate it across your systems.
+
+## Authorization Scopes
+
+Scopes restrict what your application may do on behalf of the merchant. Request only the scopes you need. When you omit scopes, SumUp grants the defaults listed below. To obtain additional scopes later, repeat the authorization code flow.
+
+| Scope name                       | Default | Access Level | Description |
+| -------------------------------- | ------- | ------------ | ----------- |
+| transactions.history             | yes     | merchant     | View transactions and transaction history for the merchant user. |
+| user.app-settings                | yes     | merchant     | View and modify SumUp mobile app settings for the merchant user. |
+| user.profile_readonly            | yes     | merchant     | View profile details of the merchant user. |
+| user.profile                     | no      | merchant     | Modify profile details of the merchant user. |
+| user.subaccounts                 | no      | merchant     | View and modify sub-account profiles for the merchant user. |
+| user.payout-settings             | no      | merchant     | View and modify payout settings for the merchant user. |
+| products                         | no      | merchant     | View and modify products, shelves, prices, and VAT rates in the merchant's product store. |
+| `restricted` payments            | no      | feature      | Create and process payment checkouts. Requires manual verification by SumUp. |
+| `restricted` payment_instruments | no      | feature      | Save customers and tokenize their payment cards. Requires manual verification by SumUp. |
+
+Restricted scopes must be enabled by SumUp for your application. [Contact us](/contact) to request them.
+
+## Client Credentials Flow
+
+The client credentials flow follows [RFC 6749 Client Credentials Grant](https://datatracker.ietf.org/doc/html/rfc6749#section-4.4). It issues an access token without involving a merchant user. Because no user is associated with the token, the flow does not allow access to merchant-specific data such as transactions or stored customers. You can still process payments for merchants linked to your application.
+
+Request an access token from `https://api.sumup.com/token` using the client credentials grant parameters. This flow does not return a refresh token.
+
+## Register an OAuth application
+
+To integrate an external application with SumUp, register an OAuth application and generate client credentials.
+These credentials let you complete the OAuth flows in this guide and obtain access tokens for protected SumUp resources.
+
+### Steps
+
+This section walks through the registration process:
+
+1. [Log in to your account](#1-log-in-to-your-account)
+2. [Create an OAuth application](#2-create-an-oauth-application)
+3. [Generate the client credentials](#3-generate-the-client-credentials)
+4. [Access the client credentials](#4-access-the-client-credentials)
+
+### Before you begin
+
+Have the following ready before you register the application:
+
+- A SumUp merchant account with completed [account details](https://me.sumup.com/account). Reach out through the [contact form](/contact) if you need a test account.
+- Your application name.
+- One or more redirect URIs. SumUp redirects users to these URIs after authentication and sends the authorization codes you exchange for tokens in the [authorization code flow](#authorization-code-flow).
+
+### 1. Log in to your account
+
+Log in to [your SumUp account](/auth/login). Once logged in, **Account** appears in place of the **Log in** button at the top right.
+
+### 2. Create an OAuth application
+
+Navigate to the [OAuth Apps](/apps/) page to create or manage OAuth applications.
+
+Select **Create application** at the bottom right to define your application.
+
+<Image alt="Create OAuth App screen" src="/img/guides/create-oauth-apps.png" width="80%" />
+
+Describe your application, provide its homepage, and select **Register application** to continue.
+
+You can edit the registered application by selecting it. The edit page lets you update details and add optional information such as a logo, terms and conditions, and privacy policy URLs.
+
+You can also select the scopes your application requires. Each scope includes a short description of the access it grants.
+
+### 3. Generate the client credentials
+
+On the [OAuth Apps](/apps) page, open your application and choose **Create client secret**.
+
+<Image alt="Create new OAuth App credentials form" src="/img/guides/client-credentials-form.png" width="80%" />
+
+Provide the following details:
+
+| Name | Required | Description |
+| -----| -------- | ----------  |
+| Client name | Yes | A descriptive name for your client application. |
+| Application type | Yes | The type of your client application. Options: Web, Android, iOS, Other. |
+| Authorized redirect URL | Yes | Redirect URL to register for your client application. Specify multiple URLs by separating them with commas. |
+| Authorized JavaScript Origin | No | Origin URI for browser-based web applications. SumUp enables CORS for registered origins. |
+
+Select **Save** to generate the credentials. The **Client secrets** section lists each credential with its name, application type, and client ID.
+
+<Aside type="note">
+
+You can register as many client credentials as you need. Repeat this step to create additional ones.
+
+</Aside>
+
+### 4. Access the client credentials
+
+After creation, credentials appear in the **Client credentials** section of your OAuth application (see screenshot).
+
+<Image alt="OAuth client credentials section" src="/img/guides/client-credentials-list.png" width="80%" />
+
+<Aside type="note">
+For security reasons, the client secrets are not displayed.
+</Aside>
+
+Use the download button to receive a JSON file with the full credential details, for example:
+
+```json
+{
+  "id": "CCCFAXYD",
+  "name": "SA web client",
+  "client_id": "fOcmczrYtYMJ7Li5GjMLLcUeC9dN",
+  "client_secret": "717bd571b54297494cd7a79b491e8f2c1da6189c4cc2d3481380e8366eef539c",
+  "application_type": "web",
+  "redirect_uris": ["https://sample-app.example.com/callback"]
+}
+```
+
+<Aside type="note">
+
+Store client secrets securely and never expose them publicly. If you suspect a secret was compromised, [contact us](/contact) immediately.
+
+</Aside>
+
+### Result
+
+You have registered at least one OAuth application and have downloaded its client credentials. Proceed with the [OAuth 2.0 flows](#authorization-flows) to obtain access tokens. Use them to accept payments with a [customer-entered card](/online-payments/guides/single-payment/) or with stored payment data in recurring scenarios.
+
+## What's Next?
+
+- [Review your OAuth application scopes](#authorization-scopes)
+- [iOS SDK Guide](/terminal-payments/sdks/ios-sdk/)
+- [Android SDK Guide](https://github.com/sumup/sumup-android-sdk)
+- [PHP SDK Guide](/online-payments/sdks/php-sdk/)
+- [React Native SDK](/terminal-payments/sdks/react-native-sdk/)
+- [Cloud API for the Solo Card Reader](/terminal-payments/cloud-api/)
diff --git a/src/content/docs/tools/authorization/register-app.mdx b/src/content/docs/tools/authorization/register-app.mdx
deleted file mode 100644
index d0adee9b..00000000
--- a/src/content/docs/tools/authorization/register-app.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Register OAuth 2.0 Application
-sidebar:
-  order: 3
----
-
-import { Aside } from '@astrojs/starlight/components';
-import Image from '@components/content/Image.astro';
-
-
-In order to integrate an external application with SumUp's ecosystem, you have to register an OAuth application and generate the client credentials which are used to make OAuth-authenticated requests on behalf of your application. You can see more on [OAuth2 authorization flows](/tools/authorization/authorization/), which explain how to request an _access token_ that is used to obtain permission to protected resources within SumUp's API.
-
-In this guide, you will learn how to register a client application and obtain OAuth client credentials for it. You will go through the following steps:
-
-1.  [Log in to your account](#1-log-in-to-your-account)
-2.  [Create an OAuth application](#2-create-an-o-auth-application)
-3.  [Generate the client credentials](#3-generate-the-client-credentials)
-4.  [Access the client credentials](#4-access-the-client-credentials)
-
-## Before you begin
-
-Here are the things that you need in order to complete the steps in this guide:
-
-- You have a merchant account with [SumUp](https://me.sumup.com/login) and have already filled in your [account details](https://me.sumup.com/account).
-  - For a **test account** reach out to our support team through this [contact form](/contact).
-- You have the following information available:
-  - Your application name.
-  - One or more redirection URIs for registering with SumUp. We will use a registered URI to redirect users to your application after authentication and to send you the authorization codes for obtaining access tokens via the [OAuth2 Authorization Code Flow](/tools/authorization/authorization/#authorization-code-flow).
-
-### 1. Log in to your account
-
-Log in to [your SumUp account](/auth/login). Once logged in, **Account** will appear in place of the **Log in** button on the top right corner of the page.
-
-### 2. Create an OAuth application
-
-Navigate to the [OAuth Apps](/apps/) page. This page allows you to create and edit OAuth applications.
-
-Click on **Create application** at the bottom right of the page to define your application.
-
-<Image alt="Create OAuth App screen" src="/img/guides/create-oauth-apps.png" width="80%" />
-
-Describe your application and provide its homepage. Click **Register application** to complete.
-
-It's possible to edit the registered application details by clicking on it. The editing page allows to update the initial data and include **optional information** such as a "Logo", "Terms & Conditions" and "Privacy policy" urls.
-
-Additionally, it's possible to specify the scope of access to your own merchant information. Each scope includes a short description of what it would give access to if selected.
-
-<Aside type="caution">
-
-For security reasons, SumUp manually verifies the following scope grants:
-
-* `payments` - required to process payments.
-* `payment_instruments` - required to store customer data and tokenize cards.
-
-[Contact us](/contact) to request those scopes to be granted to your app.
-
-SumUp does not recommend direct OAuth 2.0 integration and does not expose detailed authorization endpoint documentation for that reason.
-Please use a library that handles OAuth 2.0 protocol. We highly recommend that you use one of the [existing reputable implementations](https://openid.net/developers/certified-openid-connect-implementations/).
-
-</Aside>
-
-<Image alt="Edit OAuth App screen" src="/img/guides/edit-oauth-apps.png" width="80%" />
-
-The information provided in this section is showed to users when requesting access to their SumUp account data. To read more about how this information is presented see our [OAuth2 Authorization Code Flow](/tools/authorization/authorization/).
-
-### 3. Generate the client credentials
-
-On the [OAuth Apps](/apps) page, click on a registered application. At the bottom of the page click on **Create client secret** to begin.
-
-Click on **Create client secret** and the following form will be presented.
-
-<Image alt="Create new OAuth App credentials form" src="/img/guides/client-credentials-form.png" width="80%" />
-
-Provide the following details:
-
-| Name | Required | Description |
-| -----| -------- | ----------  |
-| Client name | Yes | A descriptive name for your client application. |
-| Application type | Yes | The type of your client application. You can select from the following options: Web, Android, iOS, Other |
-| Authorized redirect URL | Yes | A redirect URL that you want to register for your client application. When merchant users authenticate with SumUp and authorize your client app to access their account data, they are redirected to this path in your application. To specify more than one redirection URL for the client application, separate each URL with a comma. |
-| Authorized JavaScript Origin | No | The origin URI of your client application. SumUp allows Cross-Origin Resource Sharing (CORS) across various domains from the browser and is available for type web applications only. The value allows your client application to request resources from SumUp servers. |
-
-Click **Save** to generate the client credentials. In the **Client secrets** section, you will see an entry with the name, application type, and client ID of each generated credential.
-
-<Aside type="note">
-
-You can register as many client applications as you need. To register another credential, repeat this step.
-
-</Aside>
-
-### 4. Access the client credentials
-
-Once the client credentials have been created, they will be displayed in the **Client credentials** section of your OAuth application's settings (see screenshot).
-
-<Image alt="OAuth client credentials section" src="/img/guides/client-credentials-list.png" width="80%" />
-
-<Aside type="note">
-For security reasons, the client secrets are not displayed.
-</Aside>
-
-Use the download button to access a JSON file with the full client credential details for the current application.
-Below you can see an example:
-
-```json
-{
-  "id": "CCCFAXYD",
-  "name": "SA web client",
-  "client_id": "fOcmczrYtYMJ7Li5GjMLLcUeC9dN",
-  "client_secret": "717bd571b54297494cd7a79b491e8f2c1da6189c4cc2d3481380e8366eef539c",
-  "application_type": "web",
-  "redirect_uris": ["https://sample-app.example.com/callback"]
-}
-```
-
-<Aside type="note">
-
-Make sure to store your client secret keys securely and never reveal them publicly. If you suspect that the secret key for an application has been compromised, [contact us](/contact) immediately.
-
-</Aside>
-
-## Result
-
-You have registered at least one client application and have generated and downloaded your OAuth client credentials for it.
-
-You can now use one of the [OAuth2 authorization flows](/tools/authorization/authorization/#authorization-flows) to obtain an access token and start making payments with either a [payment card entered by a customer](/online-payments/guides/single-payment/) or with a token for a [recurring payment](https://developer.sumup.com/online-payments/guides/recurring-payments).
-
diff --git a/src/content/help/oauth-credentials.mdx b/src/content/help/oauth-credentials.mdx
index 0d274a4e..e39de237 100644
--- a/src/content/help/oauth-credentials.mdx
+++ b/src/content/help/oauth-credentials.mdx
@@ -2,4 +2,4 @@
 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/register-app/#steps) or in this [video](https://www.youtube.com/watch?v=0ALwF_tm8wII).
+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).