Salt Edge PSD2 Compliance Logo

V2

Signing Baskets

Create

Create a signing basket resource.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImFwcF9uYW1lIjoiRmVudHVyeSIsInBheW1lbnRfcHJvZHVjdCI6InNlcGEtY3JlZGl0LXRyYW5zZmVycyIsInJlZGlyZWN0X3VybCI6Imh0dHBzOi8vcGxlYXNlLXJlZGlyZWN0LW15LXBzdS5oZXJlIiwicHN1X2lwX2FkZHJlc3MiOiIxOTIuMTEuMi4xOCIsInNlc3Npb25fc2VjcmV0IjoiY2M1YTgwMjItNWU3MS00NjBlLTkzZmEtYWIwYmUxOTk3YTU0IiwicHJvdmlkZXJfY29kZSI6ImRlbW9iYW5rIiwicGF5bWVudHNfaWRzIjpbMTIzMCwxMjQwXSwiYnVsa19pZHMiOls1MTUxLDU0NDFdLCJwZXJpb2RpY19pZHMiOlsxMjMxLDEzMjVdfSwiZXhwIjoxNzE2MDc4MTMwfQ.JZ4rf1pMEukWdgB2VvVnCi7GEBJDLDtDeP4EhQ36_RqpsMQoDw_RmSGm07BRqm0YVt4mjuc60nUgHl-nVuk0UQhEhobFFEW6eaDYHB7T7mwaIyTPVKizJ-QpM7nBXupj89lIWukKVLTlfETi0mifQJYKZN7VxIzfIZ00HNwmEjHIcKaimdC6qsvYclln3c6tRigNHd_MZTKwnaww98F8c1Z9gxdn8Bc11MrZMtM7eVmkA1wj621NRbKi1g4WFCep4Gcd-e4pY_hN_KNaSJcerArU8ZGMGsZ4zcz9sU02T642HFHpycVywIq89f7Sn5TT0q5PBTHIniG7mzgEmq21ag" \ 
 -H "Access-Token: b2077c5c020a5e262767aac63fdbc75fd64461afc660784fbc3451766f586bb4836e3405007c2caf497a1125ba58fb49be65b3c352285dea68328aded84e2f91" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 685" \ 
 -X POST "https://your.connector.url/api/priora/v2/signing_baskets"

Example of request parameters

{"data":{"app_name":"Fentury","payment_product":"sepa-credit-transfers","redirect_url":"https://please-redirect-my-psu.here","psu_ip_address":"192.11.2.18","session_secret":"cc5a8022-5e71-460e-93fa-ab0be1997a54","provider_code":"demobank","payments_ids":[1230,1240],"bulk_ids":[5151,5441],"periodic_ids":[1231,1325]},"exp":1574093209}
Request

POST https://your.connector.url/api/priora/v2/signing_baskets

Headers
Header Type Description
Authorization string, required JSON Web Token containing payload, signed using RSA256 and application.private_key.
Accept string, required Media type that is acceptable for the response. Allowed values: application/json
Content-Type string, required The media type of the body of the request. Allowed values: application/json
Client-Id integer, required TPP application identifier in Salt Edge PSD2 Compliance.
Psu-Device-ID string, optional UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID need to be unaltered until removal from device.
Psu-User-Agent string, optional The forwarded Agent header field of the HTTP request between PSU and TPP, if available.
Psu-Geo-Location string, optional The forwarded Geo Location of the corresponding HTTP request between PSU and TPP if available.
Psu-Corporate-ID string, optional PSU corporate identifier (optional).
Unpacked Request Authorization
exp
integer, required
The lifetime of the request in timestamp UTC format. Values greater than: Current time.
Response headers
Header Type Description
Retry-After integer, optional Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request.
Response

Upon successful request, 200 status code should be returned.


Revoke

