Skip to content

docs: explain payment confirmation and order fulfillment #1078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
matoous wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: explain payment confirmation and order fulfillment #1078

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
319edbe
docs: verify payments before fulfilling orders
matoous Oct 26, 2026
43b2f39
docs: add payment confirmation examples for every SDK
matoous Oct 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/docs/online-payments/checkouts/card-widget.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,8 @@ Strong Customer Authentication (SCA) may apply to European online payments. The

</Steps>

Use `onResponse` to refresh the order status from your backend. Before fulfillment, [verify the checkout and update the order once](/online-payments/guides/confirm-payment/). Logging a callback or showing a success message in the browser does not update or verify your backend order.

## Configurations

The Payment Widget allows you to customize certain properties on the payment form, as listed below. To override the default settings, add your own configuration property-value pairs to the `SumUpCard.mount` method.
Expand Down
4 changes: 3 additions & 1 deletion src/content/docs/online-payments/checkouts/hosted-checkout.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ This is the lowest-effort way to launch an online checkout while keeping payment
1. Create a checkout and set `hosted_checkout.enabled` to `true`.
2. Store the returned checkout `id` and `hosted_checkout_url`.
3. Redirect the customer to `hosted_checkout_url`, or share that URL in the flow you are building.
4. After the customer completes the payment, verify the final result through the API or with [webhooks](/online-payments/webhooks/).
4. After the customer completes payment, [retrieve and verify the checkout on your server](/online-payments/guides/confirm-payment/). Use webhooks to trigger that verification even if the customer closes the browser.

<Callout type="note" title="Note">
A Hosted Checkout session is available for 30 minutes. After that, unpaid sessions show an expired or not found page.
Expand Down Expand Up @@ -216,6 +216,8 @@ If you want the success page to include a button back to your website, set `redi

If `redirect_url` is present, the success page shows a button that sends the customer back to your website.

To receive server notifications as well, set `return_url` to your public HTTPS webhook endpoint. It is separate from the browser-facing `redirect_url`. Follow the [payment confirmation guide](/online-payments/guides/confirm-payment/).

## Handle Payment Outcomes

Hosted Checkout covers the customer-facing flow from payment page to final status page. Depending on the outcome, customers see different pages:
Expand Down
Loading
Loading