Upgrade a SumUp Integration

Establish the target

Inspect the affected dependency manifests, lockfiles, client configuration, and used endpoints. Honor the user's requested version. When asked for the latest release, verify it through the SDK's official repository or registry and SumUp release notes; do not treat a bundled version example as current.

State the selected target and source. If current release information is unavailable, identify what remains unverified rather than guessing a version. Preserve stable versus prerelease choices and avoid downgrades or unrelated package upgrades unless requested.

Compare the affected contracts

• Read release and migration notes between the installed and target versions. Verify method names, request models, response fields, error types, and runtime/toolchain requirements against the target SDK.
• Check endpoint deprecations, merchant parameters, permissions, callback protocols, and asynchronous result behavior only where the integration uses them.
• Treat Swift Checkout as a web JavaScript SDK and Android Tap-to-Pay as a separate package from the Android Reader SDK. React Native Checkout has an alpha API; verify the selected release's signatures.
• When crossing Android Tap-to-Pay 1.1.7, check its required affiliate metadata, removed shouldDisplayReceipt field, and changed R8/ProGuard rules. Read the exact release notes rather than applying those changes to unrelated SDKs.

Find current SDK guides through the documentation index and endpoint contracts through the API index or OpenAPI specification.

Implement and validate the migration