Sales through Stripe

Sales through Stripe connects a project to the Stripe account that takes its payments, and tells you of every sale the moment the studio reads it: in the alerts column, as a notice on your computer, and on your phone. It also shows income for today, this week and this month beside the period before, the account's balance and the latest payments, and it raises an alert when sales drop, stop or grow, when someone tests stolen cards on your checkout, or when Stripe restricts the account.

It is a free plugin. It needs no aigopilot.com account and no AI subscription, its price does not grow with your sales, and nothing passes through our site: this computer reads Stripe with your own key.

Make a key that can only read

The plugin takes only a restricted key that reads. It refuses a secret key, which can do everything in your account, and a publishable key, which reads nothing.

1. In Stripe, open Developers, then API keys, and press Create restricted key. If Stripe asks, choose to build your own integration and set custom permissions.
2. Give it a name you will know, such as "AigoPilot, read only".
3. Set Balance, Events, and Charges and Refunds to Read. If Stripe offers them, also set Account, Disputes and Payouts to Read. Leave everything else at None.
4. Create the key and copy it. It starts with rk_live_.

Connect a project

1. Open Marketplace and choose Sales through Stripe.
2. Choose the project.
3. Paste the key and press Connect.

The studio tries the key before it keeps it, without changing anything in your account. If the key can write, it is refused and the page names what it could change. If it lacks a read the plugin needs, the page says which. A good key goes into this computer's own vault, never into the studio's data file, a log or anything a model reads. Stripe does not let some restricted keys read the account's state; the page then says that a restricted account will be seen only from a failed payout.

On connecting, the studio reads the last 90 days of payments for the numbers. None of that history is announced as news.

How it reads Stripe

The studio has no public address, so it adds no webhook. About once a minute while the studio runs, it asks Stripe for the events since the last one it read, with Stripe's own cursor. After a restart, or a computer that was off, it goes on from where it stopped, so nothing is missed and nothing is told twice. More than three sales found in one round, after the computer was off, are told as one summary. Up to thirty sales a day get a notice each; the rest still stand in the alerts column. A notice for every sale turns the notices off and keeps the alerts.

The alerts

• A new sale, as good news.
• Sales fell: the last seven days at half or less of the usual week, or no sale for longer than chance explains. Both need enough sales before them, so a small shop gets no false alarm.
• Sales grew, as a light alert.
• Card testing: many failed payments in minutes. This one, and an account Stripe restricted or that cannot take payments, are told even in your quiet hours.
• Stripe asks for information about the account, with its deadline.
• A customer disputed a payment, with reminders before the evidence is due; Stripe's early fraud warning; a failed payout.
• A failed payment above an amount you set under Alerts and data. Every failed payment is in the list either way.

Each currency is counted on its own and nothing is converted. Save as CSV saves every payment kept on this computer. Disconnect takes the key out of the vault and deletes the payments read from this computer; nothing changes in Stripe. Subscriptions and monthly recurring revenue are not shown yet.

The iPhone app, once it is out, has a Sales page with the same numbers and the latest payments. For apps sold in the Microsoft Store, see Microsoft Store numbers; its block stands under the Stripe sales of the same project.

Small tips

Questions