Skip to content
codeon
CodeOn Core
About CodeOn

Built for Georgia.
Single-purpose plugins for the gaps Georgian WooCommerce stores actually hit.

CodeOn is a small studio shipping focused WooCommerce plugins for Georgian e-commerce — TBC and Bank of Georgia card + installment payments, Flitt card payments, 1C and Fina synchronisation, and QuickShipper courier delivery. Each plugin is its own license, its own GitHub repo, its own release stream. Buy only what you need.

Updated from GitHub
Recent releasesShipping
  1. BoG Card v0.1.5Apr 25
    Refund flow verified end-to-end on arttime.ge
  2. TBC Card v0.1.12Apr 24
    Apikey override + status mapping for split captures
  3. Flitt v0.1.1Apr 23
    First public release — SHA-1 callback verification
  4. Fina sync v0.2.0Apr 22
    Multi-warehouse stock + per-brand price lists
  5. 1C sync v0.1.0Apr 19
    Initial public release — exchange node setup
Continuous shipping across eight plugins — every release signed + attributed.
Last commit
Today
THE WHY

A Georgian WooCommerce store stitches five or six plugins from four vendors.

We built CodeOn to make those plugins behave.

BEFORE

The old way

A typical Georgian e-commerce store needs card processing and installments from twobanks, accounting sync with their 1C or Fina back office, and a courier integration for delivery. That's five or six separate plugins from as many vendors — each with its own licensing model, its own admin panel, its own update channel, its own opinions about how WooCommerce order meta should look.

When something breaks during a checkout at midnight, you open four log files to figure out which plugin did what. When TBC rotates a credential, you update it in one vendor's plugin; when BoG does the same, you update it in another. When a plugin author disappears, you're stuck on a version that no longer matches the bank's API contract — and there's no source to fork from.

AFTER

What CodeOn does

Fourteen focused plugins. Each does one thing. BoG Card Payments: bank of Georgia card processing — Visa, Mastercard, 3D Secure. 1C ↔ WooCommerce: keep WooCommerce prices, stock and products aligned with your 1C books. QuickShipper Delivery: live courier rates at checkout — Glovo, Wolt, Go Delivery, OnWay, Easy Way, Georgian Post. SMS Notifications: order-status SMS and customer broadcasts, through Georgian SMS gateways. CodeOn Architect: interactive apartment selector for real estate developers — on your own plans. CodeOn Multilingual: make your WordPress site and WooCommerce store multilingual — any language at its own address, with every page, product and text translated. None of them know about the others. Each ships its own license, its own settings page, its own GitHub repo, its own release stream.

Buy what you need. If you only sell card payments through TBC, you don't install or pay for BoG. When the TBC installments API changes at 11pm, only the TBC Installments plugin needs a release — your BoG checkout isn't at risk. Each plugin is small enough to read in one sitting; under the hood they share a common framework (license layer, watermarking, update channel) but ship independently.

We're not trying to be a payment processor — the banks already are. We're the boring layer between WooCommerce and whatever TBC, Bank of Georgia, Flitt, 1C, Fina, or QuickShipper decide their next API change looks like.

PRINCIPLES

What we actually build around.

Six decisions we've committed to that show up in every line of the plugin and every API response.

Single-purpose, opt-in
Every plugin does one thing. You buy only what you need; settings pages don't reference features you didn't license. Add or drop a plugin without touching the others.
Signed responses, fail-closed
Every license-server response is signed RSA-SHA256 with a key you can verify offline. Each plugin ships the public key baked in and rejects any response it can't authenticate — no signature, no validation, no checkout.
One license, one domain
Each license binds to exactly one WordPress install. Simple to audit, easy to transfer on migration, no ambiguity about whether you're within licence terms.
GPL-3.0, public source
Every plugin's source is public on GitHub under GPL-3.0 — no ionCube, no minified core, no "enterprise tier" with the bits you need gated. Version-pin by release tag, fork freely for internal use.
Honest marketing
No invented customer counts, no fictional SDKs, no certifications we haven't filed. Every line on this site maps to a feature a plugin actually ships today.
Open standards for agents
sitemap.xml, robots.txt, llms.txt + llms-full.txt, an API catalog at /.well-known/api-catalog.json, agent-skills under /.well-known/agent-skills, and per-page Markdown content negotiation. If an AI agent evaluates this site, it gets the truth in one fetch.
Plugins shipping
14
Across 6 categories
Payment rails
3
TBC, Bank of Georgia, Flitt
Source license
GPL-3.0
Public on GitHub
Domains per license
1
Transferable on migration
Every figure is verifiable — see our plugin catalogue (one license per plugin) and our changelog.
THE TEAM

Driven by experience.

We are a highly qualified team of engineers with a proven track record of delivering reliable solutions for projects of all sizes—from small businesses to large-scale enterprise platforms. With years of hands-on experience in WooCommerce and WordPress, we combine deep technical knowledge with a commitment to writing clean, maintainable code. No bloated sales teams or unnecessary bureaucracy; you communicate directly with the engineers building your product.

George
Founder & Principal Engineer

Leads product design and engineering, ensuring every plugin meets our rigorous technical standards. With a rich background in building complex industrial accounting systems and CRM integrations on WordPress and Laravel for Georgian businesses, he oversees the core architecture and license server. Reachable directly at [email protected].

Next.js · ReactWordPress · WooCommerceTBC + BoG APIsPostgreSQL · Drizzle
Hiring · Join the Team
We are always on the lookout for exceptional talent to tackle complex technical challenges.
If you have shipped real WordPress payment integrations, read bank API docs for fun, and care about boring things like idempotency keys and status mapping—drop a note to [email protected] with "hiring" in the subject line.
WHAT WE BUILD ON

Boring stack, deliberately.

We rely on popular, well-documented tools with proven operational stability. Every architectural choice below is made so that any competent WordPress or Next.js engineer can step in and understand the system without unnecessary ceremony.

Plugins (merchant install)
  • PHP 7.4+ (TBC + BOG payments / installments) · 8.1+ (Flitt, sync, shipping)
  • WordPress 6.0+ · WooCommerce 8.3+
  • HPOS and Checkout Blocks support
  • Composer autoload · No ionCube
  • Personal watermarked ZIPs · build-id telemetry
codeon.ge (this site)
  • Next.js 16 · React 19 · TypeScript
  • PostgreSQL · Drizzle ORM
  • Auth.js v5 (JWT sessions)
  • Resend for transactional email
  • Static SSR for marketing surface
Infrastructure
  • Cloudflare (TLS + caching)
  • OpenLiteSpeed (reverse proxy)
  • PM2 (process supervisor)
  • Germany (EU hosting region)
  • GitHub Actions (auto-deploy on push)
Each payment plugin wraps the bank's public API directly: TBC TPay + Installments BoG Business API + Installments Flitt callback API

Got questions we didn't answer?

Email lands directly in the founder's inbox. Expect a real reply — not a ticket autoresponder — the same working day.