Revoke a signing basket resource.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiY2M1YTgwMjItNWU3MS00NjBlLTkzZmEtYWIwYmUxOTk3YTU0IiwicHJvdmlkZXJfY29kZSI6ImRlbW9iYW5rIiwiYXBwX25hbWUiOiJGZW50dXJ5IiwicmVkaXJlY3RfdXJsIjoiaHR0cHM6Ly9wbGVhc2UtcmVkaXJlY3QtbXktcHN1LmhlcmUiLCJiYXNrZXRfaWQiOiIxIn0sImV4cCI6MTcxNjA3ODEzMX0.aN-NJ-lR13TCUzUDLvvH2Tn5MavqHYpt-H0R4dQvzQb5LAdv3T1p9DP5piD3b7UaL5YFwnHYFL0GZ4eAQH3Ly6vDIua3byEBo12dJfjNDJ-06y0EJU_qZcVEzoa-lmalvr9n8jfH5bQ4gja9qQCmXMvpbAUPWWHjbQPCyqxKYGKps3t4z6dC9O_nwEb_LLq3MfhuzWbUtQTsxHB8BVKSXu84CyVYbRA_5OExzN8wODls1nQCtJ57EWnm1KD5t9_hgO1cdNI0rmE0Es_dQN3m8KAAEYqIeT2ge5LzMJrhEJZ7c0tkbTbQSpobrRDb_J2r45Ns5K5taWESNAEYaQzWNQ" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 771" \ 
 -X DELETE "https://your.connector.url/api/priora/v2/signing_baskets"

Example of request parameters

{"data":{"session_secret":"cc5a8022-5e71-460e-93fa-ab0be1997a54","provider_code":"demobank","app_name":"Fentury","redirect_url":"https://please-redirect-my-psu.here","basket_id":"1"},"exp":1574093210}
Request

DELETE https://your.connector.url/api/priora/v2/signing_baskets

Headers
Header Type Description
Authorization string, required JSON Web Token containing payload, signed using RSA256 and application.private_key.
Accept string, required Media type that is acceptable for the response. Allowed values: application/json
Content-Type string, required The media type of the body of the request. Allowed values: application/json
Client-Id integer, required TPP application identifier in Salt Edge PSD2 Compliance.
Psu-Device-ID string, optional UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of an installation identification this ID need to be unaltered until removal from device.
Psu-User-Agent string, optional The forwarded Agent header field of the HTTP request between PSU and TPP, if available.
Psu-Geo-Location string, optional The forwarded Geo Location of the corresponding HTTP request between PSU and TPP if available.
Unpacked Request Authorization
exp
integer, required
The lifetime of the request in timestamp UTC format. Values greater than: Current time.
Response headers
Header Type Description
Retry-After integer, optional Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request.
Response

Upon successful request, 200 status code should be returned.


Sessions

Session Callback Endpoints are responsible for assuring communication between ASPSP and TPP, where ASPSP notifies about its Redirect SCA authorisation page and if the authorisation process is successful or failed.

Success

Success callback should be sent to Salt Edge PSD2 Compliance when all required verification steps have been passed, and therefore access is granted.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImV4dHJhIjp7fSwic2Vzc2lvbl9zZWNyZXQiOiJCVnV2ZVNMUUNyQTVqQllVeXhYZSJ9LCJleHAiOjE3MTYwNzgxMzJ9.akF8PEskhSoV7Kra2cXpVcPpnW-uH1Gt1nDfOuYvqjW8cz5Z-QyPZ5BNL4xLTzLFuD0aSPYiYdY3DHSq1OqCjdylo2EbCvJBtFl2H2LuVOCSF7gPQ4BDIadd2DYnTloEUftW3pxbaOiKY0ippSQJmxgWoC1rf7SVaO-G2sidIgjiZFWP8bLKX6sdeyN54N_sEc4oOQrDlJAUJwVKL_OdeNV_SHnskcyaOoi4NE5J_I-d_ZKhFUoQFXqAb6EDazjO-eCcqvTVz5X6HnMkkWyYpC9kQryf0QQ5w3IJPP1mvteATZwKK_-RG9TbYIrAXtirc3BEVMf7iI5ZDbjYuak9SA" \ 
 -H "App-Id: qjQYP-jCx-8FBsZSgNVzIw" \ 
 -H "App-Secret: -XeeN2UhtdphUGtI-FZpzg" \ 
 -X PATCH "/api/connectors/v2/sessions/:session_secret/success"

