A · CRM
Customer record ↔ Charge
Transactions can post back to your CRM with a customer ID, a tokenized card reference, and metadata; failed charges can trigger a workflow.
⇌
IntegrationsThe gateway,
The gateway,
potentially wired into where you already work.
CardConnect APIs and the PAX open SDK can connect your payments to where you already keep your data — CRM, accounting, online store, internal apps. We coordinate and scope approved integration resources, subject to technical review; you keep the keys.
can connect toHubSpot
Salesforce
QuickBooks
Shopify
CloverCardConnect
HubSpotSalesforceQuickBooksShopifyCloverCardConnectCardConnect, a Fiserv company
01 · The shape
Three flows worth integrating
You run a CRM, a POS, and your books. Today someone re-types data between all three. That gap is the integration.
B · Books
Funds ↔ Ledger
Settlements can be reconciled to QuickBooks, Xero, or NetSuite, with card-brand fees broken out by category, depending on the integration scope.
C · Cart
Checkout ↔ Gateway
Branded hosted payment page or embedded checkout via the CardConnect tokenizer. Options for Shopify, WooCommerce, or a custom cart, subject to technical review.
→
02 · The build
From scope to live, in four steps
Typical timing varies based on integration scope and testing. Every integration starts with a written scope; custom work is covered by a separate written agreement.
1
Walk through your stack
30-min call. We map what tools you already use and where the money handoffs happen.
2
Written scope
You get a written scope: connectors needed, custom work if any, timeline, and fee.
3
Build & test
Approved integration resources configure connectors and build any custom work against CardConnect APIs, subject to technical review.
4
Go live & support
We coordinate go-live, review the first batch of transactions, and help resolve issues as defined in your written scope.
03 · The connections
Potential connections with the tools you already use
If your system isn’t listed, a custom integration may be possible. We can coordinate or scope approved integration resources, subject to technical review and a separate written agreement.
Customer data, potentially in sync
Potential two-way sync of contacts, deals, transaction history, and payment status, subject to technical review.
HubSpotSalesforce
ZohoCustom RESTSettlements that can be mapped to your accounting software, with card-brand fees split out, depending on integration scope.
Journal entries, fee breakdowns, and sales-tax mapping from CardConnect settlements, depending on integration scope.
QuickBooks
Xero
NetSuite
SageCheckout, tokenized
CardConnect as the gateway behind your store, with options such as card-on-file, subscriptions, or a hosted page, subject to technical review.
Shopify
WooCommerce
MagentoCustom cartLogos identify platforms we can scope integrations for; availability is subject to technical review.
Integration questions, answered
How does the integration with my POS, CRM, or accounting software work?
CardConnect offers APIs that can connect the gateway to the tools you already run. Depending on the approved scope, transactions can post back to your CRM, settlements can be reconciled in QuickBooks, Xero, or NetSuite, and your online store can check out through a hosted payment page or embedded tokenizer. Each integration is subject to technical review.
What does the written scope cover?
Every integration starts with a written scope — the connectors needed, any custom work, the timeline, and the fee — so you approve the whole picture before anything gets built. Whether a connector has a cost depends on your agreement.
What if my software isn't on the list?
A custom integration may be possible. PAX terminals offer an open SDK and CardConnect offers APIs, so we can coordinate or scope approved integration resources, subject to technical review and a separate written agreement.
Who supports the integration after it goes live?
Support after go-live is defined in your written scope. We remain your point of contact and coordinate with the resources that built the integration.
Tell us your stack.
We'll scope the integration.
One call and a written scope before anything gets built. If your system isn’t on the list, we’ll review whether a custom integration is possible.