Libraries tagged by 8.3

yunasoft/barcode

0 Favers
4 Downloads

UPC-A, UPC-E, EAN-13, EAN-8, Code 39, Code 93, Code 128, Codabar, ITF, QR Code, and Data Matrix generator

Go to Download


riftweb/storage

1 Favers
101 Downloads

Laravel package that simplifies storage services. It provides methods for storing files, retrieving paths, resizing images, and more. Developed by Leandro Santos, it uses the Spatie Image library for image manipulation and is compatible with PHP 7.3 and 8.0.

Go to Download


yangweijie/rector-thinkphp

0 Favers
3 Downloads

Rector rules for upgrading ThinkPHP projects from version 3.1.2 to 8.1

Go to Download


waynesun/ysepay-php-sdk

1 Favers
28 Downloads

银盛支付的php 支持国密签名 version 3.0 charset utf-8

Go to Download


tu6ge/ysepay-sdk

2 Favers
47 Downloads

银盛支付的php SDK version 3.0 charset utf-8

Go to Download


jsrmalvarez/similar-numbers

0 Favers
11 Downloads

Tools for getting visually similar numbers (e.g. 3 is similar to 8, 5 is similar to 6, specially when handwritten)

Go to Download


ommu/akreditasi

0 Favers
28 Downloads

Instrumen Akreditasi Perpustakaan Berdasarkan Peraturan Perpustakaan Nasional Nomor 3,4,5,6,7,8 dan 9 Tahun 2018 tentang Peraturan terkait Akreditasi Perpustakaan

Go to Download


mehdidana/job-queue-bundle

0 Favers
4 Downloads

Support for PHP 8, Symfony 5 and Doctrine Common 3

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


aegir/drupal-project-composer

1 Favers
131 Downloads

Project template for Drupal 8 projects with Composer on Aegir 3

Go to Download


zolex/job-queue-bundle

2 Favers
25283 Downloads

Support for PHP 8, Symfony 5 and Doctrine Common 3

Go to Download


chenhaitry/laravel-role-permission

0 Favers
15 Downloads

A Powerful package for handling roles and permissions in Laravel. Supports Laravel 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6.0, and 7.0.

Go to Download


erkens/polyfill-php81

0 Favers
395 Downloads

Symfony polyfill backporting some PHP 8.1+ features to lower PHP versions, compatible for >=PHP 5.3

Go to Download


<< Previous