The 'payto' URI scheme for payments
draft-dold-payto-09

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09

Independent Stream                                               F. Dold
Internet-Draft                                          Taler Systems SA
Intended status: Informational                               C. Grothoff
Expires: May 7, 2020                                                 BFH
                                                       November 04, 2019

                  The 'payto' URI scheme for payments
                          draft-dold-payto-09

Abstract

   This document defines the 'payto' Uniform Resource Identifier (URI)
   scheme for designating targets for payments.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 7, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Dold & Grothoff            Expires May 7, 2020                  [Page 1]
Internet-Draft           The 'payto' URI scheme            November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Syntax of a 'payto' URI . . . . . . . . . . . . . . . . . . .   2
   3.  Semantics . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Generic Options . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Internationalization and Character Encoding . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  URI Scheme Registration . . . . . . . . . . . . . . . . .   5
     8.2.  Payment Target Type Sub-Registry  . . . . . . . . . . . .   5
       8.2.1.  ACH Bank Account  . . . . . . . . . . . . . . . . . .   6
       8.2.2.  Business Identifier Code  . . . . . . . . . . . . . .   7
       8.2.3.  International Bank Account Number . . . . . . . . . .   7
       8.2.4.  Unified Payments Interface  . . . . . . . . . . . . .   7
       8.2.5.  Bitcoin Address . . . . . . . . . . . . . . . . . . .   8
       8.2.6.  Interledger Protocol Address  . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informational References  . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This document defines the 'payto' Uniform Resource Identifier (URI)
   [RFC3986] scheme for designating transfer form data for payments.  In
   particular, it 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.

   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 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.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Syntax of a 'payto' URI

   This document uses the Augmented Backus-Naur Form (ABNF) of
   [RFC5234].

Dold & Grothoff            Expires May 7, 2020                  [Page 2]
Internet-Draft           The 'payto' URI scheme            November 2019

     payto-URI = "payto://" authority path-abempty [ "?" opts ]
     opts = opt *( "&" opt )
     opt = (generic-opt / authority-specific-opt) "=" *pchar