Libraries tagged by divisions

Create the entities and their relationships to define the administrative political division of Chile

Go to Download

8 Division, 64 District, 491 Thana and 2350 Union fully mapped laravel package.

Go to Download

This plugin attaches a popup keyboard to a text field for mouse-driven entry or adds an inline keypad in a division or span. * Customise keypad content. * Preset keyboard layouts. * Randomise key positions. * 9 localisations.

Go to Download

Administrative provides an easy way to scaffold political administrative division (like, region, provinces, communes) to your app.

Go to Download

Implementación en PHP de las reglas de división silábica del español según la RAE, con manejo de variantes y estrategias de prefijos.

Go to Download

Division: Post & Parcel Germany The INTERNETMARKE is the online-postage for mail products of Deutsche Post AG.

Go to Download

A light little MVC framework that everybody can use. Unless you want everyone in the division to think you're chicken.

Go to Download

Approval, employee and division in common corporate

Go to Download

Division, District, Upazila level fully mapped package for laravel

Go to Download

This is a test component that will perform the four basic operations of mathematics: Addition, subtraction, multiplication, and division.

Go to Download

Provide Provinces, divisions, districts, Tehsils/Talukas and cities relations database for Pakistan.

Go to Download

This includes all Srilankan Divisioanl Secretariats

Go to Download

PHP client for App Store Server API. Manage your customers’ App Store transactions from your server.The App Store Server API is a REST API that you call from your server to request and provide information about your customers' in-app purchases. The App Store signs the transaction and subscription renewal information that this API returns using the JSON Web Signature (JWS) specification.App Store Server API is independent of the app’s installation status on the customer’s devices. The App Store server returns information based on the customer’s in-app purchase history regardless of whether the customer installed, removed, or reinstalled the app on their devices.To request transaction and subscription status information with this API, provide any original transaction identifier that belongs to the customer. The transaction history API responds with a complete list of transactions, 20 at a time, starting with the oldest first. The subscription status API returns the status for all of the customer’s subscriptions, organized by their subscription group identifier.Use the Send Consumption Information endpoint to send information to the App Store when customers request a refund for a consumable in-app purchase, after you receive the CONSUMPTION_REQUEST App Store server notification. Your data helps inform refund decisions.

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

Your most complex decisions taken the easiest way

Go to Download