Connect™

Epicor Eclipse + Cybersource Integration

Clarity Connect™ integrates Epicor Eclipse with Cybersource, 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 Cybersource 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 Cybersource.

Yes, supports mapping custom fields in Epicor Eclipse to Cybersource `merchantDefinedData` and vice-versa. Also allows adding custom fields to integration entities within the iPaaS for specific business needs.

Implementation Timeline

Go live with Epicor Eclipse + Cybersource 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 Cybersource, 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 + Cybersource deployments.

Project Phases

Discovery

Configure & Map

Validate

Launch

Engagement Model

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

Comprehensive Solution Details

Yes, supports mapping custom fields in Epicor Eclipse to Cybersource `merchantDefinedData` and vice-versa. Also allows adding custom fields to integration entities within the iPaaS for specific business needs.

Robust & Scalable Integration Architecture

Our integration architecture positions the iPaaS as the central nervous system, intelligently connecting Epicor Eclipse and Cybersource. This modern, event-driven design ensures high performance, scalability, security, and resilience for all your payment and financial workflows.

Data Flow Steps

[pattern, Event-Driven Architecture],[description, Leverage Cybersource webhooks for real-time updates (payments, fraud decisions) to trigger immediate actions in Epicor Eclipse.]

[pattern, Canonical Data Model],[description, Define a standardized intermediate data structure within the iPaaS to simplify mapping between Epicor Eclipse and Cybersource, reducing complexity and improving maintainability.]

[pattern, Idempotent Design],[description, Ensure integration workflows can safely handle duplicate requests without unintended side effects, crucial for payment processing.]

[pattern, Circuit Breaker Pattern],[description, Implement circuit breakers for API calls to prevent cascading failures in case one system becomes unavailable, ensuring the overall resilience of the integration.]

[pattern, Batch Processing for Reconciliation],[description, Utilize scheduled batch processing for daily settlement reports to Epicor Eclipse GL, optimizing resource usage for non-real-time operations.]

Data Touchpoints

[component, iPaaS Runtime Engine],[description, Executes integration flows, handles data processing, and orchestrates interactions.]

[component, Cybersource Connector],[description, Pre-built, optimized connector for Cybersource APIs (Payments, Tokenization, Reporting, Decision Manager).]

[component, Epicor Eclipse Connector],[description, Dedicated connector for Epicor Eclipse APIs (Sales Orders, Customers, GL, Invoices).]

[component, Data Transformation Engine],[description, Visual mapping canvas and low-code/no-code tools for data format conversion and enrichment.]

[component, Workflow Orchestration],[description, Drag-and-drop interface for designing complex, multi-step business process automation.]

[component, Monitoring & Alerting],[description, Centralized dashboards for real-time visibility, performance metrics, and configurable alerts.]

[component, AI Co-pilot],[description, Assists with mapping, validation, anomaly detection, and auto-generation of integration logic.]

[component, Message Queues],[description, For asynchronous processing, buffering high-volume transactions, and ensuring fault tolerance.]

[component, Secure Credential Vault],[description, Encrypts and manages API keys and secrets for both systems.]

"Conceptual diagram shows Cybersource (payment gateway, fraud, tokenization) on one side, Epicor Eclipse (ERP, GL, Sales Orders) on the other. In the middle, the iPaaS acts as the orchestrator, with distinct layers for Connectors, Data Transformation, Workflow Orchestration, Monitoring, and AI Co-pilot. Webhooks flow from Cybersource to iPaaS; API calls flow bi-directionally between iPaaS and both systems."

Pricing

Simple, transparent pricing for Epicor Eclipse + Cybersource.

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 Cybersource

Integrating Cybersource 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.

✓

Payment Initiation & Authorization
✓

Payment Capture & Sales Order Creation
✓

Refund Processing & Credit Memo Creation
✓

Daily Settlement Reconciliation
✓

Fraud Alert & Workflow Orchestration

✓

Payment Initiation & Authorization
✓

Payment Capture & Sales Order Creation
✓

Refund Processing & Credit Memo Creation
✓

Daily Settlement Reconciliation
✓

Fraud Alert & Workflow Orchestration

Data Mapping

Data Entity Mapping

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

Payment Transaction

The core financial event representing authorization, capture, sale, refund, or void from Cybersource, mapped to payment applications or journal entries in Epicor Eclipse.

Epicor Eclipse Fields

