Twelve questions about the systems you already have.

The same twelve capabilities an integration assessment measures, asked plainly. It takes about five minutes and scores immediately.

Nothing is stored, nothing is transmitted, and it asks for no contact details. If an answer is not known, say so — that is a legitimate response and frequently the most useful one on the page.

01 · Core and payment-hub integration

Where would a ledger transaction enter your payment estate today? Through the payment hub, on a documented interface with an owner. Through a point-to-point integration somebody stood up for the pilot. Nowhere yet. It would be a new path with no owner. Nobody here could answer this today.

02 · ISO 20022 message mapping

Can you map a pacs.008 to a ledger transaction and back without losing a field? Yes — mapped, tested in both directions, unmapped fields documented. One direction is mapped. The return path is unfinished. No mapping exists. Nobody here could answer this today.

03 · Settlement and posting model

A payment arrives at 2am on a Sunday. When does it post in the core? Continuously. It posts without an operator, at any hour. It queues and posts at the next cycle, without manual intervention. It waits for the next business day, or somebody has to act on it. Nobody here could answer this today.

04 · Corridor design and liquidity orchestration

Who funds the corridor, and what happens when one side is short at the wrong hour? A documented funding model whose behaviour under a shortfall has been tested. A funding model that has held so far and has not been stressed. Funding is a person watching a balance. Nobody here could answer this today.

05 · Reconciliation and break management

Ledger state and core state disagree tomorrow morning. What happens? A documented process runs on a schedule and resolves it. Reconciliation is scheduled, but breaks are resolved case by case. A person notices. There is no documented path. Nobody here could answer this today.

06 · Payment lifecycle and exception handling

A payment is stuck mid-flight with the funds already committed. What is the path? A documented exception path that operations has exercised. A path exists on paper and has never been used in anger. It becomes an incident and a conference call. Nobody here could answer this today.

07 · Node and validator operations

Who operates your ledger connectivity, and what can they see? We do, with peering, storage growth and health all monitored. A vendor does, and we receive a status page. Not established, or entirely inside somebody else's platform. Nobody here could answer this today.

08 · Amendment and upgrade governance

An amendment is scheduled to activate. What happens on your side? It is tested against our integration before it activates, by a named owner. We track amendments and would respond if something broke. We would hear about it from a vendor, or from the failure. Nobody here could answer this today.

09 · Availability, failover and continuous operation

What happens to payments during your maintenance window? Nothing stops. We run through it on failover. A reduced service continues; some functions pause. There is a window in which payments do not move. Nobody here could answer this today.

10 · Observability, SLOs and incident evidence

Could you produce a timestamped account of a payments incident from instrumentation? Yes, from instrumentation, and the path has been exercised. Partly. Some of it would be reconstructed afterwards. It would be assembled from memory across several teams. Nobody here could answer this today.

11 · Throughput, latency and load behaviour

Do you have a measured worst-case end-to-end time across every leg? Yes — measured, including correspondent and vendor legs, at the worst hour. We have a figure, but only for the legs we own. No measured figure. Three people would give three answers. Nobody here could answer this today.

12 · Interoperability and multi-ledger integration

Value has to cross from this ledger into another system you run. What carries it? A designed boundary with documented failure behaviour. A working integration whose failure behaviour is untested. It would be built when somebody asks for it. Nobody here could answer this today.

Scored on this server and rendered back to you. No answer is written to disk, logged, or sent anywhere.