Example of request parameters

Example of response

{"data":{},"meta":{"time":"2019-11-18T16:04:48.773Z"}}
Request

PATCH /api/connectors/v2/sessions/:session_secret/success

Headers
Header Type Description
Authorization string, required JSON Web Token containing payload, signed using RSA256 and application.private_key. Can raise: AuthorizationMissing
App-Id string, required Provider's app_id from connection details tab. Can raise: ProviderNotFound, ProviderDisabled, ConfigurationError
App-Secret string, required Provider's app_secret from connection details tab.
Unpacked Request Authorization
Response

Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.


data
hash, optional
Wrapper for the data.
Related Errors
Class Code Description
SessionClosed 400 Session specified in request is already closed and cannot be modified.
ConfigurationError 400 Missing configurations in dashboard.
SessionExpired 401 Found session is expired and cannot be processed anymore.
AuthorizationMissing 401 Authorization header is missing.
SessionFinalised 403 Session specified in request is already finalised and cannot be processed.
SessionNotFound 404 Session specified in request does not exist or cannot be retrieved.
ProviderNotFound 404 Provider specified in request does not exist or cannot be retrieved.
ProviderDisabled 406 Cooperation with specified Provider is impossible.

Update

Update callback may be accessed multiple times in order to request multiple steps of authorization or to send other updates to Salt Edge PSD2 Compliance session.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fZXhwaXJlc19hdCI6IjIwMjAtMDUtMTBUMTI6MzM6NTAuMjE1WiIsInN0YXR1cyI6InJlY2VpdmVkIiwic2NhX3N0YXR1cyI6InBzdUlkZW50aWZpZWQiLCJyZWRpcmVjdF91cmwiOiJodHRwczovL3JlZGlyZWN0LXVybC5jb20iLCJleHRyYSI6e30sInNlc3Npb25fc2VjcmV0IjoiQlZ1dmVTTFFDckE1akJZVXl4WGUifSwiZXhwIjoxNzE2MDc4MTMyfQ.f_R0TGwKQl5aYQTILZYNFAE_WUc2XxAjODyf2NAyJ8phqzHWQdmhkDLOngCaCQtqPvxbtjQ8hiGYaIAOH5zByn-YaSMmwnmhEQ70eU3LW5ThjdCfsKAKER6336ROQWCRysmwOwAINIeshNsKCIDTnA1Je6RAKgkK84FwcjFRvBITOOoCATfQ9WxCxPLi55LJqPJ3rYigsOgu1c8hEK2fYB9SVu4lIj1k8esvUpSE5dcCjGgXYSipFxrpUyzmXE9D2wHxmlALuGu4MajICbMLIqMCn1kKOQF785gsfno5YhjGLITc9eIp5v6HkDnGi7-PlL1n1VuRRXvd7FOZ9XNDZg" \ 
 -H "App-Id: q5QE7Dqlpm1d5weLS5pn7w" \ 
 -H "App-Secret: y8imt1cgG8x2zmBMrF-oxw" \ 
 -X PATCH "/api/connectors/v2/sessions/:session_secret/update"

Example of request parameters

Example of response

{"data":{},"meta":{"time":"2019-11-18T16:04:48.853Z"}}
Request

PATCH /api/connectors/v2/sessions/:session_secret/update

Headers
Header Type Description
Authorization string, required JSON Web Token containing payload, signed using RSA256 and application.private_key. Can raise: AuthorizationMissing
App-Id string, required Provider's app_id from connection details tab. Can raise: ProviderNotFound, ProviderDisabled, ConfigurationError
App-Secret string, required Provider's app_secret from connection details tab.
Unpacked Request Authorization
Response

Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.


