aMember Pro Docs

Stripe

Connect aMember PRO to Stripe

aMember PRO should use a dedicated restricted API key. Restricted keys begin with rk_test_ in a Stripe sandbox and rk_live_ in live mode. Although older aMember PRO versions label the configuration field Secret API Key, that field also accepts a restricted key.

  1. In aMember CP, go to Configuration > Add-ons, enable the Stripe payment plugin, and save the configuration.

  2. Open Configuration > Stripe in aMember CP. Keep this page open so that you can paste the new key into it.

  3. Sign in to the Stripe Dashboard and select the Stripe account that will receive the payments.

  4. Open Stripe's API keys page. In the current Dashboard, you can also reach it from Workbench > Overview by finding the API keys widget and clicking Manage. Some Stripe accounts still show the older path, Developers > API keys.

  5. Select Live mode for a production aMember site. Use a sandbox and its test keys only while testing; test and live keys are not interchangeable.

  6. In Restricted keys, click Create restricted key. If Stripe offers a choice of templates, start with custom or zero permissions so that you can set the permissions listed below.

  7. Enter a descriptive key name such as aMember PRO, then grant Write permission to:

    • Charges
    • Customers
    • Disputes
    • PaymentIntents
    • PaymentMethods
    • SetupIntents
    • Checkout Sessions

    Leave unrelated permissions set to None.

  8. Click Create key and complete Stripe's verification prompt.

  9. Copy the key immediately. Stripe normally displays a newly created live key only once.

  10. In aMember CP, paste the rk_live_... value into Restricted API Key or Secret API Key, depending on your aMember PRO version, and save the configuration.

Do not paste Stripe's publishable key (pk_...) or a webhook signing secret (whsec_...) into this field. Keep the restricted key private.

If the old key is disabled

A disabled, expired, or deleted Stripe key can no longer authenticate API requests. Create a new restricted key by following the steps above, replace the old value in aMember PRO, and save the Stripe configuration. Do not continue using the disabled key.

After replacing a key, make a test purchase and review the Stripe payment log in aMember CP. A Stripe error about a missing permission means that the restricted key needs the named resource permission; edit the key in Stripe and test again.

See Stripe's documentation for more information about API keys and restricted API keys.

← PaypalProPlimus →