사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/sumup/sumup-skills --skill sumup-best-practices시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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.
Choose credentials and verify payment state
- Use a secret API key on the server for its owning merchant. Use OAuth when other merchants authorize the application. Check endpoint permissions and any required OAuth scope verification in the authorization guide.
- Public
sup_pk_merchant keys belong in supported checkout clients; secretsup_sk_keys and OAuth client secrets do not. Sandbox behavior follows the authenticated merchant, not an assumed key-prefix tier. - Terminal integrations need the Affiliate Key and matching app identifiers required by that SDK or API.
- Match the checkout/transaction to the expected merchant, order reference, amount, and currency. Retrieve final payment state before fulfillment; callback delivery and HTTP success are not enough.
- Resolve an uncertain payment or refund before repeating it. A unique reference helps reconciliation but is not a guarantee of server-enforced idempotency.
- Make repeated notifications and status reads safe for order updates. Follow the selected callback protocol rather than assuming every SumUp webhook is signed.
For a selection question, explain the deciding constraint and credential requirements. For a security review, lead with concrete findings and evidence, and describe validation for the affected behavior. Add alternatives or a launch checklist only when they help the requested decision.
For implementation, use the sumup skill if installed, or continue with the selected flow's current documentation. General account reporting and MCP setup do not require an integration-selection exercise.