Stripe
Card payments & subscriptions — the billing backend that charges customers and pays out to your bank.
Why we need this
Stripe is the service that powers card payments and subscriptions in your app. It charges your customers, handles checkout and billing, and pays the money out to your bank account. Calda connects to it through the Stripe SDK and REST API, along with webhooks, so the app can take payments, manage subscriptions, and react to billing events reliably.
Like all other accounts, this one should be owned by you. Your bank account, business verification, payout details, and your customer and payment history are all tied to the account, so keeping it under your company means that money and data belong to you, not us.
Do I need a credit card?
No. Stripe accounts are free to create and free to run — there's no card or subscription to start. Stripe instead takes a small per-transaction fee on the payments you process, so you only pay when you're actually earning.
Only you can complete activation
To accept live payments and receive payouts, Stripe requires business and bank details (your legal business info, identity verification, and a payout bank account). These can only be provided by you as the account owner — we can't complete them on your behalf, and they stay with you by design.
Step-by-step setup
Create your Stripe account
Sign up at stripe.com using the company email that should own the account. This account is the container for your payments, products, customers, and payouts — everything we'll configure lives here.
Add your business & bank details
Complete your business profile and add the bank account Stripe should pay out to. This activates the account for live payments. Only you can provide this information, so it's best done before we wire everything up.
Invite Calda to the team
Open Settings → Team and security → Team members, click to invite a member, enter the Calda email we share with you, and assign the Developer (or Administrator) role. Then send the invite — we'll get an email to accept it.
This role is what we need: it lets us create and manage API keys, configure webhooks, and set up products and prices, while your billing and bank details stay with you.
Why Developer or Administrator
Lower roles like Analyst or Support can't create the API keys or webhook endpoints we rely on to connect the app. Developer covers the technical setup we need; Administrator also works if you'd prefer to grant broader access.
Confirm in Slack
Don't forget to notify us in Slack so we can accept the invitation and confirm that we can sign in.
Conclusion
That is it — with the account activated and team access granted, we can wire up payments and subscriptions on our side. Once you've added us as a team member and confirmed in Slack, we'll handle the rest of the integration.
How is this guide?