Skip to content

Payment Gateway

Rootline MCP connector

The Rootline connector lets Claude, ChatGPT, Cursor, and other MCP clients create, look up, cancel, capture, and refund Rootline payments as the signed-in person, with restrictions per action and every call recorded in an audit log.

  • How it connects. Connects with an API key. 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 Rootline to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Rootline once

  1. Open Connections, choose Add connection, and pick Rootline.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Rootline API key. One person generates a token in Rootline and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

rootline
Rootline
Chimoney
Circle
Dwolla
Finexio
Flutterwave
2

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 Rootline to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Rootline to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Rootline to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Rootline to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Rootline through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Refund a customer without leaving the chat

    When a customer writes in about a wrong charge, pull up the Rootline payment by its ID, check the amount, and issue the refund from the same conversation.

  • Finance

    Check a payment before you reconcile

    Ask for a Rootline payment by its ID and read back its amount and status, so you know whether it was captured, cancelled, or refunded before you close the books.

  • Operations

    Capture authorized payments once orders ship

    When the warehouse confirms an order has left, capture the authorized Rootline payment so the customer is charged for what actually shipped.

  • Sales

    Create a payment for a custom quote

    After agreeing a price on a call, create the Rootline payment for that amount while the customer is still on the line.

  • Support

    Cancel a payment the customer no longer wants

    If a customer changes their mind before the charge is captured, cancel the pending Rootline payment instead of charging and refunding later.

  • Finance

    Refund the returned part of an order

    When only some items come back, refund the matching amount against the original Rootline payment and leave the rest of the charge in place.

Try asking

  • “Show Rootline payments captured this week over 500.”
  • “Summarize Rootline refunds issued in the last 7 days.”
  • “List Rootline payments canceled yesterday and their amounts.”

See all 5 Rootline tools below

AI tools

Rootline tools for your AI agents

5 tools are ready to call through Elaichi's MCP endpoint the moment you connect Rootline, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Rootline gets you

6 screens from the product, each doing one job for your Rootline account.

The agent

Ask about Rootline payments in plain language.

Starter prompts pull live Rootline payments, captures and refunds into a direct answer.

  • payments
  • captures
  • refunds
  • cancelations

Ask Elaichi to work across your apps.

Show Rootline payments captured this week over 500.

Summarize Rootline refunds issued in the last 7 days.

List Rootline payments canceled yesterday and their amounts.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Rootline here.

One org MCP endpoint over OAuth, no SDK and no shared Rootline API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

5 Rootline tools ready without custom code.

Browse tool names, resources and methods across Rootline payments, captures and refunds.

  • Create a Rootline payment
  • Get single Rootline payment by ID
  • Rootline payments cancel
  • Create a Rootline payment capture
ElaichiTools
Tool Action Description
Create a Rootline payment Create Create a payment in Rootline using account_id, reference, amount, and splits. Returns id, amount, checkout_status, and reference to track and manage the created payment.
Get single Rootline payment by ID Get Get payment details in Rootline using id. Returns fields such as id, amount, account_id, checkout_status, customer, and payment_rails to provide complete payment and status information.
Rootline payments cancel Cancel Create a payment in Rootline using required parameters account_id, reference, amount, and splits. Returns fields such as id, amount, checkout_status, and payment_rails for tracking and payment details.
Create a Rootline payment capture Create Capture the authorized payment amount from a customer's payment method in rootline. Returns: id, object, created_at, reference. Required: payment_id.
Create a Rootline payment refund Create Initiate a refund to a customer's payment method in Rootline. Returns the refund response object including id, object, and created_at. Required: payment_id.

Toolboxes

Every team gets its own Rootline toolbox.

Toolboxes are scoped per team, so finance and support see different Rootline tools.

  • Finance
  • Support
  • Risk
  • Engineering
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

Rootline · payments and captures

Rootline starter 18 Mar 4, 2026

Support toolbox

Rootline · refunds and cancelations

9 Mar 2, 2026

Risk toolbox

Rootline · flagged payments

24 Feb 27, 2026

Engineering toolbox

Rootline · payment creation

Rootline starter 6 Feb 19, 2026

Billing Ops toolbox

Rootline · capture reconciliation

31 Jan 30, 2026

Revenue toolbox

Rootline · payment reporting

12 Jan 22, 2026

Shared connections

Teammates use Rootline without seeing a key.

The connections table shows who connected each Rootline account and how widely it is shared.

  • Finance EMEA
  • Support
  • Billing Ops
  • Risk Review
ElaichiConnections
Connection Scope Status Access
RO

Rootline (Finance EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
RO

Rootline (Support)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
RO

Rootline (Billing Ops)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
RO

Rootline (Risk Review)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
RO

Rootline (Marketplace)

Connected by Clara Nowak

Personal • Active Not shared
RO

Rootline (Enterprise Accounts)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who refunded which Rootline payment.

Append-only entries record when, who, what happened, type and Rootline resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Rootline Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Rootline Payments Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Rootline Payments List Toolbox

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 drafts your Rootline refund digest.

Six steps fetch and group Rootline payments, draft a digest, await approval, post back.

Rootline digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch payments

    Rootline

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Rootline

    Queued

Collections and dashboards

Rootline payment health, computed on a schedule.

Four metrics, 14 days of payments created and a team breakdown, no model involved.

Rootline health

Refreshed 4 minutes ago · every 15 minutes · from the payments collection

Live

Payments

1,284 ↓ 12%

Captures

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Payments created

Last 14 days

By team

Share of activity

Finance EMEA 34%

Support 27%

Billing Ops 21%

Risk Review 18%

FAQ

Frequently asked questions

How do I connect Rootline to Claude?

Connecting Rootline to Claude takes two steps. First, open Elaichi, choose Rootline, and paste in your Rootline API key; there is no OAuth application to register and no client ID or secret to generate. Then in Claude, go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on Rootline payments are available in your conversations.

Does Rootline work with ChatGPT and Cursor as well as Claude?

Yes. Once Rootline is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Rootline once and every client you use picks it up.

What can an AI agent actually do with my Rootline data?

With Rootline connected, an agent can create a new payment, look up an existing payment by its ID to see its amount and status, cancel a payment that has not been captured, capture an authorized payment, and issue a refund. In practice that means a support agent can ask Claude to find a customer's Rootline payment and refund it, or an operations lead can ask it to capture a payment once an order ships. This connector covers those five actions on Rootline payments and nothing beyond them.

Does connecting Rootline give the AI access to every payment?

An agent working through Elaichi can only do what the Rootline API key it was connected with allows, and Elaichi can narrow that access further but never widen it. If the key can only read payments, the agent can only read payments. Restrictions in Elaichi let you take actions such as refunds or cancellations away from the AI entirely, so Rootline access through Elaichi is always equal to or smaller than what the person who connected it holds.

Can my team share one Rootline connection?

Yes. One person connects Rootline in Elaichi with the API key and shares the connection with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so when someone refunds or cancels a Rootline payment the audit log records their name, not a shared account.

Can I stop an agent from refunding or cancelling payments in Rootline?

Yes. Restrictions in Elaichi apply per action, so you can allow an agent to look up Rootline payments while blocking refunds, cancellations, or captures. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Rootline connection when someone leaves?

When you offboard a person in Elaichi, their access to Rootline through every client ends at once. If they were using a shared Rootline connection, it keeps working for everyone else on the team. If you want to remove Rootline entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other connected client.

Put Rootline in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.