When you work with your Commerce implementation, you can review and modify the payment configuration.
When you modify the workflow configuration, make sure you properly set user permissions for the Payment component.
Payment workflow relies on a Symfony Workflow. Each transition represents a separate payment step.
Default payment workflow configuration¶
The default payment workflow is called
To see the default workflow configuration, in your project directory, go to:
You can replace the default workflow configuration with a custom one if needed.
Custom payment workflows¶
You define custom workflow implementations under the
They must support the
If your installation supports multiple languages, for each place in the workflow, you can define a label that is pulled from an XLIFF file based on the translation domain setting.
You can also define colors that are used for status labels.
primary_color key defines a color of the font used for the label, while the
secondary_color key defines a color of its background.
Additionally, you can decide whether users can manually transition between places.
You do this by setting a value for the
If you set it to
true, a button is displayed in the UI that triggers the transition.
Otherwise, the transition can only be triggered by means of the API.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
After you configure a custom workflow, reference it with
ibexa.repositories.<your_repository>.payment.workflow, so that the system can identify which of your workflows handles the payment process.
1 2 3 4 5
Configure payment methods¶
You can define the payment methods in the UI.
There is only one default payment method type available:
offline, but you can add custom ones.