Libraries tagged by transation

The IT Nerd - Magento 2 Brazilian localization module (without translation).

Go to Download

A bridge package for Localisation and Laravel packages, bringing translation code for models and collections to Laravel 4/5.

Go to Download

A library containing the English translation of Squire's Timezone model.

Go to Download

A library containing the English translation of Squire's Region model.

Go to Download

A library containing the French translation of Squire's Country model.

Go to Download

A library containing the Spanish translation of Squire's Country model.

Go to Download

A library containing the English translation of Squire's Continent model.

Go to Download

The OpenAiTranslator module provides AI translation functionality using OpenAI's ChatGPT as translation engine

Go to Download

This module provides AI translation functionality with the help of external AI engines

Go to Download

Allows to create translation labels in BE module

Go to Download

This extension extends the TYPO3 translation handling by translation records that can be edited by backend users. In this way backend users are able to translate labels without having access to the language files.

Go to Download

Laravel Translation UI. Integrates a translation UI for all Laravel Localization.

Go to Download

Unified Email Service Library: A simple mailing list subscriber factory that includes a mailing list subscription feature and the ability to send transactional emails.

Go to Download

Laravel 5+ bindings for Sendwithus transactional email API

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