Libraries tagged by PHP Repl

ebidtech/data-replicator

1 Favers
4922 Downloads

DataReplicator

Go to Download


dmitryrechkin/php-wp-database-adapter

0 Favers
6 Downloads

Drop-in replacement for wpdb class with SSL support

Go to Download


dexen/pv-php

2 Favers
8 Downloads

Drop in replacement for pv, the veritable pipe viewer.

Go to Download


cndrsdrmn/php-string-formatter

0 Favers
397 Downloads

Provides utilities to format strings by replacing specific wildcards with randomly generated characters

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


alissonlinneker/statuspage-php-sdk

0 Favers
4 Downloads

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download


abrgitlab/email-reply-parser

0 Favers
4371 Downloads

Port of the cool GitHub's EmailReplyParser library in PHP

Go to Download


24hoursmedia/php-env-inject

1 Favers
23 Downloads

Inject and interpolate environment variables into strings. Supports substituting default values for an env var, and escapers/formatters using callbacks. Partially supports POSIX compliant shell syntax.

Go to Download


itsmind/sevdesk-php-client

0 Favers
211 Downloads

This package was renamed to itsmind/sevdesk-php-sdk. Please use that package instead. To migrate, you only have to replace the dependency in your composer.json, everything else remains the same.

Go to Download


hkdobrev/email-reply-parser

0 Favers
300 Downloads

Port of the cool GitHub's EmailReplyParser library in PHP 5.3

Go to Download


azayarni/purl

0 Favers
113 Downloads

Simple cUrl PHP replacement library for hostings, which are not supporting native cUrl like Google App Engine

Go to Download


perchten/truepath

0 Favers
49 Downloads

Replace PHP's extremely buggy realpath()

Go to Download


gilbertsoft/opsone-managed-server

1 Favers
10 Downloads

Ops One Managed Server installed PHP extensions, replaces the corresponding Symfony polyfills to avoid installing these unneeded packages.

Go to Download


gwtphp/gwtphp

0 Favers
155 Downloads

The Google Web Toolkit RPC protocol server-side application, implemented in PHP. Strives to be a drop-in replacement.

Go to Download


dhutapratama/mydocx

2 Favers
94 Downloads

MsOffice .docx templating, find and replace, merge, add an image for PHP

Go to Download


<< Previous Next >>