The payment result was not applied
An interrupted or rejected notification can prevent the payment extension from recording the provider’s result.
Shopware 6 · Payment recording, not fulfillment automation
Shopware Payment Captured but Order Not Updated
This guide covers a supported financial scenario: Stripe or PayPal has captured money, but Shopware has not recorded that payment correctly. If Shopware already records the payment as paid and the next business task is missing, that is a separate workflow investigation.
Why a captured payment may not update the order
Locate the missing payment update before investigating a later business transition.
A different attempt is being inspected
The order’s transaction history, payment reference or account mode may not correspond to the capture you found.
The payment is already recorded
If the payment state is already paid, a missing flow, invoice or warehouse action is an operational issue, outside the financial check.
Diagnosis path: not recorded or not processed?
- 1
Is there a capture at Stripe or PayPal for this order?
If yes: Money arrived — go to question 2.
If no: Then the payment state Open is correct: no money was collected.
- 2
Is the payment state of the latest transaction Paid?
If yes: The payment is recorded. If the order is not processed further, check the Flow Builder, ERP or warehouse — an operational issue.
If no: Go to question 3.
- 3
Does the order have several transactions (a new one per payment attempt)?
If yes: Compare the capture with the transaction it belongs to — the paid one may be an older attempt.
If no: Go to question 4.
- 4
Do the payment extension’s logs (var/log) show the provider’s notification?
If yes: It arrived but was not applied — look for the error next to it.
If no: A delivery problem: webhook address, sales channel domain, firewall.
Trace capture → payment transaction → recorded payment
- Open the Shopware order and distinguish payment, order and delivery histories. Identify the transaction whose payment state is in question.
- Verify the matching Stripe or PayPal capture independently, including amount, currency, account and mode. Authorization alone is not capture.
- Compare provider references and the payment extension’s notification/error history. Establish whether the confirmed result reached the correct transaction.
- If Shopware already records the payment correctly, investigate the responsible Flow Builder action or external system separately. Do not use a status label as proof of an invoice, e-mail or warehouse handover.
Official references for the checks above:
Restore the payment update without replaying the purchase
Resolve the confirmed cause
For a missing payment update, repair the payment extension’s event path using its documented procedure. Before retrying an event, check that the original capture is not repeated and that processing is safe for duplicate delivery.
Verify the result
Re-read the original provider operation and Shopware payment transaction. Confirm that payment was recorded once. Any later order flow or external fulfillment outcome must be verified separately; changing the order to Done is not evidence of completion.
The supported check: capture not recorded by the store
For covered Shopware payments with reliable references and fresh sources, Business Watchdog can identify an independent capture that the store has not recorded after the grace period. It reads the evidence and leaves corrective actions to you.
- Order and payment data are compared only within the connected, supported coverage.
- Missing or stale data is shown as incomplete, not as a healthy result.
- Alerts can be delivered by e-mail or Telegram when the corresponding supported rule applies.
Where the coverage stops
Business Watchdog does not currently provide end-to-end monitoring of post-payment processing obligations. It does not verify every Flow Builder action, invoice, confirmation e-mail, warehouse handover or shipment. An open but paid order is not automatically an incident.
How to connect monitoring safely
- Connect Shopware and the relevant supported provider, then confirm payment-reference coverage and synchronization.
- Use the financial checks to review payment discrepancies. Keep operational logs and existing fulfillment monitoring for the later stages.
- Review the Security page before granting access. Monitoring reads evidence; it does not execute your order flows or change statuses.
PayPal cannot provide strictly read-only credentials; Business Watchdog restricts its own requests and explains this before connection. Read the security and access details
Questions worth separating
What if my Shopware order is already paid but not processed?
That is not automatically a financial incident. The service does not verify the later processing obligation; inspect the configured flow and destination system directly.
Does this monitor every paid order through fulfillment?
No. This page covers payment-recording discrepancies. Invoices, confirmation e-mails, warehouse handover and shipment are not proven by the current financial checks.
Related troubleshooting guides
Keep the next discrepancy visible
Connect your store and the supported payment provider. Review the coverage and first synchronization before relying on the results. Features and limits depend on your plan.