docs(DEVELOP): describe payment mechanism, new payment services#1105
Conversation
github-actions
Bot
added
the
area: documentation
Extension builds preview
|
|
|
||
| Note that, we only support [manifest version 3](https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3), and not version 2. | ||
|
|
||
| ### Payment mechanism |
There was a problem hiding this comment.
@melissahenderson would you like to optionally review this section? It relates to your recent work on interledger/open-payments#607.
| 1. Create incoming payment: | ||
| 1. Set up a non-interactive incoming payment grant for the receiving wallet address. | ||
| 1. Create an incoming payment using this grant for the receiving wallet address. | ||
| 1. Optionally, cancel the incoming payment grant, as we no longer need it (we already have the incoming payment). This prevents users wallet seeing _dangling_ grants in their wallet. |
There was a problem hiding this comment.
@sidvishnoi Can you tell me more about this step for canceling the incoming payment grant? I'm only aware of completing an incoming payment (/incoming-payments/{id}/complete), which would tell the recipient's wallet that no more payments are coming.
There was a problem hiding this comment.
Cancelling incoming payment grant helps us avoid having a large list of approved incoming payment grants (we call them dangling grants) in wallet's grants list, when the user closes website (e.g. without making a payment). When the incoming payment expires, we create a new grant, and a new incoming payment (like one grant for each incoming payment).
It essentially tells receiving user that there won't be new incoming payments for this grant, and this grant's job is done.
There was a problem hiding this comment.
To explain, the incoming payment grant is for "creating" incoming payments. Once we've created our incoming payment, we have no further use of that grant anymore.
3 participants
Context
This should help developers understand the payment mechanism better, without going through code first hand.
Should also help guide browser implementers and other curious people.
Changes proposed in this pull request
minSendAmount, one-time payments and continuous payments.