Documentation

Athia

Athia is DEUNA's agentic payments workforce, a set of AI-driven agents, orchestrated by Athia, that operate, optimize, and continuously improve your payments stack.

In practice: Athia watches your payments stack continuously, tells you what to change and why, and, where you let it, makes the change inside the payment flow and measures whether it worked.

What Athia does

PillarWhat it doesNeeds
Proactive intelligenceStrategist surfaces ranked strategies without anyone asking, each with its evidence and the actions it implies. Smart dashboards explain their own movements against your learned baselines.Data only
AI-driven optimizationAgents decide transaction by transaction: which processor to use, how the payment message is composed, whether and when to retry. They improve from every outcome. The Acceptance Agent is live today.Athia in the transaction path, or a batch file exchange
Conversational accessAsk Athia answers questions in plain language and returns the chart, the numbers and the reasoning.Data only

The two ways to run Athia

There are two, and the difference between them is not what Athia knows. It is who applies what Athia decides.

Athia with DEUNA orchestrationAthia on its own
Who executes the decisionDEUNA, on its own railsYou, in your own stack
Proactive intelligence, Ask AthiaIncludedIncluded
Per-transaction executionReal time, inside the payment flowComing SOON!
Acting on a new recommendationNothing to do. It takes effect on the next transactionAn engineering or configuration change on your side
What it asks of youRoute payments through DEUNA orchestrationSend data. Nothing changes about how you take payments
Time to first valueImmediate if you are already on DEUNA orchestrationDays, once a data path is agreed

Athia with DEUNA orchestration

Pros

  • Every recommendation is executed by the same infrastructure that made it. A new recommendation reaches your traffic without your team touching anything.
  • Nothing to integrate for Athia. The attempt-level data Athia needs is already produced by the orchestration layer.
  • Outcomes return on their own, so the agent keeps learning without a callback you maintain.
  • Real-time decisions on processor selection, message configuration and retries, transaction by transaction.
  • The full intelligence layer as well. You do not trade one for the other.

Cons

  • Your payment traffic routes through DEUNA. That is a change to your processing topology, and it carries the vendor and security review any such change carries.
  • Processor connections move to DEUNA, or are shared with it, depending on how you are set up.
  • If you are not already on DEUNA orchestration, that integration comes first. Athia is a given at that point, but the orchestration work is not.
  • DEUNA sits in the authorization path. Fail-open and your static rule configuration bound the risk, but the dependency is real and belongs in your review.

Athia on its own

Pros

  • Nothing changes about how you take payments. No routing change, no processor change, no new pipeline.
  • Fastest path to value. Data only, and Athia maps your field names on ingest, so there is no schema to agree first.
  • The full intelligence layer: Strategist, smart dashboards and Ask Athia, in full.
  • No dependency on DEUNA in the authorization path.

Cons

  • You implement every recommendation yourself. The time from a recommendation to it affecting a transaction is your release or configuration cycle, not Athia's.
  • No per-transaction execution. Athia can tell you that a segment routes badly; it cannot re-route the next transaction in that segment.
  • What Athia sees depends on the path you choose. Freshness and completeness vary, and gaps in the data become gaps in the answers.
📘

These are not a fork in the road. Most clients start with Athia on its own, prove the case on their own numbers, and add orchestration afterwards. Adding it later undoes none of the data work already done.

Where Athia sits

Athia works in two layers and you do not need both. Intelligence runs on the data you send, whatever path it arrives by; a client who never routes a transaction through DEUNA gets all of it. Execution is agents deciding what happens to a transaction, either inside the payment flow through DEUNA orchestration, or as a batch file exchange.

With DEUNA orchestration

Where Athia sits: you route payments through DEUNA
WHERE ATHIA SITS · 1 OF 2You route payments through DEUNA orchestration YOUR PAYMENT PATH Your checkout or system DEUNA orchestration with Athia agents one service, one call Processors every outcome, automatically the agent decides here, inside the orchestration call Nothing to build. The orchestration is the integration. The agent chooses the processor, corrects how the payment message is composed and decides retries, transaction by transaction. WHAT YOU GET INTELLIGENCE Runs on data alone, whatever path it arrives by Strategist ranked strategies, surfaced unasked Smart dashboards explain their own movements Ask Athia plain language, with the numbers behind it EXECUTION Agents deciding what happens to a transaction Real time, in the flow The agent decides as the payment happens. Fail-open if it does not answer in time. Available Batch Scores a file of scheduled charges before they are processed. Available What you change: nothing. If you are already on DEUNA orchestration, you are already integrated with Athia.

If you are already on DEUNA orchestration there is nothing further to integrate. The agent chooses the processor, corrects how the payment message is composed and decides retries, transaction by transaction, and every outcome returns on its own. The right-hand half of this diagram is identical in the second shape, so the two can be read side by side.

