Nick Myers
Problem
---------
Simplero only connects to a live Stripe account. If you switch your Stripe account Test Mode, payment attempts with test cards will fail. If you attempt to use a Stripe Sandbox, Simplero will fail the "test access" step, as Simplero does not use Stripe Connect.
Stripe has deprecated the account-wide test mode toggle in favour of per-environment Sandboxes. Teams now get up to five fully isolated environments, each with its own API keys and webhooks, and recommend Sandboxes over test mode for most QA tasks.
Because Simplero cannot connect to either test mode or a Sandbox, merchants must run risky one-cent live charges or clone the product in a separate Stripe account, adding friction for every launch or price change.
Why this matters
-----------------
Risk reduction: No accidental live charges during checkout or subscription testing.
Faster QA: Customers, marketers, and support staff can test pricing, coupons, failed payments, and webhooks in minutes instead of waiting for refunds or reconciling live transactions.
Parity with peers: Platforms like Shopify, WooCommerce, and MemberPress already expose Stripe test environments, making this gap more visible to prospects evaluating Simplero.
Feature proposal
------------------
Environment selector in Settings → Payment Processors → Stripe with two options: Live, Sandbox.
Credential fields for each environment:
  • Publishable key
  • Secret key
Toggle between Live + Sandbox mode for payment process configuration.
Visual indicator (banner or badge) on checkout screens when an order form is using a non-live environment, similar to Stripe’s own purple “Test data” strip.