Libraries tagged by custumers

blackspot/stripe-multiple-accounts

3 Favers
65 Downloads

Allow manages many stripe accounts (Customers, PaymentMethods, etc..)

Go to Download


birenk/module-hello-magento2

0 Favers
1 Downloads

Assign one or multiple tags to your products and improve the navigation for your customers, who can narrow the search results by tags in the Product Filters or, vice versa, see all products with the tags

Go to Download


beself/magento2-module-customer-enhancements

0 Favers
1 Downloads

Magento 2 module that adds a B2B flag to customer groups and a favorite product type attribute for customers.

Go to Download


basketin/basketin-api-php

0 Favers
1 Downloads

Monitoring and analyzing the shopping carts of customers, knowing the abandoned carts, and taking effective action with it.

Go to Download


barbotkin/send24-for-prestashop

0 Favers
6 Downloads

Offer your customers premium delivery service with Send24 Sameday Express solution.

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


bagisto/bagisto-weaccept-payment

3 Favers
28 Downloads

Allow customers to pay for others using weaccept payment gateway.

Go to Download


bagisto-eu/pickup

3 Favers
42 Downloads

Allow customers to pickup orders from physical stores

Go to Download


b2b-sellers/demodata

2 Favers
0 Downloads

The demo data plugin of the B2Bsellers Suite creates products, customers and employees to start and test directly with suitable data.

Go to Download


azra/module-pricerequest

0 Favers
4 Downloads

Module responsible for enabling customers to request price quotes

Go to Download


awm/module-customer-import

0 Favers
6 Downloads

A Magento 2 module to import customers

Go to Download


artesanik/sylius-employee-plugin

0 Favers
6 Downloads

Employee information for Customers plugin for Sylius.

Go to Download


arslanfarrukh/share-cart

0 Favers
6 Downloads

Using this extension, the customers can share his cart with his friends and they can add that items to cart on single click.

Go to Download


arseniusz8/sendpost_php

1 Favers
5 Downloads

Email API and SMTP relay to not just send and measure email sending, but also alert and optimise. We provide you with tools, expertise and support needed to reliably deliver emails to your customers inboxes on time, every time.

Go to Download


arobases/sylius-back-in-stock-notification-plugin

0 Favers
4 Downloads

Timely inform customers and guest visitors when a product return in stock

Go to Download


<< Previous Next >>