AlpaCore Trust Center
← AlpaCoreLast updated: 9 September 2026
This page records the legal operator, payment-data boundary, ledger execution model, and compute profile of AlpaCore Engine for enterprise due diligence. It is a statement of controls, not a sales document.
AlpaCore Engine is operated by the Icelandic limited company named below. The company is registered in Iceland and therefore in the European Economic Area.
Primary account numbers (PAN) and other full cardholder data are not stored on AlpaCore servers. Card collection and authentication are performed by licensed payment institutions. AlpaCore receives settlement and status events after the processor has handled the card data.
This boundary is maintained so that AlpaCore’s own systems remain outside the card-data environment required by PCI-DSS. Payment institutions that accept cards for AlpaCore operate under their own PCI-DSS obligations.
Ledger posting, price floors, allocation, and settlement routing are executed in compiled C# as explicit, testable rules. The same inputs produce the same outputs. There is no generative model in that path.
Artificial intelligence is not used to write account keys, approve or invent transactions, or alter posted amounts. Conversational assistants may explain or draft operational text; they do not authorise money movement or mutate the books. This separation removes model hallucination from financial records.
AlpaCore Engine runs on Railway cloud hosting in the US West region. We do not publish uptime, latency, energy or emissions figures.
Security controls for this service are described on the AlpaCore Security Standard page. That page is a self-assessment, not a certification.