Status in seconds
The PSP event becomes an Atena answer inside the active WebChat session.
Deméter reads the event from your PSP and translates it into plain human language: deposit confirmed, withdrawal processing, estimated time and failure reason. The one who talks to the player is always Atena.
Your R$ 500 withdrawal was approved at 14:32. The bank usually releases it within 2 hours.
The one who speaks is always Atena. Deméter is where what she knows about your money comes from.
The PSP event becomes an Atena answer inside the active WebChat session.
A failure becomes guidance: what happened and what the next possible step is.
Cortex does not process payments or touch card data. It only communicates status.
The application only writes: every status communicated enters the audit trail with a tracing identifier and a chained hash.
Pix time, available method and refusal reason explained by Atena in plain text, in the operation's currency — not in gateway error codes.
The bank refused because the account name does not match the one on your profile. Update the Pix key in your details and the withdrawal can be resent.
Processing, reconciliation and chargeback stay in your PSP. Deméter ingests the typed event and delivers the data ready for Atena to answer.
With no confirmed event, Atena communicates the uncertainty honestly instead of claiming a conclusion — Deméter does not hand over what the PSP has not confirmed. A review hold is communicated neutrally.
“It is on its way, just wait 2 hours.”
I do not have the bank confirmation yet. The status stays here and updates on its own — if you leave and come back, it will be up to date.
Every status communicated enters the audit trail with a tracing identifier and redacted PII. The application only writes: changes and deletions are blocked in the database itself, and any break in the hash chain shows up in the check. This is what is called a WORM audit trail. Disposal only happens at the end of the retention period, as the LGPD requires.
Your system sends the typed payment event; Deméter starts reading that contract.
Each tenant's times, methods and failure reasons become the basis of the messaging.
Go-live monitored for 15 days, with status accuracy in plain sight.
No. Processing, reconciliation and chargeback remain in your PSP. Deméter consumes the payment event and hands the status to Atena to answer in WebChat.
No. The messaging works with a transaction reference, status and amount — never with the card number. PCI-DSS scope remains with the operator and the PSP.
Atena communicates the uncertainty: she says the transaction is still processing, without claiming a conclusion. Deméter does not hand over a time the PSP has not confirmed — the status stays in the conversation and updates on its own when the event arrives.
Neutrally: the player knows the transaction is being verified and what the next step is. Holding or releasing is the operator's decision, and Deméter does not hand Atena anything that belongs to an investigation.
No. The one who speaks in the WebChat you already operate is Atena; Deméter delivers the payments data behind that answer. Integration with your payment system is by typed event.
Per credit. A Deméter lookup inside an Atena answer generates no extra charge — it counts as a single credit. Each plan includes a monthly credit pool.
All agents pause, compliance included, until top-up. No conversation is cut mid-way: whatever started is finished, and your team keeps working from the Backoffice, because human service consumes no credit. Usage is metered per cycle and per agent and stays available for review at any time; there is no automatic usage warning, so watching the balance is up to the operator. The legal duty of responsible gaming and anti-money-laundering remains the operator's, with or without credit.