Ramp
Connects · Banks & cards
Fiona connects to Ramp and syncs it automatically.
What happens today
Paste your Ramp client ID and secret and Fiona pulls every settled charge on a schedule, drafts the double entry for each one, and books it against your card — not your cash — so your runway stays honest.
Why it matters to your books
A corporate card is where most operating cost actually happens, and it is the half a bank feed cannot see: a charge is money you OWE, so it never appears in cash flow until the statement is paid. Books built from the bank alone understate real cost all month and then absorb it as one giant payment.
What syncs
- Settled card charges
- Merchant, cardholder and Ramp category
- Refunds and credits
- What is still owed on the card
How to set it up
- Ramp → Settings → Developer → create an app with the transactions:read scope
- Copy its client ID and client secret
- Paste both into Connect → Ramp; the first sync pulls recent settled spend as drafts
Questions people actually ask
Can Fiona spend on my Ramp card or change my limits?
No. The app only needs the transactions:read scope — she can read charges and nothing else. Fiona never holds, moves or transmits money.
Why does card spend not reduce my cash?
Because it hasn't left your bank yet. A charge is money owed to the card, so Fiona books it as a cost against a Ramp Card liability. When you pay the statement, that bank payment clears the balance instead of counting the same spend a second time.
Do pending charges get booked?
No. Only settled charges are booked — a pending authorization can still vanish and a decline never happened. Pending charges are picked up once they clear.
Can I connect Ramp and my bank without double-counting?
Yes. That is the point of booking to the card. Fiona recognises the statement payment on the bank feed and clears the card balance with it, rather than recording the same spend as a fresh expense.
Why does Ramp need a client ID and secret rather than an API key?
Ramp uses OAuth client credentials. You create an app in their developer portal with read access to transactions; we exchange those for a short-lived token on each sync and never store a standing key.
All product names, logos and brands are property of their respective owners. Naming them here describes what Fiona reads or connects to — it does not imply any affiliation with, sponsorship by, or endorsement from them.