Salt Edge PSD2 Compliance Logo

V1

Payments

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.

OAuth SCA Payment Creation Flow OAuth SCA Payment Creation Flow
OAuth Payment Creation Flow OAuth Payment Creation Flow

Create

Create a payment. As a result, Connector should send a success, update or fail callback to Salt Edge PSD2 Compliance with result of the operation.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InByb3ZpZGVyX2NvZGUiOiJkZW1vYmFuayIsInNlc3Npb25fc2VjcmV0IjoiZlZqMkxaeTl5N0pLV3V4YWJFRUQiLCJvcmlnaW5hbF9yZXF1ZXN0Ijp7ImNsaWVudF9qd3QiOiJCZWFyZXIgZXlKMGVYQWlPaUpLVjFRaUxDSmhiR2NpT2lKU1V6STFOaUo5LmV5SmtZWFJoSWpwN0luQnliM1pwWkdWeVgyTnZaR1VpT2lKa1pXMXZZbUZ1YXlJc0luUmxiWEJzWVhSbFgybGtJam81TWpnc0luSmxaR2x5WldOMFgzVnliQ0k2SW1oMGRIQnpPaTh2ZFhObGNpNTNhV3hzTG1KbEwzSmxaR2x5WldOMFpXUXZhR1Z5WlNJc0ltSmxibVZtYVdOcFlYSjVYMmxrSWpvME1UWXNJbVp2Y21ObFgzTmpZU0k2ZEhKMVpTd2laWGgwY21FaU9udDlmU3dpWlhod0lqb3hOVGMwTURrek1qQTVmUS5PT3NQX1dOSjZjM0JJNjB0YkI5bXlETGx2Y1FFWTBtZ2JpQVVsQmZKUW1UOVU3cnBDV3FFUWNTUUFsNDk1RGt1bmw4bll0UU5DYzNibVcycXNfZVg4aDYtSmszR1B4ekZlUzd1RVMzNVllZk1xeDN6SjVnWGVmZy1DV3BKUmNNQ2NJUV9paDJKX21wVEcxdmxvNGNZUl91alE4ZU9DZXVrbFdVRjFvcExINzkxYnIwMTcxU05TbUtpNkdtN3FRZm42d1Zjdmg2WDhNVXl1Q1kxaldSOU5DUDlRY2JDWGF3eFJtWFlraGZFMUU2Q2FrZkxnZ1JJOVhUcllCMVhLQ3hLUUZYYnhxWGNITDJrd1pXT0k5alJzS1lkelVxdldNNGtnVVg2T3cwQm44TlpqNHRSbXBsNUxCWWtZRk9sUlN5YjdMUVFtSGNQSDJSV1BEeEJHczQzbFEiLCJjbGllbnRfcGF5bG9hZCI6eyJkYXRhIjp7InJlZGlyZWN0X3VybCI6Imh0dHBzOi8vdXNlci53aWxsLmJlL3JlZGlyZWN0ZWQvaGVyZSIsImJlbmVmaWNpYXJ5X2lkIjo0MTYsImZvcmNlX3NjYSI6dHJ1ZSwiZXh0cmEiOnt9LCJ0ZW1wbGF0ZV9pZCI6OTI4LCJwYXltZW50X2F0dHJpYnV0ZXMiOnsiZnJvbV9hY2NvdW50IjoiMTM0NjU0NjQiLCJ0b19hY2NvdW50IjoiMjU3NjU3NDYiLCJhbW91bnQiOjEwMC41LCJkZXNjcmlwdGlvbiI6InRlc3QifSwicHJvdmlkZXJfY29kZSI6ImRlbW9iYW5rIn0sImV4cCI6MTU3NDA5MzIwOX19LCJwcmlvcmFfcGF5bWVudF9pZCI6MzA3LCJwYXltZW50X3R5cGUiOiJQU0RfQUlTUCJ9LCJleHAiOjE3MzI0MjUyNjYsImlzcyI6InByaW9yYS5zYWx0ZWRnZS5jb20ifQ.Q6hBH61LCRrxS_OlU4wtjRFiO22PHpWxBg5gYZTAqJZf-4VAZr0UBuxQg6c4QZWsGEsRTRxldF8yNxSMCF3WmK8ju68uc5fbQ5cjFBIRoSBf4IqKiqInPFqzVQDyscl0KwIXIbSQIzKl4Qw34NsB-NfS0SPeBUImiX0I5mcOQlZpZWMKA9Ww0AuDurwh9-w4bdrxITenQSaZUWpHQe_WnVrpQWHc6bivdDLIaMUPkcAG1z0GaQ8DvJWBzey3u9Dd0qrJVj1yxeHaKfQWNI8KbZzd1bhYHEaAk5fHL18Nedp6_r-kijVhI_YofB3nVarZ0Pj1UiwaRDIijKSwCIII9g" \ 
 -H "Access-Token: 724e66da1e457c6e5d309a78966d79ddd877368e142ed4b3fd36b73909a880ff69052fdfa57d09eb7b308a79b47728e80e681bbc9e9a68b72b2a10534c64220a" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 388" \ 
 -X POST "https://your.connector.url/api/priora/v1/payments/create"