Agent consulted in the decisionThe paymentOutcome returning, and what you get

The agent is not a separate hop. It is consulted inside the orchestration decision, on the same call, and orchestration executes what it decides. Every outcome returns automatically and feeds the intelligence layer. There is nothing to integrate beyond the orchestration you already have.

On your own stack

Where Athia sits: you keep your own stack
WHERE ATHIA SITS · 2 OF 2You keep your own processors and your own rails YOUR PAYMENT PATH Your checkout or system Your own processors unchanged, and your own rails Data leaves however you can already send it File dumps to SFTP or S3 A read grant on your warehouse Direct provider connectors DEUNA data, if you route part of your volume any one is enough, and they combine strategies you act on yourself WHAT YOU GET INTELLIGENCE Runs on data alone, whatever path it arrives by Strategist ranked strategies, surfaced unasked Smart dashboards explain their own movements Ask Athia plain language, with the numbers behind it EXECUTION Agents deciding what happens to a transaction Real time, in the flow Needs the payment path. Add DEUNA orchestration later and none of this is redone. Not on this path Batch A file exchange, no routing change. Scores scheduled charges before they run. Recurring billing only What you change: nothing about how you take payments. Athia maps your field names on ingest, so there is no schema to agree first.

Nothing changes about how you take payments, and the intelligence layer arrives in full. Athia maps your field names on ingest, so there is no schema to agree before you start. Real-time execution is the only capability that needs the payment path, and adding DEUNA orchestration later undoes none of this.

Data you already haveStrategies you act on yourselfWhat you get

You keep your processors, your rails and your existing integrations. Athia reads whatever you can already give it and returns the full intelligence layer, plus strategies you act on yourself.

Acting on Athia without DEUNA orchestration

If DEUNA is not in your payment path, a recommendation still has to reach a transaction somehow. How depends on what kind of transaction it is.

MIT, merchant-initiated, scheduledCIT, customer-initiated, at checkout
What it coversSubscription renewals, installments, scheduled chargesAnything with a customer waiting for an answer
How a decision reaches the transactionBatch file exchange. You upload the scheduled charges before they run, Athia returns a scored file, and you or DEUNA execute itStrategies you apply in your own orchestrator. Athia surfaces what to change; your team changes it
TimingAhead of billing, not real timeYour release or configuration cycle
Per-transaction decisionsYes, per row in the fileNot without Athia in the transaction path
How a recommendation reaches a transaction without DEUNA in the path
WITHOUT DEUNA ORCHESTRATIONTwo transaction types, two different answers MIT merchant-initiated, scheduled ahead of time Subscription renewals, installments, scheduled charges Charges due known in advance Athia scores every row, individually Result file processor, message, retry you or DEUNA run the charges A decision per transaction Available today, no integration Why a file is enough here The charge exists before it is processed, so there is something to score and time to score it. Nothing is waiting on the answer. CIT customer-initiated, at checkout Anything with a customer waiting for an answer Customer pays now, and is waiting Per-transaction score needs Athia in the path Your processor Athia surfaces the strategy, your team applies it Segment level, not per transaction On your release cycle Why a file cannot work here Nothing exists to score until the customer is already at checkout. A decision taken afterwards is analysis, not execution. There is no per-transaction recommendations API today. Real-time decisions on customer-initiated payments require Athia in the transaction path, which means DEUNA orchestration. The intelligence layer is unaffected by any of this. Strategist, smart dashboards and Ask Athia run in full on both columns.

If you are choosing between the two, the question is whether your volume is scheduled or live. Scheduled charges get a real per-transaction decision with no integration at all. Live checkout traffic gets strategies at the segment level until Athia is in the payment path. Most merchants have both, and the two are not an either-or.

Decided per transactionYou apply itAvailable todayNeeds Athia in the path

The asymmetry is the point: a scheduled charge can be decided ahead of time, so a file works. A customer-initiated payment cannot, because nothing exists to score until the customer is already waiting.

What Athia needs from you

📘

Live or recurrent transaction data, so Athia can work against what is happening now, and a one-time historical dump so it establishes your baselines from your own population. See Integrating Athia for how much history and how to send it.

Where to go next

PageRead it to
Athia FeaturesSee what each pillar does in the product.
Integrating AthiaPick an integration path and see what it asks of your team.
DEUNA OrchestrationUnderstand how agents act at runtime when DEUNA is in the payment path.
Athia ConnectorsFind your payment, anti-fraud and cost data sources and connect them.
Athia Data DictionaryCheck the fields Athia expects in the data you send.

Updated about 19 hours ago

Did this page help you?