Introduction to the Native Payments Request API

Introduction to the Native Payments Request API

Did you know many modern browsers have an in-built Payment Request API? In this article, you'll understanding to to the Native Payments Request API

Did you know many modern browsers have an in-built Payment Request API? In this article, you'll understanding to to the Native Payments Request API

Payment Request API — a W3C browser standard that facilitates the exchange of payment and contact information.

The Payment Request API provides a browser-based method of connecting users and their preferred payment systems and platforms to merchants that they want to pay for goods and services

Payment Request API Goals — https://www.w3.org/TR/payment-request/#goals

This is a brilliant idea since the idea behind the payment API is to standardize how we pay for things, reduce friction when it comes to implementing accepting payments, and less volatile bugs.

What the PaymentRequest API looks like;

new PaymentRequest(methodData: fn, details: fn, options?);

As you can see, we create a new instance of the payment API with a constructor method. The payment constructor takes two mandatory parameters and one optional parameter:

  • methodData — an object containing information concerning the payment provider, such as what payment methods are supported, etc.
  • details — an object containing information concerning the specific payment, such as the total payment amount, tax, shipping cost, etc.
  • options (optional) — an object containing additional options related to the payment.
Payment API Demo

Payment API demo

As we can see, the payment is directly integrated into the browser. No more insecure third-party redirects or API calls, everything happens in the browser directly!

Getting started the Payments Request API

The Payment API is experimental technology and is prone to change in the future. I still encourage getting familiar with this new API since I believe the proposal is strong and here to stay, maybe some incremental additional new features may be added.

If you wish to follow the examples along, grab a copy of the repository.

git clone https://github.com/indreklasn/payments-request-api-example.git && yarn && yarn start

This shell command will clone the repo, install the dependencies and start the server at localhost:3000

You should see a very simple counter with a buy button

Note; The payment API works on localhost for testing purposes.

Since our app is simple, we’re going to place all payment related logic into the app.js file.

let count = 0
const cartIncrementButton = document.getElementById('cartIncrement')
const cartDecrementButton = document.getElementById('cartDecrement')
const countElement = document.getElementById('count')
const buyButton = document.getElementById('purchase')

