Flows: improve error handling

Open
#809 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
html

Research direction

Start by reading the flow specification and the steps for processing a payment, especially “Revoke user wallet credentials.” Identify the payment errors covered by the current behavior and how the spec handles them. Done means the spec defines suitable behavior for different failure cases, including network timeouts and outgoing payments that fail due to low balance.

Written by the indexing model from the issue text.

Description

specification

Currently, when processing a payment we run Revoke user wallet credentials when there is an error. Also in cases where it's just a simple network timeout, or for any reason creating an outgoing payment would fail (low balance?). We should dive deeper into the different possible errors and adjust the spec for it.

Dominant language
HTML
Stars
608
Forks
169
Avg merge
2d 16h
Merged PRs (30d)
15

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WICG/webmonetization

All issues in WICG/webmonetization

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.