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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-01-27
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                                          Taler Systems SA
Intended status: Informational                               C. Grothoff
Expires: August 1, 2019                                              BFH
                                                        January 28, 2019

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

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 August 1, 2019.

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 August 1, 2019                 [Page 1]
Internet-Draft           The 'payto' URI scheme             January 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Syntax of a 'payto' URL . . . . . . . . . . . . . . . . . . .   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 Registry  . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informational References  . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

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

   The interpretation of the target identifier is defined by the payment
   target type, and typically represents either a bank account or an
   (unsettled) transaction.

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

Dold & Grothoff          Expires August 1, 2019                 [Page 2]
Internet-Draft           The 'payto' URI scheme             January 2019

3.  Semantics

   The authority component of a payment URI identifies the payment
   target type.  The payment target types are defined in the Payto
   Payment Target Type Registry, see Section 8.2.  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 method
   SHOULD accept the options defined in generic-opt.  The default
   operation of applications that invoke a URI with the payto scheme
Show full document text