Banqware Help Center

Change and release log:

Written by Maxime

Updated over 4 months ago

Release update: 156

Release	Version	Deployment Date
Production	156 from sandbox	tba
Sandbox	156	20.08.2021
additional information
Breaking Changes (with 1 month compatibility period)	no breaking changes
What is new?	technical release

Release update: 151

Release	Version	Deployment Date
Production	151 from sandbox	04.08.2021
Sandbox	151	26.07.2021
additional information
Breaking Changes (with 1 month compatibility period)	no breaking changes
What is new?	ING: fix for account identifier issue on ASPSP side; fix for credit card transactions - value will now be displayed correctly as negative Improvements in ASPSP error handling - mechanism is now less sensitive, so consents do not get invalidated as easily New banks: Credit Agricole Revolut - please note this ASPSP implements multicurrency accounts therefore using multicurrency endpoints is required for retrieving account and transaction data

Release update: 146

Release	Version	Deployment Date
Production	146 from sandbox	20.05.2021
Sandbox	146	11.05.2021
additional information
Breaking Changes (with 1 month compatibility period)
What is new?	1.Session blocking mechanism restrictions have been loosened - user will now be able to generate a new SCA link straight away, as long as previous authentication process was abandoned before completeng the SCA at the ASPSP side.
	2.New feature - in addition to an already existing enpoint for registering user identifiers, it is now possible to pass the identifier directly during consent creation. The feature is single-consent use only: identifiers passed in this manner will not be stored for later use. `1example: 2"userIdentifiers": 3 { 4 "Alias": "testAlias" 5 }`
	3.Fixed issue with errors sometimes being returned during user creation

Release update: 144

Release	Version	Deployment Date
Production	144 from sandbox	29.04.2021
Sandbox	144	15.04.2021
additional information
Breaking Changes
What is new?	1.Nestbank now returns iban account identifier in correct format: 'PLXXXXXX' instead of 'XXXXXXXX'.
	2. Security feature - callback authentication via encryption keys: It is now possible to generate public+private key pair for your tenant using the POST endpoint listed below. Public key may then be retrieved under GET endpoint. Callback message will be encrypted and passed in the 'Authorization' header - to be validated on the client side using the public key. The feature is optional - if no key pair is generated for your tenant, callbacks will funcion as previously. `1New endpoints: 2Management resources > KeyPair 3GET /api/tenant/signaturekey Get signature public key. 4POST /api/tenant/signaturekey Creates new asymmetric key pair. 5DELETE /api/tenant/signaturekey Deletes asymmetric key pair.`
	3. New endpoint available for checking callback structure: Coverage resources > Callback GET /api/callback/description List available callbacks and describes their structure.
	4. New endpoint available for consent refresh. If the ASPSP supports consent refresh the existing consent will be renewed, in other cases - new consent will be created. `1Consent Resources > Consent 2PUT /api/user/{userIdType}/{userId}/consent/{consentId} Refresh given consent.`

Release update: 141

Release	Version	Deployment Date
Production	141 from sandbox	04.02.2021
Sandbox	141	25.01.2021
additional information
Breaking Changes (with 1 month compatibility period)
What is new?	A mechanism blocking multiple sessions being initiated for the same user at the same time has been implemented, to prevent issues with ASPSP apis this could cause. For methods listed below, it will be impossible to start a new session if there is already an active session in progress started by one of them: POST create consent DELETE consent POST create update DELETE user
	2.Single and multiple use consent has been set up for KYC and AIS products. KYC will support single use, AIS will support multiple use. In the future AIS product will come with both single and multiple use consents. Consent information has been updated with two new flags: consentUsed: true/false usageLimit: single/multiple
	3.A new KYC service is now available - KYB. For users created in business context it is now possible to receive business information under a new endpoint: /api/identity/{userIdType}/{userId}/businessIdentity In sandbox environment you will receive a mock response to this enpoint - it will always reuturn the same data.

Release update: 138

Release	Version	Deployment Date
Production	138 from sandbox	28.12.2020
Sandbox	138	16.12.2020
additional information
Breaking Changes (with 1 month compatibility period)	rollback backwards compatibility for changes from 136: rollback backwards compatibility for changes from 136: Changed callbacks for naming uniformity - new values are all in camelCase, old values will no longer be returned user IP header has been added (X-IP-Address) - the header will become mandatory with r138 for those requests: POST Consent POST Update when isUserInteraction = true
-
What is new?	Consent page styling will now allow for limited content modification as well

