Direct questions. Direct answers.
The questions serious buyers actually ask — answered in the vocabulary we use in diligence: observed, designed, conditional.
The product
What exactly is TrustStack ORION?
A white-label, API-first control and evidence layer for high-risk digital commerce. It connects merchant, payment, risk and policy signals into decisions with a reconstructable trail — fourteen registered modules in three rings, five apps, one audit spine.
Is the platform generally available today?
No — and we will not pretend otherwise. Every module’s registry status is ‘ui’: an observed interface or read surface you can inspect, not a statement of general availability. What is observed, designed and conditional is separated explicitly on the modules page, in the manual and in diligence.
What do ‘observed’, ‘designed’ and ‘conditional’ mean?
Observed: present in the reviewed product surface, shown as-is. Designed: documented target behavior, subject to implementation and validation. Conditional: dependent on entitlement, integration, data, jurisdiction, licensing or contract. Every capability claim on this site uses one of these three states.
Is TrustStack really white-label?
By design. Merchant- and customer-facing flows carry your brand and your domain. TrustStack stays visible where auditors look — not where your customers shop.
The scenarios
Are the interactive scenarios real cases?
No. Aster Market, Lumen Digital, PSP-A and PSP-B are deliberate fictions in one synthetic universe. Every count is deterministic story data. The scenarios demonstrate the decision discipline — not customer results.
Are the numbers on this site guarantees?
They are engineering targets agreed per segment in a pilot Statement of Work and then measured weekly. They are not forecasts, and nothing on this website is a contractual commitment.
The pilot and working with us
What does the 90-day pilot involve?
Four phases — frame (weeks 1–2), connect (3–6), exercise (7–10), decide (11–12) — with KPI targets, evidence gates and stop conditions agreed up front. At day 90 the evidence supports a scale, revise or stop decision. No lock-in before the numbers.
What do you need from us to start?
One technical owner and one risk/compliance owner, payment logs (auth and decline codes) and dispute data, sandbox access to your PSPs, an approved risk appetite and a confirmed product scope. The first conversation is thirty minutes.
Who is behind the product?
E-KMC.EU P.S.A., a Gdańsk-based compliance engineering company (KRS 0001011332), led by Marek Kamiński, PhD in Law. Corporate services live at e-kmc.eu; the diligence pack is available under NDA.
Privacy and security
How is our data treated?
This website collects nothing: no cookies, no analytics, no browser storage, no third-party requests. The platform itself is designed around tenant isolation, least privilege, append-only audit design and data minimization — the security page and the diligence pack carry the specifics.
Test one decision journey against an agreed baseline.
A scoped 90-day evaluation can use synthetic, shadow/read-only, bounded-exercise or carefully approved production posture. Diligence and contract define the hypothesis, controls, evidence gate and stop conditions before any live intervention.