Libraries tagged by php 8.1

slis/tanss-php-adapter

0 Favers
44 Downloads

## Documentation of the TANSS API. Version: 5.8.22.1 ### older versions Older versions of the API documentation can be found here: * [Docs for 5.8.21.6](https://api-doc.tanss.de/5.8.21.6/) * [Docs for 5.8.21.3](https://api-doc.tanss.de/5.8.21.3/) * [Docs for 5.8.21.1](https://api-doc.tanss.de/5.8.21.1/) * [Docs for 5.8.20.5](https://api-doc.tanss.de/5.8.20.5/) * [Docs for 5.8.20.4](https://api-doc.tanss.de/5.8.20.4/) * [Docs for 5.8.20.2](https://api-doc.tanss.de/5.8.20.2/) * [Docs for 5.8.19.3](https://api-doc.tanss.de/5.8.19.3/)

Go to Download


programmatordev/sportmonksfootball-php-api

1 Favers
14 Downloads

SportMonksFootball PHP library that provides convenient access to the SportMonks Football API

Go to Download


programmatordev/openweathermap-php-api

2 Favers
7 Downloads

OpenWeatherMap PHP library that provides convenient access to the OpenWeatherMap API

Go to Download


baba/php-string-convert

1 Favers
2004 Downloads

Convert string from utf-8 to windows-1250

Go to Download


bank-io/bankio-sdk-php

1 Favers
106 Downloads

# Summary The **NextGenPSD2** *Framework Version 1.3.6* (with errata) offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Go to Download


dynamsoftsamples/php-barcode-com-component

2 Favers
41 Downloads

Dynamsoft Barcode Reader SDK for PHP - Implement Barcode Recognition to Your App

Go to Download


tsitsulin/enum

1 Favers
6 Downloads

PHP 8.1 compatible ENUM

Go to Download


thingston/http-app

0 Favers
7 Downloads

Simple HTTP application running on PHP 8.1 and backed by PSR standards.

Go to Download


pixelcreart/yii2-cart

0 Favers
0 Downloads

PHP 8.1+ Cart Module for Yii2

Go to Download


opctim/symfony-docker

0 Favers
31 Downloads

This is a complete stack for running Symfony 6 with PHP-FPM 8.1 and MySQL 8 into Docker containers using docker-compose tool.

Go to Download


nouvu/web-skeleton

0 Favers
7 Downloads

Nouvu Skeleton

Go to Download


nouvu/lerma

0 Favers
80 Downloads

Multi-screwdriver for the database Nouvu/Database

Go to Download


nouvu/framework

0 Favers
45 Downloads

Nouvu Framework

Go to Download


mobtitude/zendframework1

0 Favers
1033 Downloads

Zend Framework 1 fork compatible with PHP 8.1 by Mobtitude

Go to Download


mmnijas/strftime

1 Favers
3 Downloads

A Laravel package that provides strftime functionality compatible with PHP 8.1+. This package will serve as a drop-in replacement, leveraging IntlDateFormatter to provide locale-aware date and time formatting, similar to strftime

Go to Download


<< Previous Next >>