Libraries tagged by cer

PHP SDK for interacting with the Cerbos PDP

Go to Download

Let's Encrypt / ACME client written in PHP for the CLI.

Go to Download

Laravel 5 Client Certificate auth middleware

Go to Download

This package provides root certificates for usage in api clients on systems that have missing or outdated certificates.

Go to Download

Commonly used core PHP functionality improved upon and made for quick, easy use

Go to Download

Laravel package to dump SQL queries.

Go to Download

Data Transfer Object (DTO) for Laravel

Go to Download

Laravel package to standardize API errors in compliance with the JSON:API spec.

Go to Download

Validate that a certain value is a valid CSS color string in Laravel 5

Go to Download

This module replaces certain tags in WYSIWYG content with SilverStripe templates.

Go to Download

Another PHP client for acme protocal (version 2) implementation, used for generating letsencrypt's free ssl certificates.

Go to Download

PHP client for Apple Push Notification Service (APNs) - Send push notifications to iOS using the new APNs HTTP/2 protocol with token-based (JWT with p8 private key) or certificate-based authentication

Go to Download

Bookworm estimates how much time is needed to read a certain piece of text.

Go to Download

An unofficial PHP library for generating ZATCA Fatoora e-invoices. This library facilitates the creation of compliant e-invoices, QR Codes, and certificates, as well as the submission of e-invoices to ZATCA's servers. It provides developers with an easy-to-use, customizable, and robust toolkit to integrate and automate ZATCA e-invoicing processes in PHP applications.

Go to Download

# Introduction Welcome to the Passbase Verifications API docs. This documentation will help you understand our models and the Verification API with its endpoints. Based on this you can build your own system (i.e. verification) and hook it up to Passbase. In case of feedback or questions you can reach us under this email address: [[email protected]](mailto:[email protected]). A User submits a video selfie and valid identifying __Resources__ during a __Verification__ guided by the Passbase client-side integration. Once all the necessary __Resources__ are submitted, __Data points__ are extracted, digitized, and authenticated. These Data points then becomes part of the User's __Identity__. The User then consents to share __Resources__ and/or __Data points__ from their Identity with you. This information is passed to you and can be used to make decisions about a User (e.g. activate account). This table below explains our terminology further. | Term | Description | |-----------------------------------------|-------------| | [Identity](#tag/identity_model) | A set of Data points and Resources related to and owned by one single User. This data can be accessed by you through a Verification. | | Data points | Any data about a User extracted from a Resource (E.g. Passport Number, or Age). | | [Resource](#tag/resource_model) | A source document used to generate the Data points for a User (E.g. Passport). | | [User](#tag/user_model) | The owner of an email address associated with an Identity. | | Verification | A transaction through which a User consents to share Data points with you. If the Data points you request are not already available in the User's Identity, the Passbase client will ask the User to submit the necessary Resource required to extract them. | | Re-authentication (login) | A transaction through which a User can certify the ownership of Personal data previously shared through an Authentication. | # Authentication There are two forms of authentication for the API: • API Key • Bearer JWT Token

Go to Download