Source
Catalogue & checkout — found from sitemap — Shopware
Checked for Shopware on 5 Oct 2026
- Page
- https://developer.shopware.com/docs/concepts/commerce/checkout-concept/payments.html
- Checked
- 5 Oct 2026, 04:56 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:91b3387c615633ecfcdbc009df49781970ae2d2d0d04601fc291ec0fe6789a65
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Payment handlers Report an error
“At its core, the payment system is composed of payment handlers. These extend Shopware to support multiple different payment types. A list of all payment handlers is stored in the database.”
-
Payment flow steps Report an error
“The payment and checkout flow consist of two essential steps: Placing the order and Handling the payment”
-
Order multiple transactions Report an error
“An order can have multiple transactions, but only a single one is created in this step.”
-
Payment handler types Report an error
“There are two types of payment handlers in Shopware: Synchronous payment”
-
Async redirect headless Report an error
“In the headless scenario, Shopware returns the redirect URL within the API response so that the frontend can perform the redirect.”
-
Finalize transaction route Report an error
“It is triggered by the callback URL (which points to /payment/finalize-transaction) that has been provided to the payment gateway in step 3.1.”
-
Context endpoint payment method Report an error
“The current payment method is stored in the user context, which can be manipulated by calling the corresponding route or endpoint (/store-api/context).”
-
State machine transactions Report an error
“A payment is applied to a transaction of an order. As with any order change, this is done through the state machine.”
-
Payment states not standardized Report an error
“The actual implementation of payment integrations differs between providers. Therefore, our specification does not include any guidelines about payment states or specific API calls to be made.”
-
Session not used headless Report an error
“The session should not be used in headless payment integrations.”
-
Async steps optional Report an error
“3.2 Payment execution on gateway (optional)”
Scores citing this record
- The B2B Seller Catalogue & checkout
- The B2B Seller Extensibility & developer surface
- The Data Protection Officer Catalogue & checkout
- The Data Protection Officer Extensibility & developer surface
- The Developer Catalogue & checkout
- The Merchant Catalogue & checkout
- The Merchant Extensibility & developer surface
- The Operations Lead Catalogue & checkout
- The Operations Lead Extensibility & developer surface
- The Skeptic Catalogue & checkout
- The Skeptic Extensibility & developer surface