Aegis Rails
DocsTalk to Us
01 / GLOBAL PAYMENT INFRASTRUCTURE

THE PAYMENT
CONTROL PLANE.

Connect the rails. Control the route. Understand every transaction.

Aegis Rails provides programmable infrastructure for processing, routing, protecting and observing payments across multiple acquiring relationships.

Explore the Platform Talk to Aegis Rails
POST /v1/payments→ evaluated→ routed→ authorised→ payment.succeeded
PAYMENT CONTROL PLANE / 001
THE INTELLIGENT RAILS BEHIND GLOBAL PAYMENTS.SCROLL TO EXPLORE ↓
01 →

A payment enters Aegis Rails.

02 / PAYMENT ARCHITECTURE

ONE TRANSACTION. MULTIPLE POSSIBLE PATHS.

A transaction moves through decisions, not just connections. See the control layer between initiation and outcome.

ILLUSTRATIVE FLOW
SELECT A SCENARIO TO EXPLORE

AEGIS RAILS DOES NOT JUST FORWARD THE PAYMENT.
IT DECIDES HOW THE PAYMENT MOVES.

PAYMENT ARCHITECTURE / ILLUSTRATIVE FLOWSCENARIO / US PRIMARY
AEGIS RAILS / DECISION LAYERMERCHANTPAYMENT CREATEDAEGIS RAILSCONTROL PLANERISKEVALUATIONROUTINGENGINEMID_US_01MID / CONNECTORMID_TR_01MID / CONNECTORMID_EU_02MID / CONNECTORACQUIRER AACQUIRERLOCAL ACQUIRERACQUIRERACQUIRER BACQUIRERNETWORKCARD SCHEMEISSUERAUTHORISEISSUERNETWORKACQUIRERAEGIS RAILSNORMALISED RESPONSEMERCHANT← RESPONSE / payment.succeededREQUEST →US_PRIMARY
PATH MID_US_01 → ACQUIRER ADATA ILLUSTRATIVE FLOW
02 →

Aegis Rails evaluates it — across every connected rail.

03 / PLATFORM

ONE CONTROL LAYER. EVERY PAYMENT RAIL.

Aegis Rails is designed to abstract payment complexity behind a single operating layer.

01 / MODULE⌁

Gateway

A unified entry point for payment transactions, designed to keep integration logic consistent across processing paths.

POST /v1/payments
02 / MODULE⑂

Intelligent routing

Define how a payment should move using business rules, payment context and available downstream routes.

RULE → ROUTE
03 / MODULE◇

Risk & protection

Evaluate traffic before it reaches the processing relationships your business depends on.

EVALUATE → ACT
04 / MODULE◫

Observability

Trace decisions, responses and events across the transaction lifecycle.

TRACE / EVENTS
05 / MODULE≡

Reconciliation

Bring processing and settlement information into a clearer operational view.

MATCH / REVIEW
06 / MODULE⊞

Connector layer

Design for multiple payment relationships behind a consistent integration surface.

ONE API → MANY RAILS
03 →

Operations control it through Aegis Control.

04 / AEGIS CONTROL

YOUR PAYMENT INFRASTRUCTURE. ONE CONTROL PLANE.

Operate payments, routes, connectors, risk controls and transaction intelligence from one infrastructure layer.

AEGIS CONTROL
ILLUSTRATIVE INTERFACE
04 →

A route is selected.

05 / INTELLIGENT ROUTING

ROUTING IS INFRASTRUCTURE.

Every payment does not need to take the same path. Aegis Rails is designed to make the routing decision explicit, explainable and adaptable.

Explore Routing
ROUTING RULE / ILLUSTRATIVERULE_001
IF currency = "USD"
AND issuer_country = "US"
AND authentication = "NO_3DS"
THEN route → "ACQUIRER_US_01"
DECISIONRULE MATCHED ROUTE SELECTED
TRANSACTION TOPOLOGY / ILLUSTRATIVESELECTED
PAYMENTAEGIS RAILSRULE_001ACQUIRER_US_01TURKEY_PRIMARYFALLBACK_02
CONNECTOR MID_US_01ROUTE ACQUIRER_US_01STATUS SELECTED
DESIGNED FORRULE-BASED ROUTINGTRAFFIC SEGMENTATIONFAILOVERGEOGRAPHYCURRENCYAUTHENTICATION CONTEXTCONNECTOR HEALTH
05 →

The processing infrastructure is protected.

06 / PROTECTION

PROTECT THE RAILS.

Payment risk should protect more than the individual transaction. It should also protect the processing relationships the transaction depends on.