function init() {
  
  countElement.innerHTML = count
  cartIncrementButton.addEventListener('click', () => {
    count++
    countElement.innerHTML = `${count}
[Payment Request API ](https://www.w3.org/TR/payment-request/ "Payment Request API ")— a W3C browser standard that facilitates the exchange of payment and contact information.

The [Payment Request API](https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API "Payment Request API") provides a browser-based method of connecting users and their preferred payment systems and platforms to merchants that they want to pay for goods and services

![](https://miro.medium.com/max/700/1*-EHkIwadfV4b4lNN42Fcyg.png)

Payment Request API Goals — [https://www.w3.org/TR/payment-request/#goals](https://www.w3.org/TR/payment-request/#goals "https://www.w3.org/TR/payment-request/#goals")

This is a brilliant idea since the idea behind the *payment API* is to standardize how we pay for things, reduce friction when it comes to implementing accepting payments, and less volatile bugs.

What the *PaymentRequest API* looks like;

new PaymentRequest(methodData: fn, details: fn, options?);


As you can see, we create a new instance of the *payment API* with a constructor method. The payment constructor takes two mandatory parameters and one optional parameter:
* ```methodData``` — an object containing information concerning the payment provider, such as what payment methods are supported, etc.
* ```details``` — an object containing information concerning the specific payment, such as the total payment amount, tax, shipping cost, etc.
* ```options``` (optional) — an object containing additional options related to the payment.
## Payment API Demo

![](https://miro.medium.com/freeze/max/60/1*OQ07k84nrm47BlO-cmCKaw.gif?q=20)

![](https://miro.medium.com/max/700/1*OQ07k84nrm47BlO-cmCKaw.gif)

Payment API demo

As we can see, the payment is directly integrated into the browser. No more insecure third-party redirects or API calls, everything happens in the browser directly!
## Getting started the Payments Request API

The *Payment API* is experimental technology and is prone to change in the future. I still encourage getting familiar with this new [API](https://morioh.com/topic/api "API") since I believe the proposal is strong and here to stay, maybe some incremental additional new features may be added.

If you wish to follow the examples along, grab a copy of the repository.

git clone https://github.com/indreklasn/payments-request-api-example.git && yarn && yarn start


This shell command will clone the repo, install the dependencies and start the server at ```localhost:3000```

![](https://miro.medium.com/max/60/1*y_w0PWTir-Oj8HL2IIt9vQ.png?q=20)

![](https://miro.medium.com/max/700/1*y_w0PWTir-Oj8HL2IIt9vQ.png)

You should see a very simple counter with a buy button

*Note; The payment API works on localhost for testing purposes.*

Since our app is simple, we’re going to place all payment related logic into the ```app.js``` file.

  })
  
  cartDecrementButton.addEventListener('click', () => {
    if (count === 0) return 
    count--
    countElement.innerHTML = `${count}
[Payment Request API ](https://www.w3.org/TR/payment-request/ "Payment Request API ")— a W3C browser standard that facilitates the exchange of payment and contact information.

The [Payment Request API](https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API "Payment Request API") provides a browser-based method of connecting users and their preferred payment systems and platforms to merchants that they want to pay for goods and services

![](https://miro.medium.com/max/700/1*-EHkIwadfV4b4lNN42Fcyg.png)

Payment Request API Goals — [https://www.w3.org/TR/payment-request/#goals](https://www.w3.org/TR/payment-request/#goals "https://www.w3.org/TR/payment-request/#goals")

This is a brilliant idea since the idea behind the *payment API* is to standardize how we pay for things, reduce friction when it comes to implementing accepting payments, and less volatile bugs.

What the *PaymentRequest API* looks like;

new PaymentRequest(methodData: fn, details: fn, options?);


As you can see, we create a new instance of the *payment API* with a constructor method. The payment constructor takes two mandatory parameters and one optional parameter:
* ```methodData``` — an object containing information concerning the payment provider, such as what payment methods are supported, etc.
* ```details``` — an object containing information concerning the specific payment, such as the total payment amount, tax, shipping cost, etc.
* ```options``` (optional) — an object containing additional options related to the payment.
## Payment API Demo

![](https://miro.medium.com/freeze/max/60/1*OQ07k84nrm47BlO-cmCKaw.gif?q=20)

![](https://miro.medium.com/max/700/1*OQ07k84nrm47BlO-cmCKaw.gif)

Payment API demo

As we can see, the payment is directly integrated into the browser. No more insecure third-party redirects or API calls, everything happens in the browser directly!
## Getting started the Payments Request API

The *Payment API* is experimental technology and is prone to change in the future. I still encourage getting familiar with this new [API](https://morioh.com/topic/api "API") since I believe the proposal is strong and here to stay, maybe some incremental additional new features may be added.

If you wish to follow the examples along, grab a copy of the repository.

git clone https://github.com/indreklasn/payments-request-api-example.git && yarn && yarn start


This shell command will clone the repo, install the dependencies and start the server at ```localhost:3000```

![](https://miro.medium.com/max/60/1*y_w0PWTir-Oj8HL2IIt9vQ.png?q=20)

![](https://miro.medium.com/max/700/1*y_w0PWTir-Oj8HL2IIt9vQ.png)

You should see a very simple counter with a buy button

*Note; The payment API works on localhost for testing purposes.*

Since our app is simple, we’re going to place all payment related logic into the ```app.js``` file.

  })
}

init()

Here’s some boilerplate code, we grab the DOM elements and hook them up with the increment and decrement buttons. We also show the final count to the user.

Imagine the increment as adding an item to the basket, decrement as removing the item from the basket, and count showing the total price to pay for the cart checkout.

Implementing the Payment Request API
buyButton.addEventListener('click', () => {
  
  const request = new PaymentRequest(buildSupportedPaymentMethodData(), buildShoppingCartDetails());

})

Once the user clicks on the “BUY” button, we create a new instance of the payment request. Now we need to define buildSupportedPaymentMethodData and buildShoppingCartDetails methods.

The first argument <strong>buildSupportedPaymentMethodData</strong> is a method that returns an array of objects of all the supported payment methods.

function buildSupportedPaymentMethodData() {
  // Example supported payment methods:
  return [{
    supportedMethods: 'basic-card',
    data: {
      supportedNetworks: ['visa', 'mastercard'],
      supportedTypes: ['debit', 'credit']
    }
  }];

The second argument <strong>buildShoppingCartDetails</strong> is the information used to build up the purchase.

For example, What the user is buying, how much it costs, what is the total sum, etc.

function buildShoppingCartDetails() {
  return {
    id: 'count-order',
    displayItems: [
      {
        label: 'Example item',
        amount: {currency: 'USD', value: '1.00'}
      }
    ],
    total: {
      label: 'Total',
      amount: {currency: 'USD', value: count }
    }
  };
}


Notice this time we return an object, instead of an array of objects.

Ok, we’re ready to show the payment request window to the user. Let’s call the show method on the request instance. This returns us a paymentResponse promise.

buyButton.addEventListener('click', () => {
  const request = new PaymentRequest(
    buildSupportedPaymentMethodData(),
    buildShoppingCartDetails()
  );
  request.show().then(paymentResponse => {
    console.log(paymentResponse)
  })
})

If we press the *“Buy” *button we should see this prompt;

Review your payment

You probably need to add a payment card. I recommend using the Visa test card. Insert the number, your name, address, etc. Those don’t have to valid for test purposes.

Visa test card

Adding a Visa test card

Handling the payment

Once we insert a card and approve the payment, we’re getting a paymentResponse returned from the promise request.

PaymentResponse — https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponse

Since the payment is fulfilled now, all the methods and properties are read-only on the paymentResponse object.

Let’s call paymentResponse.complete() to indicate to the user everything went as expected.

<a href="https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponse/complete" target="_blank"><strong>PaymentResponse.complete()</strong></a><strong> — </strong>https://developer.mozilla.org/en-US/docs/Web/API/PaymentResponse#Methods

buyButton.addEventListener('click', () => {

  const request = new PaymentRequest(buildSupportedPaymentMethodData(), buildShoppingCartDetails());
  request.canMakePayment().then(result => {

    if (result) {
      request.show().then(paymentResponse => {
        console.log(paymentResponse.details)
        // Here we would process the payment. For this demo, simulate immediate success:
        paymentResponse.complete('success')
          .then(() => thankYouMessage.style.opacity = 1)
      })
    }
    
  })
})

Voila! That’s all the code we need for our super simple shopping cart.

Full Payment Request API demo

Making a payment only with the Payment API

Here’s the source code in case you want to take a deeper dive.

Browser Support Payments API

https://caniuse.com/#search=payments%20api

Since this is a relatively new API, it’s not too well supported yet. Brave, Chrome, Safari, Firefox, Edge all support the new payments API and you can already try it on your browser.

On a side note, clearly, the new Payments API needs more work to be done, especially on mobile browsers. I wouldn’t rely on this API too much yet when it comes to mobile browsers.

Mobile App Development Company India | Ecommerce Web Development Company India

Mobile App Development Company India | Ecommerce Web Development Company India

Best Mobile App Development Company India, WebClues Global is one of the leading web and mobile app development company. Our team offers complete IT solutions including Cross-Platform App Development, CMS & E-Commerce, and UI/UX Design.

We are custom eCommerce Development Company working with all types of industry verticals and providing them end-to-end solutions for their eCommerce store development.

Know more about Top E-Commerce Web Development Company

JavaScript developers should you be using Web Workers?

JavaScript developers should you be using Web Workers?

Do you think JavaScript developers should be making more use of Web Workers to shift execution off of the main thread?

Originally published by David Gilbertson at https://medium.com

So, Web Workers. Those wonderful little critters that allow us to execute JavaScript off the main thread.

Also known as “no, you’re thinking of Service Workers”.

Photo by Caleb Jones on Unsplash

Before I get into the meat of the article, please sit for a lesson in how computers work:

Understood? Good.

For the red/green colourblind, let me explain. While a CPU is doing one thing, it can’t be doing another thing, which means you can’t sort a big array while a user scrolls the screen.

This is bad, if you have a big array and users with fingers.

Enter, Web Workers. These split open the atomic concept of a ‘CPU’ and allow us to think in terms of threads. We can use one thread to handle user-facing work like touch events and rendering the UI, and different threads to carry out all other work.

Check that out, the main thread is green the whole way through, ready to receive and respond to the gentle caress of a user.

You’re excited (I can tell), if we only have UI code on the main thread and all other code can go in a worker, things are going to be amazing (said the way Oprah would say it).

But cool your jets for just a moment, because websites are mostly about the UI — it’s why we have screens. And a lot of a user’s interactions with your site will be tapping on the screen, waiting for a response, reading, tapping, looking, reading, and so on.

So we can’t just say “here’s some JS that takes 20ms to run, chuck it on a thread”, we must think about where that execution time exists in the user’s world of tap, read, look, read, tap…

I like to boil this down to one specific question:

Is the user waiting anyway?

Imagine we have created some sort of git-repository-hosting website that shows all sorts of things about a repository. We have a cool feature called ‘issues’. A user can even click an ‘issues’ tab in our website to see a list of all issues relating to the repository. Groundbreaking!

When our users click this issues tab, the site is going to fetch the issue data, process it in some way — perhaps sort, or format dates, or work out which icon to show — then render the UI.

Inside the user’s computer, that’ll look exactly like this.

Look at that processing stage, locking up the main thread even though it has nothing to do with the UI! That’s terrible, in theory.

But think about what the human is actually doing at this point. They’re waiting for the common trio of network/process/render; just sittin’ around with less to do than the Bolivian Navy.

Because we care about our users, we show a loading indicator to let them know we’ve received their request and are working on it — putting the human in a ‘waiting’ state. Let’s add that to the diagram.

Now that we have a human in the picture, we can mix in a Web Worker and think about the impact it will have on their life:

Hmmm.

First thing to note is that we’re not doing anything in parallel. We need the data from the network before we process it, and we need to process the data before we can render the UI. The elapsed time doesn’t change.

(BTW, the time involved in moving data to a Web Worker and back is negligible: 1ms per 100 KB is a decent rule of thumb.)

So we can move work off the main thread and have a page that is responsive during that time, but to what end? If our user is sitting there looking at a spinner for 600ms, have we enriched their experience by having a responsive screen for the middle third?

No.

I’ve fudged these diagrams a little bit to make them the gorgeous specimens of graphic design that they are, but they’re not really to scale.

When responding to a user request, you’ll find that the network and DOM-manipulating part of any given task take much, much longer than the pure-JS data processing part.

I saw an article recently making the case that updating a Redux store was a good candidate for Web Workers because it’s not UI work (and non-UI work doesn’t belong on the main thread).

Chucking the data processing over to a worker thread sounds sensible, but the idea struck me as a little, umm, academic.

First, let’s split instances of ‘updating a store’ into two categories:

  1. Updating a store in response to a user interaction, then updating the UI in response to the data change
  2. Not that first one

If the first scenario, a user taps a button on the screen — perhaps to change the sort order of a list. The store updates, and this results in a re-rendering of the DOM (since that’s the point of a store).

Let me just delete one thing from the previous diagram:

In my experience, it is rare that the store-updating step goes beyond a few dozen milliseconds, and is generally followed by ten times that in DOM updating, layout, and paint. If I’ve got a site that’s taking longer than this, I’d be asking questions about why I have so much data in the browser and so much DOM, rather than on which thread I should do my processing.

So the question we’re faced with is the same one from above: the user tapped something on the screen, we’re going to work on that request for hopefully less than a second, why would we want to make the screen responsive during that time?

OK what about the second scenario, where a store update isn’t in response to a user interaction? Performing an auto-save, for example — there’s nothing more annoying than an app becoming unresponsive doing something you didn’t ask it to do.

Actually there’s heaps of things more annoying than that. Teens, for example.

Anyhoo, if you’re doing an auto-save and taking 100ms to process data client-side before sending it off to a server, then you should absolutely use a Web Worker.

In fact, any ‘background’ task that the user hasn’t asked for, or isn’t waiting for, is a good candidate for moving to a Web Worker.

The matter of value

Complexity is expensive, and implementing Web Workers ain’t cheap.

If you’re using a bundler — and you are — you’ll have a lot of reading to do, and probably npm packages to install. If you’ve got a create-react-app app, prepare to eject (and put aside two days twice a year to update 30 different packages when the next version of Babel/Redux/React/ESLint comes out).

Also, if you want to share anything fancier than plain data between a worker and the main thread you’ve got some more reading to do (comlink is your friend).

What I’m getting at is this: if the benefit is real, but minimal, then you’ve gotta ask if there’s something else you could spend a day or two on with a greater benefit to your users.

This thinking is true of everything, of course, but I’ve found that Web Workers have a particularly poor benefit-to-effort ratio.

Hey David, why you hate Web Workers so bad?

Good question.

This is a doweling jig:

I own a doweling jig. I love my doweling jig. If I need to drill a hole into the end of a piece of wood and ensure that it’s perfectly perpendicular to the surface, I use my doweling jig.

But I don’t use it to eat breakfast. For that I use a spoon.

Four years ago I was working on some fancy animations. They looked slick on a fast device, but janky on a slow one. So I wrote fireball-js, which executes a rudimentary performance benchmark on the user’s device and returns a score, allowing me to run my animations only on devices that would render them smoothly.

Where’s the best spot to run some CPU intensive code that the user didn’t request? On a different thread, of course. A Web Worker was the correct tool for the job.

Fast forward to 2019 and you’ll find me writing a routing algorithm for a mapping application. This requires parsing a big fat GeoJSON map into a collection of nodes and edges, to be used when a user asks for directions. The processing isn’t in response to a user request and the user isn’t waiting on it. And so, a Web Worker is the correct tool for the job.

It was only when doing this that it dawned on me: in the intervening quartet of years, I have seen exactly zero other instances where Web Workers would have improved the user experience.

Contrast this with a recent resurgence in Web Worker wonderment, and combine that contrast with the fact that I couldn’t think of anything else to write about, then concatenate that combined contrast with my contrarian character and you’ve got yourself a blog post telling you that maybe Web Workers are a teeny-tiny bit overhyped.

Thanks for reading

If you liked this post, share it with all of your programming buddies!

Follow us on Facebook | Twitter

Further reading

An Introduction to Web Workers

JavaScript Web Workers: A Beginner’s Guide

Using Web Workers to Real-time Processing

How to use Web Workers in Angular app

Using Web Workers with Angular CLI