Aborting of in-progress push payments
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 510
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Description
With respect to Roy's demo of push payments using the 'fb' PMI, I think it would be useful to more specifically define the behaviour of when Abort() is called when a payment in 'processing'.
In particular, I wonder if a specific state of "Processing" would be useful to define in the state machine in addition to "Created", "Interactive" and "Closed".
This would allow the definition of a specific exception to be thrown in the abort() algorithm to disambiguate the various reasons for failure, e.g. "AlreadyProcessing"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Payment Request state machine and the Abort() algorithm described in the issue. Compare the existing Created, Interactive, and Closed states with the proposed Processing state and the handling of payments that are already processing. Done means the abort behavior and failure reason are explicitly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100