Changelog

We recommend updating to this version of the SDK for security enhancements.

New Features

• Added optional timeoutCardWaitSeconds to startPayment, allowing integrators to configure how long the SDK waits for card presentation.
• The default card-wait timeout is now 240 seconds. Supported values are clamped between 60 and 240 seconds.
• Updated SDK build support for Android 16 / API 36.
• Updated core security, attestation, obfuscation, and payment kernel dependencies.

Fixes

• Fixed an issue where rotating the device during an active transaction could interrupt the payment flow.
• Fixed a recovery issue where transactions could keep failing with “Could not connect to the server” after a temporary network failure until the app was restarted.
• Improved NFC card-read handling by retrying after supported L1 read errors.

Integration Notes

• Existing integrations continue to work without code changes.
• Integrators can optionally pass timeoutCardWaitSeconds when starting a payment to customize the card presentation timeout.

New Features

• Added support for SUNMI devices and other Android terminals that use internal (non-external) NFC adapters

Fixes

• Prevent fatal crash when the SDK performs an authenticated network request without an AuthTokenProvider configured

Fixes

• Reliability improvements
• Improved security

Android SDK(Opens in a new tab) 7.1.0 has been released(Opens in a new tab).

Added:

• Support for target SDK 36.
• Support for Android Gradle Plugin 9.x.
• SumUpLoginContract, SumUpCardReaderPageContract, and SumUpCheckoutContract to support Activity Result API integrations. Existing onActivityResult-based integrations remain unchanged. Please refer to the documentation for more information.

Improvements:

• Reduced SDK size by approximately 8 MB.
• In offline sessions, totalApprovedAmount now includes tip amounts.

Important: SDK v7.1.0 introduces internal changes that are not backward compatible. After upgrading and running the application with v7.1.0, downgrading to an earlier SDK version is not supported.

The Swift Checkout SDK now supports configuring wallet button labels for Apple Pay and Google Pay.

This lets you align the wallet button label with the checkout context. For example, you can now use elements({ label: "book" }) for booking flows.

See the Swift Checkout SDK guide for updated setup examples using elements({ label }).

The SumUp plugin for Medusa(Opens in a new tab) is now available.

The plugin adds SumUp as a payment provider for Medusa v2 and supports:

• Hosted Checkout for redirect-based payments
• Payment Widget integrations for embedded card payments
• Refunds through SumUp transactions
• Medusa payment webhooks for asynchronous status updates

To get started, install @sumup/medusa-plugin, configure the provider in your medusa-config.ts, and enable it for the relevant region in Medusa Admin.

See the new Medusa plugin guide for setup steps, configuration options, and testing guidance.

The SumUp plugin for Vendure(Opens in a new tab) is now available.

The plugin adds SumUp as a payment integration for Vendure and supports:

• Hosted Checkout for redirect-based payments
• Widget-oriented storefront integrations that use a returned checkoutId
• Webhook-driven payment updates through Vendure’s payment flow

To get started, install @sumup/vendure-plugin, register SumUpPlugin and sumUpPaymentHandler in your Vendure config, and create a sumup payment method in Vendure Admin.

See the new Vendure plugin guide for setup steps, configuration options, and testing guidance.

Hosted Checkout is now available for Online Payments.

Hosted Checkout gives you a SumUp-hosted payment page. Your integration creates the checkout server-side, receives a hosted_checkout_url, and redirects the customer to a SumUp-hosted page to complete the payment.

This release is designed for merchants and platforms that want the fastest path to launch online payments without building or hosting their own checkout UI.

What you can do with Hosted Checkout:

• Create a checkout with hosted_checkout.enabled set to true.
• Redirect customers to the returned hosted payment page.
• Add a redirect_url so the success page links back to your website.
• Let SumUp handle the payment page and final status screens while your backend verifies the final state through the API or webhooks.

See the new Hosted Checkout guide for the full flow, SDK examples, and integration details.

Fixes

• Fixed crashes caused by no network connection or authorization errors

New Features

• Improved security
• Improved transaction speed

Important

• Starting from this version, core library desugaring(Opens in a new tab) is required

The Swift Checkout SDK now supports Apple Pay in supported non-Safari browsers, in addition to Safari.

This update makes it easier to offer Apple Pay to more customers across supported browser environments while keeping the same Swift Checkout integration flow.

What’s included in this update:

• Apple Pay is now available in supported non-Safari browsers.
• Existing Swift Checkout integrations can use Apple Pay across a broader set of browser environments.
• Apple Pay domain verification is still required for every domain where you show the Apple Pay button.

