> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pillar8.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
# Pillar8 - Payment Decision Intelligence
**Pillar8 is a real-time decision layer that sits above payment orchestration.**
It determines how transactions should be executed before they reach PSPs.
```text theme={null}
Checkout
↓
Pillar8 (decision layer)
↓
Orchestration
↓
PSPs
```
Pillar8 operates across two key decision points in the payment lifecycle:
* Before checkout is rendered (payment experience decision)
* Before transaction execution (routing and execution strategy decision)
For each transaction, Pillar8 analyzes context and returns a decision package that guides shopper behavior and optimizes transaction execution.
***
## The Problem
Most checkout payment experiences are configured statically. Merchants define in advance which payment methods are available, how they are ordered, and which logic applies to different segments—typically relying on historical assumptions, coarse segmentation, and A/B testing cycles.
However, shopper behavior at checkout is dynamic. Each session varies based on device, country, cart value, user behavior, and payment context. This creates a gap between static configuration and real-time shopper behavior.
***
## What Pillar8 Does
Pillar8 introduces real-time decisioning across multiple stages of the payment lifecycle. For each transaction, it:
* Captures context (shopper, device, geography, payment environment)
* Analyzes patterns from transaction data
* Generates a decision package
This decision package includes:
* Recommended payment path
* Contextual scoring signals
* Confidence indicators
* Eligibility and gating logic
* Execution strategy (routing, fallback, friction)
***
## Decision vs Execution
Pillar8 focuses on **decisioning**, not execution. The system produces a decision package; how that decision is applied depends on the checkout environment.
Execution may include:
* Advisory guidance (native Pillar8 surface)
* Merchant-controlled ordering or highlighting
* Checkout-specific UI behavior
***
## Where Pillar8 Sits
Pillar8 operates at two decision points:
Before the checkout is rendered, determining how payment options should be presented and guided.
`Shopper → Pillar8 → Checkout UI`
Before the transaction is executed, determining how it should be processed.
`Checkout → Pillar8 → Orchestrator / PSP → Issuer`
***
## Integration Summary
Pillar8 integrates with minimal effort:
* **Client-side integration** in checkout
* **Server-side webhook** for transaction outcomes
Typical integration time: **a few hours to a couple of days**
***
## What Pillar8 Does Not Do
* Does not process payments
* Does not route transactions
* Does not store or require cardholder data for decisioning
* Does not modify payment infrastructure
***
## Next Steps
Integrate in minutes
Full request/response structure
System design overview
Platform-specific implementation