SplitterBot® helps groups settle up after meals out without the spreadsheet.
Brunch with the squad. Date night with friends. The bachelorette weekend that ran four meals long. When the check lands, the table goes quiet, someone pulls out the calculator, and the next ten minutes turn into "wait, who had that cocktail?"
SplitterBot ends that part of the night.
Snap the receipt. Add the people at the table. Tap to settle up. Share.
WHY PEOPLE USE SPLITTERBOT
• Fast. Most tables are done in just a few minutes.
• It captures the receipt for you. No manual entry.
• Item-by-item when it matters, evenly when it doesn't. Either is one tap.
• Tax and tip handled automatically, divvied proportionally.
• Send the result however you want via text, email, or a tap-to-open link.
• Recipients don't need the app to see what they owe.
MADE FOR THESE MOMENTS
• Restaurants & bars
• Brunch & coffee runs
• Large family group events like kids' sports
• Group travel, road trips, weekends away
• Roommate grocery hauls
• Office lunches & team dinners
• Conference sales & partner events
• Any time the check lands and someone has to do math
FREE TO TRY
Your first three receipts are on us. Subscribe for more or pay as you go.
PRIVACY FIRST
Your receipts stay in your account, never sold, never shared with anyone you didn't send them to.
Questions or feedback: hello@splitterbot.com.
SplitterBot® is a registered trademark of Ugarte Enterprises LLC.
評分與評論
此 App 尚未收到足夠的評分或評論,無法顯示概覽。
Added
- "Treated Gift" guest splitter — a guest's share redistributes evenly across the group
- Anti-bot signup protections: disposable-email rejection at signup + per-IP rate limit on /auth/social
Changed
- ™ → ® throughout the app and emails (SplitterBot is now a registered trademark)
- CORS origins for splitterbot.com / preview.splitterbot.com on the mobile API
- Social links updated to @gosplitterbot / facebook.com/splitterbot
Fixed
- Receipt API accepts web-app sign-ins (fixes web "unauthorized" errors)
- Expired/invalid session on receipt load now signs you out instead of failing silently
- All backend responses set JSON content-type (share page follow-up)
- Remaining ™ in transactional email bodies
Security
- Social sign-in rejects Google/Apple tokens whose aud doesn't match our client ID / bundle ID