Connect™

Epicor Eclipse + Heartland Integration

Clarity Connect™ integrates Epicor Eclipse with Heartland, automating business processes and data sharing. This robust integration connects your critical business systems to automate order processing, inventory management, and customer data synchronization.

Get Pricing

The Challenge

Connecting with Clarity Connect™

Clarity Connect™ links Epicor Eclipse and Heartland through automation and data sharing. Integrating these platforms benefits businesses by streamlining processes and connecting front-end and back-end systems.

Considerations when connecting these applications include security, performance, and physical access. We support both SaaS (Cloud) and On-Premises connection types.

The Solution

Seamless Integration

Our middleware platform ensures robust and reliable data transfer between Epicor Eclipse and Heartland.

Synchronize custom fields in Epicor Eclipse (e.g., project codes, department IDs) to Heartland's customer or order metadata.
Map custom attributes from Heartland's transactions (e.g., loyalty points, specific discounts) to Epicor Eclipse for detailed reporting.
Extend product attributes in Heartland POS with specific ERP data.

Implementation Timeline

Go live with Epicor Eclipse + Heartland in as little as 2–4 weeks.

A proven, repeatable implementation approach that minimizes risk while getting your team to value quickly.

Access Enabled

Secure connections established to both Epicor Eclipse and Heartland, with credentials and environments confirmed.

Configuration & Mapping

Field mappings, business rules, and workflows configured using visual tools and pre-built templates.

Go Live

Launch production-ready integration with monitoring, alerting, and support in place—typically within 2–4 weeks.

Time to Value

2–4 weeks

Typical implementation window from access granted to production go-live for most Epicor Eclipse + Heartland deployments.

Project Phases

Discovery

Configure & Map

Validate

Launch

Engagement Model

Guided by Clarity experts with your team involved at key milestones.

Comprehensive Solution Details

Synchronize custom fields in Epicor Eclipse (e.g., project codes, department IDs) to Heartland's customer or order metadata.
Map custom attributes from Heartland's transactions (e.g., loyalty points, specific discounts) to Epicor Eclipse for detailed reporting.
Extend product attributes in Heartland POS with specific ERP data.

Robust Integration Architecture for Epicor Eclipse and Heartland

The integration architecture is built on a modern iPaaS, providing a scalable, secure, and resilient bridge between Epicor Eclipse and Heartland. It prioritizes an API-first, event-driven approach, leveraging low-code capabilities for rapid development and AI for intelligent operations.

Data Flow Steps

API-First, Event-Driven Architecture: Utilize Heartland's webhooks and Epicor Eclipse's APIs for real-time data exchange, enabling immediate reactions to business events (e.g., new order, payment processed).

Canonical Data Model: Define a unified data schema within the iPaaS for common entities (Customer, Order, Payment) to simplify mapping and ensure consistency across systems.

Micro-integrations: Break down complex workflows into smaller, manageable, and independently deployable integration flows.

Publish-Subscribe Model: For broadcasting events (e.g., a new product update from Epicor Eclipse to multiple channels including Heartland POS).

Idempotent API Calls: Design integration flows to ensure that repeated API calls (due to retries) do not result in duplicate transactions in Heartland or Epicor Eclipse.

Data Touchpoints

iPaaS Platform: Central hub for integration design, deployment, and management.

Epicor Eclipse Connector: Specialized adapter for Epicor Eclipse APIs (e.g., customer, sales order, GL).

Heartland Connector: Pre-built connector for Heartland APIs (payments, POS, payroll, webhooks).

Data Transformation Engine: Low-code/no-code visual mapping tool for data schema conversion.

Workflow Orchestration Engine: Manages the sequence and logic of integration flows.

AI/ML Co-pilot: For intelligent mapping suggestions, anomaly detection, and automated testing.

Monitoring & Alerting Module: Real-time dashboards, logs, and notification services.

Secure Credential Management: Encrypted storage for API keys, OAuth tokens, and sensitive credentials.

Message Queues: For asynchronous processing and handling burst traffic.

"Conceptual Diagram: Epicor Eclipse <--> iPaaS (Connectors, Transformation, Orchestration, AI/ML) <--> Heartland. The iPaaS sits centrally, facilitating data exchange, applying business logic, and ensuring data integrity. Key components include dedicated connectors, a visual workflow designer, a data mapping engine, a rules engine, monitoring dashboards, and an AI co-pilot."

