Stripe
AvailableAPI key
Stripe supplies the money side of the customer picture: what was actually captured, what was refunded, and what recurred. That is a different question from what was ordered, which is why a Stripe connection is worth having even when an e-commerce platform is already connected.
What moves, and which way
Integrations run in both directions. What follows is what this connection is for.
En Garde to Stripe
- Nothing is written to your Stripe account. The connection reads.
Stripe to En Garde
- Charges and payment intents, with amount, currency, and status.
- Refunds and disputes, so revenue reporting nets them out.
- Customer records and, where you use them, subscriptions and recurring revenue.
Connecting it
You generate a key in the platform and paste it into En Garde. The key is tested against the live API before it is stored, so a wrong or under-scoped key fails at setup rather than silently later.
- In the Stripe Dashboard, go to Developers → API keys and create a restricted key with read access to charges, customers, and — if you bill recurring — subscriptions.
- Open Integrations in your Brand Space and find Stripe on the Integrations tab.
- Click Connect and paste the restricted key. Use the eye toggle to confirm you pasted the whole key.
- Click Test Connection. A key with too few permissions fails here rather than half-working later.
- Save once the test passes.
Worth knowing
- Use a restricted key rather than a secret key. En Garde only needs to read.
- Test-mode keys connect and test successfully but return test data, which will look like a nearly empty account.