Help us improve
Share bugs, ideas, or general feedback.
From sumup
Guides SumUp payment integrations for terminal (card-present) and online (card-not-present) checkouts using SDKs, APIs, Card Widget, and Cloud API. Useful for implementing or debugging checkout creation, payments, reader pairing, and OAuth setup.
npx claudepluginhub sumup/sumup-skills --plugin sumupHow this skill is triggered — by the user, by Claude, or both
Slash command
/sumup:sumupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Knowledge and APIs can change. Always prefer the latest SumUp docs in markdown format over stale memory.
agents/openai.yamlassets/large-logo.pngassets/small-logo.svgreferences/README.mdreferences/android-reader-sdk/README.mdreferences/android-tap-to-pay-sdk/README.mdreferences/apm/README.mdreferences/checkout-playbook.mdreferences/checkout-widget/README.mdreferences/checkouts-api/README.mdreferences/cloud-api/README.mdreferences/dotnet/README.mdreferences/go/README.mdreferences/ios-terminal-sdk/README.mdreferences/java/README.mdreferences/nodejs/README.mdreferences/payment-switch/README.mdreferences/php/README.mdreferences/python/README.mdreferences/react-native-sdk/README.mdIntegrates Stripe, PayPal, Square for checkout flows, subscriptions, webhooks, and PCI compliance. Guides secure payment processing, error handling, and best practices for billing features.
Guides PAYUNi payment gateway environment setup across PHP, Node.js, Python backends and routes to checkout/query/webhook skills by user need.
Guides Stripe API choices for payments (Checkout Sessions vs PaymentIntents), Connect Accounts v2, billing/subscriptions, Treasury accounts, Payment Element, and deprecated migrations.
Share bugs, ideas, or general feedback.
Knowledge and APIs can change. Always prefer the latest SumUp docs in markdown format over stale memory.
https://developer.sumup.com/https://developer.sumup.com/llms.txthttps://developer.sumup.com/terminal-payments/cloud-api/index.mdUse this skill to implement end-to-end SumUp checkouts for:
Need to accept a payment?
├─ In-person (card-present) → terminal
│ ├─ Native mobile app + direct reader flow → terminal/mobile (iOS SDK or Android Reader SDK)
│ ├─ Non-native POS/backend controls Solo reader → terminal/platform-agnostic (Cloud API)
│ └─ Legacy app handoff to SumUp app explicitly required → terminal/legacy-lightweight (Payment Switch)
└─ Online (card-not-present) → online
├─ Fastest secure integration, hosted/embedded UI acceptable → online/low-complexity (Card Widget)
└─ Custom orchestration and async lifecycle handling required → online/custom (Checkouts API + 3DS + webhooks)
terminal: in-person card-present paymentonline: e-commerce/web/app card-not-present paymenthybrid: both (for example, web checkout + in-store Solo)terminal/mobile: iOS SDK or Android Reader SDKterminal/platform-agnostic: Cloud API with Solo readersterminal/legacy-lightweight: Payment Switchonline/low-complexity: Card Widgetonline/custom: Checkouts API + 3DS + webhooksreferences/checkout-playbook.md.references/README.md and open only the single most relevant entrypoint for the request.checkout_reference, foreignTransactionId, or equivalent) to prevent duplicates and improve reconciliation.merchant_code as an explicit parameter when equivalent alternatives exist.next_step redirect flowEvery solution should state:
merchant_code-accepting endpoints.amount = 11 in test mode).references/README.md to pick the right reference file.