Stripe
Payouts split into gross, fees and refunds.
Payments
Payments · Two-way sync · Live since 2025 · About 10 minutes to connect
Finly reads Ramp's transactions and receipts into the same close as its own, and does not ask anyone to re-categorise what Ramp already coded. A team mid-migration closes once, on one chart, with both programmes reconciled together.
What syncs
Both directions, on every sync.Nothing here is a nightly batch —a record that changes at 14:02 is in the ledger before you look at it.
Connected


Gross, processing fees and refunds land as separate lines against the same Ramp settlement, each on its own account.The bank line that arrives two days later matches without anyone touching it.
Before you start
You need a Ramp account with owner or administrator access and a Finly plan that includes bank feeds, which means Core and above.One Ramp account maps to one Finly entity, so a group running several entities connects each one separately —that separation is also what keeps the fee accounts apart at the close.Nothing is installed, and the key never leaves Finly.
Two things it deliberately will not do.It will not move money:Finly reads Ramp and never initiates a payout, a refund or a transfer, so a bad sync cannot cost you anything.And it will not rewrite history —activity that settled before you connected stays exactly as it is unless you ask for the ninety-day backfill, which is a separate run and a reversible one.
Related
Get started
Book a 30-minute demo and we'll run your own last month through a sandbox, so you can see the close before you commit to anything.