Concept

The Payment Processing System (PPS) is an engine and a framework to provide API for Mobile banking and process payment transactions between individuals, banks, and organizations.

In this case, the transaction capabilities are one of cornerstones behind system design and can represented like this:

  • step invocation,

  • retrying attempts in case of step failure,

  • and rolling back the whole transaction.

Context Diagram

Flow

The framework enables software developers to implement transaction processing steps and compose them into a processing procedure called “Flow.”

PPS Flow
  1. The PPS engine provides HTTPS API to post payment transactions or get transaction details.

  2. The API is intended for private usage inside the enterprise.

  3. Bank software that needs transaction processing capabilities invokes the PPS engine’s API to process the transaction.

Readers familiar with Open Banking can consider the following example:

  1. PPS runs behind the Account Servicing Payment Service Provider (ASPSP) API.

  2. Payment Initiation Services Provider (PISP) negotiates payment consent and payment order with ASPSP API

  3. ASPSP sends the payment order to PPS for asynchronous processing.

Demo