Pagazul plugin
The fixed Dashboard renders Plugin settings from returned key_plugin configuration categories. Pagazul is in Plugin settings; its values and payment behavior depend on the provider and the project.
Pagazul settings
Pagazul settings include Pagazul 3DS enabled and Expiration time (seconds), with a maximum of 2100. This does not establish a default, minimum, required state, validation, units beyond the label, or the effect of 3DS.
No source-backed claim is made about cardholder verification, expiration, authorization, callback, transaction, reporting, order, or customer effects.
Fixed category and mutation boundary
AllSettings passes returned plugin categories to SettingsMenuOptions; a numeric category opens generic SettingsList. Config edits stage locally and Save persists changed items sequentially; type-5 image configs save immediately. API-core config routes do not establish Pagazul schema or payment behavior. The separate Developers → Plugins manager owns install/root/iframe actions. None ran.
Credentials, merchant/account IDs, callback/webhook data, transactions, customers, payments, cards, wallet/value, refunds, orders, and provider responses remain excluded.
Availability
Access to /all-settings requires level 0. Pagazul options depend on the plugin categories and configuration available to the project.
Related guides: Online payments · Developers · Plugin settings