Example of request parameters

Request

POST https://your.connector.url/api/priora/v1/payments/create

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.
Consent-Id integer, optional ID of the corresponding consent object as returned by an Account Information Consent Request.
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.


Show

Fetch all data relevant to a payment including fees, status and other. Response of this action should contain a corresponding payment object in JSON format.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7fSwiZXhwIjoxNzMyNDI1MjY3LCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.MZOxWKh84VQTwliRUUsxR6Swv4fhajzN_5Lhgwsnk3mJzqYQwgqNqO-MtRIfwK9166Dbm6XVWG4sMA_b9EioghnAC7iPVplCd_vez2IKeQQj6Kz00UzlFYN-f_VcxbLXmRCql9GhDZ_sloEHQHpY7crCYS4w06r8kPEFj8qs6qkEuIH2vl7iWXS_1SYudD_YFwpFzBDjei1vFxiiUPXD3rDhLZq_s4iHIqRMWnB1xPeG-lDsTanLQHqNeJ98YdtotMnd28iM3_GjAVKZ12UNGWRAnUeQkg-bXIjgKA4bvm4xjgksPS2rCuFPd1IPCuAS3C4V9kFSpWRdccNarv3GlA" \ 
 -H "Access-Token: d006c043ccc799237ec0be8137e8756c09b5add0357410a90298203705731b4da954c8108387bf8d1ef45244fee380704e7b883e66e09f51c767d776206f748c" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 951" \ 
 -X GET "https://your.connector.url/api/priora/v1/payments/show"

Example of request parameters

{"data":{},"exp":1574093209}

Example of response

{"data":{"total":-43.5,"payment_attributes":{"amount":100.5,"from_account":"13465464","to_account":"25765746","description":"test"},"status":"executing","fees":[{"amount":0.25,"description":"Bank fee.","currency_code":"EUR"},{"amount":0.1,"description":"Payment fee.","currency_code":"EUR"}],"description":"Test payment","id":198,"extra":{},"priora_payment_id":"677"}}
Request

GET https://your.connector.url/api/priora/v1/payments/show

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.
Consent-Id integer, optional ID of the corresponding consent object as returned by an Account Information Consent Request.
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.


Confirm

