Questions

The questions, with the answers we would give on a call.

If something is not here, write to contact@corlayr.com and we will answer it, then add it to this page so the next person does not have to ask.

Commercial

Do we deploy this ourselves, or do you run it?
You deploy it. Corlayr is software: it runs in your infrastructure, your customers' data stays in your database in the jurisdiction you chose, and we have no route into it. That also means we are not a banking partner sitting in the middle of your business.
Can we buy part of it?
Yes. Thirty-one modules are in every deployment because the rest depend on them; the other eighteen are licensable. An institution that does not acquire cards does not carry card acquiring.
What does it cost?
It depends on which modules you take and how many entities you run. There is no per-transaction fee, because a core banking system that charges you more for succeeding is a system you will eventually want to leave.

Technical

Can we extend it?
Both portals are built on the same public API an integrator gets, so there is no privileged internal route. Controls, questionnaires and risk cards are configuration rather than code, and provider integrations are a declared capability with an adapter behind it.
How do we get our existing book onto it?
Through the same API, with the ledger in manual mode while the rails are still being connected. An officer books the movement, the ledger posts it, and when the rail is live the identical entry is produced automatically. There is no cutover weekend.
What happens if a provider goes down?
A control that cannot reach a verdict returns an error rather than a pass, so nobody is onboarded on the strength of a timeout. A payment rail that stops answering is queried rather than resent, because the one thing worse than a payment you cannot account for is two of them.

Compliance

Will this survive an audit?
That is what it is built for. Every state change is hash-chained and append-only, the database refuses an update on the evidence table, and the chain head is anchored outside the system. An examiner asking what a record said at a point in time gets an answer rather than a reconstruction.
Which jurisdictions does it cover?
The controls, questionnaires, risk cards and limits are configuration, so a regime is a configuration rather than a fork. The reporting formats are per regime, and we will tell you plainly which ones are in the box before you sign anything.

Ask us the awkward one.

The questions that make a vendor uncomfortable are the ones worth asking, and they are the ones we would rather answer before you sign anything.