Release update: 137

Release	Version	Deployment Date
Production	137 from sandbox	09.12.2020
Sandbox	137	01.12.2020
additional information	Improved API performance
Breaking Changes (with 1 month compatibility period)
-
What is new?

Release update: 136

Release	Version	Deployment Date
Production	136 from sandbox	26.11.2020
Sandbox	136	19.11.2020
additional information
Breaking Changes (with 1 month compatibility period)	Changed callbacks for naming uniformity Changed callbacks for naming uniformity - new values are all in camelCase, old values will still be returned until r138: Consent: ConsentId > consentIdPreviousStatus > previousStatusCurrentStatus > status Update (no changes): previousStatusstatusupdateIduserId Payment: PaymentId > paymentIdStatus > statusPreviousStatus > previousStatus
-	X-IP-Adress user IP header has been added (X-IP-Address) - the header will become mandatory with r138 for those requests: POST ConsentPOST Update when isUserInteraction = true more information
What is new?	New Product! beta version of PISP now available in sandbox: POST /api/user/{userIdType}/{userId}/payment - Create a payment. GET /api/user/{userIdType}/{userId}/payment - List user payments. GET /api/user/{userIdType}/{userId}/payment/(paymentId} - Get a single payment. GET /api/bank/{bankIdType}/{bankId}/paymentModel - Get payment models for specified bank. GET /api/callback/pis/redirect-url - A callback for ASPSP to be called after a completed PIS SCA.
	New callback available Consent callbacks now available Payment callbacks now available

Release update: 135

Release	Version	Deployment Date
Production	135 from sandbox	05.11.2020
Sandbox	135	30.10.2020
additional information
Breaking Changes (with 1 month compatibility period)	Rolling back backwards compatibility for ConsentPage/styles Consent page styling urls: /consentPage/styles >>> /consentPage/style
-	Rolling back backwards compatibility for Rename callbackUrl is now updateCallbackUrl Rename: callbackUrl is now updateCallbackUrl
What is new?	Changes for mBank - due to significant differences between retail and corporate apis of this ASPSP there are now seperate configurations available for each. Corporate mBank api is still available under 'BREXPLPW' swiftCode in the form it had to this date.To use corporate-api-only config choose 'BREXPLPW_CORPO' swiftCode.
	Consent page - clicking the 'proceed' button more than once is now blocked

Release update: 134

Release	Version	Deployment Date
Production	134 from sandbox	21.10.2020
Sandbox	134	12.10.2020
additional information
Breaking Changes (with 1 month compatibility period)
-
What is new?	Consent endpoints now return info on the currency of the account linked to given consent
	Sender and recipient IBANs now available under transaction endpoints
	Consent pages for KYC and AIS have been seperated to differentiate scope for each of the services

Release update: 133

Release	Version	Deployment Date
Production	133 from sandbox	05.10.2020
Sandbox	133	28.02.2020
additional information
Breaking Changes (with 1 month compatibility period)	Consent page styling urls Consent page styling urls: /consentPage/styles >>> /consentPage/style
-
What is new?	Consent endpoints now return info on the accounts linked to given consent

Release update: 132

Release

Version

Deployment Date

Release	Version	Deployment Date
Production	132 from sandbox	tba
Sandbox	132	28.02.2020
additional information
Breaking Changes (with 1 month compatibility period)	callbackUrl is now updateCallbackUrl Breaking changes (with 1 month backwards compatibility period): Rename: callbackUrl is now updateCallbackUrl
-
What is new?	New Product! beta version of PISP now available: POST /api/user/{userIdType}/{userId}/payment - Create a payment. GET /api/user/{userIdType}/{userId}/payment - List user payments. GET /api/user/{userIdType}/{userId}/payment/(paymentId} - Get a single payment. GET /api/bank/{bankIdType}/{bankId}/paymentModel - Get payment models for specified bank. GET /api/callback/pis/redirect-url - A callback for ASPSP to be called after a completed PIS SCA.
	New callback available 1. Consent callbacks now available 2. Payment callbacks now available

Related Articles

Integration guide:

Scenariusze testowe PIS

Callback services

Zgody XS2A- implementacja PSD2Hub