This endpoint is used for processing additional interactive steps in the process of payment creation. 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.eyJkYXRhIjp7InBheW1lbnRfaWQiOiI5NzkiLCJvcmlnaW5hbF9yZXF1ZXN0Ijp7ImNsaWVudF9qd3QiOiJCZWFyZXIgZXlKMGVYQWlPaUpLVjFRaUxDSmhiR2NpT2lKU1V6STFOaUo5LmV5SmtZWFJoSWpwN0ltTnlaV1JsYm5ScFlXeHpJanA3SW5SNWNHVWlPaUp2WVhWMGFDSjlmU3dpWlhod0lqb3hOVGMwTURrek1qQTVmUS5IYUoyWksxVlZvUXJoUkZsSVBaTk01dzRtajhQVG9sT3BBbHJFRU9UY2VGSWFrYzQ1blFMd1BpUkNyUE9OQWl6blRJMTI1MEVkb01Vd1JmYVd6MUFRMEZBdi1Xc1dmb3ltTjNiaVljWlpwNEZlQXJMVzgyd3pzREZXVTlWV1VIU0h4MnpMX0k3dnZWaGxKY1BiX3R6SVJWcVJSTFRNTnp2SjJPX1hYZ0hPeG1TQXF6Q3B1UTdBVUV6QTVZdUQxWjgxZDVPcTMtNzNmMGRjenc1Nnk2cTV4blY4NnJuZ2s5M1FpYTdGR3oyRi1HY3dJbld6R0lsV2dtUXQxYk13SHltNnJ1RVVzeUxOZ09LanVObnFGaEtwOTh2V1FpaFFuVlZBdmU3bGNoUG9rWWFYMklGU0k4Z2FkT2FTZ1dyQ2FvMngySU1qQkZxMHZvaFYxQnFZbEVLYVEiLCJjbGllbnRfcGF5bG9hZCI6eyJkYXRhIjp7ImNyZWRlbnRpYWxzIjp7InNtc19waW5jb2RlIjoiMTIzNDU2In19LCJleHAiOjE1NzQwOTMyMDksImlkIjo3OTR9fSwiY3JlZGVudGlhbHMiOnsidHlwZSI6Im9hdXRoIn0sInNlc3Npb25fc2VjcmV0IjoiRTVlVk5IdmdDSDlpZjRGSkE4UGUiLCJwcmlvcmFfcGF5bWVudF9pZCI6NDQ4fSwiZXhwIjoxNzMyNDI1MjY3LCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.TmkebjE5c4Edk8yy2nHzY8F0f9AR5TKF0X6h-cG0d0V5iZwm0RN2Aeyb1KVvUY9g8-RuamQM0jauOowOfE_DTYn55nLeuGAVZO5GOCCE0Ax0wb23seNdKSx9xkCyBZ6KZYsRT_eGIYRAOL-1yqMQiE9Yq7TvEcNpl-0_fimEa-Roryg2BXylw-jrqm4iS-xJ8NGizKQpqm_k5rYz9CPUsY6NrZj4TyCyu35Yq09JD4LYTRebepfGjii92DXQOBUq5c-vfCZQVntY6ZEltHbuUycrW8vBUAclvTDhYIw7ibKGJ9JCeMjTmRCsgh9IYB_urmferemejM9YAuLRqx39Iw" \ 
 -H "Access-Token: a38cb0703965208ce622270370d5174d074385ee6f615052fb2856cde4b30c8909ea2a71fb702eb4c129aa9dd671354099c1179f3313ea3eea233a73ffc9cf91" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 305" \ 
 -X POST "https://your.connector.url/api/priora/v1/payments/confirm"

Example of request parameters

{"data":{"payment_id":"979","original_request":{"client_jwt":"Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImNyZWRlbnRpYWxzIjp7InR5cGUiOiJvYXV0aCJ9fSwiZXhwIjoxNTc0MDkzMjA5fQ.HaJ2ZK1VVoQrhRFlIPZNM5w4mj8PTolOpAlrEEOTceFIakc45nQLwPiRCrPONAiznTI1250EdoMUwRfaWz1AQ0FAv-WsWfoymN3biYcZZp4FeArLW82wzsDFWU9VWUHSHx2zL_I7vvVhlJcPb_tzIRVqRRLTMNzvJ2O_XXgHOxmSAqzCpuQ7AUEzA5YuD1Z81d5Oq3-73f0dczw56y6q5xnV86rngk93Qia7FGz2F-GcwInWzGIlWgmQt1bMwHym6ruEUsyLNgOKjuNnqFhKp98vWQihQnVVAve7lchPokYaX2IFSI8gadOaSgWrCao2x2IMjBFq0vohV1BqYlEKaQ","client_payload":{"data":{"credentials":{"sms_pincode":"123456"}},"exp":1574093209,"id":794}},"credentials":{"type":"oauth"},"session_secret":"E5eVNHvgCH9if4FJA8Pe","priora_payment_id":448},"exp":1574093209}
Request

