Latest All green. Still blind. Thesis What is autonomous payment decisioning?
Autonomous payment decisioning

Orchestration executes. Pillar8 decides what should be executed.

Pillar8 is the decision layer above payment orchestration. Before every transaction reaches execution, it decides the route, the friction, the fallback, the FX path and the recovery — and learns from every outcome.

One call before executionOrchestrator unchangedEvery decision explainable

What is at stake

$10M

recovered by a 1% authorization lift, per $1B processed a year.

Source: Worldpay
85–90%

average global card authorization. Best-in-class: 97%+.

Source: Worldpay
89% · 47%

have failover. Only 47% exceed 97% approval.

Source: PYMNTS Intelligence × Spreedly, 2026

The tooling is there. The decisions aren't.

The layer above execution

Every payment stack has an execution layer. Almost none has a decision layer.

Orchestration connects PSPs, runs the flow and executes reliably at scale. It executes what it was configured to do — by someone, months ago, for an average day.

Payments is never an average day. Pillar8 sits above orchestration and decides, per transaction, what should be executed now.

  • 01One API call before execution.
  • 02Your orchestrator executes the decision, unchanged.
  • 03No migration. No replatforming. Nothing irreversible.
Checkout
Customer session
Where the shopper — or an agent — chooses how to pay.
Decision layer
Pillar8
Decides how this transaction should be handled, right now — and learns from the outcome.
Decision package →
route3DS posturefallbackFX pathrecovery
Execution
Orchestrator
Executes the decision through its existing connections. Nothing in it changes.
Processing
PSPs & acquirers
Authorize, capture, settle. The rails stay the rails.
The shift

Same transaction. Two answers.

Pick a moment every payments team has lived through.

Busiest hour of the quarter. Approval on PSP A is sliding. Nothing is down, nothing alerts.

Same transaction€184Visa creditGermanypeak hour
The ruleconfigured months ago
Visa · DE → PSP A

Routes to PSP A, exactly as it was told.

DeclinedThe loss shows up in next week’s report.
The decisionmade now, for this transaction
route
PSP B
fallback
PSP C, ready

PSP A’s outcomes changed in the last few minutes.

ApprovedThe outcome feeds the next decision.
Illustrative example. Not real transaction data.The four moments, in full

Era 01 Static: rules written onceEra 02 Dynamic: configured, reviewed weeklyEra 03 Autonomous: decided per transaction

Two decision points

Two moments decide whether a payment succeeds. Pillar8 owns both.

DP1Before checkout

Which ways to pay, in what order.

Which payment methods to show, in what order, and which to suppress.

Ran in productionDP1 ran live for real shoppers at a Shopify Plus merchant, measured against a control group.
DP2Before orchestration

How this transaction should be executed.

Route, 3DS posture, fallback, FX path and recovery — decided for this transaction, right now.

Decision packageEUR 412.00 · card · cross-border
route
PSP-B · acquirer EU-2
3ds
frictionless · exemption requested
fallback
PSP-C → PSP-A
fx
settle in EUR · no DCC
recovery
soft decline → retry on PSP-C
guardrail
within merchant limits ✓
WhyApproval on the default route for this corridor has dropped in the last hour.

Self-learning

Every outcome feeds the next decision. Nobody writes a new rule for the market to change.

Agentic commerce

When software initiates the payment, the decision changes. Pillar8 is designed to treat agent-initiated transactions as their own channel.

Designed for control

Autonomous does not mean uncontrolled.

  1. 01

    Shadow

    Decides alongside your live flow. Nothing changes.

  2. 02

    Compare

    Decisions against outcomes, on your traffic.

  3. 03

    Activate

    A segment you choose, a percentage you set.

  4. 04

    Learn

    Every outcome sharpens the next decision.

  • Every decision explainable
  • Full trace per transaction
  • Designed for merchant-level isolation
  • Designed to be reversible at every stage
What it is not
  • Not a PSP
  • Not an orchestrator
  • Not a rules engine
  • Not a fraud tool
  • Not a dashboard

It improves the orchestrator. It never replaces it.

Start a conversation

Thinking about the layer above your orchestration?

Whether you run payments, build an orchestration platform or invest in the stack — I'm glad to compare notes.