PGateway

Features

Integration gateway for regulated businesses: forward every call, decide nothing, lose nothing.

Everything a call needs on its way through

Built for integrations where a lost, duplicated or silently altered message is not acceptable.

Channels, internal systems, callbacks and operators each come in through their own door with their own trust rules.

Every route has a data contract checked with JSON Schema, plus a mapper that converts between formats and keeps money amounts exact.

A repeated key never runs twice: the first answer is replayed, and the same key with a different body is refused.

Safe retries, circuit breakers and per-target isolation so one slow partner does not stall the rest.

Asynchronous routes and webhooks are queued in PostgreSQL; partner callbacks are verified before they are accepted.

An append-only audit trail and a journal of every exchange, with sensitive fields masked and long-term archive.

Stages run in a fixed order, and the record of the call is written before the call goes out.

1
Authenticate
The channel is identified from its certificate (or a token on listeners that allow it).
2
Validate and map
The body is checked against the route's contract and mapped to the partner's format.
3
Claim and record
The idempotency claim and the in-flight record are written in one transaction, before anything is sent.
4
Forward
The call goes out with retry, breaker and bulkhead; the verdict is classified, not guessed.
5
Journal and archive
The exchange is journaled with sensitive fields masked and archived on object-lock storage.

Tell us which systems you connect and what you must be able to prove afterwards.