Program fees to the ledger
Each morning, yesterday's recreation payments are summed by program and written to Munis as a journal entry for review.
Stripe is an online payment processor some cities, districts and departments use for fees, rentals, program registrations and donations, often through a website or a vendor app built on it.
SentraBridge reads payments and customers from Stripe and creates or updates customers. Flows can carry each payment into the ledger, billing system or a reconciliation table. Payment data moves in memory and SentraBridge keeps only counts and IDs.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Payments | list, read one | — | — | ID, Amount (cents), Currency, Status, Description, Customer… |
| Customers | list, read one | create, update | — | ID, Email, Name, Phone, Metadata |
Each morning, yesterday's recreation payments are summed by program and written to Munis as a journal entry for review.
Stripe payments are matched to open QuickBooks invoices by customer for the clerk to confirm.
All payments with their metadata are loaded into SQL Server for finance to reconcile against bank deposits.
Payments with a failed status are listed and emailed to the department.
Systems cities commonly connect with Stripe, each with its own connector page.
Yes. Stripe's REST API covers payments, customers and invoices. SentraBridge signs in with a restricted key.
Yes. A flow reads payments, summarizes them by account and writes a journal entry to the ERP, or a file for import.
No. Stripe's API doesn't return full card numbers, and SentraBridge stores no payment data.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.