POST https://your.connector.url/api/priora/v1/payments/confirm

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.
Consent-Id integer, optional ID of the corresponding consent object as returned by an Account Information Consent Request.
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.


Cancel

Cancel the payment that is in the process of creation, meaning it has not been confirmed yet.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InBheW1lbnRfaWQiOiI2ODEiLCJzZXNzaW9uX3NlY3JldCI6IlVUUmdIdFotZnh5SGRNaTZmQ2liIn0sImV4cCI6MTczMjQyNTI2OCwiaXNzIjoicHJpb3JhLnNhbHRlZGdlLmNvbSJ9.WRtKCszm_h1Fe3oektYqH4Sj8_P6DtdhQRkT_GzoHFIL2n-qUAfJQOWW438BPyKILsva2x9xONSOQJd7AFoFj4uW9i4oYTyTEPBx290m3PTrs3TPsVAxNMdqTd8JtF3T_R0GyYh_8XOFqntULgA3rWsavy3RLPnrbg0Y8n074ozOaZ2iR5sb9NsIbY0G3vgI0ccLTt8wNfs2mfNNPtH--7jhE1BsaOKqJsUqS7TPQwK7jMGEK4M2sZULSiycVLvVxAycvmqCYTd6gx7WWO6ip-Yg5enVfMW_Hm2WLt4XWNgobga3zNj_CYRJz6QudWOujgxRjc1vp5btEWwkjrOmRQ" \ 
 -H "Access-Token: caab3e072b3c178b01aa19b52e05a518e23b63d5330a4592f8d9378d24001f55e21476dd29a22334e37ec1396332804254bebf0190852be2ce2626eb6d82aa0f" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 311" \ 
 -X POST "https://your.connector.url/api/priora/v1/payments/cancel"

Example of request parameters

{"data":{"payment_id":"681","session_secret":"UTRgHtZ-fxyHdMi6fCib"},"exp":1574093209}
Request

POST https://your.connector.url/api/priora/v1/payments/cancel

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.
Consent-Id integer, optional ID of the corresponding consent object as returned by an Account Information Consent Request.
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.


Trusted Beneficiaries

These endpoints are responsible for processing trusted beneficiaries.

Get

Fetch all data relevant to trusted beneficiaries. Response of this action should contain a corresponding trusted beneficiary object in JSON format.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7fSwiZXhwIjoxNzMyNDI1MjY4LCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.VaJaalqPt_kKuGXHiUbRSjrWzXmgxqkSJFOjpSCrtXDhxQ2KBycv62r78dF0sK2Ncl5DPPHFdrkPFONs3eUKMpaxHnOKLcrc7tbfZ8KnTgIe3DUWEHeWsZ4pw8sc3ZEdhTEuWuQZ0Zvd3OwLIvbW9QVXa5WbEyJlcgZCVPcNQhAcXVSxWEV0S_IPcIqyGyLCj3sIe08mIsIqXqVWbJ5qLmaojJEplf47E8ApKcOtM_iM15_Ew-VRru6mgR9qJIBghWD2EVlrsZIkG9ePeEriO31_oukIJo_QLtj2aR7BqxdGxu6aRNiOUWDQpPloLmbowmu228jVRCzKb0tSfVK5Pw" \ 
 -H "Access-Token: 714f57a6cbedda63a9bd9f18d748ba108200cff058217d35621c17cf2790b9ef1487c905020c61bcb76c3bd1f4a17acd3bb18ada44ff9a3a2bd625580ce19224" \ 
 -H "Accept: application/json" \ 
 -H "Content-Type: application/json" \ 
 -H "Client-Id: 718" \ 
 -X GET "https://your.connector.url/api/priora/v1/trusted_beneficiaries"

