Goal

Connect the site to your Stripe account so the app can save cards and charge orders. There are exactly four values to paste — the webhook configures itself.

Before you start

• mam-main, mam-woocommerce, and WooCommerce are active.
• You have a Stripe account and can open Developers → API keys in the Stripe dashboard.
• For marketplaces: Stripe Connect is enabled on your Stripe account (the same keys are used as the platform keys for vendor accounts and transfers).

Steps

1. Get your keys from Stripe

In the Stripe dashboard under Developers → API keys, copy the publishable key (pk_live_…) and secret key (sk_live_…). Toggle the dashboard to Test mode and copy the test pair (pk_test_… / sk_test_…) as well.

2. Paste them into the Stripe Connect tab

In WordPress admin go to Mobile App Manager → WooCommerce, open the Stripe Connect tab, and fill in:

Click the save button. These four keys drive everything the plugin does — card setup, charges, refunds, Connect onboarding, and transfers.

3. Choose test or live mode

The plugin does not have its own mode switch. It follows the WooCommerce Stripe gateway’s “Enable test mode” checkbox (WooCommerce → Settings → Payments → Stripe). Test mode on = the Test key pair and Test webhook secret are used; off = the Live set. Switch modes there and the whole plugin follows.

4. The webhook provisions itself — verify, don’t configure

On your next wp-admin page load the plugin creates its own webhook endpoint in your Stripe account (URL https://your-site/wp-json/mam-stripe/v1/webhook, events payout.created and payout.paid on connected accounts, description “MAM Stripe Manager payout webhook (auto-provisioned)”) and stores the signing secret itself.

To verify: reload the Stripe Connect tab — the Stripe Webhook … Signing Secret field for your current mode now shows a whsec_… value. You can also see the new endpoint in the Stripe dashboard under Developers → Webhooks.

Notes:

• The signing-secret fields are a manual override only. Leave them alone unless you deliberately want the plugin to verify against an endpoint you manage yourself — a pasted secret is never overwritten and never auto-healed.
• If the plugin’s auto-created endpoint is later deleted in the Stripe dashboard, the plugin notices (deliveries stop verifying), discards the stale secret, and provisions a fresh endpoint automatically.
• Provisioning needs the secret key for the current mode, so it happens after step 2; it retries at most once per hour.

5. One-time cleanup of old manual endpoints

If this site previously had a hand-created webhook endpoint in the Stripe dashboard pointing at /wp-json/mam-stripe/v1/webhook, delete it once (Developers → Webhooks → … → Delete). Its deliveries are signed with a different secret and will be rejected — harmless, but they show up as failures in the Stripe dashboard. The auto-provisioned endpoint already receives the payout events.

Optional settings on the same tab

Verify the whole setup

1. With test mode on, save a card in the app (Stripe test card 4242 4242 4242 4242).
2. Place an order in the app and confirm a PaymentIntent appears in the Stripe dashboard (Test mode) with metadata wp_order_id set to the order number.

Related articles

• Plugin: mam-stripe-manager
• Recipe: Stripe Connect vendor onboarding
• Recipe: Payout flow and reconciliation

Metadata