Integration

Connect Stripe to Polaris

This is the one connection where the key you choose matters more than anything on this page.

What connecting buys

Connecting Stripe gives a Polaris worker payments and invoice data through a restricted API key. Polaris verifies the key against Stripe before storing it and shows the account name it returned. Restricted keys with read-only scopes are the right credential here: a worker reconciling invoices needs to read charges, and nothing about that job requires the ability to move money.

Credential
Restricted key
Recommended scopes
Read-only
Verified live
Stripe returns the account name

What finance work actually needs

Look at the finance tasks that go undone in a small company. Which invoices are late. What that unlabelled charge was. Whether last month closed cleanly. Whether the budget line matches the bank.

Every one of those is a reading problem. Somebody opens a dashboard, exports something, matches it against something else and writes a paragraph. The writing is the deliverable and the reading is the tedium, which is a good description of the work AI workers are worth hiring for.

None of it requires the ability to issue a refund, and a credential that can issue refunds is a credential you have to think about every time somebody joins the org.

What the connection gives a worker

Bounded by the restricted key's scopes.

  • Payments

    The record of what came in, which is the starting point of every reconciliation anybody has ever put off.

  • Invoices

    Status, amounts and dates, so a chase list is generated from Stripe rather than from a spreadsheet that was accurate a fortnight ago.

  • Customer records

    Enough to attribute a charge to an account when the finance question is really an account question.

  • Material for the monthly close

    A close checklist that arrives with the numbers already filled in is a different kind of Monday from one that starts empty.

Two credentials, two different weeks

Restricted read-only key

  • A worker can describe the state of your revenue
  • Nothing it does can alter a customer's money
  • A leaked key exposes data, which is bad and bounded
  • Security review takes one screen

A full secret key

  • The worker can read exactly the same things
  • It also holds permissions no task needs
  • A leaked key becomes an incident rather than a problem
  • You now audit every worker that carries the connection

Workers and work this connection feeds

Questions people ask

+Can an AI worker refund a customer or move money in Stripe?

Only if the key you stored permits it, which is why the catalog recommends a restricted read-only key. Stripe enforces the permissions and Polaris uses the credential exactly as issued. Create a key that cannot move money and no instruction to a worker can make it move money.

+How does Polaris verify a Stripe key?

It calls Stripe's account endpoint before storing anything. A rejected key returns Stripe's status code as an error and nothing is written. A valid one comes back with the account display name, which the connect panel shows so you can confirm you connected the account you meant to.

+Where is the Stripe key kept?

Server-side against your organisation, written by the function that verified it. The browser never receives it back. Revoking deletes the row and returns every worker carrying the Stripe connection to pending in the same action.

+Should I connect a production Stripe account at all?

For invoice tracking and reconciliation, production data is the point and a read-only key is a proportionate way to reach it. For anything experimental, connect a test-mode key first. Polaris is in free public beta and has no compliance certification to offer, so decide with that on the table.

+Can one organisation connect two Stripe accounts?

No. Credentials are stored one per tool per organisation, so a second Stripe key replaces the first rather than sitting beside it. Teams with several entities need separate organisations for now.

Your next hire takes 60 seconds.

The software is free — unlimited people, tasks, workstreams and docs. You pay only for work an AI worker actually delivers, itemised by the hour.

Get started free

Last checked .