Fiserv × HubSpot
How a bank or credit union running a Fiserv core (DNA, Premier, Signature, Cleartouch or Precision) can feed customer, product-holding and life-event signals into HubSpot for onboarding, cross-sell and relationship management, without turning HubSpot into a second core.
Does Fiserv integrate with HubSpot?
Fiserv runs the core account processing system for many banks and credit unions. The core holds every customer or member, every deposit account and loan, and the relationships between them. HubSpot is where the institution markets, onboards new customers and manages relationships.
Public documentation, but production access needs vendor approval, certification, a paid license or a specific plan.
Open with conditions. Registration in Fiserv Developer Studio and its test cores is self-serve. Production access to the institution's core comes through the institution and Fiserv.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
A Fiserv core can tell HubSpot who each customer is and what they hold, and HubSpot becomes the relationship layer without becoming a second core.
Campaign Creators assessment
Fiserv exposes its strategic cores through Communicator Open, which Fiserv describes as a normalized set of RESTful APIs designed to work across its go-forward cores. Developers register in the Banking Hub on Fiserv Developer Studio, read the documentation and test against live test cores. That makes a direct Fiserv-to-HubSpot integration buildable. Two things set the pace: production access to an institution's core is arranged through that institution and Fiserv, and the institution's compliance team decides which customer data HubSpot may hold. CC's default is data minimization: product holdings arrive as flags, counts and dates, not account numbers or balances.
Ratings are CC judgments from Fiserv's public materials. Operations available for the institution's specific core, production credentials and limits are confirmed with Fiserv during discovery.
One API design across cores
Communicator Open uses a common design across Fiserv's strategic cores, so the sync module pattern carries over whether the institution runs DNA, Premier or Signature. Coverage for the institution's core is confirmed in discovery.
Relationships, not just records
A core links people and businesses to accounts through roles such as owner, joint owner and guarantor. Matching those relationships to HubSpot contacts, companies and households needs an agreed rule, with the core customer number as the key.
Access and compliance come first
Production credentials come through the institution and Fiserv. The compliance team reviews the field list as a GLBA planning item, and approves it before any build starts.
Which Fiserv APIs does the integration use?
Seven capabilities matter to HubSpot. Four carry the integration, one enriches it, one is a scope decision, and one stays inside Fiserv.
Customers and members
Communicator Open · customer (party) dataPeople and organizations the institution serves, with contact details and the core customer number that identifies them.
- Persons become contacts, businesses become companies
- Core customer number as the match key
- Tax IDs and dates of birth never leave the integration layer
Product holdings
Communicator Open · account relationshipsWhich products each customer holds (checking, savings, certificates, consumer and mortgage loans) and their role on each account.
- Stored as yes/no flags and a product count
- Open dates for the newest product
- No account numbers or balances by default
Account and life events
Detected by the integration layerNew accounts, closures, upcoming certificate maturities, loan payoffs and address changes, turned into HubSpot events that start journeys.
- Detected by comparing scheduled reads
- Each change becomes a HubSpot timeline event
- Starts onboarding and retention workflows
Officer and branch ownership
Officer and branch codesThe officer and branch assigned to each customer in the core decide the HubSpot owner and team.
- Officer code maps to a HubSpot user
- Branch maps to a HubSpot team
- Ownership rules agreed with the institution
Digital banking signals
Fiserv digital banking (for example, Architect)Whether a customer is enrolled in online and mobile banking and in e-statements, where the institution's digital platform makes these available.
- Enrollment flags for digital adoption campaigns
- Last-login date if available
- Availability confirmed per institution
Write-back to the core
HubSpot → FiservWhere the institution's core exposes the needed write operations, HubSpot could update contact details or preferences in the core. Many institutions keep core writes inside their own systems. Decided per engagement, and confirmed in discovery.
- Off by default
- Contact preferences are the usual first candidate
- Requires the institution's operations sign-off
Balances and transactions
Account numbers, balances, transaction historyAccount numbers, balances and transaction history stay in the core. If compliance approves, HubSpot receives a derived tier rather than the number.
- No account numbers in HubSpot
- Balance tier only with written approval
- Transaction history is never copied
How does the Fiserv HubSpot integration work?
A CC-built integration layer reads from the Fiserv core through Communicator Open, works out what changed, applies the institution's minimization rules, and writes to HubSpot in batches. HubSpot owns relationship and marketing activity; the core owns accounts.
Each system owns its records
The core owns customers' accounts. HubSpot owns marketing, onboarding and relationship activity. Neither system keeps a second copy of the other's records.
Minimize by default
HubSpot receives what the team acts on: product flags, counts, dates and events. Account numbers, balances, transactions and tax IDs stay in Fiserv.
Compliance is part of the build
GLBA review is a planned project step. The institution's compliance team signs off the field list, and that list is enforced in code.
What does Fiserv HubSpot integration setup involve?
Each phase ends on a gate the institution signs off before the next begins. Read-only data comes first; any write-back is a later, separate decision.
Goals and core inventory
Confirm which Fiserv core and digital banking platform the institution runs, and which growth or onboarding decisions HubSpot should support.
Access
Register in Fiserv Developer Studio and build against the Banking Hub test environment. Arrange production credentials through the institution and Fiserv, and complete the institution's vendor security review.
Compliance and field list
Review each proposed field with compliance as a GLBA planning item. Agree what is stored as a flag, a count, a date or not at all.
HubSpot data model
Create the properties, custom events, onboarding and cross-sell pipelines, field-level permissions and property groups in a HubSpot sandbox.
Build and change detection
Build the read sync module, the change detector for account and life events, the minimization filter and an error replay queue.
Backfill
Load current customers and holdings once, then switch to scheduled change detection so events start clean.
Journeys, parallel run & launch
Build onboarding, maturity and cross-sell workflows with sends paused, run two weeks in parallel, then switch on.
What does the Fiserv HubSpot integration sync?
Field names describe Fiserv data as its public materials present it. Exact Communicator Open operations and field paths depend on the institution's core and are confirmed in discovery.
| Fiserv field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers and members | ||||
| Core customer number | fsv_customer_number | Contact / Company | Fiserv → HS | Primary match key. Unique. |
| Customer type (person or organization) | Contact or Company | Contact / Company | Fiserv → HS | Decides which HubSpot object is created. |
| Name | firstname, lastname / name | Contact / Company | Fiserv → HS | Core is the source for legal names. |
| Contact | ↔ Both | Fill blanks only. HubSpot changes go back only with approved write-back. | ||
| Phone and mailing address | phone, address, city, state, zip | Contact | Fiserv → HS | Address changes also raise a timeline event. |
| Customer since | fsv_customer_since | Contact | Fiserv → HS | Earliest relationship date. |
| Business relationship | Contact ↔ Company association | Association | Fiserv → HS | Signers and owners linked to the business. |
| Product holdings | ||||
| Checking held | fsv_has_checking | Contact | Fiserv → HS | Yes/no. No account number. |
| Savings or money market held | fsv_has_savings | Contact | Fiserv → HS | Yes/no. |
| Certificate held | fsv_has_certificate | Contact | Fiserv → HS | Yes/no. Called share certificate at credit unions. |
| Consumer loan held | fsv_has_consumer_loan | Contact | Fiserv → HS | Yes/no. |
| Mortgage or home equity held | fsv_has_mortgage | Contact | Fiserv → HS | Yes/no. |
| Number of products | fsv_product_count | Contact | Fiserv → HS | Calculated in the integration layer. |
| Newest product open date | fsv_last_open_date | Contact | Fiserv → HS | Starts onboarding journeys. |
| Next certificate maturity | fsv_next_maturity_date | Contact | Fiserv → HS | Date only, no balance. |
| Relationship balance tier | fsv_balance_tier | Contact | Fiserv → HS | Off by default. Only with compliance approval. |
| Account and life events | ||||
| New account opened | Custom event: Account opened | Contact | Fiserv → HS | Product type and date, no account number. |
| Account closed | Custom event: Account closed | Contact | Fiserv → HS | Feeds retention reporting. |
| Certificate maturing | Custom event: Certificate maturing | Contact | Fiserv → HS | Raised a set number of days before maturity. |
| Loan paid off | Custom event: Loan paid off | Contact | Fiserv → HS | Trigger for a next-product conversation. |
| Ownership and digital | ||||
| Officer code | hubspot_owner_id | Contact / Company | Fiserv → HS | Mapped through an officer-to-user table. |
| Branch | fsv_branch | Contact | Fiserv → HS | Also sets the HubSpot team. |
| Digital banking enrolled | fsv_digital_enrolled | Contact | Fiserv → HS | Where the digital platform exposes it. Confirm in discovery. |
| E-statements enrolled | fsv_estatements | Contact | Fiserv → HS | Confirm availability in discovery. |
| Contact preferences | Subscription status | Contact | ↔ Both | Source of truth agreed with compliance. |
How are authentication and API limits handled?
Fiserv opens its sandbox to developers directly. Production access to a specific institution's core is arranged through that institution. Values Fiserv does not publish are marked for confirmation.
| Topic | Fiserv | HubSpot |
|---|---|---|
| Access model | Self-service registration in Fiserv Developer Studio, with a Banking Hub workspace and test cores. Production access to the institution's core through the institution and Fiserv. | Self-serve in the client portal. Custom events and field-level permissions need an Enterprise hub. |
| Interfaces | Communicator Open: a normalized set of RESTful APIs across Fiserv's strategic cores. Confirm the operations available on the institution's core. | REST APIs: CRM objects, associations, custom events, imports. |
| Authentication | API credentials issued through Developer Studio for test; production credentials per institution. Confirm the method in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Usage pricing | Fiserv states API usage is free up to a defined threshold, then usage-based. Confirm the institution's terms. | Included in the HubSpot subscription, within API limits. |
| Freshness | Request-based API reads. CC schedules them (nightly for holdings, more often for new accounts). Event push: Not published. Confirm with Fiserv. | Writes are immediate; batch endpoints handle volume. |
| Rate limits | Not published. Confirm with Fiserv. | Per-10-second burst and daily limits by subscription tier. |
| Sensitive data | Nonpublic personal information under GLBA. Account numbers, balances, transactions and tax IDs are excluded by default. | Sensitive data properties on Enterprise; field-level permissions by team. |
What should you plan for, and what does the integration unlock?
Severity reflects impact on the SOW, not technical difficulty alone.
Challenges to plan for
Fiserv's sandbox is self-service, but production credentials for an institution's core are not. Make access a client-owned dependency in the SOW, with a target date.
Customer data in the core is nonpublic personal information. CC plans the compliance review as a project step; the institution's compliance team decides what HubSpot may hold. CC does not assume the answer.
Communicator Open is designed across Fiserv's strategic cores, but the operations available can differ by core and by institution. Budget a short discovery spike to confirm them.
Holdings change slowly and suit a nightly read. New accounts drive onboarding and may need intraday reads. Decide per data set, and do not assume event push.
One account can have several owners, and one person can own accounts with several others. Agree how joint owners and households appear in HubSpot before the build.
Preferences recorded at the branch and unsubscribes recorded in HubSpot need one source of truth. Agree it with compliance and sync accordingly.
Opportunities in HubSpot
Customers with checking but no savings, or a mortgage but no home equity line, enter HubSpot lists and journeys automatically.
An account-opened event starts a welcome journey and a pipeline for the officer, so new customers set up direct deposit, digital banking and a second product.
Certificate maturities and loan payoffs become timed tasks and emails, so the institution keeps the deposit or offers the next loan.
Each officer sees their customers, open onboarding steps and product gaps in HubSpot, ranked for follow-up.
Customers not yet enrolled in online banking or e-statements get a targeted series, and enrollment ends it.
Business customers appear as HubSpot companies with their owners and signers associated, so commercial teams see the whole relationship.
Start with who the customer is, then what they hold.
Every phase reads from the core and adds to one HubSpot data model, so value arrives in steps. Write-back comes last, if at all.
- Customers and members, matched on the core customer number, with officer ownership.
- Product holdings as flags and counts, so cross-sell lists work.
- Account and life events, so onboarding and retention journeys start on their own.
- Digital banking signals, then any approved write-back of contact preferences.
Which HubSpot properties does the integration create?
All custom properties use the fsv_ prefix in a Fiserv property group. Flags, counts and dates are calculated in the integration layer from the approved field list.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| fsv_customer_number | Core Customer Number | Contact | Single-line text | Core customer key; unique |
| fsv_customer_since | Customer Since | Contact | Date picker | Earliest relationship date |
| fsv_has_checking | Has Checking | Contact | Single checkbox | Any open checking account |
| fsv_has_savings | Has Savings | Contact | Single checkbox | Any open savings or money market |
| fsv_has_certificate | Has Certificate | Contact | Single checkbox | Any open certificate |
| fsv_has_consumer_loan | Has Consumer Loan | Contact | Single checkbox | Any open consumer loan |
| fsv_has_mortgage | Has Mortgage | Contact | Single checkbox | Any open mortgage or home equity |
| fsv_product_count | Product Count | Contact | Number | Count of open products |
| fsv_last_open_date | Newest Product Open Date | Contact | Date picker | Most recent account opening |
| fsv_next_maturity_date | Next Certificate Maturity | Contact | Date picker | Earliest upcoming maturity |
| fsv_branch | Branch | Contact | Dropdown | Branch code from the core |
| fsv_digital_enrolled | Digital Banking Enrolled | Contact | Single checkbox | From the digital banking platform |
Interactive scope builder
Choose the data sets and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Scope summary
Sources & verification
Based on Fiserv's public materials. Each item marked for confirmation is verified with Fiserv and the institution during the access phase.
- Fiserv: streamlined access to core platform APIs (Developer Studio, Banking Hub, AppMarket)
- Fiserv: How open integration helps banks compete (Communicator Open)
- Fiserv CoreAdvance (Premier, Cleartouch and Precision)
- Fiserv Cleartouch Bank Platform
- Fiserv DNA apps
- Fiserv Premier bank platform brochure
- Fiserv Architect digital banking brochure
Fiserv HubSpot integration FAQ
Does Fiserv integrate with HubSpot?
Yes, Fiserv opens a developer sandbox to anyone through Fiserv Developer Studio, but production access to a specific institution's core is arranged through that institution. Campaign Creators builds a custom integration layer on Fiserv's Communicator Open APIs once production access is granted.
What data syncs between Fiserv and HubSpot?
Core customer and member records, product holding flags and counts (checking, savings, certificates, consumer loans, mortgages), and account life events such as new-account-opened, certificate-maturing and loan-paid-off sync from Fiserv's core into HubSpot contacts and companies. Approved contact-preference changes can write back to the core; balances, transactions and account numbers never sync.
Which system owns which data?
Fiserv keeps the system of record for balances, transactions, account numbers and other nonpublic personal information covered by GLBA, and the integration never pulls those fields. HubSpot owns marketing, onboarding and cross-sell, holding only the product flags, counts, dates and events the institution's compliance team approves.
What does setting up the Fiserv HubSpot integration involve?
Seven phases, each closed by a sign-off gate: confirming the institution's core and integration goals, registering in Fiserv Developer Studio and requesting production access through the institution, a GLBA compliance review that sets the approved field list, the HubSpot data model build, a sandboxed build of the change detector and minimization filter, a backfill of current customers and holdings, and a two-week parallel run before onboarding and cross-sell journeys go live.
How long does the integration take and what does it cost?
Timeline and cost depend on which of the institution's cores are in scope, how many product and event types are included, and how long the GLBA compliance review takes. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.
Ready to Get More From HubSpot?
Whether you’re implementing HubSpot, optimizing what you already have, connecting systems, or scaling your customer experience, we’ll help you figure out the right next step.
.png?width=1920&height=553&name=cc-logo-color%20(2024).png)