Libraries tagged by e-xact

E-xact driver for the Omnipay payment processing library

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

Generates UBL 2.1 invoices and credit notes that pass PEPPOL BIS Billing 3.0 and EN 16931 validation, with Dutch and Belgian rules, VIES and company registration checks. Works in plain PHP; the Laravel integration is optional.

Go to Download

es search,es action

Go to Download

PHP client for UCFE (Uruguay Comprobante Fiscal Electrónico / e-Factura) SOAP CfeService

Go to Download

Laravel SDK for Romania's ANAF e-Factura electronic invoicing system

Go to Download

Laravel package for Storno invoicing API — e-Factura, clients, invoices, webhooks

Go to Download

Client PHP communautaire pour l'API SFEC (Systeme de Facturation Electronique Certifiee, Republique du Congo). Couvre les modes ERP, TCC et TFC.

Go to Download

Integration Laravel du client SFEC (rubensalban/sfec-client-php). ServiceProvider + Facade + config publiable.

Go to Download

Official Brivio PHP SDK — invoicing, contacts, articles, locations and module entitlements, plus drop-in compatibility shims for migrating from FGO, SmartBill and Oblio.

Go to Download

Anaf E-Factura Symfony Plugin

Go to Download

Laravel wrapper for e-Factura SDK with token storage, job scheduling, and easy model integration

Go to Download