Quickstart

Get your first in-person payment running quickly.

Prerequisites

• A SumUp merchant account
• A supported reader or Tap to Pay-capable device
• The credentials required for your chosen integration:
  • Affiliate Key for Reader SDKs and Payment Switch
  • Authorization for Cloud API and Tap to Pay SDK flows

Sandbox Merchant Account

To test without real money, create a sandbox merchant account from the SumUp Dashboard.

1. Log in to your SumUp account.
2. Open the drop-down menu between Support and your user panel.
3. Select Sandbox Merchant Account.

A screenshot of the account selection dropdown in the SumUp dashboard with the sandbox merchant account highlighted with red circle

Sandbox accounts do not process real funds. They have a separate merchant ID, show a clear warning in the Dashboard, and requests with a value of 11 always fail by design so you can test failed transaction scenarios.

A screenshot of the dashboard with sandbox merchant account selected

Choose Your Path

Reader SDKs

Best for native Android and iOS apps that want more control over the payment experience.

1. Install the SDK for Android SDK, iOS SDK, or Android Tap-to-Pay SDK.
2. Authenticate the merchant.
3. Pair a reader over Bluetooth, or initialize Tap to Pay on device.
4. Start a payment and handle the result in your app.

Cloud API

Best for server-driven, web-based, or multi-platform systems using Solo readers.

1. Set up authorization for API access.
2. Pair or register a Solo reader through the Cloud API.
3. Create a checkout for the paired reader.
4. Let the reader complete the payment and track the result asynchronously.

Payment Switch

Best for lightweight legacy mobile integrations that hand off checkout to the SumUp app.

1. Install the SumUp app on the merchant device.
2. Build a Payment Switch request with amount, currency, and a callback URL.
3. Open the SumUp app and let it handle the checkout.
4. Receive the payment result back in your app.

Note

Use a unique transaction reference such as foreignTransactionId or foreign-tx-id for each payment. That prevents duplicate transaction conflicts and makes reconciliation easier.

Next Steps

• Need an embedded mobile flow? Continue with Reader SDKs.
• Need remote Solo payments? Continue with Cloud API.
• Need app handoff to SumUp? Continue with Payment Switch.