mcpField
U
upgrade-sumup

upgrade-sumup

github.com/sumupDevelopment553 installsUpdated 1d ago
Repository

About upgrade-sumup

A migration skill for teams upgrading SumUp SDKs, integrations, and API usage. It covers version inventory, breaking-change analysis, validation, and staged rollout with rollback planning.

Key features

  1. 01SDK and endpoint upgrade coverage
  2. 02Pre-upgrade inventory checklist
  3. 03Breaking-change comparison guidance
  4. 04Sandbox payment validation steps
  5. 05Staged rollout and rollback planning

Use cases

  1. 01Upgrading a SumUp SDK version
  2. 02Replacing deprecated SumUp endpoints
  3. 03Preparing payment integrations for migration

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sumup/sumup-skills --skill upgrade-sumup

After installing, type/upgrade-sumupin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlassets/small-logo.svg

Details

From the project README

SumUp Upgrade and Migration Guide

Knowledge and APIs can change. Always prefer current official docs and release notes.

  • Docs root: https://developer.sumup.com/
  • LLM entrypoint: https://developer.sumup.com/llms.txt

Use this skill when the request is about upgrades, version bumps, deprecations, or migrations.

Supported Upgrade Targets

  • Node: @sumup/sdk
  • Go: sumup-go
  • Python: sumup
  • PHP, Java, Rust, .NET SDK/client integrations
  • iOS Terminal SDK
  • Android Reader SDK
  • Swift Checkout SDK
  • React Native SDK
  • Checkouts API and related webhook/3DS endpoint usage

Upgrade Workflow

1) Pre-upgrade inventory

Capture:

  • Current SDK/library versions by service/app.
  • All used SumUp endpoints and fields.
  • Auth mode (API key/OAuth), scopes, and webhook signature setup.
  • Environments impacted (sandbox, staging, production).
2) Breaking-change diff

For each SDK or endpoint migration:

  • Compare changelog and migration notes.
  • Identify renamed/removed fields, enums, and callback signatures.
  • Identify behavior changes in async/payment status semantics.
  • Identify deprecated endpoints and required replacements.
3) Migration implementation
  • Upgrade one surface at a time (server SDK, then mobile SDK, then UI integration).
  • Keep a compatibility adapter where necessary to isolate application code from SDK changes.
  • Replace deprecated endpoints with current equivalents, preferring endpoints that accept merchant_code where applicable.
  • Keep webhook verification and idempotency logic unchanged unless required.
4) Post-upgrade validation
  • Run happy path payment in sandbox.
  • Run deliberate failure (amount = 11) and verify order state remains unpaid.
  • Verify 3DS redirect/challenge and return handling.
  • Verify webhook retries and idempotent processing.
  • Verify duplicate reference behavior and reconciliation fields.
5) Rollout and rollback
  • Roll out in stages (internal -> low-volume -> full traffic).
  • Add release toggles where practical.
  • Keep previous version rollback path ready until metrics are stable.

Migration Checklist

  • All deprecated SumUp endpoints removed from active code paths.
  • SDK major/minor versions pinned consistently across services/apps.
  • Any generated API clients re-generated and committed.
  • Integration tests updated for new response shapes.
  • Runbook updated with new status/error codes.
  • Monitoring alerts reviewed for new failure signatures.

Required Response Contract

Every upgrade answer should include:

  1. Current state summary and target version.
  2. Breaking changes and affected code surfaces.
  3. Minimal safe migration sequence.
  4. Validation plan including forced-failure path.
  5. Rollback strategy and go/no-go criteria.

Comments

Markdown supported