Libraries tagged by party

# 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

Nikolag Core package for Laravel payment integrations that are not part of the Cashier

Go to Download

The Payments API was designed and implemented by NETOPIA Payments development team and is meant to be used in third party applications to cover the payment process.

Go to Download

Provides ResourceLoader module definitions that allow for inclusion of third-party pre-compiled resources (JS/CSS)

Go to Download

Generic MODX service class and collection of utilities, used by the modmore team, but also available for third party developers.

Go to Download

Third party 'phpMyAdmin' administration module for TYPO3. Access to admin-users only.

Go to Download

Alipay Global Third Party SDK

Go to Download

Module is a part of optimized theme.

Go to Download

PHP wrapper for the pdftoppm command which is part of poppler-utils.

Go to Download

A laravel middleware to shield against unverified webhooks from 3rd party services.

Go to Download

Single-sign-on bundle for Symfony2. Identity Provider part.

Go to Download

Provides extension points and APIs that 3rd-party developers can use to provide logging for klevu modules suites

Go to Download

Provides extension points and APIs that 3rd-party developers can use to change frontend behaviour of Klevu modules

Go to Download

Provides extension points and APIs that 3rd-party developers can use to change frontend behaviour of Klevu modules

Go to Download

Provides extension points and APIs that 3rd-party developers can use to change customer data

Go to Download