Skip to content
Lango Docs

SDKs & plugins

Lango ships official libraries so you never hand-roll the fiddly parts — request signing, idempotency keys, webhook signature verification, and the retry rules around the unknown state. Every library speaks the same API and follows the same behaviour described throughout these docs.

Libraries

  • PHP — a small, dependency-light client for creating payments, reading their status, issuing refunds, and verifying webhook signatures.
  • Node.js — a typed client with the same surface for JavaScript and TypeScript back ends.
  • Python — the same client for Django, Flask, FastAPI and scripts.
  • WooCommerce plugin — drop-in EcoCash checkout for WordPress/WooCommerce stores, no code required.

What every library gives you

  • One call to charge, one call to read. The client mirrors the API: create a payment, then poll or wait for the webhook.
  • Idempotency by default. Every create takes an Idempotency-Key, so a retried request after a network blip returns the original result instead of charging twice.
  • Webhook verification in one line. Pass the raw body and the Lango-Signature header and the library checks the HMAC for you — never trust an unverified webhook.
  • Honest states. A payment is unknown until we know, never failed while the network is still deciding. The libraries surface that faithfully so you don’t mark an order failed by mistake.

E-commerce plugins

Drop-in plugins for the main store platforms. Each one creates a Lango payment, sends the shopper to Lango’s hosted checkout, and settles the order from the payment’s authoritative status (queried on the webhook) — never the callback body — so a provider timeout never marks an order paid or failed by mistake. Point a webhook at the plugin’s notify URL and paste its signing secret; the signature is verified for you.

  • WooCommerce / WordPress — download lango-woocommerce.zip. Upload under Plugins → Add New → Upload, activate, then set your sk_ key in WooCommerce → Settings → Payments → Lango.
  • Odoo 16 — download lango-odoo.zip. Unzip into your addons path (keeps the folder name payment_lango), update the apps list, install Lango Payments, and add your key under Payment Providers → Lango.
  • Joomla (HikaShop) — download lango-joomla-hikashop.zip. Install via System → Install → Extensions, enable the plugin, then add a Lango payment method in HikaShop → Payment methods.

A sk_test_ key puts any of these in sandbox mode — no real money moves — so you can run the test numbers end to end before going live. The Odoo and Joomla plugins target Odoo 16 / HikaShop respectively; verify on a staging site first.

Getting the libraries

Install commands land here as each library publishes to its registry (Packagist, npm, PyPI and the WordPress plugin directory). In the meantime, ask us for access and start against the API reference and the five-minute quickstart — the SDKs are thin wrappers over exactly those calls.

Fulfil orders from the signed payment.succeeded webhook, which every library helps you verify — it is the source of truth, not the browser.