> ## Documentation Index > Fetch the complete documentation index at: https://grandcentral.backbase.io/llms.txt > Use this file to discover all available pages before exploring further. # Get started > Complete end-to-end configuration guide for integrating with Fiserv DNA core banking platform Before you configure the Fiserv DNA Connector, make sure you have the following credentials and connectivity: * Follow the steps in [Get started](/connectors/getting-started). * **Fiserv DNA access**: An active account in the Fiserv DNA production or test environment with necessary permissions. * **Network connectivity**: Verify that your network routes traffic between the Fiserv DNA environment and Grand Central iPaaS. For supported options, see [Network connectivity](/platform/network-connectivity). * **Environment details**: You need the following environment details from Fiserv DNA to configure the connector: | Parameter | Description | | -------------------- | --------------------------------------------------- | | `fiservdna-base-url` | The API endpoint URL for the Fiserv DNA environment | | `fiservdna-host` | The hostname for Fiserv DNA services | | `device-id` | Device identifier for DirectSignOn authentication | | `user-id` | Username for DirectSignOn authentication | | `password` | Password for DirectSignOn authentication | | `app-id` | Application identifier for core API requests | ## Configuration guide Follow these steps to initialize and authorize your Fiserv DNA Connector. ### 1. Establish connectivity Share connectivity details between Grand Central and Fiserv DNA as described in [Network connectivity](/platform/network-connectivity). ### 2. Fiserv DNA authentication The Fiserv DNA Connector uses SingleSignOn (SSO) authentication for API access. This two-step authentication process generates secure tokens for all API requests. The SSO authentication process consists of two steps: DirectSignOn (to obtain an SSOTicket) and WhoIs (to validate the ticket and obtain session credentials). #### Authentication flow **Step 1: DirectSignOn Request** The connector uses `DeviceId`, `UserId`, and `Password` to generate an `SSOTicket`: ```xml theme={"system"} {device-id} {user-id} {password} PRODUCTION SAF2006 ``` The response contains an `SSOTicket` that is extracted from the `DirectSignonResult` tag. **Step 2: WhoIs Request** The connector uses the `SSOTicket` to obtain a `WhoIsResult` token with session credentials: ```xml theme={"system"} {ssoTicket} ``` The `WhoIsResult` contains authentication details including an `ExpirationDate` for token caching and a `Signature` for API requests. **Step 3: API Requests** All API requests use the `WhoIsResult`, `NetworkNodeName`, and `AppId`: ```xml theme={"system"} {app-id} SingleSignOn {network-node-name} {WhoIsResult} ``` The connector automatically manages token lifecycle, including caching and renewal based on expiration dates. To configure authentication, create a Secrets Operations (SOPS) secret. For more information, see [How to create SOPS](/platform/developer-guides/build/configure-connector). To share credentials between Fiserv DNA and Grand Central, consider using 1Password. ### 3. Environment configuration To initialize the Fiserv DNA Connector, define the required environment variables in your `gc-applications-live` repository. These variables are stored in `values.yaml` for common configuration across all connectors and in the following files for connector-specific configuration: | Connector | Property | Description | | ------------------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------ | | `gc-fiservdna-deposit-connector` | `deposit-v0.values.yaml` | Outbound deposit connector for deposit account operations | | `gc-fiservdna-deposit-transaction-connector` | `deposit-transaction-v0.values.yaml` | Outbound deposit transactions connector for transaction operations | | `gc-fiservdna-loan-connector` | `loan-v0.values.yaml` | Outbound loan connector for loan account operations | | `gc-fiservdna-loan-transaction-connector` | `loan-transaction-v0.values.yaml` | Outbound loan transactions connector for transaction operations | | `gc-fiservdna-party-connector` | `party-v0.values.yaml` | Outbound party connector for party management operations | | `gc-fiservdna-party-access-entitlement-connector` | `party-access-entitlement-v0.values.yaml` | Outbound party access entitlement connector | | `gc-fiservdna-payment-connector` | `payment-v0.values.yaml` | Outbound payment connector for payment operations | For the full property list for each connector, including defaults and descriptions, see [Reference](/connectors/core-banking/fiserv-dna/reference). ### Define common parameters These variables are stored in `values.yaml` and are used across all Fiserv DNA connectors: | Parameter | Description | Example value | | --------------------------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------- | | `fiservdna.baseUrl` | Target API endpoint for the Fiserv DNA environment. | `https://fiservdna-api.yourbank.com/Extensions/DNA.CoreApiService/CoreApiService.svc/Soap11` | | `fiservdna.host` | Hostname for Fiserv DNA services. | `fiservdna-api.yourbank.com` | | `fiservdna.appId` | Application identifier for core API requests. | `your-app-id-uuid` | | `fiservdna.networkNodeName` | Network node identifier for core API requests. | `YOUR_NODE_NAME` | | `fiservdna.cashBoxNumber` | Cash box number for payment operations. | `1001` | The following example shows the `values.yaml` configuration: ```yaml theme={"system"} # Common Fiserv DNA Configuration # Place this in: values.yaml connector: properties: # SSL/TLS Configuration cxf.client.ssl.ca.cert.path: /etc/camel/conf.d/_secrets/fiservdna-secret/tls.crt cxf.loggingFeatureEnabled: true # Fiserv DNA Connection Settings fiservdna.baseUrl: "https://fiservdna-api.yourbank.com/Extensions/DNA.CoreApiService/CoreApiService.svc/Soap11" fiservdna.host: "fiservdna-api.yourbank.com" fiservdna.appId: "your-app-id-uuid" fiservdna.networkNodeName: "YOUR_NODE_NAME" fiservdna.cashBoxNumber: 1001 # Type conversion - attributes to skip during processing typeConversion.skipAttributes: address,addressLine,birthDate,buildingNumber,country,countryCode,countryIsoCode,countrySubDivision,demographics,driversLicenseNumber,education,educationLevel,electronicAddress,emails,employer,employerIdentificationNumber,employment,establishmentDate,expiryDate,familyName,firstName,identificationNumber,identificationType,issueDate,issuingCountry,key,legalStructure,memberNumber,middleName,name,nationalIdentityNumber,number,occupation,organisationIdentifications,organisationName,partyId,partyPartyRelationships,partyRole,partyType,passportNumber,personIdentification,personName,phoneAddresses,postalAddresses,postalCode,preferredLanguage,roleEndDate,roleStartDate,sector,status,streetName,subDepartment,subType,taxIdentificationNumber,townName,type,yearOfPassing,id,depositId,accountId,checkSerialNumber,branchId,loanId # Namespace URIs for SOAP messages # namespaceURI.MajorAccountType: http://schemas.datacontract.org/2004/07/OpenSolutions.CoreApiService.Services.Messages # namespaceURI.MinorAccountType: http://schemas.datacontract.org/2004/07/OpenSolutions.CoreApiService.Services.Messages # Mapping field configuration # mappingField.MajorAccountType: MajorAccountTypeCode # mappingField.MinorAccountType: MinorAccountTypeCode # Account Type Mappings - Single field replacement # fieldsToBeReplaced: MajorAccountType,MinorAccountType # MajorAccountTypeCode.: # MinorAccountTypeCode.: # Account Type Mappings - Combined field replacement # fieldsToBeReplaced: MajorAccountType@MinorAccountType # MajorAccountTypeCode.@MinorAccountTypeCode.: @ # Party name search configuration # For partyName search with partyType PERSON, partyName format is: # Default partyNameDelimiter is SPACE (" "). Configure a custom delimiter: # partyNameDelimiter: # Product type categories # deposit.productTypes: ,,... # loan.productTypes: ,,... # Account role codes # fiserv.accountRoleCodes: ,,... traits: knativeservice: minScale: 0 logging: level: INFO pdb: enabled: false ``` **Account type mapping patterns:** | Pattern | Description | | ----------------------------------------------------------- | ------------------------------------------------- | | `MajorAccountTypeCode.` | Single field mapping for major account type | | `MinorAccountTypeCode.` | Single field mapping for minor account type | | `MajorAccountTypeCode.@MinorAccountTypeCode.` | Combined mapping for both major and minor types | | `@` | Grand Central product ID and secondary product ID | Configure the account type mappings based on your Fiserv DNA environment's product configuration. Contact your Fiserv DNA administrator to obtain the full list of MajorAccountTypeCode and MinorAccountTypeCode values. Place the values files at the following paths: ```text theme={"system"} iPaaS/azure/runtimes/{runtime}/values/gc-fiservdna/ ├── values.yaml ├── deposit-v0.values.yaml ├── deposit-transaction-v0.values.yaml ├── loan-v0.values.yaml ├── loan-transaction-v0.values.yaml ├── party-v0.values.yaml ├── party-access-entitlement-v0.values.yaml └── payment-v0.values.yaml ``` ### Define deposit connector parameters The `deposit-v0.values.yaml` file contains configuration for deposit account operations. ```yaml theme={"system"} connector: properties: # Bank organization number # fiserv.bankOrgNumber: traits: knativeservice: minScale: 0 logging: level: INFO ``` ### Define deposit-transaction connector parameters The `deposit-transaction-v0.values.yaml` file contains configuration for deposit transaction operations including transaction type mappings. ```yaml theme={"system"} connector: properties: # Transaction type mappings # fieldsToBeReplaced: type # type.: traits: knativeservice: minScale: 0 logging: level: INFO ``` ### Define loan connector parameters The `loan-v0.values.yaml` file contains configuration for loan account operations. ```yaml theme={"system"} connector: properties: # Bank organization number # fiserv.bankOrgNumber: traits: knativeservice: minScale: 0 logging: level: INFO ``` ### Define loan-transaction connector parameters The `loan-transaction-v0.values.yaml` file contains configuration for loan transaction operations including transaction type mappings. ```yaml theme={"system"} connector: properties: # Transaction type mappings # fieldsToBeReplaced: type # type.: traits: knativeservice: minScale: 0 logging: level: INFO ``` ### Define party connector parameters The `party-v0.values.yaml` file contains configuration for party management operations. ```yaml theme={"system"} connector: customLabels: camel.apache.org/integration: "party-v0" properties: # Product Config for getAccountsByPartyId # deposit.productTypes: ,,... # loan.productTypes: ,,... # fiserv.accountRoleCodes: ,,... traits: knativeservice: minScale: 0 autoscalingTarget: 100 logging: level: INFO ``` ### Define party-access-entitlement connector parameters The `party-access-entitlement-v0.values.yaml` file contains configuration for party access entitlement operations. ```yaml theme={"system"} connector: traits: knativeservice: minScale: 0 logging: level: INFO ``` ### Define payment connector parameters The `payment-v0.values.yaml` file contains configuration for payment operations. ```yaml theme={"system"} connector: traits: knativeservice: minScale: 0 logging: level: INFO ``` ## Testing your integration To access the Unified API, include your Grand Central subscription key in the request header. If you don't have a key, contact the Grand Central Support Team to request one. | Header | Value | | --------- | ------------------------- | | `api-key` | `` | Test the API using the Postman collection. ## Troubleshooting If your connector isn't responding as expected, check these common scenarios. **Cause:** The Grand Central gateway cannot establish a handshake with the Fiserv DNA endpoint. This typically indicates an upstream service outage at Fiserv or a network routing failure. **Solution:** Verify the operational status of the Fiserv DNA environment. Check the Fiserv status page or contact Fiserv support. If the service is operational, contact [Grand Central Support](mailto:support@grandcentral.io). **Cause:** The request to Fiserv DNA exceeded the configured timeout period. This may indicate performance issues at Fiserv or network latency problems. **Solution:** Verify the operational status of the Fiserv DNA environment and check for any performance degradation. If the service is operational and performing normally, contact [Grand Central Support](mailto:support@grandcentral.io). **Cause:** The DirectSignOn credentials provided during setup are incorrect, expired, or the user lacks the required permissions in Fiserv DNA. **Solution:** Re-verify your credentials with your Fiserv DNA administrator and ensure the user has the required permissions. Contact the Grand Central team to update the connection credentials if needed. **Cause:** The SSOTicket or WhoIsResult token has expired based on the ExpirationDate field. **Solution:** The connector automatically refreshes tokens. If you continue to see errors, verify that the system clock is synchronized and contact [Grand Central Support](mailto:support@grandcentral.io). **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 Grand Central and Fiserv DNA infrastructure. **Solution:** Review your app's request patterns to identify unexpected spikes. If you need higher throughput, contact the Grand Central Team to request a higher rate limit. *** ## Need more help? Contact the Grand Central team for help with environment setup or rate limit increases.