An EverAI Charge: How to Check Whether It Matches Candy AI
Compare an EverAI statement entry with receipts, purchase identity and account records without assuming every matching descriptor is an authorized Candy.ai payment.
Candy.ai’s help center says its subscription statement descriptor is EverAI. Treat that as a clue, then match the date, amount, currency and purchase account to a receipt. The descriptor alone does not establish that a particular transaction is yours or that it was authorized.
Candy.ai’s billing-statement help page identifies EverAI as its subscription descriptor. That can explain an unfamiliar label. It cannot, by itself, prove that a specific statement entry matches your purchase or was authorized by you.
Use the label as the beginning of a reconciliation, not its conclusion. This guide does not access bank records, identify a merchant from a private statement or determine whether fraud occurred.
Match the transaction, not just the name
Search your own purchase records for a receipt or renewal acknowledgment. Compare the transaction date, amount and currency. Note the account associated with the purchase and whether the record concerns recurring access or a separate purchase.
The Terms of Service identify EverAI Limited as the operator and describe paid services. That supports the brand-to-operator connection. It is still the receipt and account record that should connect an individual charge to your activity.
| Evidence | What it can help establish |
|---|---|
| Statement descriptor | A possible merchant connection |
| Matching receipt | A dated purchase and the account used |
| Account subscription screen | The current subscription state shown to that account |
| Cancellation acknowledgment | What renewal action was confirmed and when |
If there are two similar entries, keep two separate rows in your notes. Do not assume they are duplicates merely because the descriptor is identical. Two purchase events, two accounts and a genuine unexplained second transaction require different evidence.
Avoid retrofitting an explanation
A hypothetical annual subscription paid months earlier and a recent separate purchase may share a recognizable brand connection. The recent statement entry should still match its own receipt. Do not force every line into the first subscription record you find.
If a family member or another authorized payer may be involved, check through your normal private communication and account records. Do not publish someone else’s account details or assume their consent from a shared device.
When no receipt matches, record that result honestly. A merchant name alone is not a reason to dismiss an unfamiliar payment, and the absence of a quick match is not enough to name a culprit.
Ask the channel that can investigate
For a recognized Candy.ai purchase with an account question, use official support reached through the service or its linked help center. Give the transaction reference, date and amount through that channel, with unnecessary payment details redacted.
If you believe the transaction was not authorized, use your card issuer’s established contact route for the account-specific payment concern. Do not rely on a phone number posted in a search-result snippet or a stranger offering a guaranteed refund.
Keep renewal cancellation separate from transaction identification. A current canceled state does not erase an earlier valid charge, while an unexplained transaction still deserves investigation. Your useful result is a documented match or a clearly scoped unresolved item, rather than a conclusion based only on the word EverAI.
Sources and verification
This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.