Payment Gateway
JustiFi MCP connector
The JustiFi connector brings payments, refunds, sub accounts, fee configurations, payouts, and proceeds into Claude, ChatGPT, Cursor, and the Elaichi agent, so your team can look up and act on JustiFi records in plain language while each person stays inside their own JustiFi access.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect JustiFi to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect JustiFi once
-
Open Connections, choose Add connection, and pick JustiFi.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your JustiFi app credentials. JustiFi authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect JustiFi to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect JustiFi to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect JustiFi to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect JustiFi to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with JustiFi through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Reconcile a day of payments
Pull every JustiFi payment from a given day, match it against the balance transactions and proceeds behind it, and get a short list of anything that does not line up.
-
Support
Refund a customer without leaving the ticket
Find the JustiFi payment a customer is asking about, check its status and amount, and issue a full or partial refund while the conversation is still open.
-
Operations
Onboard a new sub account in minutes
Create a JustiFi sub account for a new merchant or location, review its settings, and confirm its payout account is in place before the first sale.
-
Partnerships
Set and review fee configurations
Look at the fee configuration on a sub account, see what is scheduled to change and what changed in the past, and set up a new one for a partner on custom terms.
-
Finance
Explain a payout to a merchant
Open a JustiFi proceed by its ID, pull the report behind it, and answer exactly which payments and fees made up the amount that landed.
-
Revenue
Catch an authorization before it expires
List JustiFi payments that were authorized but not yet captured, capture the ones that are ready, and void the ones that should not go through.
Try asking
- “Show yesterday's failed payments by sub account.”
- “Which sub accounts have scheduled fee configurations this month?”
- “Summarize proceeds paid out to payout accounts last week.”
AI tools
JustiFi tools for your AI agents
90 tools are ready to call through Elaichi's MCP endpoint the moment you connect JustiFi, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting JustiFi gets you
6 screens from the product, each doing one job for your JustiFi account.
The agent
Ask about payments, read answers from JustiFi.
Plain language questions return live payments, payouts and sub accounts from JustiFi.
- payments
- payouts
- proceeds
- sub accounts
Ask Elaichi to work across your apps.
Show yesterday's failed payments by sub account.
Which sub accounts have scheduled fee configurations this month?
Summarize proceeds paid out to payout accounts last week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach JustiFi here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
90 JustiFi tools ready without custom code.
Browse tool names, resources and methods across payments, proceeds and fee configurations.
- List all JustiFi sub accounts
- Create a JustiFi sub account
- Get single JustiFi sub account by ID
- List all JustiFi sub account payout accounts
Toolboxes
Every team gets its own JustiFi toolbox.
Finance, Support and Risk each work from a toolbox scoped to them.
- Finance
- Support
- Risk
- Onboarding
Shared connections
Teammates use JustiFi accounts, never the keys.
See who connected each account and how many teams and members share it.
- Finance
- Support
- Risk
- Onboarding
Audit log
Every JustiFi call is written down.
When, who, what happened, type and resource for each payment and payout call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, JustiFi payouts move.
Six steps fetch payments, group them, draft a digest, get approval, post back.
JustiFi digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch payments
JustiFi
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
JustiFi
Queued
Collections and dashboards
JustiFi settlement numbers, refreshed on schedule.
Four metrics, fourteen days of payments created and a breakdown by team.
JustiFi health
Refreshed 4 minutes ago · every 15 minutes · from the payments collection
Payments
1,284 ↓ 12%
Payouts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Payments created
Last 14 days
By team
Share of activity
Finance 34%
Support 27%
Risk 21%
Onboarding 18%
FAQ
Frequently asked questions
How do I connect JustiFi to Claude?
Connect JustiFi in Elaichi first: pick JustiFi from the catalog, paste in the app credentials from your JustiFi account when the connection screen asks for them, and save. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude will ask you to sign in to Elaichi as yourself, and JustiFi is available from then on.
Does JustiFi work with ChatGPT and Cursor as well as Claude?
Yes. Once JustiFi is connected in Elaichi, the same https://api.elaichi.ai/mcp endpoint works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi agent. You connect JustiFi once and every client you sign into picks it up.
What can an AI agent actually do with my JustiFi data?
With JustiFi connected, an agent can list and look up payments, take a payment, capture or void an authorization, and issue a refund. It can create and review sub accounts, check their payout accounts and settings, set up or read fee configurations and their history, and pull proceeds and the reports behind them. Because JustiFi exposes a lot of actions, short concrete asks like "refund payment 4821 in full" work better than long paragraphs.
Does connecting JustiFi give the AI access to every account and every payment?
No. Everything an agent does in JustiFi runs under the access of the person who signed in, so it sees the sub accounts, payments, and payouts that person could already reach in JustiFi and nothing more. Elaichi can narrow that further with roles and restrictions, for example read only on payments for a support desk, but it can never widen access beyond what JustiFi itself allows.
Can I stop an agent from refunding, voiding, or changing things in JustiFi?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up JustiFi payments and proceeds while blocking refunds, voids, captures, or fee configuration changes. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however it is worded, can reach it.
What happens to a JustiFi connection when someone leaves?
Offboard the person in Elaichi and their access to JustiFi through every client ends at once, with their past actions still in the append-only audit log. If they were part of a shared JustiFi connection, it keeps working for everyone else on the team. If you want JustiFi gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.
Put JustiFi in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.