orvacon
Roadmap

Shipped, in flight, and honestly planned.

orvacon is v0.3. This is what's real today and what's coming — without dates we can't promise. Anything not shipped is labeled as such.

0.x semver/No hard dates/No "supports everything"
Shippedv0.3
@orvacon/paykit

Core orchestrator: state machine, money typing, idempotency, hash-chained ledger.

connector-iyzicoverified

Raw-card and stored-card 3-D Secure, verified end-to-end against the sandbox.

adapter-supabase

Schema generation with default-deny RLS.

adapter-nextjs

App Router handlers and webhook verification.

cryptokit · CLI

Ed25519 signing primitives and the orvacon CLI (keys, generate).

Documentation

The full Fumadocs reference — setup, paykit, connectors, adapters, cryptokit and the CLI.

API stabilization

The 0.x surface settled toward 1.0, shipped in 0.3.0.

In progressnext
connector-paytr

The second gateway behind the same contract — base64 signatures, panel-set callback, plain-text ack. Exercises the connector abstraction before we freeze it.

1.0 API

Freeze the surface once a second connector has proven the contract holds.

Plannedlater
Bank virtual POS

Turkish bank VPOS (3D Pay / 3D Secure) connectors.

UI components

Drop-in payment + 3DS UI for common frameworks.

Subscription · tax · fraud · ledger kits

Higher-level kits layered on the core primitives.

Priorities shift with what people actually build. The clearest signal is a GitHub issue or a thumbs-up on an existing one — the board follows real demand, not a fixed calendar.

Built in the open

Shape what ships next.

Open an issue, upvote a connector, or send a PR. The roadmap moves toward what people are actually building.