Skip to main content
The Tietoevry integration manages the card lifecycle and digital wallet provisioning through the Tietoevry Card Management System (CMS). It is delivered as three connectors: the device administration connector (card search, activation, lock, unlock, and PIN or CVV retrieval), the card authorization connector (wallet eligibility and push provisioning to Apple Pay and Google Pay), and the card e-commerce gateway webhooks connector (3D Secure authentication). For the environment details you send to Backbase, see Get started.

Configuration properties

Values to obtain from Tietoevry

Obtain the following values from Tietoevry and send them to your Backbase support team. Backbase sets them in values.yaml. These values are environment-specific, so they have no default. The connectors also authenticate with an RSA signing key from Tietoevry, stored in the tietoevry-secret SOPS secret.

Common properties

Set these properties in values.yaml. They apply to the device administration and card authorization connectors.

gc-tieto-evry-device-administration-connector

Set these properties in device-administration-v2.values.yaml, in addition to the common properties.

gc-tieto-evry-card-authorization-connector

Set these properties in card-authorization-v1.values.yaml, in addition to the common properties.

gc-tieto-evry-card-ecommerce-gateway-webhooks-connector

Set these properties in card-ecommerce-gateway-webhooks-v1.values.yaml. This connector doesn’t require the common properties.

SOPS secrets

The device administration and card authorization connectors read the HTTP signing material from the tietoevry-secret SOPS secret.

Supported operations

The Tietoevry connectors expose the Banking OS Unified API for card lifecycle, wallet provisioning, and 3DS authentication. For the operation-to-endpoint table, see Overview. For the full contract, see the API playground.

Events

Of the three connectors, only the card e-commerce gateway webhooks connector has an event-driven integration. The other two are synchronous.

gc-tieto-evry-device-administration-connector

This connector is synchronous and doesn’t publish or consume events.

gc-tieto-evry-card-authorization-connector

This connector is synchronous and doesn’t publish or consume events.

gc-tieto-evry-card-ecommerce-gateway-webhooks-connector

This connector doesn’t publish events to the Sync Hub ASB producer. It consumes inbound 3D Secure authentication webhooks from Tietoevry at its registered callback URL and forwards the challenge and completion requests to the EBP endpoints.

Error mapping

The connectors map Tietoevry error codes to Banking OS status codes using the shared transform-tieto-evry-error-details.json template. For the full list, see Error codes.

Dependencies

  • Tietoevry Card Management System API (outbound), reachable at tietoevry.baseUrl.
  • EBP upstream system (outbound), reachable at ebp.baseurl, for 3DS challenge and completion.
  • Tietoevry 3DS authentication webhooks (inbound), delivered to the registered callback URL.
  • tieto-evry-connector-sdk (shared HTTP configuration, request signing, and Tietoevry error code mapping).