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

upi-link

v1.0.1

Published

Simple npm module to generate UPI deep link

Downloads

8

Readme

upi-link

Simple npm module to generate UPI deep-links, based on UPI Linking Specifications Version 1.5.1 :money_mouth_face:

installation

$ npm i upi-link

API

Factory methods

| Function Name | Input params | Returns | | ------------- |-------------- |---------- | | Satic | VPA ID(M), Payee Name(M), Amount(O)| Builder object | | Dynamic | VPA ID(M), Payee Name(M), Amount(M) | Builder object| | SaticP | VPA ID(M), Payee Name(M), Amount(O)| Promise | | DynamicP | VPA ID(M), Payee Name(M), Amount(M) | Promise|

Setter methods

  1. setMerchant( mc, ti) : Set merchant takes tow parameter Merchant ID (mandatory) and Transaction ID (optional). Both the ID should be generated by the PSP, and should be passed as it is.

  2. setTxRef( refid, note) : Set merchant takes tow parameter Transaction Reference ID (mandatory) and Transaction Note (optional). Transaction Reference ID should generated by you. It could be order number, subscription number, Bill ID, booking ID, insurance renewal reference, etc.

    • Note : Setting up TxRef is mandatory, when either Merchant is set or the URL type is Dynamic
  3. setMinAmount(amount) : Minimum Amount will only be set when Transaction Amount is already set and the Minimum Amount is different from the Transaction Amount.

  4. setCallback(url) : This should be a URL when clicked provides customer with further transaction details like complete bill details, bill copy, order copy, ticket details, etc. This can also be used to deliver digital goods.

    • Note : Setting up Callback URL doesn't guarantee the it will be called by the PSPs post transaction. Call to this URL is subjected white listing by the PSPs.

Build Method

  • getLink() : This will return a QR code friendly formated UPI URI string is all conditions are met.

Chaining

Build object chaining

const upi = require('upi-link')

let uri = upi.Static("xxxxx@ybl", "Xyz Abc")
.setMerchant("ALPHABET")
.setTxRef('INV001')
.getLink()

console.log('URI:  ',uri);

Promise chaining ( * )

const upi = require('upi-link')

upi.DynamicP("xxxxx@ybl", "Xyz Abc", 100000)
.setMinAmount(1000)
.setTxRef('INV001')
.getLink()
.then( uri => console.log('URI:  ',uri))
.catch( err => console.error('Error: ',err.message))

* Promise chaining is the recomended method. If you are using plain build object you should handled errors asseted by each metods.