This Payment Policy describes how paying for Cortexly works. The Service at https://cortexly.cloud is operated by FINDEREKA UAB. It forms part of the Terms of Service and should be read together with the Refund & Cancellation Policy.
1. Tokens
Cortexly runs on a prepaid token model. You buy a pack from the Pricing page, tokens are credited to your balance, and each run spends them — reserving tokens at dispatch, debiting on settle, releasing them if a run fails. There is no subscription, no automatic renewal and no per-seat fee — you top up whenever you need to.
Every reserve, debit and release lands on the append-only ledger, so what you are billed for is always traceable back to a run. An estimated cost is shown before a crew is dispatched wherever we can produce one.
2. Prices, currency and taxes
Prices are shown on the Pricing page in EUR. If your card is issued in a different currency, your card scheme or bank performs the conversion at its own rate and may add fees that are outside our control. EU VAT and any other applicable indirect taxes are added at checkout in accordance with the place-of-supply rules for digital services. Business customers in the EU may supply a valid VAT identifier so that the reverse-charge mechanism or any relevant exemption can be applied.
3. Ways to pay
Depending on your country and the provider handling your checkout, we accept major credit and debit cards (Visa, Mastercard and other schemes listed on the checkout screen) and digital wallets such as Apple Pay and Google Pay where these are supported.
4. Who processes the payment
Payments are carried out by third-party payment service providers, whose identities are shown on the checkout screen and on your receipt. Those providers act as separate controllers for the payment data they handle. We never see or store your full card number — we receive only limited transaction metadata (a transaction reference, the last four digits, the card brand and the settlement amount), which is what we need to issue receipts, maintain accounting records and investigate any disputes. The payment transaction itself is governed by the provider’s own terms and privacy notice.
5. Charge and delivery
The charge is initiated when you confirm the purchase at checkout. Once payment authorisation is complete — including any Strong Customer Authentication step (3-D Secure) required by PSD2 — the tokens are credited to your balance and become immediately available to reserve for a run. If authorisation fails, no tokens are added. If authorisation succeeds but the tokens do not land on your balance, please contact us before attempting the purchase again so that we can reconcile the payment against the ledger.
6. Model-provider keys and connected accounts
Cortexly bills you only for tokens spent on the platform. Any usage costs, quotas or overage charges from the model providers whose API keys you plug in — Anthropic, OpenAI, Gemini, xAI, and the like — and from any outside services your agents connect to, are billed to you directly by those providers under their own terms and are not part of your Cortexly invoice. Manage those accounts on your side.
7. Declines, holds and duplicates
A declined payment does not capture funds, but your bank may show a short-lived authorisation hold that is released on its own schedule. If a charge appears on your statement without corresponding tokens on your balance, do not retry the purchase — write to [email protected] with the transaction reference and we will either credit the tokens or request the provider to reverse the charge.
8. Card data security
Card data is captured by our payment provider’s PCI-DSS compliant infrastructure and never touches our servers in full. Only the reduced transaction metadata described above reaches Cortexly.
9. Receipts and invoices
A receipt is emailed for every successful purchase and stored in your account. On request we can reissue an invoice showing your business details, VAT identifier where applicable, and the transaction reference. Please raise invoice-detail changes within a reasonable time — reissuing after your accounting period has closed may not always be possible.
10. Fraud and abuse controls
Purchases are screened for signals that suggest fraud, chargeback abuse or coordinated misuse. Where signals cross a risk threshold, a purchase may be blocked at checkout, a transaction may be held for manual review, an account may be paused, or the payment provider may be asked to reverse the charge. Where a hold prevents a legitimate purchase, contact us with the transaction reference so that we can look into it.
11. Chargebacks
If you believe a charge is wrong, please contact us first — we will normally resolve the matter quickly. Opening a chargeback with your bank before we have had a chance to look at it may lead us to pause the account while the dispute is examined by the payment provider, and, where a chargeback is decided against a purchase that had already delivered tokens, we may deduct the equivalent tokens from your balance.
12. Sanctions
We do not knowingly accept payments from, and cannot supply the Service to, individuals or entities on EU, UK, US or UN sanctions lists, or in embargoed jurisdictions. Where our checks flag a match, the purchase will be declined and the account may be closed.
13. Billing contact
For any billing question — a missing receipt, an incorrect invoice detail, a duplicate charge, a payment that did not go through — write to [email protected] with the transaction reference. Response targets are set out in the SLA.
Contact
FINDEREKA UAB · Company code 308066820 · V. Nagevičiaus g. 3, LT-08237 Vilnius, Lithuania · +370 691 98783 · [email protected]