Example of request parameters

{"data":{},"exp":1574093210}

Example of response

{"data":[{"id":"705","alias_name":"Example Name","payment_type":"PSD_AISP","identifiers":{"from_account":"*****111","to_account":"*****222","description":"*****tion"}}]}
Request

GET https://your.connector.url/api/priora/v1/trusted_beneficiaries

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.
Consent-Id integer, optional ID of the corresponding consent object as returned by an Account Information Consent Request.
Unpacked Request Authorization
data
hash, required
Wrapper for the data.
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

Fetch all data relevant to trusted beneficiaries. Response of this action should contain a corresponding trusted beneficiary object in JSON format.


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.eyJkYXRhIjp7InJlcXVlc3QiOnsibWV0aG9kIjoiZGVsZXRlIiwidXJsIjoiaHR0cHM6Ly91c2VyLndpbGwuYmUvcmVkaXJlY3RlZC9oZXJlIiwiaGVhZGVycyI6e319LCJlcnJvciI6eyJlcnJvcl9tZXNzYWdlIjoic29tZXRoaW5nIHdlbnQgd3JvbmciLCJlcnJvcl9jbGFzcyI6IkludGVybmFsUHJvdmlkZXJFcnJvciJ9fSwiZXhwIjoxNzMyNDI1MjY5LCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.afDHZDTMJEvJr1XW6y1DN1Xe__7a5219zFVD46ZGufHPQsO1SIcetTrtZL_-tCcMD9pgx9k0QyJPqmuy-tmvKTfwfz_CMild5_1a3Sitt2byv7n20f4fd2H2e7yCb49bzzADV_Y7tbU_U05fHxVVTBKTxgKyy4WfdDTY-quVo0FE3ThQR6a3lyZxWdfI2Rud7Rg7-NNyiWN3rVPgwv0y1r0hyygTOB2iTx2G8Pa66Dsx1db1FiedW1xi_g00aod-dXdAJ6Dd2SFg4Lk6XlTi9AQkGNw8XGRJd_vzKk_G8O935CNuOa7BAqlzh_eYxDX09-lw8NysgDZB_LIlMpbhCQ" \ 
 -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.
Consent-Id integer, optional ID of the corresponding consent object as returned by an Account Information Consent Request.
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.


Payments

Success

Success callback should be used when all verification procedures have passed and the payment has been carried out.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InByaW9yYV9wYXltZW50X2lkIjoxMzQsInBheW1lbnRfaWQiOiI1NTEiLCJleHRyYSI6e319LCJleHAiOjE3MzI0MjUyNjksImlzcyI6InByaW9yYS5zYWx0ZWRnZS5jb20ifQ.TtXnVzy1Vhb-eZwv5B70fjqlIQSTBisxKXRD2gRWQzEaopbAvnac6sUveD_zPpXUOj2NGvYAxwWxmLlihZbZSoi3TgFHEmdmjB43aXh0NrszbDRkhhaR-Z2R_PZufVGe6litTaJVxE6GbNQKl_KIIAm3TGpWaB7AP66u3zp6eSB6b_MCNdAlu48Y-pASRTP0VJqbsKnEXzsr4VCKtlUbIbv35qi1_RXgI-CzB-ohOcDtbM-DIIkrCuZYiuXhxSuvEeqT8c8mOP8m7BVTRpmxAK5lA2mt59r_tjrgDigweGF1h-MnlTAPxSQhqVgWKuLZNt_u4v8HXuRJhoGv0PgwKA" \ 
 -H "App-Id: KwQ2u8Nn3XKEu0xcMbAPUQ" \ 
 -H "App-Secret: bzTIvz_hEpQ-AAdw4Un4Xg" \ 
 -X POST "/api/connectors/v1/payments/success"

Example of request parameters

{"data":{"priora_payment_id":134,"payment_id":"551","extra":{}},"exp":1574093208}

Example of response

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

POST /api/connectors/v1/payments/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
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.
PaymentNotFound 404 Payment 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 called multiple times in order to request multiple steps of authorization or to send other updates to Sale Edge PSD2 Compliance session.

