--- title: Rootline API Integration on Truto slug: rootline category: Payment Gateway canonical: "https://truto.one/integrations/detail/rootline/" --- # Rootline API Integration on Truto **Category:** Payment Gateway **Status:** Beta ## MCP-ready AI tools Truto exposes 5 tools for Rootline that AI agents can call directly. - **create_a_rootline_payment** — 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 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** — 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** — 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** — 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. ## How it works 1. **Link your customer's Rootline account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Rootline.** The Proxy API is a 1-to-1 mapping of the Rootline API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Embed marketplace payments with automatic fee splits** — Marketplaces and vertical SaaS platforms can offer their sellers native checkout while automatically routing a platform fee to their own account on every transaction. Truto lets you ship this without directly integrating with Rootline's payment lifecycle endpoints. - **Enable booking platforms to authorize now, capture later** — Scheduling, venue, and reservation SaaS products can hold funds when a booking is placed and only move money once the service is fulfilled. If the booking is cancelled, the hold is released cleanly with no manual reconciliation. - **Automate invoice reconciliation for accounting and billing SaaS** — Invoicing and B2B billing tools can fetch payment status directly from Rootline to flip invoices to 'Paid' the moment funds clear. This removes manual bookkeeping for their end users and keeps ledgers accurate. - **Offer built-in refund and dispute handling to end users** — SaaS platforms can expose refund controls inside their own dashboards, letting merchants issue full or partial refunds without leaving the product. This reduces support overhead and gives end users self-serve control over customer returns. - **Power multi-party payouts for gig and service platforms** — Platforms managing payments between buyers, sellers, and their own revenue line can dispatch a single transaction that splits funds across all stakeholders. This eliminates custom middleware for calculating and reconciling per-transaction distributions. ## What you can build - **Embedded checkout with dynamic platform fees** — Create Rootline payments from inside your product and configure per-transaction splits so a portion of every payment automatically routes to your platform's revenue account. - **Two-step authorization and capture workflows** — Authorize a card at booking or order time and programmatically trigger capture only when the service is delivered, using Rootline's capture endpoint. - **Automated hold releases on cancellation** — Wire your cancellation flows to Rootline's cancel endpoint so authorized-but-uncaptured holds are dropped instantly when an order or reservation is voided. - **Self-serve refunds inside your app** — Let end users issue full or partial refunds against the original payment ID without leaving your product, backed by Rootline's refund endpoint. - **Real-time payment status sync** — Poll payment records by ID to keep your internal state, invoice dashboards, and CRM records in sync with Rootline's checkout status. - **Multi-stakeholder split payouts** — Send a single payment request that divides funds across seller, platform, and other sub-accounts, so complex payouts don't require custom reconciliation logic on your side. ## FAQs ### Which Rootline operations are available through Truto today? Truto currently exposes five Rootline operations: create a payment, get a single payment by ID, cancel a payment, create a payment capture, and create a payment refund. Additional endpoints can be added on request. ### Is there a unified Payments API for Rootline? Rootline is available as a direct integration only — there is no unified Payments abstraction yet. You'll work with Rootline's native payload shape (account_id, amount, reference, splits, etc.) through Truto's proxy. ### How does authentication work for end users connecting their Rootline account? Truto manages the credential handshake and stores connection tokens per end user, so your product doesn't need to build or persist Rootline auth flows. Each API call is routed with the correct end-user credentials automatically. ### Can I support split payments and platform fees? Yes. The create payment operation accepts a splits array, letting you divide a single transaction across the seller's account_id and your platform's revenue account in one call. ### How do I keep payment status in sync with my application? You can poll the get single payment by ID endpoint to read checkout_status, payment_rails, and customer data, then update your internal records accordingly. Webhook forwarding can be configured if Rootline emits events for the flows you need. ### Can I issue partial refunds or only full refunds? The create payment refund operation supports both partial and full refunds against the original payment_id, so you can expose either flow to your end users. ## Related reading - [Connect Rootline to Claude: Track Status and Cancel Payments](https://truto.one/blog/connect-rootline-to-claude-track-status-and-cancel-payments/) — Learn how to connect Rootline to Claude using a managed MCP server. Automate payment orchestration, status tracking, and refunds directly from Claude. - [Connect Rootline to ChatGPT: Automate Payments and Refund Cycles](https://truto.one/blog/connect-rootline-to-chatgpt-automate-payments-and-refund-cycles/) — Learn how to connect Rootline to ChatGPT using a managed MCP server. This technical guide covers automating payments, captures, and refund cycles securely. - [Connect Rootline to Claude: Automate Payment Creation and Tracking](https://truto.one/blog/connect-rootline-to-claude-automate-payment-creation-and-tracking/) — Learn how to build a managed MCP server to connect Rootline to Claude. Automate payment creation, captures, and refunds using natural language. - [Connect Rootline to ChatGPT: Manage Payments, Captures and Refunds](https://truto.one/blog/connect-rootline-to-chatgpt-manage-payments-captures-and-refunds/) — Learn how to connect Rootline to ChatGPT using a managed MCP server. Execute payments, captures, and refunds directly from AI prompts. - [Connect Rootline to AI Agents: Orchestrate Captures and Splits](https://truto.one/blog/connect-rootline-to-ai-agents-orchestrate-captures-and-splits/) — Learn how to connect Rootline to AI agents using Truto's /tools endpoint. Build autonomous payment workflows, orchestrate captures, and handle split logic.