Skip to content
mcorucu docs
AutoCore1.0.0-rc.1 · Release Candidate
1.0.0-rc.1 · Release Candidate1 min read

Payment Configuration

Configure payment provider readiness while preserving the disabled and financially gated Commercial 1.0 boundary.

Payment configuration is layered: a provider may be registered, configured, enabled, verified, or active. AutoCore’s international edition sets financialFlowsEnabled false; providers are not active by default. The environment validator rejects mock payment in production.

Source-backed fields include PAYMENT_PROVIDER_DEFAULT, PAYMENT_RETURN_BASE_URL, mock controls, Stripe controls, iyzico controls, and PayTR controls. Credentials, webhook secrets, and provider approval remain external.

Verification

Confirm the edition financial-flow gate, provider status, currencies, webhook verification, and checkout behavior. Never infer payment success from configuration presence.

Related articles

Currency ConfigurationConfigure the installation currency and distinguish display settings from payment-provider activation.External-Service RequirementsIdentify the external services that remain operator-configured around the AutoCore application package.Payment Provider and ReadinessUnderstand AutoCore provider adapters, configuration states, readiness checks, and payment boundaries.