Link

Introduction

Table of contents

  1. Audience
  2. What is it?
  3. Why PAYLAY?
  4. Microservices Architecture
    1. PaymentServer
    2. Dashboard
    3. IdentityServer
  5. Docker
  6. Database
  7. AppSettings
  8. Community vs Enterprise
  9. Try out PAYLAY yourself

Audience

This guide was written for developers and people in technical roles.

What is it?

PAYLAY is a complete Payments Framework solution for easily developing and integrating payment processes into your organisation’s software platform:

  • connect to Leading Payment Service Providers
  • connect to Messaging Systems
  • supports Leading Database Providers

The following high level illustration should give you a pretty good summary of what PAYLAY is.

alt text

Why PAYLAY?

The PAYLAY ecosystem acts as an abstract payment layer to which your application communicates with, instead of directly connecting to payment providers.

PAYLAY already did the heavy lifting for you: we have implemented a set of Payment Providers and will proactively add more.

So once you have implemented PAYLAY, you can simply pick a Payment Provider and start processing payments.

This means that when you need a new Payment Provider there is no need to read through lengthy documentation (again) 👍 Not only will it save you time, you now have more time for coding ❤️

You can compare this to the programming concept of interface and classes. PAYLAY acts as the interface, whereas each Payment Provider is a concrete implementation.

Microservices Architecture

The PAYLAY ecosystem was designed and built according to a microservices architecture.

It consists of a collection of independently deployable services, with each service serving a specific function.

We have the following microservices:

PaymentServer

Headless microservice that exposes a REST API that allows your application to perform payment requests without having to know the specific implementation details of the payment provider.

Dashboard

This microservice depends on the PaymentServer and acts as the presentation layer of the PaymentServer. It allows the user to configure API keys, view real-time payment information, perform refunds, etc.

IdentityServer

This microservice acts as the authentication provider that allows users to Single Sign On into the PAYLAY ecosystem.

We expect to have more microservices in the future that will extend the possibility of PAYLAY.

If you wish to develop microservices for the PAYLAY ecosystem, please contact us at info[at]paylay.io

Docker

All microservices are available via Docker images. They can be deployed to any environment that supports containerization: on-premise or in the cloud.

Database

PAYLAY microservices that require a database could support a set of Database Providers such as MySql and SqlServer.

AppSettings

Each microservice can be configured for your specific use case using environment variables, or JSON configuration files.

Community vs Enterprise

PAYLAY is available as a Community Edition (CE) and an Enterprise Edition (EE).

The CE comes with a smaller set of supported Payment Providers and Database Providers.

Try out PAYLAY yourself

We believe that the best way to understand PAYLAY is to simply try it out.

We have written a concise installation guide where you can install all PAYLAY microservices on your local dev machine in matter of minutes.