Private operational prototype briefing

Restaurant operational workflow with regulated instant payment confirmation.

Active Cluster Ltd is developing operational workflow software for restaurant, hospitality and local merchant scenarios where payment confirmation follows real-world service completion.

The initial UK focus is restaurant operational workflows where businesses need clear Faster Payments confirmation, reconciliation visibility and merchant-facing settlement status.

Payment is generated by operational completion, not by browsing or discovery.

Eight-screen restaurant workflow

Static sanitized screens arranged in operational order. The examples are intended to explain the workflow, not to expose production systems.

1. Customer selects a nearby restaurant

The customer interacts with nearby restaurant workflow surfaces connected to real merchant profiles.

2. Customer selects menu items

The customer selects dishes and prepares an operational restaurant order.

3. Customer creates and submits an operational order

The operational request is submitted to the restaurant service desk.

4. Restaurant receives the order and sends a prepayment request

The restaurant receives the operational request and generates a structured prepayment request linked to the order.

5. Customer receives the payment request and opens the payment page

The customer receives the operational payment request and opens the payment workflow page.

6. Customer submits the payment instruction to Interlock

The customer submits a payment instruction. Interlock coordinates operational payment routing toward regulated payment infrastructure.

7. Customer receives payment status confirmation

The customer receives operational payment status visibility linked to the restaurant workflow.

8. Restaurant receives merchant-visible payment confirmation

The restaurant receives merchant-visible settlement and payment confirmation status linked to the operational order.

Why the payment infrastructure partner matters

Operational requirement

The merchant needs to know whether the payment was confirmed, whether the amount is correct, and whether it belongs to the restaurant order.

Potential regulated infrastructure areas

Potential areas include Faster Payments, payment confirmation, reconciliation visibility and merchant-facing settlement status.

Illustrative API and webhook examples

Simplified examples intended to explain operational payment confirmation and reconciliation logic.

Illustrative examples only. No production endpoints, credentials, internal paths or live banking connectivity are exposed.

{
  "workflow_id": "wf_restaurant_001",
  "source": "restaurant_service_completed",
  "amount": "42.50",
  "currency": "GBP",
  "payment_method": "faster_payments",
  "status": "awaiting_payment_confirmation"
}

{
  "workflow_id": "wf_restaurant_001",
  "payment_status": "confirmed",
  "settlement_visibility": "merchant_visible",
  "confirmation_channel": "regulated_instant_payment"
}

Current status and legal clarity

Active Cluster Ltd is currently focused on private development, operational workflow modelling and infrastructure partner discussion. Public onboarding and production payment connectivity are not yet live.

Current legal entity

Active Cluster Ltd is the current UK legal and contractual entity for the initiative.

Project names

References to PVA, Interlock and Unistandard describe internal modules and operational workstreams rather than separate current contracting entities.