Skip to main content

​
Plugins

​
Intro

Khaime plugins let you accept multicurrency payments or embed a Khaime-managed storefront on your site without writing code — install, drop in your credentials, and you’re live.

​
Context

There are two plugin families, and they solve different problems:

WooCommerce

Adds Khaime as a payment gateway on top of your existing WooCommerce catalog. Includes a multicurrency switcher and Khaime-powered checkout. Your products stay in WooCommerce.

WordPress

Embeds your Khaime-managed product catalog, cart, and checkout into any WordPress site via shortcodes — plus live chat and a contact form. There is no WooCommerce dependency — the catalog lives in Khaime.
Both plugin families are thin clients over the same Partner API — they don’t reimplement pricing, fees, or gateway logic locally. If you outgrow what a plugin’s settings page can express, the same Partner API is available for a custom integration; see Plugin vs API below.

​
Hows

All plugins follow the same pattern:
  1. Multicurrency display — Prices are shown in the customer’s currency, converted in real time from live exchange rates.
  2. Smart gateway routing — Khaime picks the underlying gateway (Stripe, Paystack, and others) based on the customer’s currency and location — you don’t configure this per gateway.
  3. Webhook confirmation — Your store’s order/payment status updates automatically when Khaime confirms the charge, without polling.
  4. Settings-based setup — Credentials, currency switcher placement, and display options are configured from a WordPress admin screen, not code.

​
Plugin vs API

​
Whys

Most merchants don’t want to build a payments integration — they want a working checkout. Putting the multicurrency and gateway-routing logic behind a settings page (rather than exposing it as raw API primitives) means a store owner can get a fully working, multicurrency-aware checkout without touching code, while the underlying behavior (fee calculation, gateway selection, webhook delivery) stays identical to what a custom API integration would get. The plugin is a UI on top of the same contract, not a separate, lighter one.

​
Why nots

  • Not for headless or non-WordPress platforms. The plugins are WordPress/WooCommerce-specific. Custom platforms should integrate directly against the Partner API.
  • Not a product-catalog migration tool. The WooCommerce plugin is product-agnostic — it charges whatever total WooCommerce computes and never touches your product data. If you want Khaime to also host your catalog, that’s what the WordPress Storefront plugin is for, not the WooCommerce plugin.
  • Don’t run both catalogs at once for the same products. If you already sell through WooCommerce, use the WooCommerce plugin for payments rather than duplicating products into a Khaime-managed storefront.
  • Not for behavior the settings page can’t express. Custom checkout flows, non-standard fee splits, or logic outside what a plugin’s options support call for a direct API integration instead.