[field, SalesOrder.OrderNum],[type, string],[notes, Used for linking payment to the specific sales order.] [field, Invoice.InvoiceNum],[type, string],[notes, Reference for captured payments or refunds.] [field, GLJournalEntry.DebitCredit],[type, decimal],[notes, For posting payment amounts to respective GL accounts.] [field, Payment.PaymentAmount],[type, decimal],[notes, Applied amount from the payment.] [field, Payment.PaymentReference],[type, string],[notes, Stores Cybersource transactionId for reconciliation.]

Cybersource Fields

[field, transactionId],[type, string],[notes, Unique identifier for the Cybersource transaction.] [field, merchantDefinedData],[type, object],[notes, Custom fields to pass Epicor Eclipse OrderNum, CustomerID, etc.] [field, amount],[type, decimal],[notes, Transaction amount.] [field, currency],[type, string],[notes, Currency code (e.g., USD).] [field, status],[type, string],[notes, Payment status (e.g., AUTHORIZED, CAPTURED, REFUNDED).] [field, authCode],[type, string],[notes, Authorization code.] [field, reasonCode],[type, string],[notes, Reason for failure or success.] [field, requestID],[type, string],[notes, Unique request identifier for Cybersource API call.]

Mapping Notes

The `transactionId` from Cybersource is crucial for cross-referencing in Epicor Eclipse. `merchantDefinedData` within Cybersource requests is leveraged to pass Epicor Eclipse's `OrderNum` or `InvoiceNum` for direct linking. Payment status changes in Cybersource drive updates in Epicor Eclipse (e.g., Sales Order status, Invoice payment application).

Order

The customer's purchase request, originating from an eCommerce platform, that drives payment processing and sales order creation in Epicor Eclipse.

Epicor Eclipse Fields

[field, SalesOrder.OrderNum],[type, string],[notes, Primary identifier for the sales order in Epicor Eclipse.] [field, SalesOrder.CustomerNum],[type, string],[notes, Links to the customer master in Epicor Eclipse.] [field, SalesOrder.OrderDate],[type, date],[notes, Date the order was placed.] [field, SalesOrder.OrderAmt],[type, decimal],[notes, Total amount of the order.] [field, SalesOrder.OrderStatus],[type, string],[notes, Status reflecting payment and fulfillment progression.] [field, SalesOrder.ShipToAddr],[type, object],[notes, Shipping address details.] [field, SalesOrder.BillToAddr],[type, object],[notes, Billing address details.] [field, SalesOrderDtl.PartNum],[type, string],[notes, Line item product ID.] [field, SalesOrderDtl.OrderQty],[type, decimal],[notes, Line item quantity.]

Cybersource Fields