See the Swift Checkout SDK guide for setup instructions, payment request examples, and Apple Pay domain verification steps.

We have updated sandbox testing for Online Payments to use a dedicated set of test cards.

This affects all Online Payments integrations tested with sandbox merchant accounts.

What changed:

• Sandbox testing now relies on predefined test card numbers.
• The test set covers successful payments, payment failures, and 3D Secure scenarios.

Migration note: update your QA flows to use the documented test cards and expected outcomes.

See Testing online payments for setup steps, card numbers, and expected behavior.

New Features

• Improved test capabilities for the production environment
• WBC Rotation - January 2026
• The CardReadFailed -> UnexpectedOutcome error is caught, and the system smoothly retries reading the card

Android SDK(Opens in a new tab) 7.0.0 has been released(Opens in a new tab).

Added:

• successScreenTimeout in the payment builder to configure the duration of the success screen.
• getSavedCardReaderDetails() to retrieve details of the saved card reader (serial number, type, and battery percentage).
• isCardReaderConnected() to check if a card reader is currently connected.

Improvements:

Introduction of Offline transaction V2

• Changes the API and behavior about how offline transactions work.
• Explicit APIs to start and stop the offline session.
• Removal of Security Patch Validity API.
• Please have a look at OFFLINE_PAYMENTS_V2.md(Opens in a new tab) for more information.

Fixes

• Fixed an issue where the SecurePin Entry screen closes after the first digit is entered on Zebra TC77 and Honeywell CT45 devices

We have refactored the Go SDK into a flat package structure to simplify imports and make the public API easier to discover. This is a breaking change.

What Changed

• Types and services previously nested under subpackages are now exported directly from github.com/sumup/sumup-go.
• Import paths that referenced nested modules need to be updated.

Migration

Update your imports and type references to use the root package. For example:

1// Before
2import "github.com/sumup/sumup-go/checkouts"
3
4// After
5import "github.com/sumup/sumup-go"

If you run into issues, please open a ticket or let us know.

New Features

• Added clear error screens for common problems, such as attestation failures when USB debugging is turned on.

Fixes

• Fixed infinite loading when NFC is disabled or unavailable on the device.
• Security improvements.
• Small UI improvements and bug fixes.

We are happy to announce the release of our Java(Opens in a new tab) SDK. The SDK is maintained under sumup/sumup-java(Opens in a new tab) and covers all of SumUp’s public APIs.

1import com.sumup.sdk.SumUpClient;
2import com.sumup.sdk.models.CheckoutCreateRequest;
3import com.sumup.sdk.models.Currency;
4
5SumUpClient client = SumUpClient.builder().build();
6
7CheckoutCreateRequest request =
8    CheckoutCreateRequest.builder()
9        .amount(25.00f)
10        .currency(Currency.EUR)
11        .checkoutReference("ORDER-1001")
12        .merchantCode(System.getenv("SUMUP_MERCHANT_CODE"))
13        .description("Online payment via card widget")
14        .build();
15
16var checkout = client.checkouts().createCheckout(request);
17System.out.println(checkout.id());

See the repository for more examples(Opens in a new tab) and don’t hesitate to let us know if you have any questions.

We are happy to announce the release of our .NET(Opens in a new tab) SDK. The SDK is maintained under sumup/sumup-dotnet(Opens in a new tab) and covers all of SumUp’s public APIs.

1using SumUp;
2
3using var client = new SumUpClient();
4
5var merchantResponse = await client.Merchant.GetAsync();
6var merchantCode = merchantResponse.Data?.MerchantProfile?.MerchantCode
7    ?? throw new InvalidOperationException("Merchant code not returned.");
8
9var checkoutResponse = await client.Checkouts.CreateAsync(new CheckoutCreateRequest
10{
11    Amount = 10.00f,
12    Currency = Currency.Eur,
13    CheckoutReference = $"checkout-{Guid.NewGuid():N}",
14    MerchantCode = merchantCode,
15    Description = "Test payment",
16    RedirectUrl = "https://example.com/success",
17    ReturnUrl = "https://example.com/webhook",
18});
19
20Console.WriteLine($"Checkout ID: {checkoutResponse.Data?.Id}");

See the repository for more examples(Opens in a new tab) and don’t hesitate to let us know if you have any questions.

Today we are announcing the introduction of a new endpoint that lets you receive real-time updates from your connected card reader. You can see the current screen shown during the payment process and check the device status, including battery level, connectivity, and update progress.

Supported States

