Libraries tagged by equip

Codegen functions equivalent to type testing `as` expressions.

Go to Download

Sapama Pay API - MPESA, Equitel, Sapama Pay API

Go to Download

TLB Cell / Builder / Slice / canonical BOC encoder for The Open Network in pure PHP — byte-exact equivalent of @ton/core's cell layer.

Go to Download

Solidity ABI calldata encoder in pure PHP — function selectors plus static (address/uint/int/bytesN) and dynamic (string/bytes) types, byte-for-byte equivalent to ethers.js v6.

Go to Download

PHP SDK for using the equify API

Go to Download

SDK to access Equifax Luminate, XML2 Consumer, and Opening Banking

Go to Download

Equity Bank eazzy api library

Go to Download

Mobile payments API - Kenya

Go to Download

A library to represent equivalence relations and strategies for hashing and sorting values.

Go to Download

A Laravel package for setting up and interacting with Jenga V3 API.

Go to Download

Jengahq is Equity's Jenga API V2 wrapper for Laravel.

Go to Download

A single-tenant Laravel package for integrating Mpesa, Equity Jenga API's and NCBA Loop API through Mwaloni Wallet

Go to Download

Polyfill backporting PHP 8.5+ native RFC3986/WHATWG URI features to lower PHP versions

Go to Download

A communication wrapper between laravel and filemaker db

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download