DESIGNED TO SUPPORT
PROCEED / CHALLENGE / REROUTE / STOP
TRAFFIC CONTROL / ILLUSTRATIVEDECISION LAYER
INCOMING TRAFFIC →PROCEEDINTENDED RAILCHALLENGEAUTH / REVIEWREROUTEELIGIBLE ALT. RAILSTOP✕ NOT FORWARDEDDOWNSTREAM PROCESSING RAILSDECISION LAYERAEGIS RAILSEVALUATE → ACTVELOCITYTRAFFIC QUALITYDECLINE PATTERNCARD SIGNALISSUER COUNTRYAUTHENTICATIONROUTE HEALTHMID EXPOSURE
SIGNALS ILLUSTRATIVEDECISIONS PROCEED / CHALLENGE / REROUTE / STOP

RISK INTELLIGENCE BEFORE THE TRANSACTION REACHES THE RAIL. Aegis Rails is designed to support pre-routing evaluation and can be configured to proceed, challenge, reroute or stop traffic before it reaches downstream infrastructure.

Explore Risk & Protection
06 →

The transaction remains observable.

07 / TRANSACTION INTELLIGENCE

INFRASTRUCTURE
SHOULD EXPLAIN ITSELF.

Not just a status. The route, the response, the decision and the next available path.

TRADITIONAL VIEW
PAYMENT FAILED
Status
FAILED
Error
Payment unsuccessful
AEGIS RAILS / TRACEILLUSTRATIVE TRANSACTION
● PAYMENT DECLINED
SOURCEIssuer
ISSUER RESPONSEDo not honour
NETWORK CODE05
CONNECTORACQUIRER_EU_02
ROUTING RULEEU_PRIMARY
AUTHENTICATIONNot attempted
ATTEMPT1 of 2
NEXT AVAILABLE PATHEU_SECONDARY

Next available path shown for context. Retries only occur when configured.

KNOW WHAT HAPPENED.KNOW WHERE IT HAPPENED.KNOW WHY.
CHRONOLOGICAL TRACEILLUSTRATIVE TRANSACTION
  1. 01Payment created
  2. 02Risk evaluation completed
  3. 03Routing rule matched
  4. 04Connector selected
  5. 05Authorisation sent
  6. 06Issuer declined
  7. 07Response normalised
  8. 08Merchant notified
Explore Intelligence
07 →

Developers control it through APIs.

08 / DEVELOPERS

BUILT FOR ENGINEERS.

One integration. Clear primitives. Complete visibility.

A single API designed to sit in front of multiple acquiring relationships, so your integration stays the same while routes and connectors change behind it.

  • REST APIs
  • Webhooks
  • Idempotency
  • Structured errors
  • Event logs
  • Sandbox
  • Connector abstraction
Explore Developers Documentation

Documentation is coming soon.

API TERMINAL / ILLUSTRATIVE
POST /v1/payments
{
  "amount": 12500,
  "currency": "USD",
  "payment_method": "card",
  "capture_method": "automatic"
}
08 →

The architecture scales across payment relationships.

TRANSACTION MATRIXILLUSTRATIVE
EU_PRIMARY
EU_SECONDARY
GLOBAL_USD
09 / GLOBAL INFRASTRUCTURE

BUILT FOR PAYMENTS WITHOUT BORDERS.

  • Multiple acquirers
  • Multiple MIDs
  • Multiple currencies
  • Multiple regions
  • Multiple routes

ONE CONTROL LAYER.

Connect global and local payment infrastructure through a consistent operating architecture.

Explore Global Commerce
09 →

From requirement to live rail.

10 / MERCHANT JOURNEY

DESIGN. INTEGRATE. ACTIVATE.

  1. 01 / UNDERSTAND

    We begin by understanding how your payment operation needs to work.

    • Markets
    • Currencies
    • Business model
    • Payment methods
    • Processing requirements
    • Acquiring relationships
  2. 02 / DESIGN

    We design the processing architecture and transaction paths.

    • Connectors
    • MIDs
    • Routing
    • Authentication
    • Risk controls
    • Operational requirements
  3. 03 / INTEGRATE

    Your teams integrate and validate the flow in a controlled environment.

    • Sandbox
    • APIs
    • Webhooks
    • Testing
    • Error handling
    • Operational validation
  4. 04 / ACTIVATE

    Move into production with visibility across the payment lifecycle.

    • Production
    • Routing
    • Monitoring
    • Operations
    • Support
10 →

Built on four principles.

11 / OPERATING PRINCIPLES

CONTROL. RESILIENCE.
VISIBILITY. INTELLIGENCE.

CONTROL

Understand and shape how transactions move.

RESILIENCE

Design for multiple paths, not one dependency.

VISIBILITY

Follow the operational trail of every payment.

INTELLIGENCE

Put decision context to work.

12 / BUILD WITH AEGIS RAILS

LET’S DESIGN YOUR
PAYMENT RAILS.

Tell us about your business, your markets and the infrastructure you want to build.

Talk to Aegis Rails