Cortex Cortex
Deméter For authorized operators in Brazil

The player knows where their withdrawal is.

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.

Schedule a demo The buttons on this page open a WhatsApp conversation with the Cortex sales team. No form and no sign-up.
Withdrawal #SB-2026000395R$ 500 · Pix · Tatiana M.
demo · sample data
Request receivedtoday, 14:12
Anti-fraud review14:28 · no restriction
Approved and sent to bank14:32 · PSP event
In the bank queuePSP estimate: up to 2 hours in progress
What the player reads now

Your R$ 500 withdrawal was approved at 14:32. The bank usually releases it within 2 hours.

A withdrawal with no answer becomes a ticket, a complaint and distrust — three times over, from the same player.

Meet Deméter

The one who speaks is always Atena. Deméter is where what she knows about your money comes from.

Status in seconds

The PSP event becomes an Atena answer inside the active WebChat session.

Reason translated

A failure becomes guidance: what happened and what the next possible step is.

Without touching money

Cortex does not process payments or touch card data. It only communicates status.

A record of every notice

The application only writes: every status communicated enters the audit trail with a tracing identifier and a chained hash.

The player's language, not the gateway's.

Pix time, available method and refusal reason explained by Atena in plain text, in the operation's currency — not in gateway error codes.

From event to sentencewhat the gateway sends, what the player reads
Gateway event
status: REJECTED_BY_BANK
payee_name_match: FAILED
reason_code: E_412
What Atena replies, with Deméter's data

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.

No error code, with the next stepthe sentence resolves — no second ticket
Integration permissionsthe money stays in your PSP
ResourceAccess
Read status eventapproved, refused, under review read
Process paymentno capture or refund calls never
Card dataout of scope and out of the database never
Change balanceonly your system moves money never
Reconciliation and chargeback stay in the PSPDeméter only reads what already happened

It consumes the event, not the money.

Processing, reconciliation and chargeback stay in your PSP. Deméter ingests the typed event and delivers the data ready for Atena to answer.

Silence never becomes a promise.

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.

No answer from the bank38 minutes ago · no new event
waiting
What Atena does not say

“It is on its way, just wait 2 hours.”

a time with no event is a promise — and a broken one comes back as a ticket
What Atena replies

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.

Uncertainty shows as uncertaintya review hold becomes a neutral notice, not silence
Trace of one querythree layers of record, and only one of them is the WORM trail
recording
RecordWhere it lands
Internal query to financeEVT-ATN-INTERNAL_QUERY · demeter real-time event
Demeter check recordeddemeter_verificacao · demeter credit ledger
Answer sent to playeratena.message_sent · atena WORM trail
Chained hash of the WORM row · retained 5 years0af58e2371b6c94ad2f0e58b13c7a46d90fe2b1…

Evidence ready for audit.

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.

Live in 15 to 30 business days

Guided rollout Event-based integration 15-day hypercare Tuned to your operation
01

Connect your PSP

Your system sends the typed payment event; Deméter starts reading that contract.

02

Map times and methods

Each tenant's times, methods and failure reasons become the basis of the messaging.

03

Go live with hypercare

Go-live monitored for 15 days, with status accuracy in plain sight.

Frequently asked questions

Does Deméter process withdrawals or deposits?

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.

Does Cortex touch card data?

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.

What happens if the event is delayed?

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.

How is a withdrawal under review communicated?

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.

Do I need to replace my current WebChat?

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.

How much does it cost and how is it billed?

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.

What if the credit pool runs out?

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.