> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Reference

> Configuration properties, operations, events, and error mapping for the Tietoevry connectors.

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](https://agenticbanking.backbase.io/connectors/card-management/tietoevry/get-started.md).

| Connector | Property file | Purpose |
| :- | :- | :- |
| `gc-tieto-evry-device-administration-connector` | `device-administration-v2.values.yaml` | Card search, activation, lock, unlock, and PIN or CVV retrieval |
| `gc-tieto-evry-card-authorization-connector` | `card-authorization-v1.values.yaml` | Wallet eligibility and push provisioning to Apple Pay and Google Pay |
| `gc-tieto-evry-card-ecommerce-gateway-webhooks-connector` | `card-ecommerce-gateway-webhooks-v1.values.yaml` | 3D Secure authentication challenge and completion |

## 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.

| Property | Description |
| :- | :- |
| `tietoevry.baseUrl` | Base URL of the Tietoevry environment. |
| `tietoevry.client.clientname` | Identifier of the source sending the request. |
| `tietoevry.dataownerorgid` | Data owner institution ID that owns the requested data. |
| `tietoevry.origin` | Request origin (Open Banking third party, PSD2 third party, or internal bank use). |
| `tietoevry.userorgid` | Institution that the user belongs to. |

### Common properties

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

| Property | Description | Default |
| :- | :- | :- |
| `tietoevry.user.ipaddress` | Client IP or DNS address of the device sending the request. | N/A (set per pod) |
| `errorTemplate` | Error mapping template file used to translate Tietoevry errors. | `transform-tieto-evry-error-details.json` |
| `gc.http.connectTimeout` | HTTP connect timeout, in milliseconds. | `60000` |
| `gc.http.responseTimeout` | HTTP response timeout, in milliseconds. | `60000` |
| `gc.http.soTimeout` | HTTP socket timeout, in milliseconds. | `60000` |
| `retryStatuses` | HTTP status codes that trigger a retry. | `429,500,502,503,504` |
| `retryFlag` | Enable automatic request retries on connection failure. | `false` |
| `redelivery.maximumRetries` | Maximum number of redelivery attempts. | `3` |
| `redelivery.delay` | Initial delay between redelivery attempts, in milliseconds. | `200` |
| `redelivery.backOffMultiplier` | Backoff multiplier for redelivery attempts. | `2` |

### gc-tieto-evry-device-administration-connector

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

| Property | Description | Default |
| :- | :- | :- |
| `tietoevry.sourceApplication` | Source app sending the request. | N/A (environment-specific) |
| `tietoevry.orgunit` | Organization unit identifier included in Tietoevry SOAP requests. | N/A (environment-specific) |
| `tietoevry.orgid` | Organization identifier included in Tietoevry SOAP requests. | N/A (environment-specific) |
| `tietoevry.instId` | Institution identifier included in Tietoevry SOAP requests. | N/A (environment-specific) |
| `api.cardSearch.pageSize` | Page size for card search results. | N/A (environment-specific) |
| `api.cardblock.blockType` | Block type applied when locking a card. | N/A (environment-specific) |
| `api.cardblock.blockCode` | Block code applied when locking a card. | N/A (environment-specific) |
| `api.cardblock.regionCodes` | Region codes applied when locking a card. | N/A (environment-specific) |
| `api.cardblock.zeroBlock` | Zero-block flag applied when locking a card. | N/A (environment-specific) |
| `api.cardunblock.blockType` | Block type cleared when unlocking a card. | N/A (environment-specific) |
| `api.cardunblock.blockCode` | Block code cleared when unlocking a card. | N/A (environment-specific) |
| `api.cardunblock.regionCodes` | Region codes cleared when unlocking a card. | N/A (environment-specific) |
| `api.cardunblock.zeroBlock` | Zero-block flag cleared when unlocking a card. | N/A (environment-specific) |

### gc-tieto-evry-card-authorization-connector

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

| Property | Description | Default |
| :- | :- | :- |
| `api.path.cardAuth.basePath` | Base path for card authorization requests. | N/A (environment-specific) |
| `api.path.walletEligibility.byPartyId` | API path for wallet eligibility lookup by party ID. | N/A (environment-specific) |
| `api.path.walletEligibility.byCardId` | API path for wallet eligibility lookup by card ID. | N/A (environment-specific) |
| `api.path.addCardToGooglePayWallet` | API path to add a card to a Google Pay wallet. | N/A (environment-specific) |
| `api.path.addCardToApplePayWallet` | API path to add a card to an Apple Pay wallet. | N/A (environment-specific) |
| `api.path.provisioningDataSegment` | API path for the provisioning data segment. | N/A (environment-specific) |
| `api.googlePay.provisioningData.format` | Format of the Google Pay provisioning data. | N/A (environment-specific) |
| `api.googlePay.cardAppId` | Visa VTS identifier sent as the `cardAppId` query parameter on Google Pay (Android) push-provisioning requests. | `com-evry-android-cardcompanion-wb` |

### 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.

| Property | Description | Default |
| :- | :- | :- |
| `ebp.baseurl` | Base URL of the EBP upstream system. | N/A (environment-specific) |
| `ebp.challenge.endpoint` | Relative path of the 3DS authentication challenge endpoint. | N/A (environment-specific) |
| `ebp.completion.endpoint` | Relative path of the 3DS authentication completion endpoint. | N/A (environment-specific) |
| `retryFlag` | Enable automatic request retries on connection failure. | `true` |

## SOPS secrets

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

| Variable | Description | Environmental Key |
| :- | :- | :- |
| `signature.keyId` | Key ID for the RSA signing key. | `X-SIGNATURE-KEYID` |
| `signature.privateKeyPem` | RSA private key (PEM) used to sign outbound requests. | `X-SIGNATURE-PRIVATE-KEY-PEM` |

## 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](https://agenticbanking.backbase.io/connectors/card-management/tietoevry/overview.md). For the full contract, see the [API playground](https://agenticbanking.backbase.io/banking-os-apis/api-playground.md).

## 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.

| Source | Route mapping property |
| :- | :- |
| Tietoevry 3DS authentication challenge webhook | `ebp.challenge.endpoint` |
| Tietoevry 3DS authentication completion webhook | `ebp.completion.endpoint` |

## 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](https://agenticbanking.backbase.io/banking-os-apis/error-codes.md).

## 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).