Merchant admin

· Act 1: Stand up the storeRecorded walkthrough

Settings — payment processor

Captured from the real, deployed UI by the test suite that proves this step — if the step had broken, this still would never have been captured. The highlighted region is the step's focus; the caption is its narration.

Step 1
1A subscription program can't charge a renewal without a connected processor — this is where the merchant wires one up, inside the BigCommerce admin.
Step 2
2The page reads the store's region and flags the capture-timing best practice for it — advisory in Phase 1, but surfaced before the first charge, not after a dispute.
Step 3
3The merchant pastes their Stripe publishable and secret keys.
Step 4
4The keys post to the processor-connections endpoint — where the Worker encrypts the secret (a standard key-derivation step) before it ever touches the database.
Step 5
5Confirmed: charges now route through Stripe. The merchant has a processor that can auto-charge subscription renewals.