sumup-best-practices
Pick the right SumUp integration path and apply security best practices. Use when deciding between Hosted Checkout, Card Widget, Checkouts API, mobile SDKs, terminal SDKs, or Cloud API; choosing API key vs OAuth vs restricted keys; or reviewing SumUp integration security.
Install
With your agent
Install OMGSkills skill "sumup/sumup-skills:skills/sumup-best-practices" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/sumup/sumup-skills /tmp/sumup-skills && ln -s /tmp/sumup-skills/skills/sumup-best-practices ~/.claude/skills/sumup-best-practicesFrom README
SumUp Integration Decisions and Best Practices Knowledge and APIs can change. Always prefer the latest SumUp docs in markdown format over stale memory. Docs root: https://developer.sumup.com/ LLM entrypoint: https://developer.sumup.com/llms.txt Use this skill for architecture and security decisions, not implementation walkthroughs. Quick Decision Tree Start Here Classify the request: terminal, online, or hybrid. Choose the lowest-complexity viable path first: Prefer Hosted Checkout or Card Widget before custom orchestration. Prefer Cloud API for non-native Solo control. Select auth model: API key for single-merchant server integrations. OAuth 2.0 for delegated or multi-merchant apps. Confirm restricted access and affiliate prerequisites: payments scope activation where needed. Affiliate Key plus app/bundle identifier alignment for card-present.