.png)
Fiserv DNA Integration Guide
Fiserv DNA integrates with enterprise systems through deployment-specific APIs, authenticated data access, scheduled synchronization, and selected documented callbacks.
Fiserv DNA integration options at a glance
Fiserv DNA integration is normally based on the API definition and environment supplied for a financial institution. Fiserv provides API-based integration capabilities through its developer ecosystem, while the available DNA resources, operations, authentication model, and event coverage can vary by deployment and contract. Martini can consume documented DNA REST endpoints, and can consume SOAP services when a supported WSDL is provided. Where callbacks or webhook-style notifications are documented, Martini can receive them; otherwise scheduled workflows can retrieve Customers, Accounts, Deposits, Loans, and Transactions incrementally. Martini also exposes controlled APIs, transforms payloads, applies business rules, and stores credentials securely.
| Integration point | Supported by Fiserv DNA? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Limited | Fiserv provides API-based integration capabilities, but DNA resources, operations, versions, and availability depend on the institution's environment and contract. | Martini can consume documented DNA REST endpoints, generate reusable integration assets from supplied API definitions, transform payloads, and orchestrate downstream workflows. |
| SOAP APIs | Not confirmed | Some legacy or institution-specific Fiserv integrations may use SOAP, but a current generally available DNA SOAP interface was not verified. | Martini can consume a supported DNA SOAP service when the customer supplies a valid WSDL and service contract. |
| Webhooks / outbound callbacks | Not confirmed | Event notifications may be available for selected products, deployments, or events, but comprehensive DNA coverage was not verified. | Martini can receive documented callbacks or webhook-style notifications and invoke workflows after validating the notification. |
| Bulk / async / batch APIs | Not confirmed | No universal DNA bulk or asynchronous API was verified; institution-specific batch resources or export services may exist. | Martini can orchestrate bounded batch workflows when a documented service or file contract is supplied. |
| File / attachment APIs | Not confirmed | No general DNA file, statement, or attachment API was verified from public sources. | Martini can process an approved file exchange when Fiserv and the institution provide a supported interface and format. |
| Authentication | Limited | Fiserv's developer ecosystem supports authenticated API access, but DNA requirements may include OAuth-style credentials, API credentials, certificates, scopes, or network controls. | Martini stores secrets and certificates in secure configuration and applies environment-specific authentication to API calls. |
| Scheduled synchronization | Yes | Scheduled incremental retrieval can support synchronization when outbound event delivery is unavailable, using documented timestamps, sequence numbers, transaction dates, or other watermarks. | Martini scheduler-triggered workflows retrieve pages, persist checkpoints, deduplicate results, and retry transient failures. |
| Database access | No | Direct DNA database access should not be assumed because it can create consistency, supportability, security, and upgrade risks. | Martini should use documented Fiserv APIs or approved integration services rather than direct database reads. |
How Fiserv DNA exposes data and business events
Fiserv DNA REST APIs
Fiserv provides API-based integration capabilities through its developer ecosystem. DNA-specific resources, operations, versions, and permissions must be confirmed from the institution's contracted API definition and environment.
Martini implementation pattern
Martini implementation pattern: Martini authenticates to the documented DNA REST API, retrieves or submits the required resource, transforms the response, applies validation and business rules, and routes the result to downstream systems or an exposed Martini API.
Implementation sequence
Fiserv DNA callbacks or webhook-style notifications
Comprehensive webhook coverage was not verified for DNA. Some deployments or services may provide callbacks for selected events, but Customer, Account, Loan, or Transaction changes should not be assumed to generate notifications.
Martini implementation pattern
Martini implementation pattern: when a documented callback exists, Martini receives and authenticates the notification, validates its event type, retrieves authoritative DNA data when necessary, and starts downstream processing. Unsupported events use scheduled synchronization instead.
Implementation sequence
Scheduled Fiserv DNA synchronization
Scheduled incremental synchronization is a practical fallback when outbound events are unavailable. The implementation should use a documented change timestamp, sequence number, transaction date, or other reliable watermark.
Martini implementation pattern
Martini implementation pattern: a scheduler-triggered workflow retrieves bounded pages of changed DNA objects, handles records updated during extraction, deduplicates by stable identifiers, writes approved targets, and stores a checkpoint for the next run.
Implementation sequence
Common Fiserv DNA integration patterns
Pattern 1: Synchronize customers and accounts to a CRM
When to use this pattern
Use this pattern when customer-service or engagement users need current DNA context without direct access to the core banking platform. The workflow should retrieve only changed data and preserve Fiserv DNA as the authoritative source for core financial information.
Integration direction
Example Mapping
| Fiserv DNA Field | Canonical Field | Target Field |
|---|---|---|
| Customer.customerId | customer.externalId | Salesforce Account or Contact external ID |
| Customer.name | customer.displayName | Salesforce Contact name |
| Account.accountId | account.externalId | Salesforce Account core account ID |
| Account.status | account.status | Salesforce account status |
Martini implementation pattern
A scheduled Martini workflow queries documented DNA resources using a change watermark, maps Customers, Accounts, and Deposits into a canonical model, filters sensitive fields, and upserts Salesforce records. Stable identifiers and deterministic idempotency keys prevent duplicates; transient failures are retried and rejected records are routed for review.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Orchestrate loan applications and servicing requests
When to use this pattern
Use this pattern when a digital lending or servicing application needs a controlled way to submit requests to DNA or retrieve Loan status. It separates external application contracts from institution-specific DNA payloads and permissions.
Integration direction
Example Mapping
| Fiserv DNA Field | Canonical Field | Target Field |
|---|---|---|
| application.applicantId | customer.externalId | DNA Customer identifier |
| application.loanAmount | loan.requestedAmount | DNA Loan amount |
| application.productCode | loan.productType | DNA Loan product code |
| request.correlationId | operation.correlationId | DNA request or audit reference |
Martini implementation pattern
Martini exposes an authenticated API, validates the incoming request, applies institution-specific eligibility and field rules, maps it to the documented DNA operation, and returns a normalized result. Timeouts are not treated as definite failures; the workflow checks operation status before retrying financial or servicing commands.
Martini capabilities used
- API exposure
- API consumption
- data mapping
- business rules
- authentication
- error handling
Pattern 3: Deliver balances and transactions to approved applications
When to use this pattern
Use this pattern when reporting, fraud, notification, or digital applications require approved balance and transaction data without direct core access. The workflow should enforce scope, consent, filtering, and reconciliation controls.
Integration direction
Example Mapping
| Fiserv DNA Field | Canonical Field | Target Field |
|---|---|---|
| Account.accountId | account.externalId | Plaid account ID or approved intermediary ID |
| Account.balance | balance.available | available balance |
| Transaction.transactionId | transaction.externalId | transaction ID |
| Transaction.postedDate | transaction.date | transaction date |
Martini implementation pattern
Martini retrieves paginated Accounts and Transactions through documented DNA endpoints, applies authorization and data-minimization rules, normalizes dates and amounts, and publishes the approved result. Overlap windows and stable transaction identifiers support deduplication, while totals and counts are reconciled before completion.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- JSON handling
- validation
- reconciliation
Pattern 4: Process selected DNA servicing events
When to use this pattern
Use this pattern only when the institution's DNA implementation documents outbound callbacks or event notifications for the required business events. It provides near-real-time processing while recognizing that coverage is not universal.
Integration direction
Example Mapping
| Fiserv DNA Field | Canonical Field | Target Field |
|---|---|---|
| event.eventType | servicing.eventType | ServiceNow category |
| event.resourceId | servicing.resourceId | ServiceNow correlation reference |
| event.occurredAt | servicing.occurredAt | ServiceNow opened or activity time |
| event.status | servicing.status | ServiceNow state |
Martini implementation pattern
Martini receives the documented callback, validates credentials or signatures, applies event-level idempotency, retrieves authoritative Customer, Account, Loan, or Transaction data when necessary, and creates or updates a ServiceNow workflow. Failed notifications are retried according to policy and reconciled through scheduled checks.
Martini capabilities used
- webhook consumption
- workflows
- API consumption
- business rules
- idempotency
- error handling
Applications commonly integrated with Fiserv DNA
Fiserv DNA commonly participates in financial-services application architectures that keep core banking data authoritative while making approved information and servicing operations available to adjacent platforms. The following are practical integration targets; each institution should confirm the specific interface, data-sharing agreement, and supported use case.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize customer, household, account-relationship, and selected financial-status information for customer service and engagement workflows. | Fiserv DNA → Martini → Salesforce | A scheduled Martini workflow retrieves changed Customers, Accounts, and Deposits, normalizes identifiers, applies data-minimization rules, and upserts Salesforce records with idempotency controls. |
| Microsoft Dynamics 365 | Give service users approved customer, account, and loan context while retaining Fiserv DNA as the source of core financial data. | Fiserv DNA → Martini → Microsoft Dynamics 365 | Martini exposes a controlled API for Dynamics 365 requests and runs outbound synchronization workflows that map DNA objects to the approved customer-service model. |
| ServiceNow | Create operational workflows for account-service issues, integration exceptions, incidents, and approved servicing requests. | Fiserv DNA → Martini → ServiceNow | Martini translates selected DNA status changes or workflow failures into ServiceNow records and routes approved actions back through validation and DNA API orchestration. |
| Workday | Support approved payroll, employee, or organizational financial data exchanges where the institution has a defined banking-related use case. | Workday → Martini → Fiserv DNA | Martini validates Workday-originated requests, maps them to the institution's DNA contract when supported, and records correlation identifiers and business outcomes. |
| Fiserv Output Solutions | Exchange statement, notice, and customer-communication data associated with core banking activity where product-specific interfaces are available. | Fiserv DNA → Martini → Fiserv Output Solutions | Martini retrieves approved DNA data, transforms it into the contracted Output Solutions payload, and separates retryable transport failures from content or validation errors. |
| nCino | Coordinate lending and account-opening processes with core Customer, Deposit, and Loan information. | nCino → Martini → Fiserv DNA | A Martini API receives lending or servicing requests, validates required fields, maps them to the documented DNA operation, and returns a normalized response to nCino. |
| Plaid | Provide approved account or balance information to digital financial applications where authorization and data-sharing arrangements permit it. | Fiserv DNA → Martini → Plaid | Martini retrieves only authorized account data, applies institution-specific filtering and consent rules, and publishes a controlled response or intermediary payload. |
How to build a Fiserv DNA integration in Martini
Objective
Establish access to the institution's specific DNA environment and confirm the supported API contract, base URL, version, resources, and network requirements.
Instructions in Martini
- Obtain the contracted DNA API definition, OpenAPI document, WSDL, or integration guide.
- Configure environment-specific endpoints and network controls.
- Store credentials, tokens, certificates, and private keys in secure Martini configuration.
Objective
Apply the authentication and authorization model required by the DNA deployment without embedding secrets in workflow logic.
Instructions in Martini
- Confirm OAuth-style credentials, API credentials, certificates, scopes, and token behavior.
- Use least-privilege permissions for the required Customers, Accounts, Deposits, Loans, and Transactions.
- Test token refresh, certificate rotation, and access to non-production resources.
Objective
Select the appropriate execution model based on the confirmed DNA capabilities and business latency requirements.
Instructions in Martini
- Use a scheduler for incremental synchronization when events are unavailable.
- Receive a documented callback only for events explicitly supported by the deployment.
- Expose a Martini API when a downstream application needs controlled request-response access.
Objective
Read or submit DNA data using bounded, observable workflow operations that respect pagination and financial correctness.
Instructions in Martini
- Retrieve the required resource using documented filters and pagination.
- Persist a durable timestamp, sequence number, cursor, or other approved watermark.
- Do not blindly retry a timed-out financial or servicing command before checking its outcome.
Objective
Map deployment-specific DNA payloads into stable canonical and target models while insulating downstream systems from vendor-specific changes.
Instructions in Martini
- Map actual Customer, Account, Deposit, Loan, Transaction, and relationship fields.
- Normalize identifiers, dates, amounts, statuses, and relationship direction.
- Preserve correlation identifiers and retain unknown fields where appropriate.
Objective
Enforce authorization, validation, data-minimization, reconciliation, and institution-specific business rules before writing or responding.
Instructions in Martini
- Validate required fields and enumerations before sending requests.
- Filter personal, account, balance, and transaction data according to approved access policies.
- Apply deterministic idempotency keys and separate retryable failures from validation failures.
Common Fiserv DNA data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Customer | Synchronize person or organization identity, profile, and relationship information. | Salesforce, Microsoft Dynamics 365, nCino, reporting platforms | Martini retrieves the documented Customer representation, validates identifiers, removes non-required sensitive fields, and maps it to a canonical customer model. |
| Account | Provide account identity, status, ownership, and relationship context. | Salesforce, Microsoft Dynamics 365, Plaid, reporting platforms | Martini maps stable account identifiers and status values, applies authorization rules, and supports incremental retrieval with a durable watermark. |
| Deposit | Represent checking, savings, and other deposit-product data. | Salesforce, nCino, Fiserv Output Solutions, reporting platforms | Martini transforms product-specific fields into approved downstream models and prevents duplicate updates through deterministic keys. |
| Loan | Exchange loan balances, terms, status, and servicing information. | nCino, Microsoft Dynamics 365, Salesforce, ServiceNow | Martini validates loan operations, applies business rules, and treats financial commands differently from read-only synchronization. |
| Transaction | Deliver posted or pending financial activity associated with an Account. | Fraud platforms, reporting systems, notification platforms, Plaid | Martini retrieves Transactions using documented pagination and watermarks, reconciles identifiers and totals, and avoids blind retries for financial operations. |
| Party or relationship | Represent Customer-to-Account, household, or related-party relationships where exposed. | Salesforce, Microsoft Dynamics 365, nCino | Martini preserves relationship direction and identifiers while mapping institution-specific relationship types to a normalized model. |
Authentication and security considerations
Deployment-specific authentication
Confirm the DNA environment's OAuth-style credentials, API credentials, scopes, token behavior, certificates, mutual TLS, network controls, and IP restrictions before implementation. Fiserv requirements can vary by product, institution, and contract.
Protect financial data
- Store secrets, tokens, certificates, and private keys in Martini secure configuration.
- Use least-privilege access to Customer, Account, Deposit, Loan, and Transaction resources.
- Encrypt transport and minimize sensitive data in logs.
- Apply institutional policies to personal identifiers, account numbers, balances, and transaction details.
Operational considerations for Fiserv DNA integrations
Throughput and pagination
Confirm quotas, concurrency limits, burst limits, maintenance windows, and pagination behavior. Use bounded concurrency, incremental filters, durable watermarks, overlap windows, and deduplication by stable DNA identifiers.
Reliability and correctness
- Use exponential backoff for transient failures and route validation failures separately.
- Do not blindly retry a timed-out financial or servicing command; first establish whether it was accepted.
- Reconcile counts, totals, transaction identifiers, and synchronization lag.
- Track correlation IDs, vendor error codes, request identifiers, and retry state without logging sensitive payloads.
- Regression-test mappings when DNA versions or institution-specific schemas change.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point calls
Martini provides a maintainable workflow layer between Fiserv DNA and downstream applications. It can consume documented APIs, expose controlled APIs, schedule incremental retrieval, map deployment-specific payloads, apply business rules, and coordinate multiple systems without giving every application direct core access.
Operational consistency
- Centralize authentication, secrets, validation, transformation, and error handling.
- Reuse workflow and mapping assets across customer, account, loan, and transaction processes.
- Support retries, reconciliation, idempotency, monitoring, and environment-specific configuration.
- Use custom logic where the institution's DNA contract requires behavior beyond standard mappings.
Frequently asked questions
Fiserv DNA is typically integrated through deployment-specific authenticated APIs. REST APIs are the preferred documented mechanism where available; SOAP, callbacks, batch services, and file exchanges must be confirmed for the institution. Scheduled incremental synchronization is an alternative when event delivery is unavailable.
Yes. Martini can consume documented Fiserv DNA REST endpoints, consume a supported SOAP service when a WSDL is supplied, receive documented callbacks, expose normalized APIs, orchestrate scheduled workflows, and transform DNA data for approved downstream systems.
No. A dedicated Fiserv DNA connector is not required. Martini can use Fiserv DNA's confirmed native APIs, authentication methods, callbacks, files, or other documented endpoints supplied for the institution's deployment.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Fiserv DNA. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Fiserv, infrastructure providers, or other third-party systems depending on subscriptions, usage, and deployment model.
Use the institution's documented DNA REST API when available and confirm its resources, versions, permissions, and authentication requirements. SOAP may be relevant for a supplied legacy or institution-specific WSDL. GraphQL was not confirmed for Fiserv DNA, and direct database access should not be assumed.
Comprehensive webhook coverage was not confirmed. Some deployments or services may provide callbacks for selected events, but universal change notification should not be assumed. Where events are unavailable, Martini can run scheduled incremental synchronization using documented watermarks.
Martini can retrieve Customers, Accounts, Deposits, Loans, or Transactions through documented API resources, follow the required pagination model, persist a timestamp or other watermark, map data to a canonical model, and write approved targets. Overlap windows, stable identifiers, and reconciliation help manage updates and duplicates.
Yes. Martini can expose a secured REST API that validates requests, applies business rules, maps normalized payloads to the DNA contract, orchestrates the DNA call, and returns a controlled response so downstream applications do not depend directly on DNA-specific payloads.
Related Martini documentation
APIs
Connect Fiserv DNA with Martini
Use Martini to design a secure, deployment-aware integration between Fiserv DNA and the applications, APIs, and workflows that support your institution.