• IDLE – Reader ready for next transaction
• SELECTING_TIP – Waiting for tip input
• WAITING_FOR_CARD – Awaiting card insert/tap
• WAITING_FOR_PIN – Waiting for PIN entry
• WAITING_FOR_SIGNATURE – Waiting for customer signature
• UPDATING_FIRMWARE – Firmware update in progress

Device Status

• ONLINE – Device connected and operational
• OFFLINE – Device disconnected (last state persisted)

If you run into issues or need help, please contact our support team.

Fixes

• Added security improvements and bug fixes to enhance overall stability and performance of the SDK.

Fixes

• Added support for 16 KB page sizes.

Fixes

• Fixed wrong currency code in Peru.

Today we are announcing the deprecation of support for API requests that include a trailing slash at the end of the URL. While our documentation has never endorsed this pattern, we identified a small number of clients still relying on it. To ensure a smooth transition, a 2-month grace period will apply before the behavior is fully removed.

Details

• Requests using URLs that end with / (e.g., /v0.1/checkouts/) will continue to work during the grace period.
• After the grace period ends, these requests will return an error.
• Standard, documented URLs without trailing slashes (e.g., /v0.1/checkouts ) remain fully supported.

Timeline

• Deprecation announcement: 17.11.2025
• Grace period: 2 months
• Removal date: 17.01.2026

Required Action

Please consult the API documentation and update any API calls that include a trailing slash. This change typically only requires removing the final / in affected endpoints.

If you run into issues or need help identifying affected requests, please contact our support team.

Android SDK(Opens in a new tab) 6.0.0 has been released(Opens in a new tab).

Offline payments

• Introduces Offline payments with Solo lite, please refer to the dedicated section in OFFLINE_PAYMENTS.md(Opens in a new tab) for more information.
  • Please contact us through the contact form to enable offline payments on your SumUp merchant account.

Added:

• Payment intent now also returns the card reader model and firmware version in new response fields SumUpAPI.Response.CARD_READER_MODEL and SumUpAPI.Response.CARD_READER_FIRMWARE_VERSION at the end of every transaction.

Improvements:

• Renames package of TransactionInfo: com.sumup.merchant.reader.models.TransactionInfo > com.sumup.checkout.core.models.TransactionInfo
• Renames package of SumUpState: import com.sumup.merchant.api.SumUpState > import com.sumup.reader.sdk.api.SumUpState
• Miscellaneous bug fixes and enhancements.

Updates about the technical stack:

• Minimum supported targetSDK is 35
• Minimum Kotlin is upgraded to 1.9.0
• Minimum Kotlin Coroutine is upgraded to 1.8.0
• Minimum Hilt is upgraded to 2.51.1
• Minimum Moshi is upgraded to 1.15.0
• Minimum AppCompat is upgraded to 1.7.0
• Minimum AndroidX Annotation is upgraded to version 1.8.0
• Minimum AndroidX Activity is upgraded to version 1.9.1
• Minimum AndroidX Fragment is upgraded to version 1.7.1
• Minimum AndroidX Lifecycle is upgraded to version 2.8.1
• Minimum AndroidX Browser is upgraded to version 1.4.0
• Minimum AndroidX Navigation is upgraded to version 2.7.7
• Minimum Material Components is upgraded to 1.12.0
• Minimum Play Services Location is upgraded to 21.3.0- Minimum AGP is upgraded to 8.8.0
• Building with AGP 8.8.0 and Java 17
• Introduces Jetpack Compose BOM version 2023.06.01
• Requires desugar_jdk_libs version 2.1.5

Fixes

• Decreased the SDK size by removing unused resources.
• Fixed an issue where the testing SDK build would not initialize.

We are happy to announce the release of our Rust(Opens in a new tab) SDK. The SDK is maintained under sumup/sumup-rs(Opens in a new tab) and covers all of SumUp’s public APIs. For full documentation, see https://docs.rs/sumup(Opens in a new tab).

1use sumup::Client;
2
3#[tokio::main]
4async fn main() -> Result<(), Box<dyn std::error::Error>> {
5    let client = Client::default();
6
7    let merchant_code = std::env::var("SUMUP_MERCHANT_CODE")
8        .expect("SUMUP_MERCHANT_CODE environment variable must be set");
9
10    let readers = client
11        .readers()
12        .list(&merchant_code)
13        .await
14        .expect("couldn't list merchant's readers");
15
16    let reader = readers
17        .items
18        .first()
19        .expect("merchant doesn't have any paired card readers");
20
21    let checkout_reference = format!("checkout-{}", uuid::Uuid::new_v4());
22
23    println!("Creating checkout with reference: {}", checkout_reference);
24
25    match client
26        .readers()
27        .create_checkout(
28            &merchant_code,
29            &reader.id,
30            sumup::CreateReaderCheckoutRequest {
31                total_amount: sumup::Money {
32                    currency: "EUR".into(),
33                    minor_unit: 2,
34                    value: 1000,
35                },
36                affiliate: None,
37                card_type: None,
38                description: None,
39                installments: None,
40                return_url: None,
41                tip_rates: None,
42                tip_timeout: None,
43            },
44        )
45        .await
46    {
47        Ok(_) => {
48            println!("✓ Checkout created successfully!");
49        }
50        Err(e) => {
51            eprintln!("✗ Failed to create checkout: {}", e);
52        }
53    }
54
55    Ok(())
56}

