File: rfc8905.html

package info (click to toggle)
doc-rfc 20201128-1
links: PTS, VCS
area: non-free
in suites: bullseye
size: 1,307,124 kB
file content (2228 lines) | stat: -rw-r--r-- 84,408 bytes
parent folder | download | duplicates (2)
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8905: The 'payto' URI Scheme for Payments</title>
<meta content="Florian Dold" name="author">
<meta content="Christian Grothoff" name="author">
<meta content="
       This document defines the 'payto' Uniform Resource Identifier (URI)
      scheme for designating targets for payments. 
       A unified URI scheme for all payment target types allows applications
      to offer user interactions with URIs that represent payment targets,
      simplifying the introduction of new payment systems and
      applications. 
    " name="description">
<meta content="xml2rfc 3.3.0" name="generator">
<meta content="payments" name="keyword">
<meta content="8905" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.3.0
    Python 3.6.10
    appdirs 1.4.4
    ConfigArgParse 1.2.3
    google-i18n-address 2.3.5
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.2
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.19.0
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.3.1
    requests 2.22.0
    setuptools 40.6.2
    six 1.14.0
    WeasyPrint 51
-->
<link href="rfc8905.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  border: none;
  /* this isn't optimal, but it's an existence proof.  PrinceXML doesn't
     support flexbox yet.
  */
  display: table;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre, code {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre, code {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: avoid-page;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8905" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-dold-payto-14" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 8905</td>
<td class="center">The 'payto' URI Scheme</td>
<td class="right">October 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Dold &amp; Grothoff</td>
<td class="center">Informational</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Independent Submission</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8905" class="eref">8905</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2020-10" class="published">October 2020</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">F. Dold</div>
<div class="org">Taler Systems SA</div>
</div>
<div class="author">
      <div class="author-name">C. Grothoff</div>
<div class="org">Bern University of Applied Sciences</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8905</h1>
<h1 id="title">The 'payto' URI Scheme for Payments</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document defines the 'payto' Uniform Resource Identifier (URI)
      scheme for designating targets for payments.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">A unified URI scheme for all payment target types allows applications
      to offer user interactions with URIs that represent payment targets,
      simplifying the introduction of new payment systems and
      applications.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This document is not an Internet Standards Track specification; it is
            published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This is a contribution to the RFC Series, independently of any
            other RFC stream.  The RFC Editor has chosen to publish this
            document at its discretion and makes no statement about its value
            for implementation or deployment.  Documents approved for
            publication by the RFC Editor are not candidates for any level of
            Internet Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <span><a href="https://www.rfc-editor.org/info/rfc8905">https://www.rfc-editor.org/info/rfc8905</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2020 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-objective" class="xref">Objective</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.1.2.2">
                <p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-requirements-language" class="xref">Requirements Language</a><a href="#section-toc.1-1.1.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-syntax-of-a-payto-uri" class="xref">Syntax of a 'payto' URI</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-semantics" class="xref">Semantics</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-examples" class="xref">Examples</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-generic-options" class="xref">Generic Options</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-internationalization-and-ch" class="xref">Internationalization and Character Encoding</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-tracking-payment-target-typ" class="xref">Tracking Payment Target Types</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.7.2.1">
                <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-ach-bank-account" class="xref">ACH Bank Account</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.7.2.2">
                <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-business-identifier-code" class="xref">Business Identifier Code</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.7.2.3">
                <p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>.  <a href="#name-international-bank-account-" class="xref">International Bank Account Number</a><a href="#section-toc.1-1.7.2.3.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.7.2.4">
                <p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>.  <a href="#name-unified-payments-interface" class="xref">Unified Payments Interface</a><a href="#section-toc.1-1.7.2.4.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.7.2.5">
                <p id="section-toc.1-1.7.2.5.1"><a href="#section-7.5" class="xref">7.5</a>.  <a href="#name-bitcoin-address" class="xref">Bitcoin Address</a><a href="#section-toc.1-1.7.2.5.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.7.2.6">
                <p id="section-toc.1-1.7.2.6.1"><a href="#section-7.6" class="xref">7.6</a>.  <a href="#name-interledger-protocol-addres" class="xref">Interledger Protocol Address</a><a href="#section-toc.1-1.7.2.6.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.7.2.7">
                <p id="section-toc.1-1.7.2.7.1"><a href="#section-7.7" class="xref">7.7</a>.  <a href="#name-void-payment-target" class="xref">Void Payment Target</a><a href="#section-toc.1-1.7.2.7.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-payto-payment-target-types" class="xref">Payto Payment Target Types</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.11.2.1">
                <p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.11.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" id="section-toc.1-1.11.2.2">
                <p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.11.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="introduction">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">This document defines the 'payto' Uniform Resource Identifier (URI)
      <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span> scheme for designating
      transfer form data for payments.<a href="#section-1-1" class="pilcrow">¶</a></p>
<section id="section-1.1">
        <h3 id="name-objective">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-objective" class="section-name selfRef">Objective</a>
        </h3>
<p id="section-1.1-1">A 'payto' URI always identifies the target of a payment. A 'payto'
 URI
 consists of a payment target type, a target identifier, and optional
 parameters such as an amount or a payment reference.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
<p id="section-1.1-2">The interpretation of the target identifier is defined by the
 payment target type and typically represents either a bank account or
 an (unsettled) transaction.<a href="#section-1.1-2" class="pilcrow">¶</a></p>
<p id="section-1.1-3">A unified URI scheme for all payment target types allows
 applications to offer user interactions with URIs that represent
 payment targets, simplifying the introduction of new payment systems
 and applications.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
</section>
<section id="section-1.2">
        <h3 id="name-requirements-language">
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
        </h3>
<p id="section-1.2-1">
    The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
    "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>",
    "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
    "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are
    to be interpreted as
    described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>
    when, and only when, they appear in all capitals, as shown here.<a href="#section-1.2-1" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<div id="syntax">
<section id="section-2">
      <h2 id="name-syntax-of-a-payto-uri">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-syntax-of-a-payto-uri" class="section-name selfRef">Syntax of a 'payto' URI</a>
      </h2>
<p id="section-2-1">This document uses the Augmented Backus-Naur Form (ABNF) of <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span>.<a href="#section-2-1" class="pilcrow">¶</a></p>
<div id="section-2-2">
<pre class="sourcecode lang-abnf">
  payto-URI = "payto://" authority path-abempty [ "?" opts ]
  opts = opt *( "&amp;" opt )
  opt-name = generic-opt / authority-specific-opt
  opt-value = *pchar
  opt = opt-name "=" opt-value
  generic-opt = "amount" / "receiver-name" / "sender-name" /
                "message" / "instruction"
  authority-specific-opt = ALPHA *( ALPHA / DIGIT / "-" / "." )
  authority = ALPHA *( ALPHA / DIGIT / "-" / "." )
</pre><a href="#section-2-2" class="pilcrow">¶</a>
</div>
<p id="section-2-3">
    'path-abempty' is defined in <span><a href="https://www.rfc-editor.org/rfc/rfc3986#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC3986" class="xref">RFC3986</a>]</span>.
    'pchar' is defined in <span><a href="https://www.rfc-editor.org/rfc/rfc3986#appendix-A" class="relref">Appendix A</a> of [<a href="#RFC3986" class="xref">RFC3986</a>]</span>.<a href="#section-2-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="semantics">
<section id="section-3">
      <h2 id="name-semantics">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-semantics" class="section-name selfRef">Semantics</a>
      </h2>
<p id="section-3-1">The authority component of a payment URI identifies the payment
      target type.  The payment target types are defined in the "Payto Payment
      Target Types" registry (see <a href="#payto-registry" class="xref">Section 10</a>). The path component of the URI identifies the target
      for a payment as interpreted by the respective payment target type. The
      query component of the URI can provide additional parameters for a
      payment. Every payment target type <span class="bcp14">SHOULD</span> accept the
      options defined in generic-opt. The default operation of applications
      that invoke a URI with the 'payto' scheme <span class="bcp14">MUST</span> be to
      launch
      an application (if available) associated with the payment target type
      that can initiate a payment.

      If multiple handlers are registered for the
      same payment target type, the user <span class="bcp14">SHOULD</span> be able to
      choose which application to launch. This allows users with multiple bank
      accounts (each accessed via the respective bank's banking application)
      to
      choose which account to pay with. An application <span class="bcp14">SHOULD</span>
      allow dereferencing a 'payto' URI even if the payment target type of
      that
      URI is not registered in the "Payto Payment Target Types"
      registry. Details
      of the payment <span class="bcp14">MUST</span> be taken from the path and options
      given in the URI.  The user <span class="bcp14">SHOULD</span> be allowed to modify
      these details before confirming a payment.<a href="#section-3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="examples">
<section id="section-4">
      <h2 id="name-examples">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-examples" class="section-name selfRef">Examples</a>
      </h2>
<p id="section-4-1">Valid Example:<a href="#section-4-1" class="pilcrow">¶</a></p>
<div id="section-4-2">
<pre class="sourcecode">
payto://iban/DE75512108001245126199?amount=EUR:200.0&amp;message=hello
</pre><a href="#section-4-2" class="pilcrow">¶</a>
</div>
<p id="section-4-3">Invalid Example (authority missing):<a href="#section-4-3" class="pilcrow">¶</a></p>
<div id="section-4-4">
<pre class="sourcecode">
payto:iban/12345
</pre><a href="#section-4-4" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="generic-options">
<section id="section-5">
      <h2 id="name-generic-options">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-generic-options" class="section-name selfRef">Generic Options</a>
      </h2>
<p id="section-5-1">Applications <span class="bcp14">MUST</span> accept URIs with options in any
      order.  The "amount" option <span class="bcp14">MUST NOT</span> occur more than
      once.  Other options <span class="bcp14">MAY</span> be allowed multiple times, with
      further restrictions depending on the payment target type. The following
      options <span class="bcp14">SHOULD</span> be understood by every payment target
      type.<a href="#section-5-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-5-2">
        <dt id="section-5-2.1">amount:</dt>
        <dd style="margin-left: 1.5em" id="section-5-2.2">
          <p id="section-5-2.2.1">The amount to transfer.  The format <span class="bcp14">MUST</span> be:<a href="#section-5-2.2.1" class="pilcrow">¶</a></p>
<div id="section-5-2.2.2">
<pre class="sourcecode lang-abnf">
  amount = currency ":" unit [ "." fraction ]
  currency = 1*ALPHA
  unit = 1*(DIGIT / ",")
  fraction = 1*(DIGIT / ",")
</pre><a href="#section-5-2.2.2" class="pilcrow">¶</a>
</div>
<p id="section-5-2.2.3">If a 3-letter 'currency' is used, it <span class="bcp14">MUST</span> be an <span>[<a href="#ISO4217" class="xref">ISO4217</a>]</span> alphabetic code. A payment target
      type <span class="bcp14">MAY</span> define semantics beyond ISO 4217 for currency
      codes that are not 3 characters. The 'unit' value <span class="bcp14">MUST</span> be
      smaller than 2^53. If present, the 'fraction' <span class="bcp14">MUST</span>
      consist of no more than 8 decimal digits. The use of commas is optional
      for readability, and they <span class="bcp14">MUST</span> be ignored.<a href="#section-5-2.2.3" class="pilcrow">¶</a></p>
</dd>
        <dd class="break"></dd>
<dt id="section-5-2.3">receiver-name:</dt>
        <dd style="margin-left: 1.5em" id="section-5-2.4">Name of the entity that receives the payment (creditor). The value of
  this option <span class="bcp14">MAY</span> be subject to lossy conversion, modification,
  and truncation (for example, due to line wrapping or character set
  conversion).<a href="#section-5-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-5-2.5">sender-name:</dt>
        <dd style="margin-left: 1.5em" id="section-5-2.6">Name of the entity that makes the payment (debtor). The value of this
  option <span class="bcp14">MAY</span> be subject to lossy conversion, modification, and
  truncation (for example, due to line wrapping or character set
  conversion).<a href="#section-5-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-5-2.7">message:</dt>
        <dd style="margin-left: 1.5em" id="section-5-2.8">A short message to identify the purpose of the payment. The value of
  this option <span class="bcp14">MAY</span> be subject to lossy conversion, modification,
  and truncation (for example, due to line wrapping or character set
  conversion).<a href="#section-5-2.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-5-2.9">instruction:</dt>
        <dd style="margin-left: 1.5em" id="section-5-2.10">A short message giving payment reconciliation instructions to the
  recipient. An instruction that follows the character set and length
  limitation defined by the respective payment target type <span class="bcp14">SHOULD NOT</span> be subject to lossy conversion.<a href="#section-5-2.10" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
</div>
<div id="encoding">
<section id="section-6">
      <h2 id="name-internationalization-and-ch">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-internationalization-and-ch" class="section-name selfRef">Internationalization and Character Encoding</a>
      </h2>
<p id="section-6-1">
  Various payment systems use restricted character sets.
  An application that processes 'payto' URIs <span class="bcp14">MUST</span> convert
  characters that are not allowed by the respective payment systems
  into allowable characters using either an encoding or a replacement table.
  This conversion process <span class="bcp14">MAY</span> be lossy, except for the
  instruction field.
  If the value of the instruction field would be subject to lossy conversion,
  modification, or truncation,
  the application <span class="bcp14">SHOULD</span> refuse further processing of the
  payment until a
  different value for the instruction is provided.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">To avoid special encoding rules for the payment target identifier,
      the userinfo component <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span> is
      disallowed in 'payto' URIs.  Instead, the payment target identifier is
      given as an option, where encoding rules are uniform for all
      options.<a href="#section-6-2" class="pilcrow">¶</a></p>
<p id="section-6-3">
  Defining a generic way of tagging the language of option fields containing
  natural
  language text (such as "receiver-name", "sender-name", and "message)
  is out of the scope of this document, as internationalization must
  accommodate the restrictions
  and requirements of the underlying banking system of the payment target
  type.

  The internationalization concerns <span class="bcp14">SHOULD</span> be individually
  defined by each payment target type.<a href="#section-6-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tracking">
<section id="section-7">
      <h2 id="name-tracking-payment-target-typ">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-tracking-payment-target-typ" class="section-name selfRef">Tracking Payment Target Types</a>
      </h2>
<p id="section-7-1"> A registry of "Payto Payment Target Types" is described in <a href="#payto-registry" class="xref">Section 10</a>. The registration policy for
      this registry is "First Come First Served", as described in <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>. When requesting new entries,
      careful consideration of the following criteria is strongly advised:<a href="#section-7-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-7-2">
        <li id="section-7-2.1">The description clearly defines the syntax and semantics of the
 payment target and optional parameters if applicable.<a href="#section-7-2.1" class="pilcrow">¶</a>
</li>
        <li id="section-7-2.2">Relevant references are provided if they are available.<a href="#section-7-2.2" class="pilcrow">¶</a>
</li>
        <li id="section-7-2.3">The chosen name is appropriate for the payment target type, does
 not conflict with well-known payment systems, and avoids potential to
 confuse users.<a href="#section-7-2.3" class="pilcrow">¶</a>
</li>
        <li id="section-7-2.4">The payment system underlying the payment target type is not
 fundamentally incompatible with the general options (such as positive
 decimal amounts) in this specification.<a href="#section-7-2.4" class="pilcrow">¶</a>
</li>
        <li id="section-7-2.5">The payment target type is not a vendor-specific version of a
 payment target type that could be described more generally by a
 vendor-neutral payment target type.<a href="#section-7-2.5" class="pilcrow">¶</a>
</li>
        <li id="section-7-2.6">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.<a href="#section-7-2.6" class="pilcrow">¶</a>
</li>
        <li id="section-7-2.7">The payment target and the options do not contain the payment
 sender's account details.<a href="#section-7-2.7" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-7-3">Documents that support requests for new registry entries should
      provide the following information for each entry:<a href="#section-7-3" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-7-4">
        <dt id="section-7-4.1">Name:</dt>
        <dd style="margin-left: 1.5em" id="section-7-4.2">The name of the payment target type (case-insensitive ASCII
 string, restricted to alphanumeric characters, dots, and dashes).<a href="#section-7-4.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-7-4.3">Description:</dt>
        <dd style="margin-left: 1.5em" id="section-7-4.4">A description of the payment target type, including the semantics
 of the path in the URI if applicable.<a href="#section-7-4.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-7-4.5">Example:</dt>
        <dd style="margin-left: 1.5em" id="section-7-4.6">At least one example URI to illustrate the payment target
 type.<a href="#section-7-4.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-7-4.7">Contact:</dt>
        <dd style="margin-left: 1.5em" id="section-7-4.8">The contact information of a person to contact for further
 information.<a href="#section-7-4.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-7-4.9">References:</dt>
        <dd style="margin-left: 1.5em" id="section-7-4.10">Optionally, references describing the payment target type (such as
 an RFC) and target-specific options or references describing the
 payment system underlying the payment target type.<a href="#section-7-4.10" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-7-5">This document populates the registry with seven entries as follows
      (see
      also <a href="#payto-registry" class="xref">Section 10</a>).<a href="#section-7-5" class="pilcrow">¶</a></p>
<div id="registry-entry-ach">
<section id="section-7.1">
        <h3 id="name-ach-bank-account">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-ach-bank-account" class="section-name selfRef">ACH Bank Account</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.1-1">
          <dt id="section-7.1-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.1-1.2">ach<a href="#section-7.1-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.1-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.1-1.4">Automated Clearing House (ACH). The path consists 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
     are not supported.<a href="#section-7.1-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.1-1.5">Example:</dt>
          <dd style="margin-left: 1.5em" id="section-7.1-1.6">
            <div id="section-7.1-1.6.1">
<pre class="sourcecode">
payto://ach/122000661/1234
</pre><a href="#section-7.1-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.1-1.7">Contact:</dt>
          <dd style="margin-left: 1.5em" id="section-7.1-1.8">N/A<a href="#section-7.1-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.1-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.1-1.10">
            <span>[<a href="#NACHA" class="xref">NACHA</a>]</span>, RFC 8905<a href="#section-7.1-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="registry-entry-bic">
<section id="section-7.2">
        <h3 id="name-business-identifier-code">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-business-identifier-code" class="section-name selfRef">Business Identifier Code</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.2-1">
          <dt id="section-7.2-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.2-1.2">bic<a href="#section-7.2-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.2-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.2-1.4">Business Identifier Code (BIC). The path consists of just
    a BIC. This is used for wire transfers between banks. The registry
      for BICs is provided by the Society for Worldwide Interbank
        Financial Telecommunication (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
       are not
         supported.<a href="#section-7.2-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.2-1.5">Example:</dt>
          <dd style="margin-left: 1.5em" id="section-7.2-1.6">
            <div id="section-7.2-1.6.1">
<pre class="sourcecode">
payto://bic/SOGEDEFFXXX
</pre><a href="#section-7.2-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.2-1.7">Contact:</dt>
          <dd style="margin-left: 1.5em" id="section-7.2-1.8">N/A<a href="#section-7.2-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.2-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.2-1.10">
            <span>[<a href="#BIC" class="xref">BIC</a>]</span>, RFC 8905<a href="#section-7.2-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="registry-entry-iban">
<section id="section-7.3">
        <h3 id="name-international-bank-account-">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-international-bank-account-" class="section-name selfRef">International Bank Account Number</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.3-1">
          <dt id="section-7.3-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.3-1.2">iban<a href="#section-7.3-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.3-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.3-1.4">International Bank Account Number (IBAN).  Generally, the IBAN
    allows to unambiguously derive the associated Business
      Identifier Code (BIC) using a lookup in the respective
      proprietary translation table.  However, some legacy applications
      process
        payments to the same IBAN differently based on the specified BIC.
   Thus, the path can consist of either a single component (the IBAN)
   or
     two components (BIC followed by IBAN).  The "message" option of
     the
       'payto' URI corresponds to the "unstructured remittance
       information"
         of Single Euro Payments Area (SEPA) credit transfers and is
 thus
   limited to 140 characters with
     character set limitations that differ according to the
     countries of
       the 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, which can be alphanumeric or from
     the allowed set of
       special characters, i.e., "+?/-:().,'". Language
       tagging and
         internationalization of options are not
  supported.<a href="#section-7.3-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.3-1.5">Examples:</dt>
          <dd style="margin-left: 1.5em" id="section-7.3-1.6">
            <div id="section-7.3-1.6.1">
<pre class="sourcecode">
payto://iban/DE75512108001245126199
payto://iban/SOGEDEFFXXX/DE75512108001245126199
</pre><a href="#section-7.3-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.3-1.7">Contact:</dt>
          <dd style="margin-left: 1.5em" id="section-7.3-1.8">N/A<a href="#section-7.3-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.3-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.3-1.10">
            <span>[<a href="#ISO20022" class="xref">ISO20022</a>]</span>, RFC 8905<a href="#section-7.3-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="registry-entry-upi">
<section id="section-7.4">
        <h3 id="name-unified-payments-interface">
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-unified-payments-interface" class="section-name selfRef">Unified Payments Interface</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.4-1">
          <dt id="section-7.4-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.4-1.2">upi<a href="#section-7.4-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.4-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.4-1.4">Unified Payment Interface (UPI). The path is an account
     alias.  The
       amount and receiver-name 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.<a href="#section-7.4-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.4-1.5">Example:</dt>
          <dd style="margin-left: 1.5em" id="section-7.4-1.6">
            <div id="section-7.4-1.6.1">
<pre class="sourcecode">
payto://upi/alice@example.com?receiver-name=Alice&amp;amount=INR:200
</pre><a href="#section-7.4-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.4-1.7">Contact:</dt>
          <dd style="margin-left: 1.5em" id="section-7.4-1.8">N/A<a href="#section-7.4-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.4-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.4-1.10">
            <span>[<a href="#UPILinking" class="xref">UPILinking</a>]</span>, RFC 8905<a href="#section-7.4-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="registry-entry-bitcoin">
<section id="section-7.5">
        <h3 id="name-bitcoin-address">
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-bitcoin-address" class="section-name selfRef">Bitcoin Address</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.5-1">
          <dt id="section-7.5-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.5-1.2">bitcoin<a href="#section-7.5-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.5-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.5-1.4">Bitcoin protocol. The path is a "bitcoinaddress", as per <span>[<a href="#BIP0021" class="xref">BIP0021</a>]</span>. 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.<a href="#section-7.5-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.5-1.5">Example:</dt>
          <dd style="margin-left: 1.5em" id="section-7.5-1.6">
            <div id="section-7.5-1.6.1">
<pre class="sourcecode">
payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu
</pre><a href="#section-7.5-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.5-1.7">Contact:</dt>
          <dd style="margin-left: 1.5em" id="section-7.5-1.8">N/A<a href="#section-7.5-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.5-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.5-1.10">
            <span>[<a href="#BIP0021" class="xref">BIP0021</a>]</span>, RFC 8905<a href="#section-7.5-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="registry-entry-ilp">
<section id="section-7.6">
        <h3 id="name-interledger-protocol-addres">
<a href="#section-7.6" class="section-number selfRef">7.6. </a><a href="#name-interledger-protocol-addres" class="section-name selfRef">Interledger Protocol Address</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.6-1">
          <dt id="section-7.6-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.6-1.2">ilp<a href="#section-7.6-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.6-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.6-1.4">Interledger protocol (ILP). The path is an ILP address, as per
     <span>[<a href="#ILP-ADDR" class="xref">ILP-ADDR</a>]</span>. Limitations on the
     length and
       character set of option values are defined by the implementation
       of
         the handler. Language tagging and internationalization of
 options
   are not supported.<a href="#section-7.6-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.6-1.5">Example:</dt>
          <dd style="margin-left: 1.5em" id="section-7.6-1.6">
            <div id="section-7.6-1.6.1">
<pre class="sourcecode">
payto://ilp/g.acme.bob
</pre><a href="#section-7.6-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.6-1.7">Contact: </dt>
          <dd style="margin-left: 1.5em" id="section-7.6-1.8">N/A<a href="#section-7.6-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.6-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.6-1.10">
            <span>[<a href="#ILP-ADDR" class="xref">ILP-ADDR</a>]</span>, RFC 8905<a href="#section-7.6-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="registry-entry-void">
<section id="section-7.7">
        <h3 id="name-void-payment-target">
<a href="#section-7.7" class="section-number selfRef">7.7. </a><a href="#name-void-payment-target" class="section-name selfRef">Void Payment Target</a>
        </h3>
<span class="break"></span><dl class="dlParallel" id="section-7.7-1">
          <dt id="section-7.7-1.1">Name:</dt>
          <dd style="margin-left: 1.5em" id="section-7.7-1.2">void<a href="#section-7.7-1.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.7-1.3">Description:</dt>
          <dd style="margin-left: 1.5em" id="section-7.7-1.4">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.<a href="#section-7.7-1.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.7-1.5">Example:</dt>
          <dd style="margin-left: 1.5em" id="section-7.7-1.6">
            <div id="section-7.7-1.6.1">
<pre class="sourcecode">
payto://void/?amount=EUR:10.5
</pre><a href="#section-7.7-1.6.1" class="pilcrow">¶</a>
</div>
</dd>
          <dd class="break"></dd>
<dt id="section-7.7-1.7">Contact:</dt>
          <dd style="margin-left: 1.5em" id="section-7.7-1.8">N/A<a href="#section-7.7-1.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-7.7-1.9">References:</dt>
          <dd style="margin-left: 1.5em" id="section-7.7-1.10">RFC 8905<a href="#section-7.7-1.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
</section>
</div>
<div id="security">
<section id="section-8">
      <h2 id="name-security-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-8-1">Interactive applications handling the 'payto' URI scheme <span class="bcp14">MUST NOT</span> initiate any financial transactions without prior review and
      confirmation from the user and <span class="bcp14">MUST</span> take measures to
      prevent clickjacking <span>[<a href="#HMW12" class="xref">HMW12</a>]</span>.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">Unless a 'payto' URI is received over a trusted, authenticated
      channel,
      a user might not be able to identify the target of a payment.  In
      particular, due to homographs <span>[<a href="#unicode-tr36" class="xref">unicode-tr36</a>]</span>, a payment target type <span class="bcp14">SHOULD NOT</span> use
      human-readable names in combination with unicode in the target account
      specification, as it could give the user the illusion of being able to
      identify the target account from the URI.<a href="#section-8-2" class="pilcrow">¶</a></p>
<p id="section-8-3">The authentication/authorization mechanisms and transport security
      services used to process a payment encoded in a 'payto' URI are handled
      by
      the application and are not in scope of this document.<a href="#section-8-3" class="pilcrow">¶</a></p>
<p id="section-8-4">To avoid unnecessary data collection, payment target types
      <span class="bcp14">SHOULD NOT</span> include personally identifying information
      about the sender of a payment that is not essential for an application
      to conduct a payment.<a href="#section-8-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="iana">
<section id="section-9">
      <h2 id="name-iana-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-9-1">
  IANA maintains the "Uniform Resource Identifier (URI) Schemes" registry,
  which contains an entry for the 'payto' URI scheme as follows.  IANA has updated that
  entry to reference this document.<a href="#section-9-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-9-2">
        <dt id="section-9-2.1">Scheme name:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.2"> payto<a href="#section-9-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.3">Status:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.4"> provisional<a href="#section-9-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.5">URI scheme syntax:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.6">See <a href="#syntax" class="xref">Section 2</a> of RFC 8905.<a href="#section-9-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.7">URI scheme semantics:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.8">See <a href="#semantics" class="xref">Section 3</a> of RFC
  8905.<a href="#section-9-2.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.9">Applications/protocols that use this scheme name:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.10"> payto URIs are
  mainly used by financial software.<a href="#section-9-2.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.11">Contact:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.12">
          <p id="section-9-2.12.1"><span class="contact-name">Christian Grothoff</span> &lt;grothoff@gnu.org&gt;<a href="#section-9-2.12.1" class="pilcrow">¶</a></p>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.13">Change controller:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.14">
          <p id="section-9-2.14.1"><span class="contact-name">Christian Grothoff</span> &lt;grothoff@gnu.org&gt;<a href="#section-9-2.14.1" class="pilcrow">¶</a></p>
</dd>
        <dd class="break"></dd>
<dt id="section-9-2.15">References:</dt>
        <dd style="margin-left: 1.5em" id="section-9-2.16"> See <a href="#refs" class="xref">Section 11</a> of RFC 8905.<a href="#section-9-2.16" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
</div>
<div id="payto-registry">
<section id="section-10">
      <h2 id="name-payto-payment-target-types">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-payto-payment-target-types" class="section-name selfRef">Payto Payment Target Types</a>
      </h2>
<p id="section-10-1">
   This document specifies a list of payment target types.  It is
   possible that future work will need to specify additional payment
   target types.  The GNUnet Assigned Numbers Authority (GANA) <span>[<a href="#GANA" class="xref">GANA</a>]</span>
   operates the "Payto Payment Target Types" registry to track
   the following information for each payment target type:<a href="#section-10-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-10-2">
        <dt id="section-10-2.1">Name:</dt>
        <dd style="margin-left: 1.5em" id="section-10-2.2">The name of the payment target type (case-insensitive ASCII
 string, restricted to alphanumeric characters, dots, and dashes)<a href="#section-10-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-10-2.3">Contact:</dt>
        <dd style="margin-left: 1.5em" id="section-10-2.4">The contact information of a person to contact for further
 information<a href="#section-10-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-10-2.5">References:</dt>
        <dd style="margin-left: 1.5em" id="section-10-2.6">Optionally, references describing the payment target type (such as
 an RFC) and target-specific options or references describing the
 payment system underlying the payment target type<a href="#section-10-2.6" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-10-3">
  The entries in the "Payto Payment Target Types" registry
  defined in this document are as follows:<a href="#section-10-3" class="pilcrow">¶</a></p>
<table class="center" id="table-1">
        <caption><a href="#table-1" class="selfRef">Table 1</a></caption>
<thead>
          <tr>
            <th class="text-left" rowspan="1" colspan="1">Name</th>
            <th class="text-left" rowspan="1" colspan="1">Contact</th>
            <th class="text-left" rowspan="1" colspan="1">Reference</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">ach</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">bic</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">iban</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">upi</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">bitcoin</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">ilp</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">void</td>
            <td class="text-left" rowspan="1" colspan="1">N/A</td>
            <td class="text-left" rowspan="1" colspan="1">RFC 8905</td>
          </tr>
        </tbody>
      </table>
</section>
</div>
<div id="refs">
<section id="section-11">
      <h2 id="name-references">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-11.1">
        <h3 id="name-normative-references">
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="ISO20022">[ISO20022]</dt>
        <dd>
<span class="refAuthor">International Organization for Standardization</span>, <span class="refTitle">"Financial Services - Universal financial industry message scheme"</span>, <span class="seriesInfo">ISO 20022</span>, <time datetime="2013-05" class="refDate">May 2013</time>, <span>&lt;<a href="https://www.iso.org">https://www.iso.org</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="ISO4217">[ISO4217]</dt>
        <dd>
<span class="refAuthor">International Organization for Standardization</span>, <span class="refTitle">"Codes for the representation of currencies"</span>, <span class="seriesInfo">ISO 4217</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://www.iso.org">https://www.iso.org</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="NACHA">[NACHA]</dt>
        <dd>
<span class="refAuthor">Nacha</span>, <span class="refTitle">"2020 Nacha Operating Rules &amp; Guidelines"</span>, <time datetime="2019" class="refDate">2019</time>. </dd>
<dd class="break"></dd>
<dt id="RFC2119">[RFC2119]</dt>
        <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3986">[RFC3986]</dt>
        <dd>
<span class="refAuthor">Berners-Lee, T.</span><span class="refAuthor">, Fielding, R.</span><span class="refAuthor">, and L. Masinter</span>, <span class="refTitle">"Uniform Resource Identifier (URI): Generic Syntax"</span>, <span class="seriesInfo">STD 66</span>, <span class="seriesInfo">RFC 3986</span>, <span class="seriesInfo">DOI 10.17487/RFC3986</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5234">[RFC5234]</dt>
        <dd>
<span class="refAuthor">Crocker, D., Ed.</span><span class="refAuthor"> and P. Overell</span>, <span class="refTitle">"Augmented BNF for Syntax Specifications: ABNF"</span>, <span class="seriesInfo">STD 68</span>, <span class="seriesInfo">RFC 5234</span>, <span class="seriesInfo">DOI 10.17487/RFC5234</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8126">[RFC8126]</dt>
        <dd>
<span class="refAuthor">Cotton, M.</span><span class="refAuthor">, Leiba, B.</span><span class="refAuthor">, and T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8174">[RFC8174]</dt>
        <dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="unicode-tr36">[unicode-tr36]</dt>
      <dd>
<span class="refAuthor">Davis, M., Ed.</span><span class="refAuthor"> and M. Suignard, Ed.</span>, <span class="refTitle">"Unicode Technical Report #36: Unicode Security Considerations"</span>, <time datetime="2014-09" class="refDate">September 2014</time>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-11.2">
        <h3 id="name-informative-references">
<a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="BIC">[BIC]</dt>
        <dd>
<span class="refAuthor">International Organization for Standardization</span>, <span class="refTitle">"Banking -- Banking telecommunication messages -- Business identifier code (BIC)"</span>, <span class="seriesInfo">ISO 9362</span>, <time datetime="2014-12" class="refDate">December 2014</time>, <span>&lt;<a href="https://www.iso.org">https://www.iso.org</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="BIP0021">[BIP0021]</dt>
        <dd>
<span class="refAuthor">Schneider, N.</span><span class="refAuthor"> and M. Corallo</span>, <span class="refTitle">"Bitcoin Improvement Proposal 21"</span>, <time datetime="2019-09" class="refDate">September 2019</time>, <span>&lt;<a href="https://en.bitcoin.it/w/index.php?title=BIP_0021&amp;oldid=66778">https://en.bitcoin.it/w/index.php?title=BIP_0021&amp;oldid=66778</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="GANA">[GANA]</dt>
        <dd>
<span class="refAuthor">GNUnet e.V.</span>, <span class="refTitle">"GNUnet Assigned Numbers Authority (GANA)"</span>, <time datetime="2020-04" class="refDate">April 2020</time>, <span>&lt;<a href="https://gana.gnunet.org/">https://gana.gnunet.org/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="HMW12">[HMW12]</dt>
        <dd>
<span class="refAuthor">Huang, L.</span><span class="refAuthor">, Moshchuk, A.</span><span class="refAuthor">, Wang, H.</span><span class="refAuthor">, Schecter, S.</span><span class="refAuthor">, and C. Jackson</span>, <span class="refTitle">"Clickjacking: Attacks and Defenses"</span>, <time datetime="2012" class="refDate">2012</time>, <span>&lt;<a href="https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final39.pdf">https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final39.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="ILP-ADDR">[ILP-ADDR]</dt>
        <dd>
<span class="refAuthor">Interledger</span>, <span class="refTitle">"ILP Addresses - v2.0.0"</span>, <span>&lt;<a href="https://interledger.org/rfcs/0015-ilp-addresses/">https://interledger.org/rfcs/0015-ilp-addresses/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="UPILinking">[UPILinking]</dt>
      <dd>
<span class="refAuthor">National Payments Corporation of India</span>, <span class="refTitle">"Unified Payment Interface - Common URL Specifications For Deep Linking And Proximity Integration"</span>, <time datetime="2017-11" class="refDate">November 2017</time>, <span>&lt;<a href="https://www.npci.org.in/sites/default/files/UPI%20Linking%20Specs_ver%201.6.pdf">https://www.npci.org.in/sites/default/files/UPI%20Linking%20Specs_ver%201.6.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.a">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Florian Dold</span></div>
<div dir="auto" class="left"><span class="org">Taler Systems SA</span></div>
<div dir="auto" class="left"><span class="street-address">7, rue de Mondorf</span></div>
<div dir="auto" class="left">L-<span class="postal-code">5421</span> <span class="locality">Erpeldange</span>
</div>
<div dir="auto" class="left"><span class="country-name">Luxembourg</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:dold@taler.net" class="email">dold@taler.net</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Christian Grothoff</span></div>
<div dir="auto" class="left"><span class="org">Bern University of Applied Sciences</span></div>
<div dir="auto" class="left"><span class="street-address">Quellgasse 21</span></div>
<div dir="auto" class="left">CH-<span class="postal-code">2501</span> <span class="locality">Biel/Bienne</span>
</div>
<div dir="auto" class="left"><span class="country-name">Switzerland</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:christian.grothoff@bfh.ch" class="email">christian.grothoff@bfh.ch</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>