From d1f007d9a04f37c0b75f1a4ecbaa9c8f397dcc30 Mon Sep 17 00:00:00 2001 From: Nemo Date: Sat, 2 May 2020 10:02:01 +0530 Subject: [PATCH] fix --- webpayments/index.html | 154 ++++++++++++++++++++++++++++++++--------- 1 file changed, 120 insertions(+), 34 deletions(-) diff --git a/webpayments/index.html b/webpayments/index.html index cb89b35..4d7eacc 100644 --- a/webpayments/index.html +++ b/webpayments/index.html @@ -13,18 +13,21 @@

- nemo
(RFCs We Love, May 2020)

-
+

whoami

-

TODO

+
-
+

webpayments

The goal is to create a safe, decentralized system and a set of open, patent and royalty-free specifications that allow people on the Web to send each other money as easily as they exchange instant messages and e-mail today.

-
+

W3C

  • ActivityPub
    • @@ -41,11 +44,11 @@
  • XPath
-
+

demo

Before we start, let's do a quick demo of how it all comes together.

-
+

specifications*

-
+

specifications*

-
+

the talk

Try to understand how we can complete a payment entirely from within your browser without relying on any proprietary APIs (as a processor/merchant), and yet being compatible with any payment instrument.

-
+

definitions

The payment method: the means that the payer uses to pay the payee (e.g., a basic card payment). They are uniquely identified via a Payment Method Identifier (PMI)

The payment method provider establishes the ecosystem to support that payment method.

The details of how to fulfill a payment request for a given payment method is an implementation detail of a payment handler, which is a Web application that can handle a request for payment on behalf of the user.

-
+

examples

payment method: Paytm Wallet Account, UPI, Card, Gift Card, Voucher Code, Bitcoin.

Payment Method Identifier: https://paytm.com, https://npci.org.in/upi, basic-card

payment method provider: Razorpay, Stripe, PayPal, NPCI/UPI, your-bank-goes-here

-
+
+

+
+
+

+
+

Payment Method Identifier

  • URL-based payment method identifier (say, https://bitcoincore.org/ or https://pay.wechat.com).
    • @@ -99,14 +108,14 @@

humanized: how to identify and categorize various payment methods?

-
+

Payment Method Manifest

allows the curators of a defined payment method or owners of a proprietary payment method to authorize (via a manifest file) which payment handlers may be used to fulfill the payment method.

-

humanized: defines the schema of a specific payment method. The one for basic-card is standardized in a specification already.

+

humanized: defines the "how-to-process" action of a specific payment method. The one for basic-card is standardized in a specification already.

-
+

How to get to the manifest?

GET / HTTP/2
 Host: alicepay.com
@@ -114,8 +123,9 @@
 HTTP/2 204
 Link: </pay/payment-manifest.json>; rel="payment-method-manifest"
+

You can alternatively just redirect from your PMI URL, or serve the JSON directly on the PMI URL

-
+

What's inside a Manifest?

A payment method manifest tells the user-agent "how to process payments for a particular method".

URL: https://alicepay.com/pay/payment-manifest.json

@@ -127,10 +137,13 @@ ] } -

user-agent can go next to https://alicepay.com/pay/app/webappmanifest.json to install the AlicePay application.

+
+
+

what happens?

+

user-agent can go next to https://alicepay.com/pay/app/webappmanifest.json to install the AlicePay application.

supported_origins defines which origins can be trusted to install an application for this payment method.

-
+

What's inside a Manifest (1)

