You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
If the prospect if building out an entire accounting system within the application is unappealing, the Splitwise API may be beneficial. It allows for the creation of expenses assigned to a user (an email address) and can process the payments through a handful of processors.
We OAuth a bot (not sure if we should auth individuals, but a bot seems plausible)
Bot creates a group that aligns 1-to-1 with the SeatShare group (tracks Splitwise group ID)
Bot adds expenses for individual tickets when transfer request is processed (track expense ID with request)
Bot can cancel a given expense when a ticket request is cancelled
Users can log into Splitwise to make payments or edit terms
Platform pulls in current balances for group
The text was updated successfully, but these errors were encountered:
If the prospect if building out an entire accounting system within the application is unappealing, the Splitwise API may be beneficial. It allows for the creation of expenses assigned to a user (an email address) and can process the payments through a handful of processors.
The text was updated successfully, but these errors were encountered: