Libraries tagged by this7 framework

An asynchronous event driven PHP framework for easily building fast, scalable network applications.This library is match for thinkphp v3.2.x cli mode

Go to Download

You can use this package whenever you want to integrate an access control system based on roles in a project with MySQL as your RDBMS. It is easy to use and can be integrated with any php framework in the same way.

Go to Download

This library add additional functionality for WP Bones framework.

Go to Download

This module provides a simple wrapper for the PHP_FFmpeg library, exposing the library as a Zend Framework service

Go to Download

This helps binds the php-airbrake module into a Symfony2 bundle for easy use with the framework.

Go to Download

A powerful tool for developers who use Laravel framework and want to implement filtering functionality in their web applications. This package allows you to easily add filters to your queries, enabling users to search for specific data based on various criteria.

Go to Download

This package extends some features of Laravel 5.1 Framework

Go to Download

# 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

This bundle is an overlay to the Symfony framework.

Go to Download

Website Bundle is a Symfony 2/3 bundle for create and manage frontends in your Symfony 2/3 application. This package is a part of Artscore Studio Framework.

Go to Download

User Bundle is a Symfony 2/3 bundle for create and manage users in Symfony 2/3 application. This package is a part of Artscore Studio Framework.

Go to Download

Scheduler Bundle is a Symfony 2/3 bundle for create and manage calendar events in your Symfony 2+ application. This package is a part of Artscore Studio Framework.

Go to Download

Product Bundle is a Symfony 2/3 bundle for create and manage products in your Symfony 2/3 application. This package is a part of Artscore Studio Framework.

Go to Download

Document Bundle is a Symfony 2/3 bundle for create and manage documents in your Symfony 2/3 application. This package is a part of Artscore Studio Framework.

Go to Download

Contact Bundle is a Symfony 2/3 bundle for create and manage contacts in your Symfony 2/3 application. This package is a part of Artscore Studio Framework.

Go to Download