Skip to main content
Follow the steps in Get started with connectors before proceeding. Tietoevry access: An active account in the Tietoevry environment. Network connectivity: Confirmed routing between Tietoevry and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment details from Tietoevry:
The device administration connector and the card authorization connector need the Tietoevry private key. Send that key to your Backbase support team through a secure channel.

​
Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and Tietoevry as described in Network connectivity.
  2. Send environment details to Backbase. Send the environment details in the table above to your Backbase support team.
For property names and defaults, see Reference.

​
Test your integration

To call the Cards Unified API, include your Banking OS subscription key in the request header. If you don’t have a key, contact your Backbase support team to request one.
Webhook integration: share the API key with Tietoevry through a secure channel so Tietoevry can call the inbound APIs.
Test the API using the Device Administration V2 Postman collection.

​
Troubleshooting

If your connector isn’t responding as expected, review the following common scenarios.
Cause: the Banking OS (GC) gateway can’t establish a handshake with the Tietoevry endpoint. This typically indicates an upstream service outage at Tietoevry or a network routing failure.Solution: verify the operational status of the Tietoevry environment with Tietoevry. If the service is operational, contact the GC Support team.
Cause: the Banking OS (GC) gateway can’t establish a handshake with the Tietoevry endpoint. This typically indicates an upstream service outage at Tietoevry or a network routing failure.Solution: verify the operational status of the Tietoevry environment with Tietoevry. If the service is operational, contact the GC Support team.

​
Cause

Request authentication failed due to an invalid or mismatched HTTP signature or digest. This can occur when one or more of the following conditions apply:
  • The RSA signature does not match the signed headers or request payload.
  • The digest value was calculated from a request body that differs (even by whitespace or encoding) from the body sent to Tietoevry.
  • One or more mandatory X-EVRY-* headers are missing, incorrectly set, or not included in the signature.
  • The keyId in the Signature header does not match the public key registered with Tietoevry.
  • The (request-target) or (created) values used during signature generation do not align with the actual request.
  • Clock skew between the client and Tietoevry systems causes the created timestamp to fall outside the accepted window.

​
Solution

  • Regenerate the HTTP signature, ensuring that:
  • All required headers (X-EVRY-*, (request-target), (created), and digest) are included and signed in the correct order.
  • The digest is computed using the exact request body bytes sent over the wire (no formatting or whitespace differences).
  • The keyId corresponds to the RSA key pair registered with Tietoevry.
  • Verify that the request body encoding is UTF-8 and that the Content-Type header is correctly set.
  • Ensure system clocks are synchronized to avoid timestamp validation issues.
  • If the issue persists, verify the encryption and signing logic with Tietoevry. Tietoevry provides or validates the expected signature and digest generation logic as part of the integration support process.
Cause: the number of incoming requests exceeds the defined threshold for your subscription tier. This 429 Too Many Requests response protects the stability of the Banking OS and core banking infrastructure.Solution: review your app’s request patterns to identify unexpected spikes. If your business requirements change and you need higher throughput, contact your Backbase support team to request an adjustment to your APIM rate limit policy.