AutoCore Payment Activation and Incident Checklist
A controlled checklist for provider readiness, activation, rollback, and payment incidents.
Treat provider activation as a staged change. A configured provider is not automatically verified, and a verified sandbox is not a live launch approval.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Configuration | Edition, provider, mode, credentials, callback URLs, currency, feature flags, and safety locks agree. |
| Verification | Readiness reports credential-free health and distinguishes unconfigured, unavailable, degraded, and available. |
| Canary | Run a bounded hosted checkout, callback, duplicate event, failure, refund, and reconciliation scenario. |
| Rollback | Disable the provider or payment feature, preserve evidence, reconcile outstanding attempts, and communicate the user impact. |
| No activation claim | Public documentation must not imply that any live provider is enabled by default. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Result format
For each item, record pass, fail, or not_applicable, the evidence reference, the reviewer, and the next action. Do not paste credentials or raw provider payloads into the record.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.