summaryrefslogtreecommitdiff
path: root/standards/draft-dold-payto.xml
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2018-04-07 03:16:18 +0200
committerFlorian Dold <florian.dold@gmail.com>2018-04-07 03:16:18 +0200
commitd204157f05bc1d916ce76b2b4bd8b1d6fa582e6e (patch)
treec56fa71447ab750f9f5a0247fdbdc17ab7432887 /standards/draft-dold-payto.xml
parent9bd179cf84f59d234edfee18d8be6efceed05089 (diff)
downloadmarketing-d204157f05bc1d916ce76b2b4bd8b1d6fa582e6e.tar.gz
marketing-d204157f05bc1d916ce76b2b4bd8b1d6fa582e6e.tar.bz2
marketing-d204157f05bc1d916ce76b2b4bd8b1d6fa582e6e.zip
put existing payment methods into registry defaults
Diffstat (limited to 'standards/draft-dold-payto.xml')
-rw-r--r--standards/draft-dold-payto.xml18
1 files changed, 12 insertions, 6 deletions
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index 80553f3..e0e55d3 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -134,11 +134,7 @@ Questions:
<section anchor="payment-methods" title="Payment Methods">
-<t>sepa: Single European Payment Area. The path is an IBAN, as defined by <xref target="ISO20022" />.</t>
-<t>upi: Unified Payment Interface. The path is an account alias, as defined by <xref target="UPILinking" />.</t>
-<t>bitcoin: Bitcoin protocol. The path is a bitcoinaddress, as defined by <xref target="BIP0021" />.</t>
-<t>ach: Automated Clearing House. The path is a bank account number, as defined by <xref target="NACHA" /></t>
-
+<t>The payment methods are defined in the Payto Payment Method Registry, see <xref target="payto-registry" />.</t>
</section>
<section anchor="generic-options" title="Generic Options">
@@ -220,12 +216,22 @@ is "Payto Payment Method Registry".
<t>The registry shall record for each entry:
<list style="symbols">
<t>Name: The name of the payment method (case insensitive ASCII string)</t>
-<t>Description: A description of the payment method</t>
+<t>Description: A description of the payment method, including the semantics of the path in the URI if applicable.</t>
<t>Contact: The contact information of a person to contact for further information</t>
<t>References: Optionally, references describing the payment method (such as an RFC) and method-specific options</t>
</list>
The registration policy for this registry is "First Come First Served", as described in <xref target="RFC5226" />.
</t>
+
+<t>The registry is initially populated with the following entries:</t>
+<texttable>
+<ttcol>Name</ttcol><ttcol>Description</ttcol><ttcol>Contact></ttcol><ttcol>References</ttcol>
+<c>ach</c><c>Automated Clearing House. The path is a bank account number.</c><c>N/A</c><c><xref target="NACHA" /></c>
+<c>sepa</c><c>Single European Payment Area. The path is an IBAN.</c><c>N/A</c><c><xref target="ISO20022" /></c>
+<c>upi</c><c>Unified Payment Interface. The path is an account alias.</c><c>N/A</c><c><xref target="UPILinking" /></c>
+<c>bitcoin</c><c>Bitcoin protocol. The path is a "bitcoinaddress" as per <xref target="BIP0021" />.</c><c>N/A</c><c><xref target="BIP0021" /></c>
+</texttable>
+
</section>
</section>