Payment Gateway · Beta
Rootline
API integration
Ship Payment Gateway features without building the integration. Full Rootline API access via Proxy and 5 MCP-ready tools for AI agents — extend models and mappings to fit your product.
Built for specific customer use cases. Issues are resolved quickly.
Talk to usUse Cases
Why integrate with Rootline
Common scenarios for SaaS companies building Rootline integrations for their customers.
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
Ship these features with Truto + Rootline
Concrete product features your team can ship faster by leveraging Truto’s Rootline integration instead of building from scratch.
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.
SuperAI
Rootline AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
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.
Why Truto
Why use Truto’s MCP server for Rootline
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 600+ integrations.
Auto-generated, always up to date
Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.
Fine-grained access control
Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.
Multi-tenant by design
Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.
Works with every MCP client
Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.
Built-in auth, rate limits, and error handling
Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.
Expiring and auditable servers
Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.
How It Works
From zero to integrated
Go live with Rootline in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Rootline account
Use Truto’s frontend SDK to connect your customer’s Rootline account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.
We handle authentication
Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.
Call our API, we call Rootline
Truto’s Proxy API is a 1-to-1 mapping of the Rootline API. You call us, we call Rootline, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Rootline’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Rootline on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
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.
From the Blog
Rootline integration guides
Deep dives, architecture guides, and practical tutorials for building Rootline integrations.
Rootline
Get Rootline integrated into your app
Our team understands what it takes to make a Rootline integration successful. A short, crisp 30 minute call with folks who understand the problem.