05 / INTELLIGENCE

DON’T JUST PROCESS. UNDERSTAND.

A transaction is more than a final status. See the route, response, timing and decisions behind its outcome.

HOW IT WORKS

EVERY RESPONSE. ONE LANGUAGE.

01 / TIMELINE

The transaction as a sequence of events.

Each payment carries a timestamped record from request to webhook, including internal decisions that a connector never sees.

TIMELINE / PAY_AG_7MX10ILLUSTRATIVE
10:42:17.021payment.created
10:42:17.089risk.evaluated — PROCEED
10:42:17.101route.selected — EU_PRIMARY
10:42:18.031attempt_1.declined — issuer 05WARN
10:42:18.040payment.failed — returned to merchant
02 / RESPONSES

Issuer, connector and unified responses side by side.

Different acquirers describe the same decline differently. Intelligence keeps the raw issuer code and connector message, and adds a unified category merchants can act on.

RESPONSE MAPPINGILLUSTRATIVE
ISSUERCONNECTOR RAWUNIFIED
05DO_NOT_HONORissuer_declined
51INSUFFICIENT_FUNDSinsufficient_funds
91ISSUER_UNAVAILABLEissuer_unavailable · retryable
—TIMEOUTprocessor_timeout · retryable
03 / ATTEMPTS

One payment, several attempts — counted honestly.

When a payment is retried on a fallback route, approval analysis separates first-attempt outcomes from recovered ones, so retries do not hide a weak primary route.

ATTEMPTS / PAY_AG_3RT88ILLUSTRATIVE
#ROUTERESULTLATENCY
1EU_PRIMARYprocessor_timeout8,000 ms
2EU_SECONDARYapproved910 ms
NEXT STEP

BUILD THE RIGHT
PAYMENT PATH.

Let's discuss the infrastructure your business needs.

Talk to Aegis Rails