Skip to main content

​
Scopes

  • Account Information 🔒
  • Payment Initiation 🔒

​
Supported ASPSPs

ASPSPLinkSupportedInstitution ID
DSK Bulgaria and its Sandboxhttps://developer.dskbank.bg/TPP-JourneyYesdsk_bg
dsk_bg-sandbox

​
Registration Process

DSK Bank does not support dynamic registration. Manual registration is supported for any of the above institutions.

​
Accounts and Payments Supported

​
Accounts

  • Accounts
  • Balance
  • Transactions

​
Payments

  • Domestic Payments
  • Domestic EEA Payments
  • International Payments

​
Onboarding ASPSP’s to Yapily Application

​
LIVE & SANDBOX:

Precondition: To connect to Live and Sandbox DSK supported ASPSP, whether you are accessing account information or initiating payments, your business must have the right permission to access the resource. You need valid eiDAS certificates to connect. Please refer to the respective ASPSPs link given above for more details. Below steps need to be performed for registration until our Dashboard is integrated with V2 . Pre-requisites:
  • eiDAS certificates
Steps Required for registration
  1. Upload the signing and transport certificates into V2 services
You will need to register your signing (QSEAL) and transport keys (QWAC). For each of them, use the following API: Request 
curl --location --request POST 'https://api.yapily.com/certificates/keys/' \
--header 'Authorization: Basic YOUR_APPLICATION_CREDENTIALS_AS_BASIC_AUTH' \
--header 'Content-Type: application/json' \
--data-raw '{
   "pem": "$YOUR_PUBLIC_KEY_AS_PEM",
   "key": "$YOUR_PRIVATE_KEY"
}'
Response 
{
   "id": "d16f87d3-4222-4173-b8b9-44aeccacae7d",
   "applicationId": "7e9f7ffe-11f6-46f1-bcbb-fbf786ff1f35",
   "thumbprint": "CUq0cooTXDiFh0_xlV-z3-AW-aKbE4ht0U75fol71Vg",
   "key": ...
}
Save the id and remember for which kind of key it corresponds: SIGNING_KEY_ID=d16f87d3-4222-4173-b8b9-44aeccacae7d Once you have done it for the signing key, do the same request for your transport key.
  1. For manual registration we need to provide:
    • Client ID
    • Secret ID
Request 
curl --location --request POST 'https://api.yapily.com/institutions/$BANK_ID/manual/register' \
--header 'Content-Type: application/json' \
--header 'x-yapily-force-platform: P2' \
--header 'Authorization: Bearer YOUR_APPLICATION_CREDENTIALS_AS_BASIC_AUTH' \
--data-raw '{
   "signingKeyID": "$SIGNING_KEY_ID",
   "transportKeyID": "$TRANSPORT_KEY_ID",
   "apiTypes": ["AISP","PISP"],
   "clientId": "$CLIENT_ID",
   "secretId": "$SECRET_ID"
}'
Response example 
{
   "id": "a0460a91-4b4c-422a-bbe6-bebe0b92e308"
}

​
Support

If you require technical support with certificate management, please contact Support.