diff options
author | Christian Grothoff <christian@grothoff.org> | 2019-03-20 16:16:59 +0100 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2019-03-20 16:16:59 +0100 |
commit | f946edb14d0e9a22a6dc1b37e1c680c63266bb8f (patch) | |
tree | 6b93faa2cb2348c35ed0b932b79bca0a1f4089cf /standards | |
parent | 85dbf2f20149c29b4a0020f9383a2d2756bc97fa (diff) | |
download | marketing-f946edb14d0e9a22a6dc1b37e1c680c63266bb8f.tar.gz marketing-f946edb14d0e9a22a6dc1b37e1c680c63266bb8f.tar.bz2 marketing-f946edb14d0e9a22a6dc1b37e1c680c63266bb8f.zip |
get ready for 05
add BIC, remove remaining sepa-leftovers (should be iban now), formatting, change to independent stream
Diffstat (limited to 'standards')
-rw-r--r-- | standards/draft-dold-payto.xml | 49 |
1 files changed, 36 insertions, 13 deletions
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml index e6827b1..6d77d19 100644 --- a/standards/draft-dold-payto.xml +++ b/standards/draft-dold-payto.xml @@ -13,7 +13,7 @@ <?rfc subcompact="no" ?> <rfc category="info" - docName="draft-dold-payto-04" + docName="draft-dold-payto-05" ipr="trust200902"> <front> @@ -52,8 +52,10 @@ <!-- Meta-data Declarations --> <area>General</area> - <workgroup>Internet Engineering Task Force</workgroup> - + <workgroup>Independent Stream</workgroup> + <submissionType>independent</submissionType> + <stream>independent</stream> + <status>experimental</status> <keyword>payments</keyword> <abstract> @@ -126,7 +128,7 @@ payment target type, the user SHOULD be able to choose which application to launch. This allows users with multiple bank accounts (each accessed the respective bank's banking application) to choose which account to pay with. - + Details of the payment MUST be taken from the path and options given in the URI. The user SHOULD be allowed to modify these details before confirming a payment. @@ -136,9 +138,9 @@ <section anchor="examples" title="Examples"> <figure> <artwork><![CDATA[ - payto://sepa/CH9300762011623852957?amount=EUR:200.0&message=hello + payto://iban/DE75512108001245126199?amount=EUR:200.0&message=hello - INVALID (authority missing): payto:sepa/12345 + INVALID (authority missing): payto:iban/12345 ]]> </artwork> </figure> @@ -166,8 +168,8 @@ ]]> </artwork> </figure> -The unit value MUST be smaller than 2^53. -If present, the fraction MUST consist of no more than 8 decimal digits. +The unit value MUST be smaller than 2<sup>53</sup>. +If present, the fraction MUST consist of no more than 8 decimal digits. The use of commas is optional for readability and they MUST be ignored. </t> @@ -281,19 +283,31 @@ The registration policy for this registry is "First Come First Served", as descr </t> </section> +<section anchor="registry-entry-bic" title="Business Identifier Code"> +<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>Example: payto://bic/SOGEDEFFXXX</t> +<t>Contact: N/A</t> +<t>References: <xref target="BIC" /></t> +</list> +</t> +</section> + <section anchor="registry-entry-iban" title="International Bank Account Number"> <t> <list style="symbols"> <t>Name: iban</t> <t>Description: International Bank Account Number (IBAN). Generally the IBAN allows to unambiguously derive - the the associated BIC (Bank Identifier Code). However, some legacy applications process payments to the same IBAN differently based on the + 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 and IBAN). </t> <t>Example: - + payto://iban/DE75512108001245126199 - + payto://iban/SOGEDEFFXXX/DE75512108001245126199 </t> <t>Contact: N/A</t> @@ -345,7 +359,7 @@ options are mandatory for this payment target.</t> <texttable> <ttcol>Name</ttcol><ttcol>Description</ttcol><ttcol>Contact></ttcol><ttcol>References</ttcol> <c>ach</c><c></c><c>N/A</c><c></c> -<c>sepa</c><c>Single European Payment Area. The path is an IBAN.</c><c>N/A</c><c></c> +<c>iban</c><c>Single European Payment Area. The path is an IBAN. An optional BIC may preceed the IBAN.</c><c>N/A</c><c></c> <c>upi</c><c>Unified Payment Interface. The path is an account alias.</c><c>N/A</c><c></c> <c>bitcoin</c><c></c><c>N/A</c><c></c> <c>ilp</c><c></c><c>N/A</c><c></c> @@ -510,10 +524,19 @@ options are mandatory for this payment target.</t> </front> </reference> + <reference anchor="BIC" target="https://www.iso.org/standard/60390.html"> + <front> + <title>ISO 9362:2014 Business Identifier Code (BIC)</title> + <author><organization>International Organization for Standardization</organization> + </author> + <date month="March" year="2019" /> + </front> + </reference> + </references> <!-- Change Log - +v05 2019-05-20 CG Addressing coments, preparing for independent stream submission, adding BIC v01 2017-02-15 CG References and formatting v01 2017-02-13 CG Minimal clarifications v00 2017-01-17 FD Initial version |