Connector Endpoints
Funds Check
This endpoints are responsible for creating payment orders on behalf of PSU via TPP interface. Process of payment creation starts once PSU fills a payment template form and submits the request. You can find below sequence diagrams represeting oauth payment creation, oauth payment creation using SCA and funds availability flows.
Funds Availability Flow
Check
This endpoint is used to check availability of funds for a specific account. As a result, Connector should send a success or fail callback to Salt Edge PSD2 Compliance with result of the operation.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImN1cnJlbmN5X2NvZGUiOiJFVVIiLCJhY2NvdW50IjoiODQ1NzI0ODYiLCJzZXNzaW9uX3NlY3JldCI6ImVTU1c1ZEFWYWdib3o4S1h2NGc3IiwicHJvdmlkZXJfY29kZSI6ImRlbW9iYW5rIiwiYW1vdW50IjoiNDAuNzcifSwiZXhwIjoxNzE0NzU3MTc3fQ.pmzXoVzl_IkyZ8sewkfzIVfcZK-XDfcNrw1aR387Go46WZqSMil3qdmoKOt9twBvtCDZjj724cJ3e4O24SpE8oPlkb2m2jVjrviBFoPSIrHwMyKiK7ZuiuLuGcPqfLaFBlC8I5Xh5lCtn37xX96WG-PtIZ20QUEgZ7KwzOeQ5-tR1eCDQZFtSrHEXc1eja6UwtFrg5o7R1xm9CBWYhhueRJU3072FMaONBjgVN6_Hxj7zYQuywcyRQlhhrlKSE9HfOWDy_C1CCd6snp2NxWEIZ2Z4CUaMe8TyTxKaaKn-5utp8uDj0iaRumvrS_hjEbL1PlPoyd9UPuwYUIrg46Y-w" \
-H "Access-Token: e41d6d72e68723224cb6e25c2c99ddee95376d1b33e6522f2e36d4e8194fc84f71655993eabf6f020afa10fdbddd54f7d1a60ffbda7b90961045f977f7c450de" \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Client-Id: 216" \
-X POST "https://your.connector.url/api/priora/v1/payments/check_funds"Example of request parameters
{"data":{"currency_code":"EUR","account":"84572486","session_secret":"eSSW5dAVagboz8KXv4g7","provider_code":"demobank","amount":"40.77"},"exp":1574093209}
Request
POST
https://your.connector.url/api/priora/v1/payments/check_funds
Headers
| Header | Type | Description |
|---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key.
|
Access-Token
|
string, required | The token which is created by a connector as a result of successful authentication. |
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 | Client application identifier in Salt Edge PSD2 Compliance. Should be used to get public key for Authorization header validation. |
Unpacked Request Authorization
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.
Related Errors
| Class | Code | Description |
|---|---|---|
| UnknownCurrency | 404 | Unknown Currency code |
×
![]()
Errors
Additional endpoints to be implemented on connector side to improve communication between Salt Edge PSD2 Compliance Solution and Connector.
Notify
This endpoint is responsible for receiving validation errors of responses which Connector sends to Salt Edge PSD2 Compliance Solution
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InJlcXVlc3QiOnsibWV0aG9kIjoiZGVsZXRlIiwidXJsIjoiaHR0cHM6Ly91c2VyLndpbGwuYmUvcmVkaXJlY3RlZC9oZXJlIiwiaGVhZGVycyI6e319LCJlcnJvciI6eyJlcnJvcl9tZXNzYWdlIjoic29tZXRoaW5nIHdlbnQgd3JvbmciLCJlcnJvcl9jbGFzcyI6IkludGVybmFsUHJvdmlkZXJFcnJvciJ9fSwiZXhwIjoxNzE0NzU3MTc4fQ.B4zf8ZcQxRKid3j_GRcVgZvgsrc2610Hzg1x_-Mkvz3QbcdbCBRoFe7V7S3pTaRdpI8d48HFxUz13JBZykKHYmT4qNNguZjTSyRnLR7dw0mOjTa96IuluuyQPaR0Jtgwb5YKlRVSINnIv-EaLVVQDbFvaVrNFS3ehWAhh6lmYKPmIIty993qjJNSNCu5hG1gJX-457PnZSdky5dtKg5G9bdoSL-idfIqEYYRtIqb_gIWvOr9QWohYr2YEUF1npOGyw5ARzD1QrjR37o0Gfk6DPWZ-AoGtZ8tvwHuSHjNcIRGkro9dWmivGTVxmnpsNUSlAMhg0gUFu_46Pqp4X6elA" \
-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/v1/errors"Example of request parameters
{"data":{"request":{"method":"delete","url":"https://user.will.be/redirected/here","headers":{}},"error":{"error_message":"something went wrong","error_class":"InternalProviderError"}},"exp":1574093209}
Request
POST
https://your.connector.url/api/priora/v1/errors
Headers
| Header | Type | Description |
|---|---|---|
Authorization
|
string, required |
JSON Web Token containing payload, signed using RSA256 and application.private_key.
|
Access-Token
|
string, required | The token which is created by a connector as a result of successful authentication. |
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 | Client application identifier in Salt Edge PSD2 Compliance. Should be used to get public key for Authorization header validation. |
Unpacked Request Authorization
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.
×
![]()
Salt Edge Endpoints
Funds Availability
Success
Success callback should be used when all verification procedures have passed and connector can tell wether funds are available or not for indicated account.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiUnBBb0hQbUg3RHdSTExMeWNqREwiLCJmdW5kc19hdmFpbGFibGUiOnRydWV9LCJleHAiOjE3MTQ3NTcxNzh9.ww3yRGUO8WCAZOSa4yNheepqRtKzEtMkrFJ2FBcUak_xMAZsX-0GdOdVFDW2H1UJNa7zQdTq5VwsJXkD0xbqwlKIV-qP8QYz9me91A_MrWu3pz9eqJdL-LgZrfWxC_o84l7jnPEXulbeTGWQ3dHjy6io3kC5dGU5jkrEHfWpJmXukuq7ItMYT6iu1ypf3MoQG-XcZd9S5iY0hEg32bzLkHOxSbpgFiNKiDZpUIR2ZVB8pjdXsy5u1qBQLI3iTS1BWRY0J2DfCWV1sIqW8y_VuAtmkr284jmev4qJXOBWH7ltJLm5e1ggIbeRUydcn_FxCBryOqZpe2FZpnA_PFautg" \
-H "App-Id: tmseeTcEhV-x1t2ZSIOQ4Q" \
-H "App-Secret: wARHNQnMuIhcv3Z21ot-1g" \
-X POST "/api/connectors/v1/funds_availability/success"Example of request parameters
{"data":{"session_secret":"RpAoHPmH7DwRLLLycjDL","funds_available":true},"exp":1574093208}
Example of response
{"data":{},"meta":{"time":"2019-11-18T16:04:48.634Z"}}
Request
POST
/api/connectors/v1/funds_availability/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.
Related Errors
| Class | Code | Description |
|---|---|---|
| ConfigurationError | 400 | Missing configurations in dashboard. |
| AuthorizationMissing | 401 | Authorization header is missing. |
| 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 account could not be found or currency_code is not supported.
CURL
curl -i \
-H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoieXl6YnlMaFpTYU05RFpBWF9zVG8iLCJlcnJvcl9jbGFzcyI6IkludGVybmFsUHJvdmlkZXJFcnJvciIsImVycm9yX21lc3NhZ2UiOiJJbnRlcm5hbCBlcnJvciIsImV4dHJhIjp7fX0sImV4cCI6MTcxNDc1NzE3OX0.Q5IoiUwu1Xq02My1LfIi_wRQ2trulpo-B-Ohxlp-33luA-ujv22kL_4TYbU-nn_6cj09uYrO4XCK9zwG3UdLfgSFqKnXoA8WHYn79tSG8N2xMJbmyMPVaZ-RIXQ9XOlG_AGRL8zYyGyk3OJbKbYNaLq43x-GJd4w2wkOOsckzIE0h7zfv_wYyo0oRkoyvY5Y1PGwbDBtaesGxa621HyBpbVR_uRavibKZw6_sRkvNsOLB9y3IR8lWmngq87eM4hV3jPO_bV_q0uJ3c-ugEikJOSerqN_0AM6nk2Cr_PZesTzbFMvsitP10oelcDaSCqorSgbKKRUSGBk3buaXJLPyw" \
-H "App-Id: 7K6q6MmnPgOlJbkuFk1Cgg" \
-H "App-Secret: hET3DChd1v0WVZHTbrS7xw" \
-X POST "/api/connectors/v1/funds_availability/fail"Example of request parameters
{"data":{"session_secret":"yyzbyLhZSaM9DZAX_sTo","error_class":"InternalProviderError","error_message":"Internal error","extra":{}},"exp":1574093208}
Example of response
{"data":{},"meta":{"time":"2019-11-18T16:04:48.567Z"}}
Request
POST
/api/connectors/v1/funds_availability/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
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
| Class | Code | Description |
|---|---|---|
| ConfigurationError | 400 | Missing configurations in dashboard. |
| AuthorizationMissing | 401 | Authorization header is missing. |
| 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. |
×
![]()