Payment Gateway
Peach
API integration
Ship Payment Gateway features without building the integration. Full Peach API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.
Talk to usUse Cases
Why integrate with Peach
Common scenarios for SaaS companies building Peach integrations for their customers.
Power giving-day platforms with live campaign stats
Fundraising and crowdfunding SaaS products can process donations through Peach and pull real-time campaign statistics to render live thermometers, leaderboards, and ambassador rankings on their own frontends.
Sync donor identities into nonprofit CRMs
Donor management and CRM platforms can create and update Peach contacts—including the Israeli `tz` needed for tax receipts—so donor records stay consistent across the nonprofit's stack without manual data entry.
Automate donor win-back and engagement workflows
Marketing automation tools can react to donation activity, trigger email sequences, and log those touchpoints as notes on the donor's Peach profile so nonprofit staff have a unified interaction history.
Automate nonprofit bookkeeping and reconciliation
Accounting and ERP SaaS built for nonprofits can pull transactions from Peach on a schedule, categorize them by campaign, and reconcile donation amounts against bank deposits—eliminating manual CSV exports.
Enable self-serve donor portals for recurring giving
SaaS products can let donors or nonprofit admins manage subscriptions—updating or canceling recurring gifts—directly inside a third-party dashboard by calling Peach's payment update endpoint.
What You Can Build
Ship these features with Truto + Peach
Concrete product features your team can ship faster by leveraging Truto’s Peach integration instead of building from scratch.
Live fundraising thermometer and leaderboard
Use campaign stats to render real-time totals raised, donor counts, and per-ambassador breakdowns on your platform's public campaign pages.
Donor profile sync with Israeli tax compliance
Create and update Peach contacts with `tz`, email, phone, and name so your CRM stays deduplicated and tax-receipt-ready.
Recurring donation management console
Let admins or donors update, pause, or cancel subscription payments in Peach from your own dashboard via the payment update endpoint.
Nightly transaction reconciliation job
Search Peach transactions by date range and campaign to feed a general ledger, categorize donations, and match them to deposits.
Donor timeline enrichment
Append contextual notes to a donor's Peach profile whenever they engage with your platform—emails opened, events attended, or forms submitted.
Bulk donor cleanup tooling
Offer admins the ability to remove test or duplicate donor records at scale using Peach's bulk contact delete operation.
SuperAI
Peach AI agent tools
Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.
get_single_peach_campaign_by_id
Get a specific peach campaign by id. Returns: updatedAt, type, limit, startDate, endDate. Required: id.
peach_campaigns_get_stats
Get detailed public statistics for a specific peach campaign including total amount raised, donation count, and per-group breakdowns. Returns: limit, startDate, endDate. Required: account_id, campaign_id.
create_a_peach_payment
Create a payment in Peach. Returns the created payment object including paymentId, status, donationSum, donationCurrency, donorDisplayName, email, campaignId, and createdAt. Required: sum. Currency defaults to ILS; billingCycles is required when isSubscription is true.
update_a_peach_payment_by_id
Update a payment in Peach by performing an action such as canceling a subscription, changing the charge day, freezing, or updating a payment field. Returns: message. Required: id, action.
create_a_peach_contact
Create a new contact in Peach. Returns: contactBody, contactResponse, contactId, failedCustomProperties. Required: firstName, lastName, email.
get_single_peach_contact_by_id
Get a single Peach contact by contactId, email, phoneNumber, or tz. Returns: email, contactId. At least one of contactId, email, phoneNumber, or tz must be provided.
update_a_peach_contact_by_id
Update an existing Peach contact by id. Returns: success, message, contact. Required: id.
peach_contacts_bulk_delete
Delete a Peach contact by contactId. Returns: success, message. Required: contactId.
peach_interactions_create_note
Create a note for a contact in Peach. Returns the created note object (noteBody) with category, contactId, noteTitle, noteBody, and source, plus an interactionResponse identifier. Required: contactId, noteBody.
list_all_peach_search_transactions
Search Peach transactions within a date range, optionally filtered by campaign. Returns: createdAt, updatedAt. Date range defaults to the last 30 days; max 1000 results per page.
Why Truto
Why use Truto’s MCP server for Peach
Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 650+ 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 Peach in under an hour. No boilerplate, no maintenance burden.
Link your customer’s Peach account
Use Truto’s frontend SDK to connect your customer’s Peach 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 Peach
Truto’s Proxy API is a 1-to-1 mapping of the Peach API. You call us, we call Peach, and pass the response back in the same cycle.
Unified response format
Every response follows a single format across all integrations. We translate Peach’s pagination into unified cursor-based pagination. Data is always in the result attribute.
FAQs
Common questions about Peach on Truto
Authentication, rate limits, data freshness, and everything else you need to know before you integrate.
How does authentication with Peach work through Truto?
Your end users connect their Peach account through Truto's managed auth flow. Truto stores and refreshes credentials so your application never handles Peach API keys directly.
Which Peach operations are supported today?
The current integration supports creating and updating payments, creating/reading/updating contacts and bulk-deleting them, creating interaction notes, fetching a single campaign by ID, retrieving campaign statistics, and searching transactions.
Can I manage recurring donations (subscriptions) via the API?
Yes. Recurring gifts are represented as payments with `isSubscription` and `billingCycles`, and you can modify them—for example to pause or cancel—using the update payment endpoint.
Does the integration support Israeli tax compliance fields like `tz`?
Yes. The contact endpoints accept the `tz` (Israeli national ID / company number) alongside standard PII, which is what Peach uses to generate tax-deductible receipts.
How fresh is campaign and transaction data?
Data is fetched on demand from Peach's API at call time, so campaign stats and transaction searches reflect Peach's latest state. For live leaderboards or reconciliation jobs, you control the polling cadence.
Can I search historical transactions for reconciliation?
Yes. The transaction search endpoint lets you filter by date range and campaign, which is the primary building block for nightly reconciliation and finance reporting workflows.
From the Blog
Peach integration guides
Deep dives, architecture guides, and practical tutorials for building Peach integrations.
Peach
Get Peach integrated into your app
Our team understands what it takes to make a Peach integration successful. A short, crisp 30 minute call with folks who understand the problem.