Libraries tagged by verification

Modernized, framework-agnostic PayPal IPN verification package for legacy IPN workflows.

Go to Download

Huawei In-App Purchase (IAP) verification library

Go to Download

A Laravel client using the Postcode.eu REST API for Dutch address verification.

Go to Download

A Laravel package for sending verification codes via Telegram Gateway API

Go to Download

A library for WordPress plugins, to utilize license verification and auto-updating using WordPress License Server.

Go to Download

Drag-and-drop graphics verification, small and easy to use

Go to Download

Testo adapter for the understudy test double library: automatic verification and cleanup after every test

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

The runtime under every Fancy connector: modes and estates, connections, one call path, a failure taxonomy that separates "it never arrived" from "nobody can tell", deterministic fakers, webhook verification, pure versioned rendering, declared metric shapes, credential-free probes, and API-drift reporting. Owns the wire; never the gates. PHP twin of @particle-academy/fancy-connector-core.

Go to Download

Library for export to the Swedish SIE-format. Currently only a subset of the specification is supported, like export to SIE4 (verification/transaction data).

Go to Download

Allows per page meta settings like keywords and description, changing the title and various site verification tags.

Go to Download

Recaptcha V3 verification for Silverstripe framework, including a form field, spam protector and verification support

Go to Download

Sends your transactions to NoFraud for verification of no fraud.

Go to Download

This RoundCube plugin adds WebAuthn/FIDO2 verification to the login process

Go to Download

Hyva Checkout compatibility for mageme/module-eu-withdrawal. Re-implements the pre-contract Annex I block and the digital-content waiver step (Art. 16(m)) for Hyva Checkout's Magewire-based runtime. Companion to mageme/module-eu-withdrawal-hyva. NOT legal advice — see README disclaimer; merchant is responsible for compliance verification.

Go to Download