Stripe
Money is the most reliable signal that a tool is in use. Urengi reads outbound subscriptions and invoices, so a vendor being paid every month without a review on file stops being invisible.
- Category
- Finance & spend
- Auth method
- Restricted API key
- Direction
- Read-only
- Sync frequency
- Daily
- Scopes requested
- 3
- Available on
- Growth and Enterprise
- Maintained by
- Urengi
What the Stripe integration does
Three reads that turn a ledger into a vendor list.
Unreviewed spend, listed
Every recurring payee is matched against reviewed vendors. What does not match is the report nobody currently runs.
Spend feeds the tier
Annual run rate lands as a scoring input, so review depth tracks what you are actually committing rather than what someone estimated at intake.
A jump in spend reopens the review
A tool whose bill triples has usually changed what it does with your data. Urengi treats that as a reason to look again.
Exactly what Urengi can see
Three read-only scopes on a restricted key. Urengi cannot move money or see a cardholder.
Urengi reads
- Subscription and invoice amounts
- Payee and product names
- Billing period and currency
Urengi writes
- Nothing — this connection is read-only
Urengi never touches
- Card numbers or any cardholder data
- Customer records or payment methods
- Payouts, balances or transfers
- Anything after you roll the key
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Stripe from this page and approve the scopes listed above — OAuth in a browser tab, or a scoped API key you paste. An admin approves them once.
02
Choose what syncs
Pick the projects, spaces or accounts Urengi should watch. Narrow is fine to start with; widening it later does not re-authorise anything.
03
Map your fields
Match owners, cost centres and tiers to what Urengi already tracks. Defaults arrive pre-filled from the first sync, so most teams change nothing.
04
Run a test sync
Pull one record and check it landed on the right review. The audit entry confirms the mapping before a real vendor is touched.
Your token, your rules.
Urengi stores the Stripe token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Stripe and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Stripe
- one click, no ticket
- EU or US residency
- chosen at signup