diff options
| author | Christian Grothoff <christian@grothoff.org> | 2022-09-18 11:34:06 +0200 |
|---|---|---|
| committer | Christian Grothoff <christian@grothoff.org> | 2022-09-18 11:34:06 +0200 |
| commit | 561e76a26b1e63e6c604c427799de6a8ae69939d (patch) | |
| tree | 380047de8c63f5a204001e99875d51aab1a9f04c /design-documents/031-invoicing.rst | |
| parent | 3f7927f435da3ff89b126f6837b5fb0016025a23 (diff) | |
| download | docs-561e76a26b1e63e6c604c427799de6a8ae69939d.tar.gz docs-561e76a26b1e63e6c604c427799de6a8ae69939d.tar.bz2 docs-561e76a26b1e63e6c604c427799de6a8ae69939d.zip | |
note on #7365
Diffstat (limited to 'design-documents/031-invoicing.rst')
| -rw-r--r-- | design-documents/031-invoicing.rst | 16 |
1 files changed, 7 insertions, 9 deletions
diff --git a/design-documents/031-invoicing.rst b/design-documents/031-invoicing.rst index 24c64d79..419c299d 100644 --- a/design-documents/031-invoicing.rst +++ b/design-documents/031-invoicing.rst @@ -29,21 +29,19 @@ Requirements (or require purse fees if limit is exceeded). * Ensure user has done KYC before doing a merge. - - * Support fees to be paid by the user for KYC process. + (Assuming the exchange does KYC at all.) * Use information from KYC process to help payer identify payee. * Reasonable UX and overall design impact. -Unclear in the current proposal are: + * Wallets may want to pay for the reserve with coins + (reserve fresh, not created via bank transfer), while + tipping merchants likely want to pay from the reserve + balance itself. So both styles of payment should be + supported. - * How to pay for the opening. Do we support the use of - coins, or should we require the user to have a - sufficient balance in the reserve, or do we allow - both? Probably best to only support one. As - reserves are typically instant-drained by the - wallet, might be best to require coins? +Unclear in the current proposal are: * Here (and in other places!), the payment of the KYC fee remains, eh, obscure. This should probably be |