Libraries tagged by 2.6.0

pejmankheyri/smsir-joomla-plugin-contact

1 Favers
7 Downloads

send sms via sms.ir

Go to Download


pejmankheyri/smsir-joomla-component

1 Favers
7 Downloads

send sms via sms.ir

Go to Download


pejmankheyri/smsir-joomla-acy

1 Favers
7 Downloads

send sms via sms.ir

Go to Download


apiverve/mayancalendar

1 Favers
0 Downloads

Mayan Calendar converts Gregorian dates to the ancient Mayan calendar system. Returns the Long Count, Tzolkin (260-day sacred calendar), and Haab (365-day civil calendar) dates.

Go to Download


kenod/isdoc-exporter

0 Favers
2 Downloads

PHP library for generating ISDOC/ISDOCX invoices according to the Czech ISDOC standard version 6.0.2

Go to Download


nyholm/google-api-php-client

0 Favers
9863 Downloads

Google API library for PHP (with namespaces). This packet is maintained! Version 0.6.2 of original code.

Go to Download


philip1337/php-extjs-loader

0 Favers
28 Downloads

Sencha - ExtJS 4.0.x - 6.2.x Architect project loader

Go to Download


kkqy/think-oauth

0 Favers
0 Downloads

OAuth 2.0 for ThinkPHP 6

Go to Download


mintermania/laracent

0 Favers
866 Downloads

Centrifugo broadcaster for laravel 6 > and Centrifugo >= 2.1.0 (forked)

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


digifa/mobile-detect-bundle

0 Favers
195 Downloads

Symfony 6.4, 7.0 / PHP 8.2 bundle to detect mobile devices, manage mobile view and redirect to the mobile and tablet version.

Go to Download


oneb-pub/oauth2-zoho

0 Favers
1 Downloads

Zoho OAuth 2.0 Client Provider for The PHP5.6 League OAuth2-Client

Go to Download


vluzrmos/jsonrpc

0 Favers
10 Downloads

JSON-RPC 2.0 Client and Server implementation for PHP 5.6+

Go to Download


mfadul24/kount-commerce

0 Favers
5 Downloads

PHP SDK for the Kount 360 Commerce APIs (Payments Fraud 2.0) — PSR-18/PSR-17 based, OAuth2 client-credentials with optional PSR-6 token caching, plus a legacy RIS migration facade.

Go to Download


<< Previous