Libraries tagged by generate files
bonuscred/classmap-generator
6 Downloads
Library for mapping and extracting file identification information for importing classes
beesoft/generator-html
6 Downloads
Static site
arthurh/web-md-generator
23 Downloads
Create a static website from markdown files easily
yarco/phpdotenv-generator
3 Downloads
a tool for managing .env file which is a common config solution nowadays
leewillis77/medialibrary-gcs-url-generator
1167 Downloads
Custom URL generator for spatei/medialibrary that generators URLs for files stored on Google Cloud Storage using Superbalist/laravel-google-cloud-storage
imponeer/project-cached-code-generator-from-composer.json-data-base
16 Downloads
Library that can be used for plugins that can be used for composer-plugins that register services or configuration based on project composer.json files
derhaeuptling/contao-multi-file-upload-with-dropzone
539 Downloads
Contao multi file uploader with DropZone for the formular generator.
delorier/nacha-generator
21 Downloads
A simple library for generating Nacha compliant text files
cslant/laravel-generator-ui
245 Downloads
Laravel Generator UI is a collection of HTML, CSS, and JS files that implement a clean, responsive, and customizable UI for the Laravel Generator.
rcsi/filesystem-uploads
38 Downloads
General Upload Library
rcsi/filesystem-config
128 Downloads
General Config Library
smalot/vagrantfile
5 Downloads
Vagrant file generator.
met_mw/phpstormmetagenerator
24 Downloads
PhpStorm meta-file generator (.phpstorm.meta.php).
bank-io/bankio-sdk-php
104 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
aedart/scaffold
54 Downloads
Tool for creating and installing various files and directories into your project, based on created scaffolds