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 🙏

© 2026 – Pkg Stats / Ryan Hefner

strapi-plugin-payments-aggregator

v0.0.1

Published

General payment providers aggregator for Strapi 3.

Readme

Strapi plugin strapi-plugin-payments-aggregator

General payment providers aggregator for Strapi 3.

Configuration

Plugin configuration is stored in the ./config/plugins.js file of the application. Here is example of the configuration file

module.exports = ({ env }) => ({
  'payments-aggregator': {
    enabled: true,
    providers: {
      <some-provider>: {...}
    },
    callback: async (payment) => {....}
  }
});

Integration

The plugin configures the following routes

POST /payments-aggreagor/initiate
POST /payments-aggreagor/:provider/:paymentId/callback
 GET /payments-aggreagor/:provider/:paymentId/callback
 GET /payments-aggreagor/providers

Besides configured routes the plugin functionality is accessible through strapi.plugins['payments-aggregator'].services.payments service with functions:

function initiatePayment(payment:PaymentRequest):PaymentInitiation
function validatePayment(data:PaymentValidationRequest):void
function listProviders():ProviderPaymentMethod[]

Besides these callable functions there is option to configure a callback function that will be called any time a status change is recorded from communication with service provider. This callback function is defined in the plugin configuration.

Providers

This plugins uses providers. Each provider needs to have name like strapi-provider-payments-<name> and must implement the following interfaces. The exported default function must accept object that contains configuration options for the provider. This function must return an object that conforms to the following interface:

interface Provider {
  name: string
  initiate(data:PaymentRequest&&{webhookUrl:string, amount:float}):PaymentInitiation
  validate(data:Object):PaymentDetails
  getPaymentMethods():CountryPaymentMethods
}

Types

enum PaymentStatusType {
  CREATED = 'created'
  FAILED = 'failed'
  COMPLETED = 'completed'
  CANCELLED = 'cancelled'
}

interface PaymentDetails {
  status:PaymentStatusType
  externalId:string
  clientIBAN:string
  metadata:Object
  reference:string
}

interface PaymentRequest {
  provider:string
  amount:number // Amount in cents
  currencyCode:string
  locale:string
  reference:string
  description:string
  bank:string
  returnUrl:string
  email:string
}

interface PaymentValidationRequest {
  provider:string
  paymentId:string
  // provider specific data
}

interface Header {
  name:string
  value:string
}

interface Payment {
  provider:string
  status:PaymentStatusType
  amount:number
  currency:string
  referenceId:string
  externalId:string
}

interface PaymentInitiation {
  payment?: Payment
  url: string
  headers:Header[]
}
interface PaymentMethod {
  bic:string
  name:string
  logo_url:string
}

interface CountryPaymentMethods {
  <countryCode>:PaymentMethod[]
  <countryCode>:PaymentMethod[]
  ...
}

interface ProviderPaymentMethod {
  <providerName>:CountryPaymentMethods
}