gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [taler-marketing] 01/03: payto: debitor->debtor, prefer sen


From: gnunet
Subject: [GNUnet-SVN] [taler-marketing] 01/03: payto: debitor->debtor, prefer sender/receiver
Date: Wed, 17 Apr 2019 16:46:01 +0200

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository marketing.

commit d4fac820666a40eadf55280f70a97c4e647fe2de
Author: Florian Dold <address@hidden>
AuthorDate: Wed Apr 17 16:11:15 2019 +0200

    payto: debitor->debtor, prefer sender/receiver
---
 standards/draft-dold-payto.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index 4777c64..6f3727b 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -97,7 +97,7 @@
   payto-URI = "payto" "://" authority path-abempty [ "?" opts ]
   opts = opt *( "&" opt )
   opt = (generic-opt / authority-specific-opt) "=" *( pchar )
-  generic-opt = "amount" / "creditor-name" / "debitor-name" /
+  generic-opt = "amount" / "receiver-name" / "sender-name" /
                 "message" / "instruction"
   authority = ALPHA *( ALPHA / DIGIT / "-" / "." )
   path-abempty = <path-abempty, see [RFC3986], Section 3.3>
@@ -171,11 +171,11 @@ The use of commas is optional for readability and they 
MUST be ignored.
 </t>
 
 <t>
-  creditor-name:  Name of the entity that is credited (receives the payment).
+  receiver-name:  Name of the entity that receives the payment (creditor).
 </t>
 
 <t>
-  debitor-name:  Name of the entity that is debited (makes the payment).
+  sender-name:  Name of the entity that makes the payment (debtor).
 </t>
 
 <t>
@@ -283,7 +283,7 @@ The expert's review SHOULD consider the following criteria:
   <t>The specification of the new payment target type remains within the scope 
of payment transfer form data.
     In particular specifying complete invoices is not in scope.  Neither are 
processing instructions to the
     payment processor or bank beyond a simple payment.</t>
-  <t>The payment target and the options do not contain the debitor's account 
details.</t>
+  <t>The payment target and the options do not contain the payment sender's 
account details.</t>
 </list>
 </t>
 
@@ -336,9 +336,9 @@ The expert's review SHOULD consider the following criteria:
 <t>
 <list style="symbols">
 <t>Name: upi</t>
-<t>Description: Unified Payment Interface. The path is an account alias.  The 
amount and creditor-name
+<t>Description: Unified Payment Interface. The path is an account alias.  The 
amount and receiver-name
 options are mandatory for this payment target.</t>
-<t>Example: payto://upi/address@hidden&amp;amount=INR:200</t>
+<t>Example: payto://upi/address@hidden&amp;amount=INR:200</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="UPILinking" /></t>
 </list>

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]