In case payment processing on ASPSP side requires extra time and it is not fully automated, you might use status **executing** to inform TPP about status of the payment.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7InBheW1lbnRfaWQiOiI1NTAiLCJwcmlvcmFfcGF5bWVudF9pZCI6MjI4LCJleHRyYSI6e30sImV4cGlyZXNfYXQiOiIyMDE5LTExLTE4VDE2OjA5OjQ4LjUxNFoiLCJzdGF0dXMiOiJleGVjdXRpbmcifSwiZXhwIjoxNzMyNDI1MjcwLCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.eEUpnbfk4vjPuxwTndsEtVWn63lBzhY2xZixvEuvc_eHO2qxLn_VCRLTBTOoftJFjFwnQVDqOMKu4hvJBM6-99LxHIAOQ17ffFxxqlrD2_OzZ0CWlu0RwfbVyvms77KT5MCsIMvqD08uSDC5HKtJw6aqcj8sBJrtwvm85Iq_ue0N6azXNVVZTG39khEDEuiYyHwFP_ZLgcDRWwuGyTZ_gpQAHO4ViqAtPy6_t3Ubt23_yGpz66b0n3Tm_8L8_82tPwy1jgFsbuJZ8ye6SrFDbQ4VJtQpdNvbAW12Gw-NOJvInPvIuPY_QJzB3Mg622MSvAlUXZTPmRcO3jzHBlrrjA" \ 
 -H "App-Id: zDyFXCDE217MvWKQg1-h7w" \ 
 -H "App-Secret: ri05Whlc9Nb0Rz5Y6PDFKw" \ 
 -X POST "/api/connectors/v1/payments/update"

Example of request parameters

Example of response

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

POST /api/connectors/v1/payments/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.
PaymentNotFound 404 Payment 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.eyJkYXRhIjp7InBheW1lbnRfaWQiOiIzMzkiLCJlcnJvcl9tZXNzYWdlIjoiU29tZXRoaW5nIHdlbnQgd3JvbmcuIiwiZXJyb3JfY2xhc3MiOiJJbnRlcm5hbFByb3ZpZGVyRXJyb3IiLCJleHRyYSI6e30sInByaW9yYV9wYXltZW50X2lkIjoyNDF9LCJleHAiOjE3MzI0MjUyNzAsImlzcyI6InByaW9yYS5zYWx0ZWRnZS5jb20ifQ.YSIGrCdpzc4mkXxF2N2fYS0pELQIAKEMk75ZG6bbHMt0RHmz7Ws3Wzvd960IGTND8JEaaNlTx7YSQOmHq1Z6vnhoVRMb5yvYSavdwletT9IMar-maYz8L9dMSBpH-ZdJ2Z2iUn8CT4vL1eUDfI68oeOBRtyY-aKXg5wkLdRhzzehD5zJRoJxfgi_o9F9zMEBdrp4K6dNlMW3Hl9YibiAXTHmuK3eliFM4kOhRFR4oxDxFz5ogU1axOeGQDKFViGPAoS5VObKv-hp2mJeowEKcHdv02tEGmyZs-QVRkV-_-7xjigQ-1ieYplPOlz0ZbX2dwwc6F14ljiIxO23fMIUdA" \ 
 -H "App-Id: 5qNBNdE2YhZViFumcu-RFA" \ 
 -H "App-Secret: nsI4wPpMeAyBWGYNSresIQ" \ 
 -X POST "/api/connectors/v1/payments/fail"

Example of request parameters

{"data":{"payment_id":"339","error_message":"Something went wrong.","error_class":"InternalProviderError","extra":{},"priora_payment_id":241},"exp":1574093208}

Example of response

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

POST /api/connectors/v1/payments/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.
PaymentNotFound 404 Payment 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.

