sumup-best-practices
Installation
SKILL.md
Choose a SumUp Integration
Start with the user's constraints and existing stack. Recommend the simplest supported path that meets them; preserve an explicit integration choice unless evidence shows it cannot satisfy the requirement. Use the current documentation index to verify availability and product-specific requirements.
Choose by requirement
| Requirement | Default choice and deciding constraint |
|---|---|
| Online checkout with redirect UX | Hosted Checkout; the backend creates the checkout and redirects to its hosted URL. |
| Embedded website payment collection | Card Widget; SumUp provides the payment interface and authentication flow. |
| Website wallet buttons | Swift Checkout JavaScript SDK; verify browser/wallet and merchant-domain requirements. |
| React Native payment sheet | React Native Checkout; check the current alpha API and use a public merchant key in the app. |
| Save cards and charge later | Customers plus tokenization; the stored token belongs to its customer and each later charge is a separate attempt. |
| Native mobile app controls a reader | iOS Terminal or Android Reader SDK; check supported devices and platform permissions. |
| Contactless payment on the phone | Tap to Pay on iPhone or the separate Android Tap-to-Pay SDK; verify device eligibility and access requirements. |
| POS or backend controls Solo | Cloud API; design around asynchronous transaction results. |
| Existing app must hand off to the SumUp app | Payment Switch; retain it when that handoff is a requirement. |
A custom backend may still use hosted, widget, or SDK payment collection. Do not introduce direct card-data handling just because the application needs custom order logic.