Skip to content

Commit d162cae

Browse files
committed
chore: cleanup duplicate page titles
1 parent 2e11bf8 commit d162cae

3 files changed

Lines changed: 4 additions & 11 deletions

File tree

src/content/docs/online-payments/checkouts/swift-checkout.mdx

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,6 @@ sidebar:
88
import { Aside } from '@astrojs/starlight/components';
99

1010

11-
## About Swift Checkout SDK
12-
1311
The Swift Checkout SDK enables you to offer a complete and fast checkout experience to your end users, allowing you to collect payment, address, and contact information with a click of a button. Swift Checkout SDK allows for Google Pay and Apple Pay setup.
1412

1513
### Prerequisites
@@ -195,8 +193,8 @@ paymentRequest.onShippingAddressChange(async (newShippingAddress) => {
195193

196194
<Aside type="note">
197195
To protect user privacy, browsers might hide non-essential and sensitive details from the shipping address, and only provide data required for shipping cost estimation.
198-
The extent of information provided can vary based on the chosen browser and payment method, leading to certain fields being absent.
199-
For example, the displayed shipping address might be limited to the city, state, country, and ZIP code.
196+
The extent of information provided can vary based on the chosen browser and payment method, leading to certain fields being absent.
197+
For example, the displayed shipping address might be limited to the city, state, country, and ZIP code.
200198

201199
The full shipping address is disclosed only in the `PaymentResponse` object after the payment is authorized by the account holder.
202200
</Aside>
@@ -241,7 +239,7 @@ buttons
241239
{ id: 'apple_pay' },
242240
{ id: 'google_pay' }
243241
// See `paymentRequest.availablePaymentMethods()` for all available payment methods
244-
],
242+
],
245243
container: document.querySelector('#express-checkout-container'),
246244
});
247245
```
@@ -465,4 +463,3 @@ Once the hash has been applied you can proceed with the domain validation steps:
465463
3. Navigate to the **Integrate with your website** and click on **+ Add website**
466464
4. Fill out the form with the requested information (domain name, buyflow screenshots, etc.)
467465
5. At the top of the page click on **Submit for approval**
468-

src/content/docs/terminal-payments/cloud-api.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ import Video from '@components/content/Video.astro';
1010
import SoloScreen from '@components/content/SoloScreen.astro';
1111
import { cloudapiname } from '@lib/productnames.ts';
1212

13-
## About Payments with Cloud API
14-
1513
The { cloudapiname } lets you start a transaction from a Point of Sale (POS) running on any platform (Windows, iOS, Linux, Android, Web-based, etc.) capable of sending HTTPS requests and complete that transaction via a Solo reader.
1614

1715
Key advantages include:
@@ -353,7 +351,7 @@ Read the [Get Reader Status endpoint documentation](/api/readers/get-status) for
353351

354352
### Update Reader
355353

356-
Update the data of a specific reader.
354+
Update the data of a specific reader.
357355

358356
Check the [Update a Reader endpoint documentation](/api/readers/update) for details on the API request, examples, and parameter descriptions.
359357

src/content/docs/terminal-payments/payment-switch.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ sidebar:
55
order: 3
66
---
77

8-
## Overview
9-
108
SumUp API Payment Switch is a light integration where your app opens the SumUp app to request and execute a payment. This integration approach has been the go-to solution for web аpplications before the platform-agnostic [Cloud API](/terminal-payments/cloud-api) was released.
119

1210
Your app initiates a request to charge a card, opens the SumUp app on the merchant's mobile device, and we handle the rest. Once the payment has been processed, the transaction result is communicated back, and the merchant is returned to your app.

0 commit comments

Comments
 (0)