Ramp
Card spend is where shadow IT actually shows up. Urengi maps each merchant to a vendor and its current tier, so finance can see which cards are paying for tools that were never reviewed.
- Category
- Finance & spend
- Auth method
- OAuth 2.0
- Direction
- Read-only
- Sync frequency
- Daily
- Scopes requested
- 3
- Available on
- Growth and Enterprise
- Maintained by
- Urengi
What the Ramp integration does
Three reads aimed at the spend that never went through procurement.
Merchants become vendors
Each merchant is matched to a known vendor, and unmatched ones queue for intake with the cardholder as the likely owner.
Tier shown against the card
Spend rolls up per vendor with its risk tier attached, so a Tier 1 vendor on somebody's personal card is visible rather than buried.
New merchants raise a flag
A merchant appearing for the first time is a new third party. Urengi opens an intake instead of waiting for the quarterly review.
Exactly what Urengi can see
Three read-only scopes. Urengi cannot issue, freeze or change a card.
Urengi reads
- Transaction merchant names and amounts
- Cardholder display names and emails
- Department and cost centre labels
Urengi writes
- Nothing — this connection is read-only
Urengi never touches
- Full card numbers or CVVs
- Reimbursement receipts or personal expenses
- Bank accounts, limits or statements
- Anything after you revoke the token
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Ramp 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 Ramp token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Ramp 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 Ramp
- one click, no ticket
- EU or US residency
- chosen at signup