[field, orderId],[type, string],[notes, Unique ID for the order, often used as `merchantReferenceCode`.] [field, totalAmount],[type, decimal],[notes, Total amount of the order.] [field, currency],[type, string],[notes, Currency of the order.] [field, customerEmail],[type, string],[notes, Customer's email address.] [field, billingAddress],[type, object],[notes, Customer's billing address.] [field, shippingAddress],[type, object],[notes, Customer's shipping address.] [field, lineItems],[type, array],[notes, Details of products/services ordered.] [field, status],[type, string],[notes, Order status (relevant to payment processing).]

Mapping Notes

The Cybersource `orderId` is typically mapped to Epicor Eclipse's `SalesOrder.OrderNum` or a custom field for traceability. Line item details from the eCommerce order, passed to Cybersource for fraud analysis, are also mapped to Epicor Eclipse `SalesOrderDtl` for inventory and fulfillment.

Customer Profile

Customer information, including tokenized payment methods, synchronized to support recurring payments and secure transactions.

Epicor Eclipse Fields

[field, Customer.CustNum],[type, string],[notes, Primary identifier for the customer in Epicor Eclipse.] [field, Customer.Name],[type, string],[notes, Customer's full name.] [field, Customer.Email],[type, string],[notes, Customer's email address.] [field, Customer.BillToAddress],[type, object],[notes, Customer's billing address.] [field, Customer.CybersourceTokenId],[type, string],[notes, Custom field to store the Cybersource payment token for recurring billing.]

Cybersource Fields

[field, customerId],[type, string],[notes, Cybersource's internal customer identifier (if applicable, or mapped from ERP).] [field, firstName],[type, string] [field, lastName],[type, string] [field, email],[type, string] [field, billingAddress],[type, object] [field, cybersourceTokenId],[type, string],[notes, Secure token generated by Cybersource for a payment method.]

Mapping Notes

The `cybersourceTokenId` is a critical piece of data that should be stored in a custom field on the Epicor Eclipse `Customer` record (or a dedicated payment profile object) for future transactions, without storing raw card data. This ensures PCI DSS compliance.

Refund

Represents the return of funds to a customer, linked to an original payment, and reflected as a credit in Epicor Eclipse.

Epicor Eclipse Fields

[field, CreditMemo.CreditMemoNum],[type, string],[notes, Identifier for the credit memo in Epicor Eclipse.] [field, CreditMemo.InvoiceNum],[type, string],[notes, Links to the original invoice.] [field, CreditMemo.Amount],[type, decimal],[notes, Amount of the credit.] [field, GLJournalEntry.DebitCredit],[type, decimal],[notes, For posting refund amounts to respective GL accounts.] [field, Payment.RefundReference],[type, string],[notes, Stores Cybersource refundId for reconciliation.]

Cybersource Fields

[field, refundId],[type, string],[notes, Unique identifier for the refund transaction in Cybersource.] [field, originalTransactionId],[type, string],[notes, The ID of the original payment transaction being refunded.] [field, amount],[type, decimal],[notes, Amount of the refund.] [field, currency],[type, string],[notes, Currency of the refund.] [field, reason],[type, string],[notes, Reason for the refund.] [field, status],[type, string],[notes, Status of the refund (e.g., PENDING, COMPLETED, FAILED).]

Mapping Notes

The `originalTransactionId` from Cybersource is essential to link the refund to its parent payment. In Epicor Eclipse, a refund typically corresponds to a Credit Memo or a direct GL adjustment.

Settlement Batch

Daily aggregate of transactions from Cybersource, used for comprehensive financial reconciliation and posting to Epicor Eclipse General Ledger.

Epicor Eclipse Fields

[field, GLJournalEntry.JournalCode],[type, string],[notes, Code for the journal entry (e.g., 'CYBERSETL').] [field, GLJournalEntry.JournalDate],[type, date],[notes, Date of the settlement.] [field, GLJournalEntry.Description],[type, string],[notes, Description for the journal entry.] [field, GLJournalEntry.DebitCredit],[type, decimal],[notes, Aggregated debit/credit amounts for various accounts (sales, refunds, fees, chargebacks).] [field, GLAccount.AccountNum],[type, string],[notes, Specific GL accounts for sales, fees, refunds, etc.]

Cybersource Fields

[field, batchId],[type, string],[notes, Unique identifier for the settlement batch.] [field, settlementDate],[type, date],[notes, Date of the settlement.] [field, grossAmount],[type, decimal],[notes, Total gross amount of captured transactions.] [field, netAmount],[type, decimal],[notes, Net amount after fees, refunds, chargebacks.] [field, totalFees],[type, decimal],[notes, Total processing fees.] [field, totalRefunds],[type, decimal],[notes, Total refunds processed.] [field, totalChargebacks],[type, decimal],[notes, Total chargebacks incurred.] [field, transactionCount],[type, integer],[notes, Number of transactions in the batch.]

Mapping Notes

The settlement batch data is aggregated and transformed into multiple journal entries in Epicor Eclipse's General Ledger, typically debiting bank accounts and crediting sales, and debiting expense accounts for fees and chargebacks.

Next Steps

See Epicor Eclipse + Cybersource 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-Cash Automation

Automate the entire lifecycle from a customer placing an order online to the payment being processed by Cybersource and the corresponding sales order being created and updated in Epicor Eclipse.

Integration Steps:

0 Customer places order on eCommerce platform.
1 Cybersource authorizes and captures payment securely.
2 iPaaS receives Cybersource payment success webhook.
3 iPaaS creates a new Sales Order in Epicor Eclipse, linking payment details.
4 Order status is updated in eCommerce and Epicor Eclipse.

Business Outcome

Faster order fulfillment, reduced manual data entry, improved order accuracy, accelerated revenue recognition.

Frequency

Real-time, event-driven

Technical Documentation

API Endpoints & Data Logic

Technical details for developers and architects.

Method	Endpoint	Purpose
POST, GET, PUT	/api/v2/SalesOrder	Create, retrieve, or update sales orders in Epicor Eclipse, including payment references. Critical for order-to-cash workflows.
GET, PUT	/api/v2/Customer	Retrieve customer details or update customer payment profiles (e.g., storing Cybersource tokens).
POST, GET, PUT	/api/v2/Invoice	Create invoices or apply payments/credits to existing invoices in Epicor Eclipse.
POST	/api/v2/GLJournalEntry	Post general ledger entries for financial reconciliation of Cybersource settlements, refunds, and fees.
POST, GET	/api/v2/CreditMemo	Create and manage credit memos linked to refunds.

Method	Endpoint	Purpose
POST	/payments/v1/payments	Initiate a payment authorization and/or capture. Core for processing online transactions and linking to Epicor Eclipse sales orders.
POST	/payments/v1/refunds	Process full or partial refunds for previously captured payments, triggering updates in Epicor Eclipse.
POST	/payments/v1/voids	Cancel a payment authorization before it's captured or a captured payment within a certain window, updating Epicor Eclipse.
POST	/tokenization/v1/tokens	Create a secure payment token for customer card data, essential for PCI DSS compliance and recurring billing, storing tokens in Epicor Eclipse customer profiles.
POST	/decisionmanager/v2/decisions	Submit transaction data for real-time fraud screening and decisioning using Cybersource Decision Manager, informing Epicor Eclipse order holds.
GET	/reporting/v3/reports	Retrieve various reports including daily transaction reports and settlement details for financial reconciliation with Epicor Eclipse GL.
GET, PUT, DELETE	/tms/v1/customers/{customer_id}/paymentinstruments	Manage customer payment instruments (tokens) stored in the Cybersource Token Management Service, synchronized with Epicor Eclipse customer profiles.

Event	Name	Payload Data

⚡ Transformation Logic

[rule, Currency Conversion],[description, Automatically convert transaction amounts between Cybersource and Epicor Eclipse's base currency, or handle multi-currency transactions if configured.]
[rule, Status Mapping],[description, Map Cybersource payment statuses (e.g., AUTHORIZED, CAPTURED, REFUNDED) to corresponding Epicor Eclipse Sales Order or Invoice statuses.]
[rule, ID Extraction & Linking],[description, Extract Epicor Eclipse `OrderNum` or `CustomerNum` from Cybersource `merchantDefinedData` for direct linking and lookup.]
[rule, GL Account Derivation],[description, Dynamically determine appropriate Epicor Eclipse General Ledger accounts for settlement amounts, fees, refunds, and chargebacks based on transaction type and predefined rules.]
[rule, Address Normalization],[description, Standardize billing and shipping address formats between systems to ensure consistency and improve data quality.]

🛡️ Error Handling

[scenario, Cybersource Payment Gateway Downtime],[resolution, iPaaS queues requests, implements retries, and notifies administrators. Once service resumes, queued transactions are processed.]
[scenario, Invalid Epicor Eclipse Sales Order ID],[resolution, Transaction routed to dead-letter queue, alert sent to operations, allowing manual correction and re-processing.]
[scenario, Mismatched Currencies],[resolution, iPaaS applies defined currency conversion rules; if conversion fails or is not configured, an alert is triggered.]
[scenario, Duplicate Transaction Attempt],[resolution, Idempotency logic prevents duplicate charges/refunds, logging the attempt as a non-actionable warning.]
[scenario, Cybersource HTTP Signature Failure],[resolution, Immediate alert for credential issues, preventing any further API calls until resolved.]

Support & Information

Frequently Asked Questions

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

General FAQs

▸ What is Cybersource and how does it fit into my enterprise ecosystem?

Cybersource, a Visa solution, is a global payment management platform offering payment gateway, fraud management, and payment security services. In an enterprise ecosystem, it acts as the secure conduit for processing all digital payments, integrating with your eCommerce platform (for online sales), Epicor Eclipse ERP (for financial reconciliation), CRM (for customer payment profiles), and billing systems (for subscriptions).

iPaaS Benefits FAQs

▸ Why should I integrate Cybersource with Epicor Eclipse using an iPaaS instead of custom code?

An iPaaS provides a scalable, low-code/no-code environment for connecting Cybersource to Epicor Eclipse and all your enterprise systems. It offers pre-built connectors, robust data mapping, error handling, and monitoring, significantly reducing development time, maintenance costs, and technical debt compared to custom-coded point-to-point integrations. It also centralizes orchestration and governance, accelerating your time to value.

Fraud Management FAQs

▸ How does iPaaS enhance Cybersource's fraud management capabilities with Epicor Eclipse?

iPaaS can ingest fraud decisions from Cybersource Decision Manager in real-time via webhooks. It can then orchestrate automated responses across systems – such as holding an order in Epicor Eclipse, creating a review task in CRM, notifying a fraud analyst via Slack, or even triggering an AI model for further risk assessment, creating a more dynamic and efficient fraud workflow that proactively protects your revenue.

Security & Compliance FAQs

▸ Is Cybersource integration PCI DSS compliant when using an iPaaS with Epicor Eclipse?

Yes, when implemented correctly. The key is to ensure that your iPaaS and Epicor Eclipse never store or process raw cardholder data. By leveraging Cybersource's tokenization services (e.g., Secure Acceptance), your iPaaS only handles secure tokens, keeping sensitive data out of your environment and significantly reducing your PCI DSS scope and compliance burden.

Financial Reconciliation FAQs

▸ Can I automate payment reconciliation between Cybersource and Epicor Eclipse's General Ledger with iPaaS?

Absolutely. iPaaS can be configured to automatically download daily settlement reports from Cybersource, parse the data (gross sales, refunds, fees, chargebacks), harmonize it with your Epicor Eclipse's chart of accounts, and then create corresponding journal entries or payment batches in your ERP's General Ledger. This dramatically speeds up financial close, reduces manual effort, and improves accuracy.

Technical FAQs

▸ What kind of data transformation is typically needed for Epicor Eclipse Cybersource integrations?

Data transformation often involves mapping eCommerce order fields to Cybersource payment request fields, converting currency formats, harmonizing customer addresses, passing Epicor Eclipse `OrderNum` via `merchantDefinedData`, and transforming Cybersource settlement data into Epicor Eclipse-specific journal entry formats and GL account mappings. iPaaS mapping engines are crucial for these tasks.

▸ How do I manage different Cybersource environments (sandbox, production) with iPaaS for Epicor Eclipse?

A robust iPaaS supports environment promotion pipelines (Dev -> QA -> Prod). This allows you to configure separate Cybersource sandbox API keys and endpoints for testing and then seamlessly promote your integration flows to production using production API keys and endpoints, ensuring proper segregation and thorough testing before impacting live Epicor Eclipse data.

AI Enhancements FAQs

▸ Can AI help with Cybersource data mapping and validation for Epicor Eclipse?

Yes, AI can significantly augment data mapping by suggesting optimal field mappings based on historical data patterns and semantic analysis. For validation, AI can detect anomalies in transaction data, flag potentially incorrect amounts or customer details before they are sent to Cybersource or posted to Epicor Eclipse, improving data quality and reducing errors and reconciliation effort.

Pricing

Simple, transparent pricing for Epicor Eclipse + Cybersource.

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 + Cybersource 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 + Cybersource Integration

See how it works

Connecting with Clarity Connect™

Seamless Integration

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

Access Enabled

Configuration & Mapping

Go Live

Comprehensive Solution Details

Robust & Scalable Integration Architecture

Data Flow Steps

Data Touchpoints

Simple, transparent pricing for Epicor Eclipse + Cybersource.

Clarity Connect

How Middleware Integration Works

Epicor Eclipse

Cybersource

Benefits of Integrating Epicor Eclipse

Payment Initiation & Authorization

Payment Capture & Sales Order Creation

Refund Processing & Credit Memo Creation

Daily Settlement Reconciliation

Fraud Alert & Workflow Orchestration

Benefits of Integrating Cybersource

Payment Initiation & Authorization

Payment Capture & Sales Order Creation

Refund Processing & Credit Memo Creation

Daily Settlement Reconciliation

Fraud Alert & Workflow Orchestration

Data Entity Mapping

Epicor Eclipse Fields

Cybersource Fields

Mapping Notes

Epicor Eclipse Fields

Cybersource Fields

Mapping Notes

Epicor Eclipse Fields

Cybersource Fields

Mapping Notes

Epicor Eclipse Fields

Cybersource Fields

Mapping Notes

Epicor Eclipse Fields

Cybersource Fields

Mapping Notes

See Epicor Eclipse + Cybersource integration in action.

Integration Use Cases

eCommerce Order-to-Cash Automation

Integration Steps:

Business Outcome

Automated Refund Processing

Integration Steps:

Business Outcome

Daily Settlement Reconciliation to ERP GL

Integration Steps:

Business Outcome

AI-Enhanced Fraud Alert & Workflow Automation

Integration Steps:

Business Outcome

Secure Customer Payment Profile & Token Sync

Integration Steps:

Business Outcome

API Endpoints & Data Logic

⚡ Transformation Logic

🛡️ Error Handling

Frequently Asked Questions

General FAQs

iPaaS Benefits FAQs

Secure HIPAA
eCommerce

Any Payment
Gateway

Integrate the
way you want

Start your AI
journey here