Skip to content
QR code to Stripe paymentsQR2Stripe documentation

← All guides

Stripe account and keys

You need a Stripe account and up to three restricted keys. Everything in Stripe is separate for test mode and live mode, so do the setup in test mode first and repeat it in live mode when you go live.

A. Setup key For the one-click Stripe setup. Permissions set to Write: Terminal → Locations and Webhook Endpoints. Paste it into the form in the plugin once, then delete it in Stripe.
B. Website key For API mode (recommended). Permissions set to Write: Payment Intents and Terminal → Connection Tokens. It goes into the plugin settings or wp-config.php and stays on the server.
C. Phone key For inline mode only. Permission set to Write: Terminal → Connection Tokens. It goes into the phone app and stays there.

Use a separate key for each purpose, never one key for all. The webhook permission can read events, so it must not stay on a long-lived key. Never enter a secret key (sk_…) in the app.

To create a restricted key (the same for A, B and C) open Developers → API keys in the Stripe Dashboard (Workbench → API keys in newer Dashboards; you need the Administrator or Developer role) and click Create restricted key.

If Stripe asks what the key is for, choose Building your own integration and give the key a name, for example QR2Stripe setup.

Leave all permissions on None (the list is long, use Ctrl+F and search for Locations, Webhook, Payment Intents or Connection) and set only the ones listed above to Write.

Click Create key and copy the rk_test_… value. A live key is shown only once.

Row names occasionally change at Stripe. If a request later fails, the error message names the missing permission, for example payment_intent_write.