See the repository for more examples(Opens in a new tab) and don’t hesitate to let us know if you have any questions.

New Features

• Added support of Online Pin SCA (Strong Customer Authentication).
• Added card data to PaymentEvent.TransactionDone event: card type, card scheme, last four digits, and merchant code.
• Transparent attestation process. The SDK now returns error details if attestation fails in PaymentEvent.TransactionFailed event. This helps developers understand and resolve attestation issues more effectively.
• API changes to make it more concise. Now TapToPay.startPayment() function returns Flow<PaymentEvent> instead of Flow<Result<PaymentEvent>>.

New Features

• Added Products to TapToPay.startPayment method.
• Enabled periodic monitoring and attestation.
• Now SDK uses Google Trusted Time API.

Fixes

• Fixed a crash that occurred when attempting to make a payment without explicitly setting skipSuccessScreen parameter.
• Fixed a bug in Pixel 8 and Pixel 9 devices with Android 16 where the payment would immediately fail a transaction with timeout error.

Fixes

• Fixed a bug with payment availability when using OkHttp 5.0.0 or higher.

We are happy to announce the release of our Python(Opens in a new tab) SDK. The SDK is maintained under sumup/sumup-py(Opens in a new tab) and covers all of SumUp’s public APIs. sumup-py support both synchronous and asynchronous calling convention.

1import os
2import asyncio
3
4from sumup import AsyncSumup
5from sumup.readers.resource import CreateReaderCheckoutBody, CreateReaderCheckoutBodyTotalAmount
6
7
8async def main():
9    client = AsyncSumup()
10    merchant_code = os.environ["SUMUP_MERCHANT_CODE"]
11
12    readers = await client.readers.list(merchant_code)
13    reader = readers.items[0]
14
15    checkout = await client.readers().create_checkout(
16        merchant_code,
17        reader.id,
18        CreateReaderCheckoutBody(
19            total_amount=CreateReaderCheckoutBodyTotalAmount(
20                currency="EUR",
21                minor_unit=2,
22                value=1000,
23            ),
24            description="sumup-py card reader checkout example",
25        ),
26    )
27
28    print(checkout)
29
30
31if __name__ == "__main__":
32    asyncio.run(main())

See the repository for more examples(Opens in a new tab) and don’t hesitate to let us know if you have any questions.

Fixes

• Miscellaneous bug and crash fixes

Fixes

• NoBeanFoundDefinitionError exception that occurred in some cases when starting a payment
• Miscellaneous bug and crash fixes

New Features

• Faster Transactions – Reduced latency when initiating transactions, resulting in faster checkout.
• Mitigated Threats Filter – Attestation now excludes resolved threats for smoother processing and less transaction failures.
• Affiliate Key Support – Added support for affiliate key integration.
• Success Screen Skip Flag – New flag to bypass the success screen.
• Support for targetSDK 35
• Client-Side Certificate Verification – Enhanced security with device certificate checks during attestation.
• Pre-PIN Attestation – Attestation is initiated before displaying the PIN screen to enhance security.

Fixes

• Resolved an issue during TapToPay initialization.

We are happy to announce the release of our TypeScript(Opens in a new tab) / JavaScript(Opens in a new tab) SDK. The SDK is maintained under sumup/sumup-ts(Opens in a new tab) and covers all of SumUp’s public APIs.

The SDK provides easy access to SumUp APIs:

1import SumUp from "@sumup/sdk";
2
3const client = new SumUp({
4  apiKey: process.env.SUMUP_API_KEY,
5});
6
7async function main() {
8  const merchantCode = process.env.SUMUP_MERCHANT_CODE;
9  if (!merchantCode) {
10    console.warn(
11      "Missing merchant code, please specify merchant code using SUMUP_MERCHANT_CODE env variable.",
12    );
13    return;
14  }
15
16  const { items: readers } = await client.readers.list(merchantCode);
17  if (!readers.length) {
18    console.warn("No readers found, please pair a card reader first.");
19    return;
20  }
21
22  const reader = readers[0];
23
24  const checkout = client.readers.createCheckout(merchantCode, reader.id, {
25    total_amount: {
26      // Must match the currency of your merchant account
27      currency: "EUR",
28      minor_unit: 100,
29      value: 500,
30    },
31  });
32
33  console.info({ checkout });
34}
35
36main();

