Before you connect
- A Stripe account that may create API keys.
- An owner or admin account in Northdeck.
Connect Stripe
- In Northdeck, open Data → Sources and choose Stripe.
- In Stripe, go to Developers, API keys, click Create secret key and choose Share with an external service: Stripe then makes a restricted key (rk_live_…). Fill in Northdeck as the name and https://northdeck.nl as the URL.
- Choose Custom permissions and set Read on Customers, Subscriptions, Invoices, Charges and Products, and nothing else.
- Copy the key (it starts with rk_live_) and paste it in Northdeck.
- Click Connect Stripe. The first sync adds a module for subscriptions and payments, with MRR.
Someone else holds the access? In Data → Sources, click Send an invite link: they fill in the key without a Northdeck account. The link is valid for 7 days and works once.
Keeping it up to date
Every hour Northdeck reads everything in Stripe again; Stripe has no list of changes since the last read. Sync now does the same at once.
Troubleshoot
The message in Northdeck says what went wrong. These are the most common ones.
Use a restricted key (rk_live_…), not a standard secret key (sk_live_…).
A standard secret key could write, so Northdeck refuses it. Create a restricted key as in step 2.
Stripe did not accept the key.
Create a new restricted key and connect again.
This key may not read ….
Give the restricted key Read on Customers, Subscriptions, Invoices, Charges and Products.
Stripe asks us to slow down.
Wait a few minutes and try again.
Good to know
- Only euros count in the totals; payments in another currency stay visible with their own currency.
- No e-mail addresses, phone numbers, addresses or card details are copied; only name, country and the domain of the e-mail address.
- MRR is counted the way Stripe counts it, excluding VAT and trials.