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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-04-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                  F. Dold
Internet-Draft                                                     INRIA
Intended status: Informational                               C. Grothoff
Expires: October 9, 2018                                             BFH
                                                           April 7, 2018

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

Abstract

   This document defines the 'payto' Uniform Resource Identifier (URI)
   scheme for specifying 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 October 9, 2018.

Copyright Notice

   Copyright (c) 2018 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 October 9, 2018                [Page 1]
Internet-Draft           The 'payto' URI scheme               April 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Syntax of a 'payto' URL . . . . . . . . . . . . . . . . . . .   2
   3.  Semantics . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Generic Options . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  URI Scheme Registration . . . . . . . . . . . . . . . . .   4
   9.  Payto Payment Method Registry . . . . . . . . . . . . . . . .   4
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     10.2.  Informational References . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document defines the 'payto' Uniform Resource Identifier (URI)
   [RFC3986] scheme for specifying payments.  In its simplest form, a
   'payto' URL identifies a payment method and optionally an account
   identifier.  Additional parameters for a payment, such as an amount
   or a payment reference, can be provided.

2.  Syntax of a 'payto' URL

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

     payto-URI = "payto" "://" authority path-abempty [ "?" opts ]
     opts = opt *( "&" opt )
     opt = (generic-opt / authority-specific-opt) "=" *( pchar )
     generic-opt = "amount" / "creditor-name" / "debitor-name" /
                   "message" / "instruction"
     authority = <authority, see [RFC3986], Section 3.2>
     path-abempty = <path-abempty, see [RFC3986], Section 3.3>
     pchar = <pchar, see [RFC3986], Appendix A.>

3.  Semantics

   The authority component of a payment URI identifies the payment
   method.  The payment methods are defined in the Payto Payment Method
   Registry, see Section 9.  The path component of the URI identifies
   the target account for a payment as interpreted by the respective
   payment method.  The query component of the URI can provide
   additional parameters for a payment.  Every payment method SHOULD

Dold & Grothoff          Expires October 9, 2018                [Page 2]
Internet-Draft           The 'payto' URI scheme               April 2018

   accept the options defined in generic-opt.  The default operation of
   applications that invoke a URI with the payto scheme SHOULD be to
   launch an application (if available) associated with the payment
   method that can initiate a payment.  Details of the payment MUST be
   taken from the path and options given in the URI.  The user SHOULD be
Show full document text