Introduction
Eclipse is a headless, API-first platform. Every capability — wallet management, card issuance, payments, KYC, reconciliation, reporting — is exposed through a documented REST API. There are no GUI-only workflows and no functionality locked behind a console. This makes Eclipse well-suited to AI-assisted development: any operation a developer can perform, an AI agent can call.
This section covers three ways to build on Eclipse using AI tools.
1. Headless APIs + Skills + MCP
What it is: Build standalone applications, services, or integrations against Eclipse APIs using AI coding tools directly.
Eclipse provides two resources that make AI-assisted API development more reliable:
The MCP Server — Eclipse hosts a Model Context Protocol (MCP) server at https://developer.eftcorp.com/mcp. Connect Claude, Cursor, Copilot, or any MCP-compatible tool once, and the AI agent has authenticated access to Eclipse API documentation, schema definitions, and platform context. This eliminates the need to copy-paste documentation into your AI tool manually.
The AI Skills Library — Skills are curated recipes for specific Eclipse operations. Each skill covers a workflow — authentication, customer onboarding, wallet management, card issuance, payments, withdrawals, KYC, reconciliation — with the correct API call sequence, required fields, and realistic request/response examples. Skills are designed to be loaded into an AI coding session to guide the agent toward correct, idiomatic Eclipse integrations.
The practical workflow:
- Connect your AI tool to the Eclipse MCP server
- Load the relevant skills for your use case from this library
- Describe what you want to build
- The AI generates code that calls real Eclipse APIs with authentication handled by the platform
What you can build: Any application that uses Eclipse capabilities — wallet apps, card companion apps, payment portals, merchant dashboards, mobile applications, backend services. Because Eclipse manages PCI compliance, security, and infrastructure, the code the AI generates is production-capable from the start.
2. Admin Portal Portlets
What it is: Build custom HTML/JavaScript pages and embed them directly inside the Eclipse Admin Portal.
The Eclipse Admin Portal supports portlets — any web page registered with the portal appears as a native section in the navigation. Eclipse handles authentication automatically via lightweight OIDC: when a portal user navigates to a portlet, Eclipse injects a signed JWT into the page context. No auth code is required in the portlet itself.
This means:
- Your page has access to the authenticated user's tenant, organisation, and role context
- You can call Eclipse APIs directly from the portlet using the injected JWT
- The portlet appears inside the Eclipse admin UI, branded and context-aware, without any portal code changes
With AI: An AI tool can generate a complete, functional portlet — a custom transaction dashboard, reconciliation view, merchant analytics page, or brand configurator — using the Eclipse APIs and the injected JWT. Register the URL with the portal and it is live immediately.
3. Runtime Plugins
What it is: Extend or override Eclipse core platform behaviour by uploading a compiled JAR. Eclipse hot-loads the plugin at runtime — no deployment required, no source code access needed.
Plugins interact with Eclipse through defined extension points:
| Plugin type | What it can do |
|---|---|
| Injection-point plugins | Hook into wallet transfers, transactions, HTTP requests, and domain events — listen, mutate, or short-circuit |
| Implementation plugins | Fully replace a platform interface — fraud engine, notification handler, custom payment gateway |
Eclipse exposes 11 wallet events that plugins can handle. Plugins can:
- Override wallet behaviour (credit/debit logic, limits, validations)
- Add new payment rails and gateway integrations
- Write custom fraud and risk engines
- Intercept and transform transactions in flight
- Handle any of the supported domain events
With AI: AI tools generate the plugin skeleton from the base classes and interface definitions. You define the business logic. A working plugin can be uploaded and live in Eclipse within hours of starting.
Choosing the Right Approach
| Scenario | Recommended approach |
|---|---|
| Building a customer-facing mobile or web app | Headless APIs + Skills |
| Building a backend service or integration | Headless APIs + Skills |
| Embedding an ops tool inside the Eclipse admin UI | Admin Portal Portlet |
| Adding a custom dashboard or analytics view for operators | Admin Portal Portlet |
| Adding a new payment rail or gateway | Runtime Plugin |
| Overriding wallet behaviour or adding custom fraud logic | Runtime Plugin |
| Extending platform behaviour without modifying platform code | Runtime Plugin |
The three approaches are not mutually exclusive. A common pattern is to build a customer-facing application using the headless APIs, a custom ops view using a portlet, and connect them to custom business logic in a plugin.
Updated about 7 hours ago