Cardpointe Connector

Cardpointe Connector lets SaaS teams embed CardPointe payment acceptance and terminal flows to authorize and capture payments, store card tokens, issue refunds and surface settlement reporting through CardPointe’s REST APIs and integrated terminals. (support.cardpointe.com)

Build with this Connector Talk to an integration expert

Faster time to market

Deliver in-app payments faster with reusable flows.

Reduce PCI scope

Use CardPointe tokenization and hosted pages to limit card data handling.

Centralized reconciliation

Automate settlement and reporting across merchant accounts.

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

What you can integrate or automate with CardPointe

Integrate payment acceptance, tokenization, refunds, captures, voids, transaction reporting and settlements using CardPointe’s RESTful Gateway and Integrated Terminal APIs. (support.cardpointe.com) With Cyclr you can orchestrate these operations into reusable, tenant-aware workflows — for example: accept a card, store a CardSecure token, capture or refund a transaction and then reconcile settlement batches automatically. (support.cardpointe.com)

PRODUCT USE CASES

Top use cases for CardPointe integrations

Quickly create tenant-aware automations for authorizations, tokenization, refunds, batch reconciliation and terminal-initiated payments. Publish integrations in a white-label embedded marketplace so customers can enable CardPointe inside your app.

In-app payment capture and authorization

Authorize and capture card-present or card-not-present transactions, returning transaction IDs for order records. (support.cardpointe.com)

Save card on file and charge later

Store card details as CardSecure tokens and charge tokens later for subscriptions or order renewals. (support.cardpointe.com)

Refunds, voids and lifecycle management

Automate refunds, voids and release operations against transaction IDs to reconcile customer requests. (support.cardpointe.com)},{

ORCHESTRATION

How Cardpointe works with Cyclr

Cyclr sits between your SaaS product and Cardpointe to handle authentication, govern access and orchestrate every API call per customer, at scale.

1
Your SaaS product
Your app requests an action for a specific customer.
2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
3
Cardpointe
Cardpointe processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Cardpointe methods you can orchestrate through Cyclr.

Transactions2

List Transactions

Action

List transactions for a given day.

Get Transaction

Action

Get a single transaction record.

TECHNICAL DETAILS

Cardpointe integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Cardpointe integrations in Cyclr.

API and authentication

API host: https://github.com/ilrWebServices/cardpointe-gateway-rest-api-client?utm_source=openai
Authentication: HTTP Basic Auth for server API calls; client-side tokenization and hosted payment pages reduce PCI scope
Credentials: Merchant ID, API password/key and site subdomain (site-specific base URL). (github.com)
Method categories: Transactions, tokenization/profiles, refunds/voids, captures, reporting, terminal session APIs. (support.cardpointe.com)

View vendor API documentation →

Pagination and rate limits

Pagination

Method-specific behavior should be confirmed before implementation.

Rate limits

Refer to the vendor API documentation for current limits.

IMPLEMENTATION

Authentication at a glance

HTTP Basic Auth (merchant ID and API key) for server calls; client tokenization via CardPointe hosted fields reduces PCI exposure. (support.cardpointe.com)

Authentication method: HTTP Basic Auth for server API calls; client-side tokenization and hosted payment pages reduce PCI scope
Credential required: Merchant ID, API password/key and site subdomain (site-specific base URL). (github.com)

Before you begin:

Requires an active CardPointe merchant account and API credentials from CardPointe/Fiserv. (support.cardpointe.com)

View setup guide

COMMON QUESTIONS

Frequently asked questions

It can accept and capture payments, store CardSecure tokens, issue refunds or voids, and surface settlement and transaction reporting via CardPointe’s Gateway and Terminal APIs. (support.cardpointe.com)

CardPointe uses HTTP Basic Auth for server-to-server API calls (merchant ID and API key); client-side tokenization or hosted payment pages reduce PCI exposure. (github.com)

Yes. Cyclr can orchestrate tenant-specific CardPointe credentials and deploy reusable, tenant-aware workflows so each customer uses their own merchant account. This requires each customer’s CardPointe credentials. (support.cardpointe.com)

Yes. Cyclr lets product teams expose selected CardPointe actions (authorize, capture, refund, report) as governed MCP tools with centralized credential governance and role controls. This is configured inside Cyclr, not CardPointe.

KEEP EXPLORING

Related resources and connectors

Documentation