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.
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)
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.
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.