Pilar Core Banking Integration Hub

Every digital channel at the bank had its own way of talking to the host. Pilar put a single, monitored hub between them so that new channels could be added in weeks rather than quarters.

The brief

One integration layer for internet banking, mobile, ATM switching and partner APIs, with consistent limits, audit trails and a dashboard operations could read at three in the morning.

Key points

• Message mapping specifications for every host transaction.
• Cut-off and limit rules documented in BPMN.
• Operations dashboard with alerting.
• Regression pack executed before every host release.

What we built

A Spring Boot hub translating REST and queue messages into ISO 8583 and host formats, a rules engine for limits and cut-off times, and an operations console with per-channel health.

Example in code

<?php

namespace App\Models;

use App\Support\Enums\PostStatus;
use Illuminate\Database\Eloquent\Builder;

class Post extends Model
{
    public function scopePublished(Builder $query): Builder
    {
        return $query
            ->where('status', PostStatus::Published)
            ->where('published_at', '<=', now());
    }
}

Outcome

Four channels migrated without a single host change, and the end-of-day batch stopped being the thing everyone feared.

Documentation that nobody reads is still better than tribal knowledge that leaves with people.

Takeaways

The hub succeeded because the mappings were written down before the code; the code was the easy part.