OpenFinance
Development Portal

Support

Get help with your integration and learn what to include in a support request.

Before you contact us

Most integration issues are resolved by one of these checks:

  • The Errors page covers the most common errors and a signing failures checklist.
  • If data calls suddenly start failing, check the consent status endpoint first — the consent may have expired or been revoked by the customer.
  • The Availability page shows the operational status of the API.
  • For sandbox setup — test credentials and the Postman collection — see the Test credentials page.

Contact support

Email compliance@saltedge.com — your email automatically opens a support ticket. You will usually receive a reply the same day, and within 2–3 business days at the latest. The same address covers both the Open Banking API and the Premium API.

Include in your report:

  • The endpoint and HTTP method of the failing call
  • The environment — the provider code you are calling
  • The X-Request-ID of the failing call
  • The timestamp of the call, in UTC
  • The full error response body
  • For certificate or signature issues, the full request log

Certificate and access issues

Registration is implicit — licensed TPPs have access by default, with no onboarding step. If your requests are rejected while you are using a valid QWAC and QSealC, email support with the full request log so the certificate validation can be traced.