npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@highnoteplatform/secure-inputs

v1.0.5

Published

Secure input fields for your customer.

Downloads

468

Readme

@highnoteplatform/secure-inputs

Note: This library is in a pre-release phase. Prior to the release of version 1.0.0, breaking changes may be introduced.

The Highnote Secure Inputs SDK allows you to accept sensitive data from your customer securely and seamlessly using iframes. This allows you to avoid sensitive data (like PCI-scoped data) flowing through your servers or being accessible to scripts running on your page.

Usage

Secure Inputs Fields

Note: Read the full documentation here.

Installation

With npm:

npm i @highnoteplatform/secure-inputs

With yarn:

yarn add @highnoteplatform/secure-inputs

Generate a client token

On your server, generate a client token using the GraphQL API.

See the generatePaymentCardClientToken docs.

GraphQL query

mutation GeneratePaymentCardClientToken(
  $input: GeneratePaymentCardClientTokenInput!
) {
  generatePaymentCardClientToken(input: $input) {
    ... on ClientToken {
      value
      expirationDate
    }
  }
}

Input variables

{
  "input": {
    "paymentCardId": "MC43LjE=",
    "permissions": ["SET_PAYMENT_CARD_PIN"]
  }
}

Response

{
  "data": {
    "generatePaymentCardClientToken": {
      "value": "TOKEN",
      "expirationDate": "2022-02-07T20:04:50.633Z"
    }
  },
  "extensions": {
    "requestId": "example-request-id"
  }
}

Prepare your HTML

You will need to provide the Secure Inputs with the elements you want to render iframes into for each use case.

PIN
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Edit Payment Card PIN</title>
  </head>
  <body>
    <p>Set your new PIN here:</p>
    <div id="pin">
      <!-- An iframe will be injected here -->
    </div>
  </body>
</html>

Initialize the library

import { renderFields } from "@highnoteplatform/secure-inputs";

const { unmount } = await renderFields({
  onSuccess: (element) => {
    // Inform the user on success
  },
  onError: (error) => {
    // Handle errors
  },

  // Specify the individual fields to render data into
  elements: {
    pin: {
      clientToken: "client token from server",
      // This is the same paymentCardId used to generate the token
      paymentCardId: "MC43LjE=",
      selector: "#pin",
    },
});