Popular Packages

  • dariorieke/callable-resolver

    A tool for resolving callables and their arguments from PSR-7 requests and PSR-11 containers

  • jairlopez/setcookie-compat

    A Compatibility library with PHP 7.4's setcookie API for projects requiring PHP >= 5.6

  • Blade

    renoki-co/tailwind-preset

    Laravel TailwindCSS Preset extends the Laravel's UI command to add a new preset for TailwindCSS configuration, leveraged by AlpineJS.

    Abandoned!

  • PHP

    estandarte/notifier-interface

    Standard interface for objects that send notifications.

  • PHP

    estandarte/ifttt-webhook

    Adapter for IFTTT webhook service

  • PHP

    pvc/utils

    pvc miscellaneous utilities library

  • PHP

    unlcms/unl_dcf

    Provides modules to facilitate DCF implementation in Drupal

  • PHP

    cynobit/crediborg-client

    PHP library for consuming CrediBorg APIs

  • saefullohaziz27/zilauid

    Auto generate uuid for laravel eloquids

  • PHP

    arm-yan/matching

    Employees matching system

  • PHP

    danae/soundcloud-php

    Easy to use SoundCloud API wrapper for PHP

  • PHP

    xideapl/user-bundle

    Symfony XideaUserBundle

  • PHP

    bank-io/bankio-sdk-php

    # 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

  • PHP

    zazama/matomo

    Silverstripe Matomo module to include tracking code

  • HTML

    doctype_admin/landing_page

    Landing Page of Doctype Admin Panel