See the repository for more examples(Opens in a new tab) and don’t hesitate to let us know if you have any questions.

Fixes

• Fixed the class duplication issue occurring after obfuscation.

Fixes

• Mitigated threats are now filtered out during attestation. If a threat has "mitigated": true, it is excluded from the threat list that is used to determine whether the COTS is attested.

New Features

• New events of the payment process: card requested, card presented, CVM requested, CVM presented - New PaymentException types

Fixes

• Cleanup PAN data from memory
• Disable NFC for other apps during the payment process. - Handling empty candidates list in payment processing

We are happy to announce the beta release of our Go(Opens in a new tab) SDK. The SDK is maintained under sumup/sumup-go(Opens in a new tab) with its acompanying documentation at pkg.go.dev(Opens in a new tab).

The Go SDK provides easy access to SumUp APIs:

1package main
2
3import (
4	"context"
5	"log"
6
7	"github.com/sumup/sumup-go"
8)
9
10func main() {
11	ctx := context.Background()
12	client := sumup.NewClient()
13
14	checkout, err := client.Checkouts.Create(ctx, sumup.CheckoutsCreateParams{
15		Amount:            123,
16		CheckoutReference: "TX000001",
17		Currency:          sumup.CurrencyEUR,
18		MerchantCode:      "MK0001",
19	})
20	if err != nil {
21		log.Printf("[ERROR] create checkout: %v", err)
22		return
23	}
24
25	log.Printf("[INFO] checkout created: id=%q, amount=%v, currency=%q", *checkout.ID, *checkout.Amount, string(*checkout.Currency))
26
27	checkoutSuccess, err := client.Checkouts.Process(ctx, *checkout.ID, sumup.CheckoutsProcessParams{
28		Card: &sumup.Card{
29			Cvv:         "123",
30			ExpiryMonth: "12",
31			ExpiryYear:  "2023",
32			Name:        "Boaty McBoatface",
33			Number:      "4200000000000042",
34		},
35		PaymentType: sumup.ProcessCheckoutPaymentTypeCard,
36	})
37	if err != nil {
38		log.Printf("[ERROR] process checkout: %v", err)
39		return
40	}
41
42	success, _ := checkoutSuccess.AsCheckoutSuccess()
43	log.Printf("[INFO] checkout processed: id=%q, transaction_id=%q", *success.ID, string((*success.Transactions)[0].ID))
44}

See the repository for more examples(Opens in a new tab) and don’t hesitate to let us know if you have any questions.

Android SDK(Opens in a new tab) 4.3.0 has been released(Opens in a new tab).

Solo USB (Beta)

The Solo card reader now supports connecting and transacting over USB cable. The minimum required Solo software version that supports the USB mode is 3.3.17.2.

If this version (3.3.17.2) is not yet available on your Solo when connected via Bluetooth, you can switch it to standalone mode (Menu -> Connection -> WiFi), login directly on the Solo, and update it to the latest version.

Solo USB is under beta phase which means that the feature still requires some optimization to ensure full stability.

Known limitations: currently, if the USB cable is unplugged, the USB permission on the mobile device will need to be regranted. As of now, Solo is not able to wake up automatically from sleep mode. A connection needs to be reestablished from

Removed:

• Dropping support for Android 7 (API 25) and below

New features:

• Accept payments with alternative payment methods (Follow guides for enabling in your account)
• Accept card payments with installments in BR.
• Accept payments with Apple Pay.
• Support for WooCommerce stock management feature
• New user experience configuration: merchant can choose to open the payment option in a pop-up instead of the checkout page.

Improvements:

• Easier reconciliation of orders between WooCommerce and SumUp dashboard:
• Display WooCommerce order Id on SumUp Sales History.
• Added transaction code to order description on WooCommerce
• Added checkout_id in order notes to improve customer support
• New settings screen for easier setup
• Multiple code maintenance improvements.
• Support for Wordpress 6.3
• Require PHP version 7.2 or greater.

Bugs fixed:

• Errors during checkout that caused duplicated payment.
• Issues loading payment methods on checkout.
• Fixed issue with customer creation during checkout that caused duplicated payment.