Verified option record · updated 2026-08-25

woocommerce_bacs_accounts

Secret state

woocommerce_bacs_accounts is attributed to WooCommerce. Verified owner; local credential state that ConfigOps does not persist in clear text.

Tested owner
WooCommerceTested ConfigOps adapter assignment
Version contract
WooCommerce 10.3, 10.7, 10.9 & 11.0Adapter schema 1
Stored shape
Plugin-owned scalar or structured runtime value1 mapped field
ConfigOps recovery
Review onlyCurrent-state check required

Who writes woocommerce_bacs_accounts?

WooCommerce is the tested owner for woocommerce_bacs_accounts under the WooCommerce 10.3, 10.7, 10.9 & 11.0 ConfigOps adapter contract. This is a source-backed adapter claim, not a guess based on naming.

Component type
WordPress plugin
Component entry point
woocommerce/woocommerce.php
Adapter ID
woocommerce
Adapter schema
1
Visible setting
No stable visible setting; plugin-generated or boundary state
Classification
Secret state

Plugin-owned scalar or structured runtime value.

Mapped paths1
Secret paths1
Field kinds1
Exact fields mapped by ConfigOps adapter schema 1
PathVisible meaningKindWhy it matters
/Bank transfer accountsProtected payment detailssecretBank account values are removed before ConfigOps stores the capture.

What belongs beside the setting—but not inside the decision?

Known version, inbox, scheduler, onboarding, task-list, empty-selector, note, and rewrite state stays technical. Orders, products, customers, tax tables, shipping zones, webhooks, API keys, Action Scheduler jobs, and analytics tables remain outside option-only recovery.

No option-specific neighboring value is asserted.

The adapter-wide technical boundary still applies; absence here is not proof that a save has no runtime side effects.

Known secret paths

  • /

Adapter-backed, not Smart Undo.

ConfigOps adapterYes · woocommerce

Schema 1; tested against WooCommerce 10.3, 10.7, 10.9 & 11.0.

Adapter-aware UndoUnavailable

No automatic Undo. This option is technical, secret-only, or outside the supported configuration boundary.

Smart Undo eligibilityNo

No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.

History boundary: ConfigOps records only saves it observes while active. It cannot tell you what changed this row before installation.

Inspect without writing.

Run these on the intended environment. The commands read current state; they do not reconstruct history.

Read the current value
wp option get woocommerce_bacs_accounts
Inspect matching storage and autoload metadata
wp option list --search=woocommerce_bacs_accounts --fields=option_name,autoload --format=table

This option contains declared secret paths. Terminal output, scrollback, CI logs, and support transcripts can expose the current value. Prefer ConfigOps’ redacted evidence for incident review.

No option-specific autopsy published yet.

Contract coverage is not a save autopsy.

The owner and field map are verified by the adapter source, but this Atlas record does not claim an option-specific browser or integration save trace.

Questions developers ask mid-incident.

What plugin writes woocommerce_bacs_accounts?

WooCommerce is the tested owner in the ConfigOps WooCommerce 10.3, 10.7, 10.9 & 11.0 adapter contract. The assignment is verified, not inferred from the option prefix.

What is stored in the woocommerce_bacs_accounts WordPress option?

Plugin-owned scalar or structured runtime value. woocommerce_bacs_accounts contains 1 mapped field in this adapter schema, including 1 secret path that ConfigOps redacts.

Can ConfigOps track and undo changes to woocommerce_bacs_accounts?

ConfigOps can attribute and record supported Options API writes while active. No automatic Undo. This option is technical, secret-only, or outside the supported configuration boundary. No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.

Does WordPress keep a history of woocommerce_bacs_accounts?

WordPress normally exposes the current option value, not a universal before-and-after history. ConfigOps must observe the original save to create local evidence; it cannot reconstruct older changes retroactively.

Why this page exists.

This record was generated from pinned ConfigOps source commit e319f502ff677bd76e53b7034650f9ee2afead72. The exact option name passed the publication allowlist; arbitrary searches do not.