Skip to main content
Sajilo Charge
🌐 नेपाली Log in Download App

Connect your chargers to Sajilo Charge

Put your charging stations in the Sajilo Charge app over standard OCPI 2.2.1. Our drivers charge on your hardware; we bill their wallets from the CDRs you issue and settle with you monthly — you never build driver accounts, wallets, or billing. Pick your stack below; every SDK does the same job.

PY

Django

Works with Django ≥ 4.2 · Python ≥ 3.10

A Django app you mount with one include() — models, endpoints and hub client ready-made.

Tutorial → ⬇ SDK zip
PHP

Laravel

Works with Laravel 10 / 11 / 12 · PHP ≥ 8.1

A composer package with auto-discovery — one artisan command scaffolds everything, you edit one file.

Tutorial → ⬇ SDK zip
JS

Node.js

Works with Node ≥ 18 · Express ≥ 4

An Express router plus hub client — zero dependencies, wire it up in one createSajiloCharge() call.

Tutorial → ⬇ SDK zip
JAVA

Spring Boot

Works with Spring Boot 3.2+ · Java 17+

A Spring Boot starter — auto-configured endpoints, JPA entities and hub client; you provide one handlers bean.

Tutorial → ⬇ SDK zip
Building with an AI coding agent? Hand your agent (Claude, Cursor, ChatGPT…) this link — the entire integration, all four SDKs, and the raw wire contract in one machine-readable page:
https://sajilocharge.com/developers/ocpi/ai/
Open the AI guide →

How a roaming charge flows

Sajilo Charge driver       Sajilo Charge hub                 Your backend (any SDK)
      │ taps "Start" ────▶ POST /commands/START_SESSION ──▶ onStartSession(charge)
      │                                                      your CSMS starts the charger
      │   charging…   ◀── PUT  sessions push ◀───────────── setActive() / meter(kwh)
      │ taps "Stop"  ────▶ POST /commands/STOP_SESSION ───▶ onStopSession(charge)
      │ wallet debited ◀── POST cdrs ◀──────────────────────  complete(kwh, cost)
      │                    monthly netting ─────────────────▶ you get paid

Whatever the stack, the integration is the same five moves: install, configure, implement two callbacks, join with a one-shot registration token, and publish your station catalog. Each tutorial covers the full lifecycle including settlement and troubleshooting.

Money and settlement

  • All amounts are NPR; costs are VAT-exclusive.
  • Each CDR you issue debits the driver's wallet and credits your inter-party ledger at the hub; settlement is monthly netting minus the hub clearing fee.
  • Disputes go through the hub's CDR dispute endpoint or partners@sajilocharge.com — open disputes pause netting for that CDR.

Getting a registration token

Email partners@sajilocharge.com with your company name and the public base URL of your backend. You'll receive a one-shot registration token; every tutorial shows the single command that completes the handshake with it.

OCPI 2.2.1 · SDKs v0.1.0 · Questions: partners@sajilocharge.com