Sessions

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.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiV3VSQ2p1Zlg5b1Z5eW12UFFRaV8iLCJiZW5lZmljaWFyeV9pZCI6IjQ5NCIsImlkZW50aWZpZXJzIjp7fX0sImV4cCI6MTczMjQyNTI3MSwiaXNzIjoicHJpb3JhLnNhbHRlZGdlLmNvbSJ9.pZjfkXOJQ2awz493neTSPR5c_-mMSuPU4tEwxJjjiPmh81jms_CID57rBmCKo7j6U7JIsZy9lGnC95psl-vBHIoQd0rZX17hsKivDwRK5WbXNfUOrlv7sQcDoBKPmc80-e5RY5KuI1BnWmBR51ySj00Q9C1W7XHJzeaGr19FL1O0PJcVV6gcQ3-x_-saLUwvjiNACIXiJ-MHKX_o7-88MiRPHmYv73XbEG-3VAzROihZgQTaT0p-m_i3H8tjjJqlQZ4nlHZU3AclEiy0h9Hz4JzDiMubUvV4NWqo628pDbADPpouJIAmQl7MN_49vhqFfrqORFltYSF8mPjNXuBLSg" \ 
 -H "App-Id: qjQYP-jCx-8FBsZSgNVzIw" \ 
 -H "App-Secret: -XeeN2UhtdphUGtI-FZpzg" \ 
 -X POST "/api/connectors/v1/sessions/success"

Example of request parameters

Example of response

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

POST /api/connectors/v1/sessions/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.
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.
ActionNotAllowed 406 You're not allowed to perform this action. This might be a configuration problem or parameters incompatibility.
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.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiSHMteGM4b3pBV0xrMXh0X3pUNHYiLCJzdGF0dXMiOiJyZWRpcmVjdCIsImV4dHJhIjp7InJlZGlyZWN0X3VybCI6Imh0dHBzOi8vdXNlci53aWxsLmJlL3JlZGlyZWN0ZWQvaGVyZSJ9LCJzZXNzaW9uX2V4cGlyZXNfYXQiOiIyMDIwLTAzLTA1VDE2OjQ0OjE5Ljk3N1oifSwiZXhwIjoxNzMyNDI1MjcxLCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.X6kXLSTpS8S61bXxSzwsHe6ni0U6n7bjQSUQ-ZJl_wk9zIKV8NtEbWzM5i1ztYHg62-mK9Mh5FpcI0HzcA3h5rPSTgUrssPd980Tfo2SUiR4FJJ3ARU4BAKZiTiDflemlgZgnz9Ic5O0BNqvMcyciCRtGGHcRdjQRyh6EtELICQpccFgneHP0SOi7xOjwm4fMVQL4oXMG7NEL2Gjo4v2USIesJhPkoVokk1f3mLMz5hNm32_HnAk5XCWS1jXy1vYCPySwCF-P8GxoBjhN6GXSVg4EjwxOoVo97VP7BFG4qFMxgw_690AlNcTyz4E6JMfXBzDb1X8Lf4hqhpuH2ID4g" \ 
 -H "App-Id: q5QE7Dqlpm1d5weLS5pn7w" \ 
 -H "App-Secret: y8imt1cgG8x2zmBMrF-oxw" \ 
 -X POST "/api/connectors/v1/sessions/update"

Example of request parameters

Example of response

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

