commit c329b2dc6a183477c38e4e7cf293462441c2059c
parent 9f86e98f75b28f3e461062f3c08e64404e239e09
Author: Christian Grothoff <christian@grothoff.org>
Date: Fri, 26 Jun 2020 09:17:31 +0200
Merge branch 'master' of git+ssh://git.taler.net/marketing
Diffstat:
1 file changed, 37 insertions(+), 8 deletions(-)
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
@@ -17,7 +17,7 @@
<?rfc subcompact="no" ?>
<rfc category="info"
- docName="draft-dold-payto-13"
+ docName="draft-dold-payto-14"
ipr="trust200902">
<front>
@@ -52,7 +52,7 @@
</address>
</author>
- <date day="28" month="April" year="2020" />
+ <date day="01" month="May" year="2020" />
<!-- Meta-data Declarations -->
<area>General</area>
@@ -306,7 +306,11 @@ also <xref target="payto-registry" />).
<t>
<list style="symbols">
<t>Name: ach</t>
-<t>Description: Automated Clearing House. The path consist of two components, the routing number and the account number.</t>
+<t>Description: Automated Clearing House. The path consist of two components, the routing number and the account number.
+ Limitations on the length and character set of option values are defined by the implementation
+ of the handler.
+ Language tagging and internationalization of options is not supported.
+</t>
<t>Example: payto://ach/122000661/1234</t>
<t>Contact: N/A</t>
<t>References: <xref target="NACHA" />, [this.I-D]</t>
@@ -318,7 +322,11 @@ also <xref target="payto-registry" />).
<t>
<list style="symbols">
<t>Name: bic</t>
-<t>Description: Business Identifier Code. The path consist of just a BIC. This is used for wire transfers between banks. The registry for BICs is provided by SWIFT. The path does not allow specifying a bank account number.</t>
+<t>Description: Business Identifier Code. The path consist of just a BIC. This is used for wire transfers between banks. The registry for BICs is provided by SWIFT. The path does not allow specifying a bank account number.
+ Limitations on the length and character set of option values are defined by the implementation
+ of the handler.
+ Language tagging and internationalization of options is not supported.
+</t>
<t>Example: payto://bic/SOGEDEFFXXX</t>
<t>Contact: N/A</t>
<t>References: <xref target="BIC" />, [this.I-D]</t>
@@ -333,7 +341,13 @@ also <xref target="payto-registry" />).
<t>Description: International Bank Account Number (IBAN). Generally the IBAN allows to unambiguously derive
the the associated Business Identifier Code (BIC). However, some legacy applications process payments to the same IBAN differently based on the
specified BIC. Thus the path can either consist of a single component (the IBAN) or two components
- (BIC followed by IBAN).
+ (BIC followed by IBAN). The "message" option of the payto URI corresponds to the "unstructured remittance information"
+ of SEPA credit transfers and is thus limited to 140 characters with character set limitations that
+ differ according to the countries of banks and payment processors involved in the payment.
+ The "instruction" option of the payto URI corresponds to the "end to end identifier" of SEPA credit transfers
+ and is thus limited to at most 35 characters that can be alphanumeric or from the allowed set
+ of special characters "+?/-:().,'".
+ Language tagging and internationalization of options is not supported.
</t>
<t>Example:
@@ -352,7 +366,11 @@ also <xref target="payto-registry" />).
<list style="symbols">
<t>Name: upi</t>
<t>Description: Unified Payment Interface. The path is an account alias. The amount and receiver-name
-options are mandatory for this payment target.</t>
+ options are mandatory for this payment target.
+ Limitations on the length and character set of option values are defined by the implementation
+ of the handler.
+ Language tags and internationalization of options are not supported.
+ </t>
<t>Example: payto://upi/alice@example.com?receiver-name=Alice&amount=INR:200</t>
<t>Contact: N/A</t>
<t>References: <xref target="UPILinking" />, [this.I-D]</t>
@@ -364,7 +382,11 @@ options are mandatory for this payment target.</t>
<t>
<list style="symbols">
<t>Name: bitcoin</t>
-<t>Description: Bitcoin protocol. The path is a "bitcoinaddress" as per <xref target="BIP0021" />.</t>
+<t>Description: Bitcoin protocol. The path is a "bitcoinaddress" as per <xref target="BIP0021" />.
+Limitations on the length and character set of option values are defined by the implementation
+of the handler.
+Language tags and internationalization of options are not supported.
+</t>
<t>Example: payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu</t>
<t>Contact: N/A</t>
<t>References: <xref target="BIP0021" />, [this.I-D]</t>
@@ -376,7 +398,11 @@ options are mandatory for this payment target.</t>
<t>
<list style="symbols">
<t>Name: ilp</t>
-<t>Description: Interledger protocol. The path is an ILP address as per <xref target="ILP-ADDR" />.</t>
+<t>Description: Interledger protocol. The path is an ILP address as per <xref target="ILP-ADDR" />.
+Limitations on the length and character set of option values are defined by the implementation
+of the handler.
+Language tagging and internationalization of options is not supported.
+</t>
<t>Example: payto://ilp/g.acme.bob</t>
<t>Contact: N/A</t>
<t>References: <xref target="ILP-ADDR" />, [this.I-D]</t>
@@ -392,6 +418,9 @@ options are mandatory for this payment target.</t>
Description: The "void" payment target type allows specifying the parameters
of an out-of-band payment (such as cash or other types of in-person
transactions). The path is optional and interpreted as a comment.
+ Limitations on the length and character set of option values are defined by the implementation
+ of the handler.
+ Language tags and internationalization of options are not supported.
</t>
<t>Example: payto://void/?amount=EUR:10.5</t>
<t>Contact: N/A</t>
