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

@one-cp/web-checkout

v1.0.0

Published

This is the One-CP Web Checkout package

Downloads

9

Readme

One-CP Web SDK

The One-CP Web SDK is a library designed to facilitate the integration of the One-Cp checkout system into web applications. It provides a simple and seamless way to embed the One-Cp checkout experience into your web pages.

Installation

You can install the One-CP Web SDK via npm:

npm install @one-cp/web-checkout

Alternatively, you can include it directly in your HTML file using a script tag:

<script src="//one-cp-web-checkout/init.js"></script>

Usage

Initialization

To integrate the One-Cp checkout into your web application, follow these steps:

  • Import or include the One-CP Web SDK in your JavaScript file or HTML file.
  • Call the init function with the required parameters:
import { init } from '@one-cp/web-checkout'; // for npm installation

// Initialize One-Cp checkout
init({
  transactionID: 'transaction_id',
  widgetID: 'your_widget_id',
  config: {
    env: 'sandbox', // or 'production'
    mode: 'lightbox', // or 'inline'
    containerID: 'checkout-container' // required only for inline mode
  },
  onScuuess: function() {
    // Callback function on successful transaction
    console.log('Transaction completed successfully');
  },
  onError: function(errorMessage) {
    // Callback function on transaction error
    console.error('Transaction failed:', errorMessage);
  },
  onClose: function() {
    // Callback function on iframe close
    console.log('Checkout iframe closed');
  }
});

Parameters

| Parameter | Description | Values | Default Value | | -------------------- | --------------------------------------------------- | ----------------------------- | ------------- | | transactionID | Unique ID for the transaction. | - | - | | widgetID | ID of the widget associated with the transaction. | - | - | | config.env | Environment for the checkout. | 'sandbox' or 'production' | 'sandbox' | | config.mode | Mode of checkout display. | 'lightbox' or 'inline' | 'lightbox' | | config.containerID | ID of the container element for inline mode. | (optional) | undefined | | onScuuess | Callback function called on successful transaction. | (optional) | undefined | | onError | Callback function called on transaction error. | (optional) | undefined | | onClose | Callback function called when checkout is closed. | (optional) | undefined |

How to optian a transactionId:

Your backend needs to call /init-transaction endpoint One-CP API and provide the clint-id and clinet-secret in the headers. To obtain clint-id and clinet-secret on the One-CP Dashboard please go to - config -> widget create your one widget and config it. then you will have the widget-id, clint-id, and clinet-secret.

Example HTML

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>One-Cp Checkout Example</title>
</head>
<body>
  <div id="checkout-container"></div>
  <script src="//one-cp-web-checkout/init.js"></script>
  <script>
    const transactionID = await request('your-api-to-create-transaction')

    // Initialize One-Cp checkout
    init({
      transactionID,
      widgetID: 'your_widget_id',
      config: {
        env: 'sandbox',
        mode: 'inline'
      },
      onScuuess: function() {
        console.log('Transaction completed successfully');
      },
      onError: function(errorMessage) {
        console.error('Transaction failed:', errorMessage);
      },
      onClose: function() {
        console.log('Checkout iframe closed');
      }
    });
  </script>
</body>
</html>