Payment terms
Last reviewed 2026-09-30. Served live at /legal/payment.
Price change from 30 October 2026. From that date a statement costs 5 credits for its first plot and 1 credit for each further plot (a three-plot statement costs 7). A one-plot statement stays at 5 credits. Until then every statement costs 5 credits, however many plots it has. This notice is given 30 days ahead, as section 9 of the Terms of Service requires. Credits already bought keep their value: one credit is still one euro.
This page summarises the billing terms for the hosted eudr.dev instance operated by Vortx AI Private Limited. It complements the Terms of Service, the Refund Policy and the Service Level Commitment.
Prices and charges are exclusive of taxes unless stated otherwise. The Customer is liable for all taxes, duties and similar government levies applicable to its jurisdiction. Charges are non-cancellable and non-refundable except as expressly provided in the Refund Policy or as required by applicable mandatory law.
1. Pricing model
The hosted service runs on prepaid credits. One credit is one euro.
| Free credits on sign-up | 100, once per organisation |
| Cost of a compiled, signed Annex II statement | 5 credits; from 30 October 2026, 5 credits for the first plot and 1 for each further plot |
| Statements the free credits cover | 20 one-plot statements |
| Everything else | free |
"Everything else" is meant literally: plot checks against the Article 2(13) cut-off, supplier evidence-gap assessments, country tier lookups, receipt verification, execution traces, exports and reading anything the Customer already holds are not charged, and the Provider does not intend to charge for them. A plot check is how a problem is found; putting a price on it would encourage checking less.
Credits are spent when a statement is compiled. They do not expire, do not reset monthly, and carry forward indefinitely while the account is open.
1.1 What is charged, and when
The charge is taken when the compile starts, because that is the point at which the earth-observation work is committed upstream and cannot be recalled. The price is fixed when the compile starts, from the number of plots the statement covers: each plot is its own satellite check.
The charge is for the analysis, not for a particular answer. A statement that comes back non-negligible — the shipment cannot be placed on the market as it stands — costs the same as one that comes back negligible. That is deliberate: the same measurement work is done either way, and the finding that stops a non-compliant shipment is the more valuable of the two results. An earlier draft of this page described a "pay-on-pass" model that charged only on a filable statement; that model was never billed against and has been replaced by the one described here.
If a compile fails — an error in the engine, or an upstream outage that prevents a verdict being reached — the credits are returned automatically. The refund appears on the wallet ledger against the same task. No request is necessary.
1.2 The public demo
The demo scenarios published on the homepage compile without an account and without credits. They are a fixed set of synthetic consignments over real land, shipped with the software, and they are the only plots that run free of charge to an unauthenticated caller. Analysing any other plot requires an account, and every account receives the 100 free credits described above.
1.3 Buying more credits
Credits are bought in the console under Wallet, at one euro per credit, net of VAT (see section 2). The smallest top-up is five credits, the cost of one statement. There is no subscription and no recurring charge: an account that buys nothing after its free credits are used simply stops being able to compile new statements, and everything else keeps working.
2. Currency and taxes
| Item | Default |
|---|---|
| Display currency | EUR |
| Settlement currency | EUR, through Razorpay |
| VAT / GST | Quoted net of VAT/GST. The Provider invoices in compliance with the place-of-supply rules applicable to the Customer's location. EU B2B customers with a valid EU VAT id receive a reverse-charge invoice (Art. 196 of the VAT Directive); customers without a valid id are charged at the rate applicable to the place of supply. |
| Indian GST | For Customers established in India, IGST/CGST/SGST applies per the Provider's GSTIN and the place-of-supply rules of the IGST Act. |
| Withholding tax | Where applicable mandatory withholding applies to a Customer's jurisdiction, the Customer is responsible for the withholding; the Provider will issue a credit against the invoice on receipt of the corresponding tax certificate. |
3. Payment methods
Credits are bought through the channels below. Whether a given channel is enabled on the hosted instance is shown in the console on the Wallet page; where none is enabled, the free credits still work exactly as described in section 1 and further credits can be arranged by email.
- Razorpay Checkout (enabled on
eudr.dev): card, net banking or UPI, in EUR, one credit per euro. The console creates an order for the number of credits chosen; the payer completes it in Razorpay's own window; the engine checks Razorpay's signature and then reads the settled amount back from Razorpay before crediting the wallet, so a page cannot claim a payment that did not settle. Card and contact details go to Razorpay directly and never reach the engine; the order and payment identifiers are the only payment artefacts kept on our side. Razorpay acts as an independent Data Fiduciary for the payer's data (see Sub-processors). - PayPal Orders v2 and x402 (on-chain USDC) are supported by the software for other deployments but are not enabled on
eudr.dev.
Additional channels for enterprise customers (bank transfer against an invoice, SEPA direct debit, etc.) are available on request via avijeet@vortx.ai. The Provider will confirm in writing what is supported at the time of the request.
4. Invoicing
For credit purchases, the receipt is issued by the payment processor (Razorpay) at the moment of payment. The wallet ledger in the console records every movement — purchases, statement charges and refunds — with the balance each produced, and is exportable for reconciliation against those receipts. Tax invoicing for the Customer's jurisdiction (where applicable) is handled either by the processor or by the Provider on request to avijeet@vortx.ai.
Enterprise customers on a periodic plan (negotiated separately) are invoiced per the terms of their order form.
5. Late payment
Pre-launch placeholder — the late-payment workflow below is drafting intent and will be finalised before the hosted service opens to invoiced enterprise customers.
For enterprise / invoiced plans only, the Provider intends to send a written reminder after the due date and, after a further notice period, suspend service until the invoice is settled. Statutory interest may be applied per the law of the Customer's jurisdiction (Reg. (EU) 2011/7 on combating late payment in commercial transactions for EU-resident Customers; the corresponding Indian commercial-law provisions otherwise). Credit purchases settle at the moment of purchase and are not subject to this section.
6. Refunds, chargebacks, cancellation
See the Refund Policy. In short:
- Automatic, immediate credit return when a compile fails.
- Defect-driven refunds within 14 days of compile.
- A "first compile" 24-hour cool-off for new accounts.
- Service-credit refunds tied to the Service Level Commitment.
- Chargebacks should be preceded by an email to
avijeet@vortx.ai.
7. Price changes
Pricing for new compiles may change. The schedule on the agent card and the README is authoritative; changes take effect on publication for new compiles only and never retroactively against compiles already issued. Enterprise customers receive 30 days' written notice before a change applies to their negotiated plan.
The Provider reserves the right to introduce, change or discontinue any pricing tier at any time subject to the notice obligations stated above; nothing in this policy locks the Provider into any particular price.
8. Data after termination
After account closure the Provider retains:
- the audit-aggregate columns required by Reg. 2023/1115 Art. 4(3), 9(1), 12(5) — HS code, country, quantity, verdict, receipt CID, DDS reference — for 5 years;
- payment metadata required by applicable tax law (the exact retention is set by the Customer's and the Provider's tax-residency rules and is documented at the time an invoice is issued) — vault token id, invoice id, settlement amount; no card data is ever stored on the Provider's side.
The scenario JSON, Annex II body and signed receipt of a statement are the organisation's record: they are kept five years from the statement (Reg. (EU) 2023/1115 Art. 4(3); GDPR Art. 17(3)(b)), even when the member who made it deletes their account, and are erased when the five years end. The Privacy Notice is the operative document on retention.
9. Contact
Billing questions, invoicing requests, dispute notices: avijeet@vortx.ai.
Provider: Vortx AI Private Limited (see Imprint).
This page last changed on . It describes the Regulation as it stood then; where a date or a code matters to a decision, check it against the EUR-Lex text it cites.