API Changelog
Hosted Checkout
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.enabledset totrue. - Redirect customers to the returned hosted payment page.
- Add a
redirect_urlso 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.
Online Payments Test Cards
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.
Cloud API
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 transactionSELECTING_TIP– Waiting for tip inputWAITING_FOR_CARD– Awaiting card insert/tapWAITING_FOR_PIN– Waiting for PIN entryWAITING_FOR_SIGNATURE– Waiting for customer signatureUPDATING_FIRMWARE– Firmware update in progress
Device Status
ONLINE– Device connected and operationalOFFLINE– Device disconnected (last state persisted)
If you run into issues or need help, please contact our support team.
Deprecation of Trailing Slashes in URLs
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.