Manage platform settings

Public help

DocumentPayment high-riskprovider configuration may come from both database-backed settings such as fees, taxes, SMTP, map keys, verification, and maintenanceLaravel mode.

configuration/service

Internal guidance

Use this page as an internal operating guide.binding. Do not exposeassume admin-onlyan proceduresempty topayment_provider_configurations publictable users.

Implementationmeans note

all payments are disabled. Confirm the relatedactive Filamentprovider resource, standalone page, report, model, or legacy fallbackpath before treatingchanging theplatform workflowpayment as live.settings.

Implementation status

Expected behaviorStatusSurfaceManual check Internal workflow exists and is reachable.Needs VerificationAdmin panel / BackendOpen the matching admin page and perform a safe read-only check.Risky actions have review steps.Needs VerificationAdmin processConfirm approval, refund, payout, or setting changes require the right role.

Verification checklistevidence

• Open

  Admin And Internal Finance Surface.

  Last verified

  Verified against the relatedstaging adminwebsite page.

• Confirmon permissions.
• Run2026-06-12. aMobile safeapps testwere ornot read-only review.
• Record any mismatchtested in this article.

Gaps / notes

• Internal pages need role-specific screenshots later.
• Do not publish these pages publicly without permission review.

pass.