bevyengine / bevyengine/bevy-donors
Add a fake / manual transaction stream
- Dominant language
- Rust
- Stars
- 9
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes, something goes wrong when a donor pays, and they end up paying us using a different mechanism than they usually do. We would like to keep the bookkeeping straight, and ensure they don't fall off the donor page when this happens.
Rather than mucking with the data from Stripe / Every.org, we should add and hook up a transaction stream for these manually added transactions.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing how Stripe and Every.org transaction data reaches the donor page, then determine where a manually added transaction stream belongs; done means manual payments are represented without changing the external data and the donor remains visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100