Legacy ledger provider
/*
 * The legacy model of core banking,
 * built around batch cycles and manual ops.
 */
void core_run(ledger_t *ledger) {
    ledger_open(ledger);
    run_batch_posting();
    run_overnight_recon();
    run_manual_review();
}
Solid Banking Technologies
/*
 * A real-time core,
 * where humans and agents co-operate.
 */
void core_run(ledger_t *ledger) {
    ledger_open(ledger);
    run_realtime();
    run_api_first();
    run_agent_ready();
}

API-FIRST CORE BANKING

Build on a real-time core with stable interfaces

Solid is built for teams who prioritize versioned APIs, event-driven integration, and audit lineage from request to state change.

UNIFIED DATA LAYER

Shared contracts across loan, credit, and deposit

The API model follows the platform data model. The same operations apply across loan, credit, and deposit — configured rather than duplicated.

  • One contract, three products. Same operations across loan, credit, and deposit — not three parallel endpoint families.
  • Compact surface. Fewer routes to learn, less contract drift, cleaner reconciliation between operational systems.
  • Consistent through the core. Identifiers, lifecycle states, and event ordering match the platform data model — strongly typed end to end.

WEBHOOKS AND EVENT FLOWS

Choose pull, push, or stream by integration need

Use synchronous APIs for command paths and event delivery for downstream state propagation.

Command APIs

Initiate account, payment, and credit actions through explicit write endpoints.

Webhooks

Push critical lifecycle changes to consuming systems as they happen.

Streams

Feed analytics and decision services with ordered event data.

Replay and recovery

Reprocess event chains safely during outages or subscriber changes.

STABILITY AND VERSIONING

Integrations should age predictably

Core integrations are long-lived. Contract governance is treated as an operating requirement, not a documentation task.

Release discipline

  • Versioned endpoints with explicit deprecation timelines
  • Backward compatibility for active consumers
  • Change logs focused on operational impact

Operational safeguards

  • Idempotency keys for write consistency
  • Deterministic error semantics for retry logic
  • Observability hooks for tracing and incident analysis

AGENT-READY

An API agents can drive directly — no wrapper layer

The same compact, contract-first API that integration teams use is what agents call directly. Same authorization, same audit trail, same events — whether the caller is a human integrator, a service, or an AI agent.

TALK TO THE TEAM

Architects and platform leads welcome

Schedule a call to walk through the API surface, event model, and versioning approach in detail.

Schedule a call See architecture page