Payment Test Mode

Before taking real payments from subscribers, you should test the entire signup flow — from choosing a tier to receiving the welcome email with a working feed URL — using Stripe’s test environment. Benecaster makes this straightforward with a persistent Test Mode toggle and visible indicators throughout the admin.

How Test Mode Works

Benecaster stores two complete Stripe key sets independently: one for test and one for live. You enter both sets once and then switch between them with a single toggle. Switching never requires re-entering keys and never risks overwriting the wrong set.

Test Mode toggle — in Settings → Membership → Payments, the toggle labeled “Test Mode” switches the active key set:

On (Test Mode) — Benecaster uses your pk_test_... and sk_test_... keys. No real charges occur. Stripe’s test cards work.
Off (Live Mode) — Benecaster uses your pk_live_... and sk_live_... keys. Real charges occur.

The toggle defaults to on (Test Mode) until you explicitly switch it off.

What’s Visible in Test Mode

Benecaster makes test mode impossible to miss:

Admin badge — a persistent orange TEST MODE badge appears on all Benecaster admin screens whenever any gateway is in test mode. It’s always in the top-right corner of the Benecaster admin header.

Subscriber account page — when a subscriber views their account page while test mode is active, a prominent banner reads: “Test Mode — payments are not real.” This prevents confusion when you’re testing the subscriber experience on a development or staging site and a subscriber (or you, logged in as a test subscriber) opens the account page.

Staging site warning — if Benecaster detects that the current site is a staging environment and at least one gateway is configured with live keys, a warning notice appears in the admin: “Live payment keys detected on a staging site.” This is a safety check — it fires independently of the Test Mode toggle, so misconfigured clones of production sites are caught even if test mode was not enabled.

Entering Your Keys

Go to Settings → Membership → Payments.

The form has two sections — Test and Live — each accepting a publishable key and a secret key:

Section	Publishable key	Secret key
Test	`pk_test_...`	`sk_test_...`
Live	`pk_live_...`	`sk_live_...`

Benecaster validates key prefixes at save time. Saving a pk_live_... key into the Test section, or a pk_test_... key into the Live section, is rejected with an error — this prevents silent cross-environment charges.

You don’t need to enter both sections before testing. Enter only the test keys to begin testing immediately. Add the live keys when you’re ready to go live.

Running a Test Subscription

Confirm the Test Mode toggle is on in Settings → Membership → Payments.
Open your subscription page (using [benecaster_subscribe]).
Choose a tier and proceed to checkout.
Use a Stripe test card — for example, 4242 4242 4242 4242 with any future expiry date and any CVC.
Complete the payment.
Verify: welcome email received, feed URL works, subscriber appears in Benecaster → Subscribers.

All activity in test mode is completely isolated from live mode. Test subscribers, test invoices, and test payment intents are not visible in your live Stripe dashboard and do not affect your live subscriber count.

Going Live

When you’re ready to accept real payments:

Confirm your live keys are saved in the Live section of Settings → Membership → Payments.
Switch the toggle off (Live Mode).
The orange TEST MODE badge disappears immediately. The subscriber-facing test mode banner is gone.
New subscriptions will be charged via your live Stripe keys.

Existing test subscriptions created in Test Mode are not transferred to live mode — they exist only in the Stripe test environment. Real subscribers will need to sign up fresh once you go live.

Staging Sites

If you run a staging copy of your production site, be careful with key sets:

Never use live keys on a staging site. The staging-site live-key warning will fire if you do, but the safest approach is to only enter test keys on staging environments.
The Test Mode toggle is per-site, not per-key-set. A live site accidentally cloned to staging retains whatever toggle state was exported with the database — Benecaster’s staging detection catches this and warns you, but always verify the toggle manually after a database clone.

See Setting Up a Staging Site for Benecaster’s full staging site guidance.