What is PayPlus+? What can I do?

PayPlus+ is a payment gateway designed to handle a variety of use cases you might require with your system.
With PayPlus+ you can:

  • Accept payments from Mastercard or VISA credit cards
  • Accept payments from other systems, like PayPal, Klarna, Mybank, and others
  • Accept recurring payments, like subscriptions.
  • PCI-DSS compliance - you (the merchant) will never encounter a credit card number.
  • Simplify the billing of your applications by allocating to us the management of your account's wallets

Getting started

Using only a few lines of code, you will be able to integrate payment management with virtual wallets to your application.
PayPlus+ can be integrated via our RESTful API.

Testing is available in the sandbox environment - simply deploy to production as soon as you are ready by switching the URL endpoint.

Step 1 - Signing up

Register on PayPlus+ back office.
Our self-provisioning form is not yet ready, though in the meantime you can complete this step by sending your request to our support team here.
Please include the following information:

  • Details of your company (name, country, full address and VAT code if any)
  • Business sector
  • Description of the services/products sold
  • Currency
  • Total monthly volume

Step 2 - Configure your PayPlus+ account

Our support team will reply with the necessary information you need to authorize the API - in particular:

  • An application key, to be passed within parameters when it is necessary
  • A unique passphrase, to be used to create the Authorization Token

Step 3 - Connect your application

With the parameters received you can now make use of our API as indicated in the Reference Guide.

Please remember that the production environment is available on the following endpoint:


API Authentication

  1. Once you have a passphrase, you can create an authorization token.
  2. That token must be passed adding an "Authorization" HTTP header
  3. The token is the base64-encoded SHA–256 hash of the POST body.
  4. The signing key used to encrypt the authorization token must be the passphrase associated with the application referenced in POST body.

Here is a javascript sample:

            const nJwt = require('nJwt')
            // create authorization token
            let jwt = nJwt.create(body, AppPassPhrase, 'HS256')
            let token = jwt.compact()
            console.log("Authorization:", token)

Encrypted communication

PayPlus+ supports encryption to protect communications between us and your web application. Just specify an HTTPS URL.
In addition, PayPlus+ supports the TLS cryptographic protocol.
Note: PayPlus+ does not support self-signed certificates.


Application - any app or service you connect to and use the PayPlus+ API.
Each application is made of:

  • A date range: timeframe of the application’s usabilit
  • Accounts: to manage users, cash, and/or services
  • Products: to manage billing services and validate transactions

You can further manage your applications by setting up notifications, getting transaction histories and accessing overdrafts.


Each app you link to PayPlus+ has a dedicated account. Every account houses master and child accounts to help you administer your app and its users.

Accounts (and so their child accounts) can be filled either with cash or with what we call "billable actions". Hence, with app queries, it is not only possible to work on a user's wallet, but also on the available actions given the amount they have charged the account. This is useful for companies who sell particular services (e.g: telco companies, food delivery, etc.) or have billing models based on user interaction.

Example: Imagine Addy, a brand new advertising marketplace. Addy delivers ads from its users, and pay on the volume of valid interactions that ad viewers have with those; hence Addy users buy prepaid packages of viewers clicks, while PayPlus+ cares for filling and withdrawing the account with available interactions.

Example: Let's imagine "CoffeeBreak!" - an app allowing people to pay for food & drink from vending machines. Users will have to decide whether to fill a personal wallet or use a credit card to proceed with the purchase. PayPlus+ back-office can both manage the "one-shot-payment" via Credit Card or simply fill with money and withdraw from the wallet based on the actions the user takes (purchasing an espresso or a sandwich.)


With product(s) we refer to what you sell:

  • Monthly subscriptions
  • Single items
  • One-shot payments

Products have a unique name, a defined amount, and they can be:

  • One-Time: Imagine you are selling fresh organic vegetables to be delivered everywhere in the city. Users will pay a one-shot based on the goods they choose (products and queries).
  • Recurring: Imagine you are a SaaS company that uses a subscription-based business model. You simply set the subscription name, the amount, and the recurring period to see it work.
  • Pay-As-You-Go: In this case, you linked the account to a wallet that users will fund in exchange for services and/or goods (billable actions). Say you created an app that simplifies the payment of car parking, users will fulfil the wallet and will use it to pay for parking.