Adyen authorization and capture deserve different order states

Adyen's webhook reference distinguishes authorization from capture, and capture-event behavior depends on the configured flow, including automatic capture settings.

For the Adyen integration, test the payment lifecycle in the test environment and map each relevant event to an explicit order state. Do not infer settlement from a browser redirect or assume every setup emits the same capture notification. Reconcile the configured payment flow with the events your application actually expects.