data
hash, optional
Wrapper for the data.
Related Errors
Class Code Description
SessionClosed 400 Session specified in request is already closed and cannot be modified.
ConfigurationError 400 Missing configurations in dashboard.
SessionExpired 401 Found session is expired and cannot be processed anymore.
AuthorizationMissing 401 Authorization header is missing.
SessionFinalised 403 Session specified in request is already finalised and cannot be processed.
SessionNotFound 404 Session specified in request does not exist or cannot be retrieved.
ProviderNotFound 404 Provider specified in request does not exist or cannot be retrieved.
ProviderDisabled 406 Cooperation with specified Provider is impossible.

Fail

Fail callback should be used when authorization process has been compromised for any reason: broken request, invalid credentials, etc.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiM1BRaXB1RFBvV3BhMTFGY1ZFVjYiLCJlcnJvcl9jbGFzcyI6IkludGVybmFsUHJvdmlkZXJFcnJvciIsImVycm9yX21lc3NhZ2UiOiJJbnRlcm5hbCBlcnJvciIsImV4dHJhIjp7fX0sImV4cCI6MTcxNjA3ODEzMn0.kmcuBHR7GrQF61UAy-E-3iRb_cN02UCudgIV2lb-3PtriA0rLVXPSon1oQ8ACjhfCWM20RQcKIioI5W9uEyh2SjoJTi0nj4JGkvFPVMM_kPjoBV0RpzdmRHDf1X-aCDDzb1Lyf_SsBq6GrwhmXtVd7lEWeOAt24AXQgVXfCA60taO9yWRF8N4Ag3Js0lenXpL0DwBCM60WAzA0NiO2zxbDHK1siznOFHTXRu3KKbXuEK3NZhVD9ShHX4jw1r1jq1DWOV0ccuwbgRaBQg4ye8Dim9qlNmA1SnAfy1HIrJW-QfrIavl-KOZOt6_7RPiWjsX4vi8qc-nbDgWCOil9V3wA" \ 
 -H "App-Id: xU7SyhPrd95GAPSMNo_XMQ" \ 
 -H "App-Secret: BVSkESo7zpRdzk_hWUUwCQ" \ 
 -X PATCH "/api/connectors/v2/sessions/:session_secret/fail"

Example of request parameters

{"data":{"session_secret":"3PQipuDPoWpa11FcVEV6","error_class":"InternalProviderError","error_message":"Internal error","extra":{}},"exp":1574093208}

Example of response

{"data":{},"meta":{"time":"2019-11-18T16:04:48.710Z"}}
Request

PATCH /api/connectors/v2/sessions/:session_secret/fail

Headers
Header Type Description
Authorization string, required JSON Web Token containing payload, signed using RSA256 and application.private_key. Can raise: AuthorizationMissing
App-Id string, required Provider's app_id from connection details tab. Can raise: ProviderNotFound, ProviderDisabled, ConfigurationError
App-Secret string, required Provider's app_secret from connection details tab.
Unpacked Request Authorization
exp
integer, required
The lifetime of the request in timestamp UTC format. Values greater than: Current time.
Response

Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.


data
hash, optional
Wrapper for the data.
Related Errors
Class Code Description
SessionClosed 400 Session specified in request is already closed and cannot be modified.
ConfigurationError 400 Missing configurations in dashboard.
SessionExpired 401 Found session is expired and cannot be processed anymore.
AuthorizationMissing 401 Authorization header is missing.
SessionFinalised 403 Session specified in request is already finalised and cannot be processed.
SessionNotFound 404 Session specified in request does not exist or cannot be retrieved.
ProviderNotFound 404 Provider specified in request does not exist or cannot be retrieved.
ProviderDisabled 406 Cooperation with specified Provider is impossible.