Libraries tagged by apple id

A simple library to decode and parse Apple Sign In client tokens.苹果账号登陆

Go to Download

One-command Google and Apple social login for Laravel APIs (Android and iOS). Handles dynamic client ID resolution, Sanctum token issuance, and automatic user provisioning.

Go to Download

Verify Apple App Attest attestations and assertions in PHP: certificate chain, nonce, key id, counter. Stateless, no I/O.

Go to Download

CAWL Solutions / Worldline payment gateway module for Thelia 3. Supports 30+ payment methods including cards, PayPal, Apple Pay, Klarna, and more.

Go to Download

Mollie API client library for PHP. Mollie is a European Payment Service provider and offers international payment methods such as Mastercard, VISA, American Express and PayPal, and local payment methods such as iDEAL, Bancontact, SOFORT Banking, SEPA direct debit, Belfius Direct Net, KBC Payment Button and various gift cards such as Podiumcadeaukaart and fashioncheque.

Go to Download

Mollie API client library for PHP. Mollie is a European Payment Service provider and offers international payment methods such as Mastercard, VISA, American Express and PayPal, and local payment methods such as iDEAL, Bancontact, SOFORT Banking, SEPA direct debit, Belfius Direct Net, KBC Payment Button and various gift cards such as Podiumcadeaukaart and fashioncheque.

Go to Download

emerchantpay Payment Gateway for Magento 2

Go to Download

E-Comprocessing Payment Gateway for Magento 2

Go to Download

Mollie API client library for hack. Forked from https://github.com/mollie/mollie-api-php

Go to Download

Mollie API client wrapper for Laravel & Mollie Connect provider for Laravel Socialite

Go to Download

Fourth party settlement platform for enterprises

Go to Download

Accept.js tokenization (PCI SAQ A-EP) with direct card fields (no iframe) Accept Hosted (PCI SAQ A) supported as an alternative hosted flow Apple Pay: server-side merchant validation, cert management via env.php, domain verification support Google Pay: native sheet UX + automatic gateway ID detection PayPal: processed through Authorize.Net’s wallet integration Saved Cards: Authorize.Net Customer Profiles + opt-in save checkbox + saved card dropdown Webhooks: signed (HMAC-SHA512) endpoint + order history updates + event mapping for refunds/voids/chargebacks Security: encrypted API keys at rest, certs stored outside webroot, SSRF hardening, session transaction validation Modern stack: no Knockout dependencies, REST compatible, modular architecture

Go to Download

Framework-agnostic PHP database library with unified API for MySQL, MariaDB, PostgreSQL, SQLite, MSSQL, and Oracle. Query Builder, caching, sharding, window functions, CTEs, JSON, migrations, ActiveRecord, CLI tools, AI-powered analysis. Zero external dependencies.

Go to Download

Tool to extract, import and apply localizable strings from a source base.

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