Skip to content

PayBlock — Payment Orchestration Service

Tokenise-Broker Architecture

Dev URL: https://payblock.veropulse.com

Purpose

PayBlock is the central payment orchestration service for the Tokenise ecosystem.

Instead of integrating payment gateways directly into the Broker Backend-Core, all payment-related logic is implemented in this separate service. Other applications (such as the Broker, or future apps like VeroVault) call PayBlock over a well-defined API.

This design keeps payments decoupled from the core broker logic and allows us to adapt to changing payment requirements more easily.

Why PayBlock is a Separate Service

We could have implemented payment gateways directly inside Backend-Core, but we intentionally separated PayBlock as its own service for several reasons:

1. Frequent Changes in Payment Gateways

Payment providers and gateways change often:

  • new gateways are added
  • contracts and commercial conditions change
  • API versions are updated

By keeping all integrations inside PayBlock:

  • we do not need to change or redeploy the main broker core every time a gateway changes
  • payment logic and integration code are localized in one place
  • the broker core remains stable and focused on business rules

2. Per-User / Per-Nationality Gateway Selection

In the future, different users may have access to different payment methods depending on:

  • nationality
  • country of residence
  • regulatory constraints
  • risk profile

PayBlock is responsible for:

  • mapping users (or profiles) to the allowed payment gateways
  • applying rules to determine which PSPs and payment methods are available
  • centralizing this logic so it is not duplicated across multiple applications

This allows us to manage complex payment rules in one place, instead of spreading them across the Broker and other services.

3. Reusability Across Multiple Applications

PayBlock is not only for the Broker.

Other services and applications in the ecosystem (for example VeroVault or any future app) can also use PayBlock for payment operations.

Benefits:

  • Each new application reuses the same payment orchestration layer.
  • We implement and maintain integrations with gateways once instead of duplicating them in multiple codebases.
  • Consistent behavior and logging for all payments across the platform.

Role in the Overall Architecture

Within the Tokenise architecture:

  • The Broker (Backend-Core) initiates deposit/payment flows by calling PayBlock.
  • PayBlock communicates with external payment gateways and returns standardized responses and statuses.
  • Admin tools (e.g. Admin Panel) can display deposit/payment information by reading data from Backend-Core, which in turn relies on PayBlock for the actual payment processing.

This separation makes the system:

  • easier to maintain
  • more flexible when changing or adding payment providers
  • ready for future products that also need payment capabilities