Download the PHP package bank-io/bankio-sdk-php without Composer
On this page you can find all versions of the php package bank-io/bankio-sdk-php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Table of contents
Download bank-io/bankio-sdk-php
More information about bank-io/bankio-sdk-php
Files in bank-io/bankio-sdk-php
Download bank-io/bankio-sdk-php
More information about bank-io/bankio-sdk-php
Files in bank-io/bankio-sdk-php
Vendor bank-io
Package bankio-sdk-php
Short Description # 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
License MIT
Homepage https://bankio.co.uk/bankio-link/
Package bankio-sdk-php
Short Description # 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
License MIT
Homepage https://bankio.co.uk/bankio-link/
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?
Informations about the package bankio-sdk-php
OpenAPIClient-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
This PHP package is automatically generated by the OpenAPI Generator project:
- API version: 1.3.6_2020-05-28
- Build package: org.openapitools.codegen.languages.PhpClientCodegen For more information, please visit https://bankio.co.uk/
Requirements
PHP 7.2 and later
Installation & Usage
Composer
To install the bindings via Composer, add the following to composer.json:
Then run composer install
Manual Installation
Download the files and include autoload.php:
Tests
To run the unit tests:
Getting Started
Please follow the installation procedure and then run the following:
Documentation for API Endpoints
All URIs are relative to https://ob.bankio.ro
| Class | Method | HTTP request | Description |
|---|---|---|---|
| AccountInformationServiceAISApi | createConsent | POST /api/org/{organisation}/v1/consents | Create consent |
| AccountInformationServiceAISApi | deleteConsent | DELETE /api/org/{organisation}/v1/consents/{consentId} | Delete consent |
| AccountInformationServiceAISApi | getAccountList | GET /api/org/{organisation}/v1/accounts | Read account list |
| AccountInformationServiceAISApi | getBalances | GET /api/org/{organisation}/v1/accounts/{account-id}/balances | Read balance |
| AccountInformationServiceAISApi | getCardAccount | GET /api/org/{organisation}/v1/card-accounts | Read a list of card accounts |
| AccountInformationServiceAISApi | getCardAccountBalances | GET /api/org/{organisation}/v1/card-accounts/{account-id}/balances | Read card account balances |
| AccountInformationServiceAISApi | getCardAccountTransactionList | GET /api/org/{organisation}/v1/card-accounts/{account-id}/transactions | Read transaction list of an account |
| AccountInformationServiceAISApi | getConsentAuthorisation | GET /api/org/{organisation}/v1/consents/{consentId}/authorisations | Get consent authorisation sub-resources request |
| AccountInformationServiceAISApi | getConsentInformation | GET /api/org/{organisation}/v1/consents/{consentId} | Get consent request |
| AccountInformationServiceAISApi | getConsentScaStatus | GET /api/org/{organisation}/v1/consents/{consentId}/authorisations/{authorisationId} | Read the SCA status of the consent authorisation |
| AccountInformationServiceAISApi | getConsentStatus | GET /api/org/{organisation}/v1/consents/{consentId}/status | Consent status request |
| AccountInformationServiceAISApi | getTransactionDetails | GET /api/org/{organisation}/v1/accounts/{account-id}/transactions/{transactionId} | Read transaction details |
| AccountInformationServiceAISApi | getTransactionList | GET /api/org/{organisation}/v1/accounts/{account-id}/transactions | Read transaction list of an account |
| AccountInformationServiceAISApi | readAccountDetails | GET /api/org/{organisation}/v1/accounts/{account-id} | Read account details |
| AccountInformationServiceAISApi | readCardAccount | GET /api/org/{organisation}/v1/card-accounts/{account-id} | Read details about a card account |
| AccountInformationServiceAISApi | startConsentAuthorisation | POST /api/org/{organisation}/v1/consents/{consentId}/authorisations | Start the authorisation process for a consent |
| AccountInformationServiceAISApi | updateConsentsPsuData | PUT /api/org/{organisation}/v1/consents/{consentId}/authorisations/{authorisationId} | Update PSU Data for consents |
| AuthenticationApi | authorize | GET /api/auth/authorize | Authenticate a user |
| AuthenticationApi | token | POST /api/auth/token | Request Access Tokens |
| AuthenticationApi | userInfo | GET /api/auth/me | Retrieve user profile |
| ClientManagementApi | clientClientId | DELETE /api/auth/register/{client_id} | Delete a client |
| ClientManagementApi | getClient | GET /api/auth/register/{client_id} | View a client |
| ClientManagementApi | updateClient | PUT /api/auth/register/{client_id} | Update a client |
| CommonServicesApi | getConsentScaStatus | GET /api/org/{organisation}/v1/consents/{consentId}/authorisations/{authorisationId} | Read the SCA status of the consent authorisation |
| CommonServicesApi | getPaymentCancellationScaStatus | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations/{authorisationId} | Read the SCA status of the payment cancellation's authorisation |
| CommonServicesApi | getPaymentInitiationAuthorisation | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations | Get payment initiation authorisation sub-resources request |
| CommonServicesApi | getPaymentInitiationScaStatus | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations/{authorisationId} | Read the SCA status of the payment authorisation |
| CommonServicesApi | startConsentAuthorisation | POST /api/org/{organisation}/v1/consents/{consentId}/authorisations | Start the authorisation process for a consent |
| CommonServicesApi | startPaymentAuthorisation | POST /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations | Start the authorisation process for a payment initiation |
| CommonServicesApi | startPaymentInitiationCancellationAuthorisation | POST /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations | Start the authorisation process for the cancellation of the addressed payment |
| CommonServicesApi | updateConsentsPsuData | PUT /api/org/{organisation}/v1/consents/{consentId}/authorisations/{authorisationId} | Update PSU Data for consents |
| CommonServicesApi | updatePaymentCancellationPsuData | PUT /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations/{authorisationId} | Update PSU data for payment initiation cancellation |
| CommonServicesApi | updatePaymentPsuData | PUT /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations/{authorisationId} | Update PSU data for payment initiation |
| ConfirmationOfFundsServicePIISApi | checkAvailabilityOfFunds | POST /api/org/{organisation}/v1/funds-confirmations | Confirmation of funds request |
| PaymentInitiationServicePISApi | cancelPayment | DELETE /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId} | Payment cancellation request |
| PaymentInitiationServicePISApi | getPaymentCancellationScaStatus | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations/{authorisationId} | Read the SCA status of the payment cancellation's authorisation |
| PaymentInitiationServicePISApi | getPaymentInformation | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId} | Get payment information |
| PaymentInitiationServicePISApi | getPaymentInitiationAuthorisation | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations | Get payment initiation authorisation sub-resources request |
| PaymentInitiationServicePISApi | getPaymentInitiationCancellationAuthorisationInformation | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations | Will deliver an array of resource identifications to all generated cancellation authorisation sub-resources |
| PaymentInitiationServicePISApi | getPaymentInitiationScaStatus | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations/{authorisationId} | Read the SCA status of the payment authorisation |
| PaymentInitiationServicePISApi | getPaymentInitiationStatus | GET /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/status | Payment initiation status request |
| PaymentInitiationServicePISApi | initiatePayment | POST /api/org/{organisation}/v1/{payment-service}/{payment-product} | Payment initiation request |
| PaymentInitiationServicePISApi | startPaymentAuthorisation | POST /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations | Start the authorisation process for a payment initiation |
| PaymentInitiationServicePISApi | startPaymentInitiationCancellationAuthorisation | POST /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations | Start the authorisation process for the cancellation of the addressed payment |
| PaymentInitiationServicePISApi | updatePaymentCancellationPsuData | PUT /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations/{authorisationId} | Update PSU data for payment initiation cancellation |
| PaymentInitiationServicePISApi | updatePaymentPsuData | PUT /api/org/{organisation}/v1/{payment-service}/{payment-product}/{paymentId}/authorisations/{authorisationId} | Update PSU data for payment initiation |
Documentation For Models
- AccountAccess
- AccountDetails
- AccountList
- AccountReference
- AccountReport
- AccountStatus
- AdditionalInformationAccess
- AdditionalInformationStructured
- Address
- Amount
- AuthenticationObject
- AuthenticationType
- AuthorisationConfirmation
- AuthorisationConfirmationResponse
- Authorisations
- Balance
- BalanceType
- BulkPaymentInitiationJson
- BulkPaymentInitiationWithStatusResponse
- CardAccountDetails
- CardAccountList
- CardAccountReport
- CardAccountsTransactionsResponse200
- CardTransaction
- ChallengeData
- ChargeBearer
- Client
- ConfirmationOfFunds
- ConsentInformationResponse200Json
- ConsentStatus
- ConsentStatusResponse200
- Consents
- ConsentsResponse201
- DayOfExecution
- Error400AIS
- Error400AISAdditionalErrors
- Error400NGAIS
- Error400NGPIIS
- Error400NGPIS
- Error400NGSBS
- Error400PIIS
- Error400PIISAdditionalErrors
- Error400PIS
- Error400PISAdditionalErrors
- Error400SBS
- Error400SBSAdditionalErrors
- Error401AIS
- Error401AISAdditionalErrors
- Error401NGAIS
- Error401NGPIIS
- Error401NGPIS
- Error401NGSBS
- Error401PIIS
- Error401PIISAdditionalErrors
- Error401PIS
- Error401PISAdditionalErrors
- Error401SBS
- Error401SBSAdditionalErrors
- Error403AIS
- Error403AISAdditionalErrors
- Error403NGAIS
- Error403NGPIIS
- Error403NGPIS
- Error403NGSBS
- Error403PIIS
- Error403PIISAdditionalErrors
- Error403PIS
- Error403PISAdditionalErrors
- Error403SBS
- Error403SBSAdditionalErrors
- Error404AIS
- Error404AISAdditionalErrors
- Error404NGAIS
- Error404NGPIIS
- Error404NGPIS
- Error404NGSBS
- Error404PIIS
- Error404PIISAdditionalErrors
- Error404PIS
- Error404PISAdditionalErrors
- Error404SBS
- Error404SBSAdditionalErrors
- Error405AIS
- Error405AISAdditionalErrors
- Error405NGAIS
- Error405NGPIIS
- Error405NGPIS
- Error405NGPISCANC
- Error405NGSBS
- Error405PIIS
- Error405PIISAdditionalErrors
- Error405PIS
- Error405PISAdditionalErrors
- Error405PISCANC
- Error405PISCANCAdditionalErrors
- Error405SBS
- Error405SBSAdditionalErrors
- Error406AIS
- Error406AISAdditionalErrors
- Error406NGAIS
- Error409AIS
- Error409AISAdditionalErrors
- Error409NGAIS
- Error409NGPIIS
- Error409NGPIS
- Error409NGSBS
- Error409PIIS
- Error409PIISAdditionalErrors
- Error409PIS
- Error409PISAdditionalErrors
- Error409SBS
- Error409SBSAdditionalErrors
- Error429AIS
- Error429AISAdditionalErrors
- Error429NGAIS
- ExecutionRule
- FrequencyCode
- HrefType
- InlineObject
- InlineResponse200
- InlineResponse2001
- InlineResponse2002
- InlineResponse2003
- LinksAccountDetails
- LinksAccountReport
- LinksAll
- LinksAuthorisationConfirmation
- LinksCardAccountReport
- LinksConsents
- LinksDownload
- LinksGetConsent
- LinksPaymentInitiation
- LinksPaymentInitiationCancel
- LinksSelectPsuAuthenticationMethod
- LinksSigningBasket
- LinksStartScaProcess
- LinksTransactionDetails
- LinksUpdatePsuAuthentication
- LinksUpdatePsuIdentification
- MessageCode2XX
- MessageCode400AIS
- MessageCode400PIIS
- MessageCode400PIS
- MessageCode400SBS
- MessageCode401AIS
- MessageCode401PIIS
- MessageCode401PIS
- MessageCode401SBS
- MessageCode403AIS
- MessageCode403PIIS
- MessageCode403PIS
- MessageCode403SBS
- MessageCode404AIS
- MessageCode404PIIS
- MessageCode404PIS
- MessageCode404SBS
- MessageCode405AIS
- MessageCode405PIIS
- MessageCode405PIS
- MessageCode405PISCANC
- MessageCode405SBS
- MessageCode406AIS
- MessageCode409AIS
- MessageCode409PIIS
- MessageCode409PIS
- MessageCode409SBS
- MessageCode429AIS
- OAuth2Error
- PaymentExchangeRate
- PaymentInitationRequestResponse201
- PaymentInitiationBodyJson
- PaymentInitiationBulkElementJson
- PaymentInitiationCancelResponse202
- PaymentInitiationJson
- PaymentInitiationStatusResponse200Json
- PaymentInitiationWithStatusResponse
- PeriodicPaymentInitiationJson
- PeriodicPaymentInitiationMultipartBody
- PeriodicPaymentInitiationWithStatusResponse
- PeriodicPaymentInitiationXmlPart2StandingorderTypeJson
- ProblemDetail
- PsuData
- PurposeCode
- ReadAccountBalanceResponse200
- ReadCardAccountBalanceResponse200
- RemittanceInformationStructured
- ReportExchangeRate
- ScaStatus
- ScaStatusAuthorisationConfirmation
- ScaStatusResponse
- SelectPsuAuthenticationMethod
- SelectPsuAuthenticationMethodResponse
- Session
- SigningBasket
- SigningBasketResponse200
- SigningBasketResponse201
- SigningBasketStatusResponse200
- StandingOrderDetails
- StartScaprocessResponse
- Token
- TppMessage2XX
- TppMessage400AIS
- TppMessage400PIIS
- TppMessage400PIS
- TppMessage400SBS
- TppMessage401AIS
- TppMessage401PIIS
- TppMessage401PIS
- TppMessage401SBS
- TppMessage403AIS
- TppMessage403PIIS
- TppMessage403PIS
- TppMessage403SBS
- TppMessage404AIS
- TppMessage404PIIS
- TppMessage404PIS
- TppMessage404SBS
- TppMessage405AIS
- TppMessage405PIIS
- TppMessage405PIS
- TppMessage405PISCANC
- TppMessage405SBS
- TppMessage406AIS
- TppMessage409AIS
- TppMessage409PIIS
- TppMessage409PIS
- TppMessage409SBS
- TppMessage429AIS
- TppMessageCategory
- TransactionAuthorisation
- TransactionDetails
- TransactionStatus
- TransactionStatusSBS
- TransactionsResponse200Json
- UpdatePsuAuthentication
- UpdatePsuAuthenticationResponse
- UpdatePsuIdenticationResponse
- UserInfo
Documentation For Authorization
BearerAuthOAuth
basicAuth
- Type: HTTP basic authentication
client_registration_token
- Type: API key
- API key parameter name: Authorization
- Location: HTTP header
client_secret
- Type: OAuth
- Flow: password
- Authorization URL:
- Scopes:
- clients: Enable client management
oAuth2AuthCode
- Type: OAuth
- Flow: accessCode
- Authorization URL: /api/auth/authorize
- Scopes:
- openid: openid
- offline_access: Offline access - refresh token
- aisp: Account information
- pisp: Payment initiation
oAuth2ClientCredentials
- Type: OAuth
- Flow: application
- Authorization URL:
- Scopes:
- aisp: Account information
- pisp: Payment initiation
oAuth2SSO
- Type: OAuth
- Flow: accessCode
- Authorization URL: /api/auth/authorize
- Scopes:
- openid: openid
- offline_access: Offline access - refresh token
- email: Email address
openId
Author
All versions of bankio-sdk-php with dependencies
PHP Build Version
Package Version
Requires
php Version
>=5.6
ext-curl Version *
ext-json Version *
ext-mbstring Version *
php-http/message Version *
php-http/multipart-stream-builder Version *
php-http/client-implementation Version *
ext-curl Version *
ext-json Version *
ext-mbstring Version *
php-http/message Version *
php-http/multipart-stream-builder Version *
php-http/client-implementation Version *
The package bank-io/bankio-sdk-php contains the following files
Loading the files please wait ....