Payment Provider and Readiness
Understand AutoCore provider adapters, configuration states, readiness checks, and payment boundaries.
AutoCore uses provider-neutral payment records and adapter interfaces. Current
provider keys include mock, iyzico, paytr, stripe, and paypal, but
edition configuration can disable providers and live operation remains an
external configuration and approval boundary.
Configuration states
PaymentProviderConfiguration records disabled, unconfigured, configured,
verification_failed, verified, or suspended, plus test/live mode,
currencies, market country, safe public references, secret environment
references, webhook state, and verification timestamps.
Readiness means that the required configuration and feature gates are satisfied for a supported flow. It does not mean merchant approval, live transaction activation, or legal readiness.
Payment lifecycle boundaries
Orders and attempts have separate status models. Provider callbacks create deduplicated webhook records, verify signatures through the provider adapter, and only then can a verified payment move the internal order toward paid and fulfilment states. Refunds and reconciliation retain their own status and audit history.
Explicit limitations
Providers are not active by default. Credentials remain external secrets. The current AutoCore edition disables financial flows and keeps Stripe/PayPal as planned providers in the edition registry; the mock provider is for local/test use. No real payment activation or customer merchant approval is claimed here.