> For the complete documentation index, see [llms.txt](https://docs.spiroq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spiroq.com/en/guides/navody/payments/sumup-solo.md). # SumUp Solo Card payment on the machine can be handled by a **SumUp Solo** terminal over the internet. There is **no MDB cable** between the machine and the terminal. Coins still go over their own cable. ## What you will need * A **SumUp Business account** (merchant) — sign-in at [me.sumup.com](https://me.sumup.com) * A **SumUp Solo** terminal turned on and connected to **Wi-Fi or LTE**. Solo Lite without internet is not enough. * Access to the **Admin Hub** (operator / Provider role, **Pro** plan or higher) * A machine **online** in the Admin Hub, with a current Spiroq app One Solo belongs to **exactly one machine**. The same terminal cannot be paired with two machines at once. ## How installation goes 1. In your SumUp account you create an API key and Affiliate Keys. 2. In the Hub, in **Settings → Payments**, you connect the account. 3. On the SumUp Solo terminal you generate a pairing code and enter it in the machine detail. 4. On the machine, in **Payments**, you switch the card to **Cloud API** and verify a purchase. ## Step 1: Details from the SumUp account You take all values from the **company's own** SumUp account, the company that operates the machines. It is not a Spiroq account. The SumUp Solo terminal must be registered to the same account you create the keys from. ### 1.1 Sign in 1. Open [me.sumup.com](https://me.sumup.com). 2. Sign in with the account that has the Solo. ### 1.2 Create an API key 1. In the dashboard, open **Settings** (the gear). 2. Go to **For developers** / **Developers**. 3. Open **API keys**. 4. Tap **Create API key**. 5. Choose a clear key name, for example `SPIROQ HUB`. 6. Allow the rights SumUp offers on the key: * **Readers** (terminals and Solo pairing) * **Transactions** (payments) * **Refunds** (refunds when part of the purchase is not dispensed) 7. Confirm creation. SumUp shows a secret key in the form `sup_sk_…`. It is shown **only once**. Copy it immediately and keep it at hand for step 2. If you lose it, revoke the key in SumUp and create a new one. Do not send the key by e-mail or chat. ### 1.3 Create Affiliate Keys The API key alone is not enough for payment. On the same account you also need an **Affiliate Application ID** and an **Affiliate Key**. Without them the account can connect in the Hub, but card payment on the machine will not go through. 1. Open [developer.sumup.com](https://developer.sumup.com) and sign in with the same account as in step 1.1. 2. Open **Affiliate Keys**. 3. Create a new key (**Create key**). 4. Choose the **Application ID** as your company's identifier, for example `com.yourcompany.vending`. It is not a Spiroq identifier. 5. Copy the **Affiliate Key**. It starts with `sup_afk_…`. On an older account it may be in UUID form. The Application ID stays visible in the portal later. Copy the Affiliate Key immediately, the same as the API key. Both values are entered into the Hub together with the API key. Before you go on, have the Solo turned on and connected to Wi-Fi or LTE. On the Solo that is **Settings → Connections**. ## Step 2: Connection in the Hub 1. In the Admin Hub, open **Settings → Payments**. 2. Select SumUp. 3. Enter the **API key** (`sup_sk_…`), the **Affiliate Application ID**, and the **Affiliate Key** (`sup_afk_…`). 4. Tap **Connect account**. The Hub checks the key with SumUp. After success the status is **Connected**, and you see the **Merchant code** and the account currency. All three fields disappear from the screen. The Hub does not show them again, only the last four characters of the API key and the Affiliate Key. The details can be changed later with **Replace account credentials** — you enter the key, the Application ID, and the Affiliate Key again. **Disconnect** deletes the stored details. Machines that were running through SumUp return to the cabled card, and paired terminals are unpaired. The next connection requires entering the keys again. ### Transaction cap The **transaction cap** is the ceiling of one card payment. Above it the Hub will not accept the payment, even if the machine sent a higher amount. Enter the amount in **Max. amount per payment** and tap **Save cap**. **Check status** checks that the key is still valid at SumUp. When SumUp rejects the key, the status is **API key rejected — reconnect** — connect the account again with a new key. ## Step 3: Pairing the Solo with the machine The account from step 2 applies to the whole company. Each SumUp Solo terminal is then paired separately, always with one machine. 1. In the Hub **Settings → Payments**, check that the account is **Active**. 2. The machine that SumUp Solo should serve must be **online** in the Hub. 3. On the terminal, open **Settings → Connections → API** (Settings → Connections → Pair with API). 4. The display shows a pairing code, 8 to 9 characters. It is valid for about 5 minutes. When it expires, a new one is generated. 5. In the Hub, open **machine detail → Edit machine → Pair reader** and enter the code. The reader name is optional. After success, **Card: SumUp** appears in the detail header. The detail has a **SumUp terminal** card: online or offline status and an **Unpair** button. Pairing in the Hub by itself **does not switch the card mode** on the machine. On the machine, open Service menu → **Payments** and at the top choose **Cloud API** (instead of MDB). Without this switch the machine keeps waiting for a connected MDB terminal. ## Step 4: Test In the service menu **Payments**, in the **SUMUP CLOUD (CARD VIA INTERNET)** section, there are **Refresh status** and **Test 1 CZK (reversal)**. The test briefly shows 1 CZK on the SumUp Solo terminal and cancels the payment immediately. No goods are dispensed. A customer purchase: 1. On the customer screen, put goods in the cart and choose **Card payment**. 2. **Tap your card on the terminal** appears on the machine. The same amount is on the SumUp Solo terminal. 3. Tap the card. After approval the goods come out. 4. The sale is in the Hub in the machine detail on the **Sales** tab. **Cancel payment** on the machine ends the prompt, and nothing is charged. ## Troubleshooting | What you see | What to do | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Payments** are locked | Activate the **Pro** plan | | **Connect account** fails | Replace it with a new `sup_sk_…` key from the same account as the SumUp Solo, with Readers + Transactions + Refunds rights, and Affiliate Keys filled in | | The account is missing Affiliate Keys | **Replace account credentials** and enter the Application ID and the Affiliate Key | | Status **API key rejected — reconnect** | The key is not valid in SumUp. Create a new API key and connect the account in the Hub again | | The pairing code is not valid | Generate a new one on the SumUp Solo terminal. The Solo terminal must be on the same SumUp account as the API key | | **Pay by card** is missing on the machine | Likely causes: the SumUp Solo terminal is offline, the account is disconnected, the reader is not paired, or **Cloud API** is not selected in Service menu → **Payments** | | Part of the cart did not come out | Spiroq tries to refund the difference itself. The sale detail shows Partially refunded / Refund failed. Otherwise refund it manually in the SumUp dashboard | | SumUp Solo without internet | Use a Solo with Wi‑Fi or LTE, or stay with the MDB card |