Stripe Manual (your own keys)
Stripe Manual connects your own existing Stripe account to Pay2Book. It is available on the Pro plan and gives you full control of your Stripe account. To set it up you give Pay2Book two things from Stripe: a restricted API key (so Pay2Book can create checkouts and refunds on your account) and a webhook signing secret (so Stripe can tell Pay2Book the moment a payment succeeds).
You do all of this in Settings → Stripe in your Pay2Book console.
1. Create a restricted API key
Section titled “1. Create a restricted API key”A restricted key gives Pay2Book only the permissions it needs - nothing more.
-
Open your Stripe API keys page: dashboard.stripe.com/apikeys.
-
Select Create restricted key.
-
Give it a name (for example,
Pay2Book) and set these permissions:Resource Permission Checkout Sessions Write PaymentIntents Write Refunds Write Balance Read Webhook Endpoints Read Leave every other permission as None.
-
Create the key and copy it (it starts with
rk_). -
In Pay2Book, go to Settings → Stripe and paste the key into Secret key.
2. Add the webhook
Section titled “2. Add the webhook”The webhook is how Stripe tells Pay2Book that a payment has succeeded.
-
In Pay2Book’s Settings → Stripe, copy your Webhook URL (it is unique to your account).
-
In Stripe, open Workbench → Webhooks → Add destination, or go straight to dashboard.stripe.com/workbench/webhooks/create.
-
For events, choose Your account, then All events. Search for and tick both of these, then Continue:
checkout.session.completedpayment_intent.created
-
For the destination type, choose Webhook endpoint. Paste your Pay2Book Webhook URL as the Endpoint URL, then Create destination.
-
Open the new destination and copy its signing secret (it starts with
whsec_). -
Back in Pay2Book’s Settings → Stripe, paste it into Webhook signing secret and save.
3. Test the connection
Section titled “3. Test the connection”Once the key and webhook secret are saved, open the Health page in your Pay2Book console and run Test setup. It checks that the key works, the webhook is registered, and the right events are subscribed - all without taking a real payment.

The results show exactly what is and is not working. Fix anything it flags - in the example above, the key is fine but the webhook still needs adding.