Platform
Security and operations, stated plainly.
What the platform is hosted on, who can do what inside it, and what we are not claiming on this page. Written for the people who have to assess a vendor.
Where the platform sits.
The Liquiditas platform is hosted on infrastructure that holds ISO 27001 certification. That certificate is held by the hosting infrastructure provider, not by Liquiditas Ltd: we rely on the provider’s certification rather than holding one of our own.
On top of that infrastructure we run the platform itself — programme configuration, invoice and approval workflows, access control, audit trails and reporting. Data is encrypted in transit and at rest. Each of the three parties below holds a different piece of it, so the split is worth stating explicitly.
Who is responsible for what
- Hosting provider: the infrastructure and its ISO 27001 certification.
- Liquiditas: the platform itself, its configuration options, workflow controls and the audit record.
- You: your users, your programme rules and your own regulatory obligations.
Access, approvals and records.
What the platform enforces inside a programme, and what it keeps afterwards.
-
Role-based permissions
Access is defined by role. A user can see and do what their role allows, and permissions are set per institution rather than shared across the platform.
-
Users administered per institution
User accounts are administered per institution, by that institution’s own administrators.
-
Configurable approval steps
Approval steps are configured around your operating model, so an invoice follows the chain your organisation requires before it becomes available for early payment.
-
Full audit trails
Actions on the platform are recorded: approvals, early-payment requests and configuration changes all leave a trail that can be reviewed afterwards.
-
Programme records
The platform records programme activity for reporting: what was approved, what early payment was requested and the status of each item.
Integrations and platform scope.
How the platform fits the systems and markets a programme actually runs in.
-
Multi-currency and multi-language
The platform runs in multiple currencies and languages, so a programme can be configured for the markets it serves.
-
Modular
The platform is modular. A programme can start with one solution and add others as it grows.
-
ERP and plugin integrations
ERP and accounting systems connect through integrations and plugins, for invoice import, data exchange and reporting.
-
API for core banking or lending systems
An API is available for core banking or lending systems, for institutions that need programme data inside their own stack.
AML/KYC: workflow controls, not a compliance service.
The platform provides workflow controls that may support a customer’s own AML/KYC processes: onboarding steps, document collection and approval gates inside the programme workflow.
The institution remains responsible for its AML/KYC obligations and for the decisions taken under them. Liquiditas does not perform AML/KYC on the institution’s behalf.
What this page does not claim.
-
Liquiditas does not itself hold the ISO 27001 certificate; the hosting infrastructure provider does.
-
Liquiditas does not provide funding, take credit decisions or make payments.
-
Anything not stated on this page has not been assessed here.
Programme capabilities, workflows and integrations are described on the platform page. If your assessment needs something this page does not cover, put the question to us directly rather than inferring an answer from silence.
Explore the platform