POST /api/connectors/v1/sessions/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.
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.
ActionNotAllowed 406 You're not allowed to perform this action. This might be a configuration problem or parameters incompatibility.
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.eyJkYXRhIjp7InNlc3Npb25fc2VjcmV0IjoiM1BRaXB1RFBvV3BhMTFGY1ZFVjYiLCJlcnJvcl9jbGFzcyI6IkludGVybmFsUHJvdmlkZXJFcnJvciIsImVycm9yX21lc3NhZ2UiOiJJbnRlcm5hbCBlcnJvciIsImV4dHJhIjp7fX0sImV4cCI6MTczMjQyNTI3MSwiaXNzIjoicHJpb3JhLnNhbHRlZGdlLmNvbSJ9.IzmyPJt5wIzAv0b9Aky8jt5K6T3M743rko1GzD50PvJk2HhQ8IOUMkyshMKbY9H_JysGkGKaVLvwkKgpOZd78vk4R5tEz8RYvx5SPoycqqhy8FDVcEAKBL9-GmlzItI6k9xRaMARFL1trVKZZl2gyLHRESbWud_MNsZZq2GpgilU76v7b1SuIDMjGdQrLm99Dd3EZNxmcSnBI3bUS7fiSoXcgLKWG07o8S03YhUmA7jHTY4b-u_pssMEQAC6-TGWMT__h21iVfWNcymDtRJ4_uRJcA8so_RCc_bFJDF9d9vzQx7mWcVbKLu7uIswhfcB27_qMG-gLXZlA9w58qwi8A" \ 
 -H "App-Id: xU7SyhPrd95GAPSMNo_XMQ" \ 
 -H "App-Secret: BVSkESo7zpRdzk_hWUUwCQ" \ 
 -X POST "/api/connectors/v1/sessions/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

POST /api/connectors/v1/sessions/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.
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.
ActionNotAllowed 406 You're not allowed to perform this action. This might be a configuration problem or parameters incompatibility.
ProviderDisabled 406 Cooperation with specified Provider is impossible.

Clients

Info

All requests that are forwarded by Salt Edge PSD2 Compliance Solution are signed by TPP applications. Provider can decide whether to decode the original request by itself or use decoded payload by Salt Edge PSD2 Compliance Solution which is stored in client_payload key. In order to decode the client_jwt, Connector has to perform the following request to obtain TPP's public key. The client_id is present in Client-Id header along with Authorization header.

CURL

curl -i  \ 
 -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9.eyJkYXRhIjp7ImNsaWVudF9pZCI6NTE3fSwiZXhwIjoxNzMyNDI1MjcyLCJpc3MiOiJwcmlvcmEuc2FsdGVkZ2UuY29tIn0.IEGkU-niiAixZtVwCCp2XeKmqIpK4_8ueRTNnGR1jzX-e7LRtA8sNITYJOXW8uDu-Yt-Rdb4joB24ibvsHa6vUoj0wYKHf0gl5NQ2Gdc1Q0VsijLQgH6_MaGR60gQubRnRPlYDJQcOvmzwpgREzbt7VV81F2kuUivvDp3ImGV-v3EjpFMND80h_EU7kYNV3q2tJlb7UDhKQTql-RjxycZTZjyxofCp3U4HC3F8iYYd10U0otLD7BPyfSbtxS12rFOtUYdGy-OAowSL2WDWhiNLQyxI5movF6ynUoxsZWabkxaghVmcQ6_MG4B-J-j4iRm7DP4KCOI9LVIA2dZra4ew" \ 
 -H "App-Id: hAnmNmGFFBN3W_jNWJd_fQ" \ 
 -H "App-Secret: h6rzA_lw2wVuCpDaBKlxAA" \ 
 -X GET "/api/connectors/v1/clients/info"

Example of request parameters

{"data":{"client_id":517},"exp":1574093208}

Example of response

{"data":{"name":"Fentury","scopes":["accounts","transactions","kyc"],"public_key":"-----BEGIN PUBLIC KEY-----\nMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe4eCZ0\nFPqri0cb2JZfXJ/DgYSF6vUpwmJG8wVQZKjeGcjDOL5UlsuusFncCzWBQ7RKNUSesmQRMSGkVb1/\n3j+skZ6UtW+5u09lHNsj6tQ51s1SPrCBkedbNf0Tp0GbMJDyR4e9T04ZZwIDAQAB\n-----END PUBLIC KEY-----"},"meta":{"time":"2019-11-18T16:04:48.271Z"}}
Request

GET /api/connectors/v1/clients/info

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.


Related Errors
Class Code Description
ConfigurationError 400 Missing configurations in dashboard.
AuthorizationMissing 401 Authorization header is missing.
ProviderNotFound 404 Provider specified in request does not exist or cannot be retrieved.
ProviderDisabled 406 Cooperation with specified Provider is impossible.