Payment Provider
Connect Stripe to Wilph
A restricted Stripe key lets Wilph read the payment, refund and dispute behind a customer's question.
- Roughly how long
- About 5 minutes
- Who can do it
- A Stripe user with permission to create API keys.
Before you start
- Your Stripe Dashboard, logged in to the right account.
Step by step
Open API keys
In the Stripe Dashboard go to Developers → API keys and find the Restricted keys section.
Create a restricted key
Choose Create restricted key, name it Wilph, and grant Read on Customers, Charges or PaymentIntents, Refunds and Disputes. Leave everything else at None.
Never paste a standard secret key (sk_live_…) into any tool, Wilph included. A restricted key can be scoped and revoked on its own.
Copy the key
Stripe reveals the rk_live_… value once. Copy it before leaving the page.
Paste it into Wilph
In Wilph, open Dashboard → Integrations → Stripe → Connect and save the key.
What Wilph asks for
The exact fields on the connection form, in order.
- Restricted API keyStored encrypted
Prefer a restricted key with read access to customers, payments, refunds, and disputes.
The key is encrypted before storage. This is entirely separate from Wilph's own subscription billing, which never uses a key you supply.
Create a restricted Stripe key ↗If something goes wrong
You are unsure whether you are in test mode.
A test key starts rk_test_. Use the live key unless you are deliberately testing against test data.
Some lookups fail after connecting.
Edit the restricted key in Stripe and check the resource you need has Read rather than None. Wilph never needs write permissions.
Still stuck? Get in touch — tell us which step it failed on and what it said.
More payment provider guides
Ready to connect Stripe?
Open Integrations in your Wilph dashboard and paste in what you collected.