{
   //...
@@ -142,7 +155,7 @@

A payment application hosted at either alicepay.com, beta.alicepay.com, or bobpay.com is now authorized for the payment method https://alicepay.com.

-
+

What's inside a Manifest (2)

{
   //...
@@ -151,7 +164,7 @@

any third party is allowed to support the payment method.

-
+

recap

So far, the user-agent has done the following:

    @@ -163,47 +176,120 @@

The application installation is based on W3C's Web App Manifest specification.

-
+
+

What's inside the Payment Handler?

+

A PaymentManager is an additional attribute to the ServiceWorker specification, which allows a piece of code to run/listen in background in your browser, even after the tab is closed.

+
PaymentManager {
+  instruments = PaymentInstruments {
+      delete(instrumentKey)
+      get(instrumentKey)
+      keys()
+      has(instrumentKey);
+      set(instrumentKey, PaymentInstrument details);
+      clear();
+  }
+  userHint
+}
+
+
+
+

Payment Instrument

+

Defines what all different instruments a user might have registered against this method (Multiple wallets, bank accounts, cards etc).

+
PaymentInstrument {
+  // Visa Card ending in **1214
+  name;
+  // Visa icon
+  icons;
+  // PMI
+  method;
+  // Can be used to restrict card usage by network for eg.
+  capabilities;
+}
+
+
+
+

PaymentHandler API

+

A payment handler listens on the PaymentRequestEvent, and returns a PaymentHandlerResponse once done.

+
PaymentHandlerResponse {
+  methodName // PMI
+  details {}
+  payerName;
+  payerEmail;
+  payerPhone;
+  shippingAddress;
+  shippingOption;
+}
+
+
+
+

Payment Handler

Each payment handler defines:

    -
  1. Steps to check if a payment can be made:
    2. -
  2. Steps to respond to a payment request:
    3. +
  3. Steps to check if a payment can be made (listen to CanMakePaymentEvent)
    4. +
  4. Steps to respond to a payment request: (PaymentRequestEvent)

The structure of this object is specific to each payment method.

    -
  1. Steps for when a user changes payment method (optional)
    2. +
  2. Steps for when a user changes payment method (optional) (PaymentRequestDetailsUpdate)

Steps that describe how to handle the user changing payment method or monetary instrument (e.g., from a debit card to a credit card)

-
-

overview

-

TODO: Move this higher?

-

-

ref

-
-
+

Payment Request API

-
+
+

Native Applications?

+

You can declare support for native applications via a few non-standardized changes to the payment method manifest:

+
{
+  "related_applications": [{
+    "platform": "play",
+    "id": "com.bobpay.app",
+    "min_version": "1",
+    "fingerprints": [{
+      "type": "sha256_cert",
+      "value": "92:5A:39:05:C5:B9:EA:BC:71:48:5F:F2"
+    }],
+    "url": "https://play.google.com/store/apps/details?id=com.bobpay.app"
+  }]
+}
+
+
+
+

Native applications (2)

+

Instead of using service-workers now, your payment application can rely on platform-specific APIs for the same purpose. Android uses Intents, for eg.

+

+
+
+

In the Wild

+ +
+

Future Scope

  • Installing a payment app is clunky, maybe we can just install the service-worker directly.
    • +
  • Lots of work happening towards standardization of non-card payments (such as SEPA).
-
-

references

+
+

References

Talk about all the innovations that have happened over the last 2 decades because of the internet and how none of them relate to money transfer (except for bitcoin)

: standardizes an API to allow merchants (i.e., Web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user, mediating the user experience and providing consistency between different merchants and providers.

: defines the validation and (where applicable) registration of identifiers used for matching purposes by other W3C payments specifications.

:defines capabilities that enable Web applications to handle payment requests. The specification defines how Web-based payment handlers register their capabilities with the user agent, how the user agent communicates with them, and what information is exchanged. Note: Based on experience with the Payment Handler API, the Working Group is discussing creation of a new UI component where payments, authentication, and other activities can occur. This functionality would generalize some of the current payment-specific functionality of Payment Handler API.

: allows the curators of a defined payment method or owners of a proprietary payment method to authorize (via a manifest file) which payment handlers may be used to fulfill the payment method. The scope of this work extends to all types of payment handlers, including native mobile apps and Web apps.

Talk about all the innovations that have happened over the last 2 decades because of the internet and how none of them relate to money transfer (except for bitcoin)

: standardizes an API to allow merchants (i.e., Web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user, mediating the user experience and providing consistency between different merchants and providers.

: defines the validation and (where applicable) registration of identifiers used for matching purposes by other W3C payments specifications.

:defines capabilities that enable Web applications to handle payment requests. The specification defines how Web-based payment handlers register their capabilities with the user agent, how the user agent communicates with them, and what information is exchanged. Note: Based on experience with the Payment Handler API, the Working Group is discussing creation of a new UI component where payments, authentication, and other activities can occur. This functionality would generalize some of the current payment-specific functionality of Payment Handler API.

: allows the curators of a defined payment method or owners of a proprietary payment method to authorize (via a manifest file) which payment handlers may be used to fulfill the payment method. The scope of this work extends to all types of payment handlers, including native mobile apps and Web apps.

- [Payment Request API](https://w3c.github.io/payment-request/)

: standardizes an API to allow merchants (i.e., Web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user, mediating the user experience and providing consistency between different merchants and providers.

- [Payment Method Identifiers](https://w3c.github.io/payment-method-id/)

: defines the validation and (where applicable) registration of identifiers used for matching purposes by other W3C payments specifications.

- [Payment Handler API](https://w3c.github.io/payment-handler/)

:defines capabilities that enable Web applications to handle payment requests. The specification defines how Web-based payment handlers register their capabilities with the user agent, how the user agent communicates with them, and what information is exchanged. Note: Based on experience with the Payment Handler API, the Working Group is discussing creation of a new UI component where payments, authentication, and other activities can occur. This functionality would generalize some of the current payment-specific functionality of Payment Handler API.

- [Payment Method Manifest](https://w3c.github.io/payment-method-manifest/)

: allows the curators of a defined payment method or owners of a proprietary payment method to authorize (via a manifest file) which payment handlers may be used to fulfill the payment method. The scope of this work extends to all types of payment handlers, including native mobile apps and Web apps.