Pricing

Simple, transparent pricing for Epicor Eclipse + Heartland.

Start with a single integration pair and scale as your business grows—without surprise fees or transaction penalties.

Connect™ Plan

Clarity Connect

$595 /mo

Billed annually • Includes one production integration pair

Unlimited transactions and API calls within fair-use limits.
Visual workflow designer and reusable mapping templates.
Monitoring, alerting, and access to Clarity’s support team.

View full pricing & options

Innovative & Robust

How Middleware Integration Works

Benefits of Integrating Epicor Eclipse

Integrating Epicor Eclipse fosters greater efficiency and data accuracy. Automate your critical business processes to deliver consistently outstanding results.

Hover over the steps on the right to see detailed integration points.

Benefits of Integrating Heartland

Integrating Heartland streamlines your operations. Connect your systems to ensure data flows seamlessly across your organization.

Hover over the steps on the right to see detailed integration points.

Data Mapping

Data Entity Mapping

Explore how data flows between systems with intelligent field mapping and transformation logic.

Payment Transaction

Represents a single financial transaction processed through Heartland, including sales, authorizations, captures, and refunds. This is a core entity for financial reconciliation and reporting within Epicor Eclipse.

Epicor Eclipse Fields

[field, TransactionID (ERP)],[type, string],[description, Unique identifier for the transaction in Epicor Eclipse's general ledger or sales order.] [field, CustomerID (ERP)],[type, string],[description, Customer account ID in Epicor Eclipse.] [field, InvoiceNumber],[type, string],[description, Associated invoice number in Epicor Eclipse.] [field, AmountPaid],[type, decimal],[description, The amount received/refunded.] [field, PaymentDate],[type, datetime],[description, Date and time of payment.] [field, PaymentMethod],[type, string],[description, e.g., Credit Card, Debit Card, Gift Card.] [field, GLAccountID],[type, string],[description, General Ledger account for posting payment.] [field, Status],[type, string],[description, Payment status (e.g., Captured, Refunded, Voided).]

Heartland Fields

[field, transactionId],[type, string],[description, Heartland's unique transaction identifier.] [field, amount],[type, decimal],[description, Total amount of the transaction.] [field, currency],[type, string],[description, Currency code (e.g., USD).] [field, transactionType],[type, string],[description, Type of transaction (e.g., Sale, Auth, Refund).] [field, status],[type, string],[description, Current status of the transaction.] [field, cardType],[type, string],[description, Type of card used (e.g., Visa, MasterCard).] [field, last4],[type, string],[description, Last four digits of the card number.] [field, entryMethod],[type, string],[description, Method of entry (e.g., Swipe, EMV, eCommerce).] [field, timestamp],[type, datetime],[description, Timestamp of the transaction.] [field, orderId],[type, string],[description, Associated order ID from source system.] [field, customerId],[type, string],[description, Associated customer ID in Heartland.]

Mapping Notes

Heartland's `transactionId` maps to a custom `HeartlandTransactionRef` field in Epicor Eclipse or `TransactionID (ERP)`. `Heartland.amount` maps to `EpicorEclipse.AmountPaid`. `Heartland.customerId` must be cross-referenced with `EpicorEclipse.CustomerID (ERP)` using a unique identifier. `Heartland.transactionType` and `status` require transformation to Epicor Eclipse's specific payment event types.

Customer

Contains details about a customer, used for loyalty programs, recurring billing in Heartland, and associating transactions with customer accounts in Epicor Eclipse.

Epicor Eclipse Fields

[field, CustomerID (ERP)],[type, string],[description, Primary customer identifier in Epicor Eclipse.] [field, CustomerName],[type, string],[description, Full customer name.] [field, BillingAddress],[type, object],[description, Customer's billing address.] [field, ShippingAddress],[type, object],[description, Customer's shipping address.] [field, Email],[type, string],[description, Customer's primary email address.] [field, Phone],[type, string],[description, Customer's primary phone number.] [field, AccountStatus],[type, string],[description, Active, Inactive, etc.]

Heartland Fields

[field, customerId],[type, string],[description, Heartland's unique customer identifier.] [field, firstName],[type, string],[description, Customer's first name.] [field, lastName],[type, string],[description, Customer's last name.] [field, email],[type, string],[description, Customer's email address.] [field, phone],[type, string],[description, Customer's phone number.] [field, address],[type, object],[description, Customer's primary address.] [field, heartlandCustomerId (if different from external ID)],[type, string],[description, Internal Heartland ID if different from external source.]

Mapping Notes

Epicor Eclipse's `CustomerID (ERP)` should ideally map to Heartland's `customerId` for consistent cross-system identification. Address fields require careful sub-field mapping. Deduplication logic is crucial when syncing from multiple sources.

Order

Represents a customer's purchase, originating from an eCommerce platform or Heartland POS. Contains line items, totals, and shipping information, flowing to Epicor Eclipse for fulfillment and accounting.

Epicor Eclipse Fields

[field, SalesOrderNumber],[type, string],[description, Unique sales order ID in Epicor Eclipse.] [field, CustomerID (ERP)],[type, string],[description, Associated customer ID.] [field, OrderDate],[type, datetime],[description, Date the order was placed.] [field, TotalAmount],[type, decimal],[description, Total value of the order.] [field, OrderStatus],[type, string],[description, Status in Epicor Eclipse (e.g., Open, Shipped, Billed).] [field, LineItems],[type, array],[description, Details of products ordered.] [field, ShippingAddress],[type, object],[description, Shipping address for the order.] [field, BillingAddress],[type, object],[description, Billing address for the order.]

Heartland Fields

[field, orderId],[type, string],[description, Unique order ID from source (e.g., eCommerce).] [field, orderNumber],[type, string],[description, External order number.] [field, status],[type, string],[description, Order status (e.g., New, Paid, Fulfilled).] [field, totalAmount],[type, decimal],[description, Total amount of the order.] [field, shippingAddress],[type, object],[description, Shipping address.] [field, billingAddress],[type, object],[description, Billing address.] [field, lineItems],[type, array],[description, Array of product line items.] [field, customerId],[type, string],[description, Customer associated with the order.] [field, paymentMethod],[type, string],[description, Method used for payment.]

Mapping Notes

Heartland `orderId` typically originates from an eCommerce platform and needs to map to `EpicorEclipse.SalesOrderNumber` or a reference field. Line items require detailed mapping including SKU, quantity, and price. Payment status from Heartland directly impacts `EpicorEclipse.OrderStatus`.

Product/SKU

Details about an item sold, including its identifier, description, price, and inventory level. Managed by Heartland POS and synchronized with Epicor Eclipse for master data and inventory control.

Epicor Eclipse Fields

[field, ItemNumber],[type, string],[description, Unique product identifier in Epicor Eclipse.] [field, ItemDescription],[type, string],[description, Product description.] [field, UnitPrice],[type, decimal],[description, Selling price.] [field, Cost],[type, decimal],[description, Cost of the item.] [field, QuantityOnHand],[type, integer],[description, Current inventory level.] [field, ProductCategory],[type, string],[description, Category of the product.] [field, Barcode],[type, string],[description, UPC/EAN barcode.]

Heartland Fields

[field, sku],[type, string],[description, Heartland POS product identifier.] [field, name],[type, string],[description, Product name in POS.] [field, description],[type, string],[description, Product description in POS.] [field, price],[type, decimal],[description, Selling price in POS.] [field, cost],[type, decimal],[description, Cost of goods in POS.] [field, quantityOnHand],[type, integer],[description, Current inventory level in POS.] [field, barcode],[type, string],[description, Barcode for scanning.]

Mapping Notes

`EpicorEclipse.ItemNumber` should be the master and sync to `Heartland.sku`. `QuantityOnHand` is critical for two-way sync to prevent overselling. Price updates can originate from either system, requiring clear master data governance.

Settlement Batch

A group of transactions processed and settled together, typically at the end of a business day. Essential for bank and general ledger reconciliation in Epicor Eclipse.

Epicor Eclipse Fields

[field, BatchID (ERP)],[type, string],[description, Unique identifier for the settlement batch in Epicor Eclipse.] [field, SettlementDate],[type, date],[description, Date of settlement.] [field, TotalSettledAmount],[type, decimal],[description, Total amount settled in the batch.] [field, TransactionCount],[type, integer],[description, Number of transactions in the batch.] [field, BankDepositID],[type, string],[description, Reference to the bank deposit in Epicor Eclipse.] [field, GLPostingStatus],[type, string],[description, Status of GL posting (e.g., Posted, Pending).]

Heartland Fields

[field, batchId],[type, string],[description, Heartland's unique batch identifier.] [field, settlementDate],[type, date],[description, Date the batch was settled.] [field, totalAmount],[type, decimal],[description, Total amount of the batch.] [field, transactionCount],[type, integer],[description, Number of transactions in the batch.] [field, status],[type, string],[description, Status of the settlement batch.] [field, merchantId],[type, string],[description, Heartland merchant ID.]

Mapping Notes

Heartland's `batchId` maps directly to `EpicorEclipse.BatchID (ERP)`. `totalAmount` and `transactionCount` are crucial for reconciliation. The `settlementDate` aligns with the accounting period.

Employee

Employee record for payroll processing within Heartland Payroll, sourced from an HRIS or Epicor Eclipse's employee master, ensuring timely setup for payroll processing and benefits enrollment.

Epicor Eclipse Fields

[field, EmployeeID (ERP)],[type, string],[description, Unique employee identifier in Epicor Eclipse.] [field, FirstName],[type, string],[description, Employee's first name.] [field, LastName],[type, string],[description, Employee's last name.] [field, SSN],[type, string],[description, Social Security Number (sensitive).] [field, HireDate],[type, date],[description, Date of hire.] [field, JobTitle],[type, string],[description, Employee's job title.] [field, PayRate],[type, decimal],[description, Hourly or annual pay rate.] [field, DepartmentID],[type, string],[description, Department ID.] [field, Address],[type, object],[description, Employee's home address.]

Heartland Fields

[field, employeeId],[type, string],[description, Heartland Payroll's employee identifier.] [field, firstName],[type, string],[description, Employee's first name.] [field, lastName],[type, string],[description, Employee's last name.] [field, ssn],[type, string],[description, Social Security Number.] [field, hireDate],[type, date],[description, Date of hire.] [field, jobTitle],[type, string],[description, Employee's job title.] [field, payRate],[type, decimal],[description, Employee's pay rate.] [field, deductions],[type, array],[description, List of deductions (e.g., health insurance).] [field, departmentId],[type, string],[description, Department ID.]

Mapping Notes

Epicor Eclipse's `EmployeeID (ERP)` should map consistently to `Heartland.employeeId`. Sensitive PII like `SSN` requires secure handling and tokenization if possible. Pay rate and deduction changes need to be reflected promptly.

Next Steps

See Epicor Eclipse + Heartland integration in action.

Explore a guided demo, start a sandbox integration, or speak directly with our solution architects about your specific use cases.

Start Free Trial Request Live Demo

Real-World Applications

Integration Use Cases

Explore how the integration behaves in real business scenarios, with clearly defined steps, outcomes, and execution patterns.

eCommerce Order to Heartland Payment & POS Sync

Automate the entire order-to-payment-to-inventory workflow. When a customer places an order on an eCommerce platform, the iPaaS captures the order, processes payment via Heartland, and updates inventory in both Heartland POS and Epicor Eclipse.

Integration Steps:

0 Customer places order on eCommerce platform.
1 iPaaS captures order event and details.
2 Payment initiated through Heartland's API.
3 Heartland processes payment; status updated.
4 iPaaS updates inventory levels in Heartland POS.
5 iPaaS creates sales order and updates inventory in Epicor Eclipse ERP.
6 Order status updated on eCommerce platform.

Business Outcome

Real-time inventory accuracy across channels, instant payment processing, reduced overselling, faster order fulfillment.

Frequency

Real-time (event-driven)

Technical Documentation

API Endpoints & Data Logic

Technical details for developers and architects.

Method	Endpoint	Purpose
POST/GET/PUT	/api/v1/customers	Create, retrieve, or update customer master data in Epicor Eclipse ERP.
POST/GET/PUT	/api/v1/salesorders	Create, retrieve, or update sales orders, crucial for order-to-cash process.
GET/PUT	/api/v1/inventory/items	Retrieve or update product inventory levels and master data.
POST	/api/v1/financials/journalentries	Post general ledger journal entries for sales, payments, and payroll.
POST/GET/PUT	/api/v1/employees	Manage employee master data for payroll integration.

Method	Endpoint	Purpose
POST	/v1/payments/transactions	Process new payment transactions (authorization, capture).
POST	/v1/payments/transactions/{transactionId}/refunds	Initiate a refund for a specific transaction.
POST/GET	/v1/customers	Create new customer profiles or retrieve existing ones (for loyalty, recurring billing).
PUT/GET	/v1/pos/inventory	Update or retrieve inventory levels for POS items.
GET	/v1/pos/sales	Retrieve daily or historical sales data from POS terminals.
POST/GET/PUT	/v1/payroll/employees	Manage employee records for payroll processing.
POST	/v1/webhooks/subscriptions	Subscribe to event notifications (e.g., transaction complete, settlement posted).

Event	Name	Payload Data

⚡ Transformation Logic

Currency Conversion: Ensure consistent currency codes and apply conversion rates if transactions span multiple currencies.
Date/Time Formatting: Standardize `timestamp` and `date` fields to a common format (e.g., ISO 8601).
Customer ID Reconciliation: Map and synchronize unique customer identifiers between Epicor Eclipse, Heartland, and potentially a CRM, creating cross-reference tables.
Product SKU Matching: Reconcile product SKUs and inventory quantities, handling variations in product identifiers.
Payment Status Mapping: Convert Heartland's `transactionType` and `status` to Epicor Eclipse's specific payment event codes for GL posting.
Address Normalization: Parse and standardize address components to ensure consistency for shipping and billing.
Payroll Deduction Mapping: Translate specific deduction types and benefit codes from HRIS/Epicor Eclipse to Heartland Payroll's schema.

🛡️ Error Handling

Heartland API downtime leading to payment processing delays.
Epicor Eclipse ERP being offline, preventing GL posting.
Data validation failures due to incorrect formats or missing required fields.
Duplicate transaction attempts due to network issues.
Mismatched customer IDs causing unlinked transactions.

Support & Information

Frequently Asked Questions

Common questions about integration implementation, security, and best practices.

General Integration FAQs

▸ What kind of systems can Heartland integrate with?

Heartland can integrate with a wide range of business systems including eCommerce platforms (Shopify, BigCommerce), CRM systems (Salesforce, HubSpot), ERPs (like Epicor Eclipse, NetSuite, SAP Business One), accounting software (QuickBooks, Xero), HRIS platforms, inventory management systems, and custom applications, primarily through its robust APIs and event-driven architecture facilitated by an iPaaS.

iPaaS Benefits FAQs

▸ How does iPaaS improve Heartland's payment processing integration with Epicor Eclipse?

iPaaS enhances Heartland's payment processing integration with Epicor Eclipse by providing real-time data synchronization, automated transaction routing, centralized error handling, and robust data mapping capabilities. This ensures secure, compliant, and accurate flow of payment data to Epicor Eclipse's accounting and ERP modules, reducing manual reconciliation and improving financial reporting speed and accuracy.

Inventory Management FAQs

▸ Can I automate my Heartland POS inventory updates with Epicor Eclipse?

Yes, absolutely. Using an iPaaS, you can create real-time or near real-time automation workflows to synchronize inventory levels between your Heartland POS system and your Epicor Eclipse ERP. This prevents overselling, reduces stockouts, ensures accurate inventory valuation in Epicor Eclipse, and provides customers with accurate product availability across all channels.

AI & Automation FAQs

▸ What is AI-augmented integration for Heartland and Epicor Eclipse?

AI-augmented integration for Heartland and Epicor Eclipse involves embedding artificial intelligence capabilities into your iPaaS workflows. This can include AI for automated transaction validation, anomaly detection for potential fraud in Heartland data, intelligent data mapping suggestions between systems, and autonomous handling of common exceptions, significantly reducing manual oversight and improving data quality across your ERP and payment systems.

Security & Compliance FAQs

▸ Are Heartland and Epicor Eclipse integrations PCI DSS compliant?

Maintaining PCI DSS compliance is paramount for any system handling payment data. While Heartland itself is compliant, your integration strategy must also adhere to these standards. Using an iPaaS that supports tokenization, secure data encryption (TLS 1.2+), and audited access controls is crucial to ensure end-to-end compliance for all integrated workflows involving Heartland and Epicor Eclipse, protecting sensitive cardholder data.

Low-Code/No-Code FAQs

▸ How do low-code/no-code tools help with Heartland and Epicor Eclipse integrations?

Low-code/no-code tools empower business users and citizen integrators to build, modify, and manage Heartland and Epicor Eclipse integration workflows visually, without extensive coding. This accelerates development cycles, reduces reliance on IT, and allows business teams to quickly adapt integrations to evolving needs, such as adding new sales channels, payment methods, or updating Epicor Eclipse accounting rules.

Error Handling FAQs

▸ How do I handle errors and failed transactions in Heartland and Epicor Eclipse integrations?

A robust integration strategy utilizes iPaaS capabilities for comprehensive error handling. This includes automated retries with exponential backoff for transient errors, dead-letter queues for messages that cannot be processed, configurable alerts for critical failures (e.g., failed GL postings in Epicor Eclipse), and centralized logging for auditing and troubleshooting. AI can further assist by suggesting resolutions for recurring error patterns.

Architecture FAQs

▸ What is event-driven architecture in the context of Heartland and Epicor Eclipse integration?

Event-driven architecture (EDA) means that integrations react to 'events' happening in Heartland (e.g., a payment is authorized, a settlement is posted) or Epicor Eclipse (e.g., a new sales order is created). This allows for real-time data flow, immediate system updates, and highly responsive workflows, which is crucial for dynamic environments like eCommerce, payment processing, and financial operations, ensuring Epicor Eclipse always has the latest financial data.

Pricing

Simple, transparent pricing for Epicor Eclipse + Heartland.

Start with a single integration pair and scale as your business grows—without surprise fees or transaction penalties.

Connect™ Plan

Clarity Connect

$599 /mo

Billed annually • Includes one production integration pair

Unlimited transactions and API calls within fair-use limits.
Visual workflow designer and reusable mapping templates.
Monitoring, alerting, and access to Clarity’s support team.

View full pricing & options

Next Steps

See Epicor Eclipse + Heartland integration in action.

Explore a guided demo, start a sandbox integration, or speak directly with our solution architects about your specific use cases.

Start Free Trial Request Live Demo

Everything eCommerce

Everything Marketplace

Everything Auction

Secure HIPAA eCommerce

Any Payment Gateway

Integrate the way you want

Start your AI journey here

Online Selling Just for You

Business Integrations

Custom Development

Secure Portals

We'd love to hear from you!

Epicor Eclipse + Heartland Integration

See how it works

Connecting with Clarity Connect™

Seamless Integration

Go live with Epicor Eclipse + Heartland in as little as 2–4 weeks.

Access Enabled

Configuration & Mapping

Go Live

Comprehensive Solution Details

Robust Integration Architecture for Epicor Eclipse and Heartland

Data Flow Steps

Data Touchpoints

Simple, transparent pricing for Epicor Eclipse + Heartland.

Clarity Connect

How Middleware Integration Works

Epicor Eclipse

Heartland

Benefits of Integrating Epicor Eclipse

Benefits of Integrating Heartland

Data Entity Mapping

Epicor Eclipse Fields

Heartland Fields

Mapping Notes

Epicor Eclipse Fields

Heartland Fields

Mapping Notes

Epicor Eclipse Fields

Heartland Fields

Mapping Notes

Epicor Eclipse Fields

Heartland Fields

Mapping Notes

Epicor Eclipse Fields

Heartland Fields

Mapping Notes

Epicor Eclipse Fields

Heartland Fields

Mapping Notes

See Epicor Eclipse + Heartland integration in action.

Integration Use Cases

eCommerce Order to Heartland Payment & POS Sync

Integration Steps:

Business Outcome

Heartland POS Sale to Epicor Eclipse Accounting Reconciliation

Integration Steps:

Business Outcome

New Customer Onboarding & Sync

Integration Steps:

Business Outcome

AI-Augmented Fraud Detection & Exception Handling

Integration Steps:

Business Outcome

API Endpoints & Data Logic

⚡ Transformation Logic

🛡️ Error Handling

Frequently Asked Questions

General Integration FAQs

iPaaS Benefits FAQs

Inventory Management FAQs

AI & Automation FAQs

Security & Compliance FAQs

Low-Code/No-Code FAQs

Error Handling FAQs

Architecture FAQs

Simple, transparent pricing for Epicor Eclipse + Heartland.

Clarity Connect

See Epicor Eclipse + Heartland integration in action.

Secure HIPAA
eCommerce

Any Payment
Gateway

Integrate the
way you want

Start your AI
journey here