Pushpay Church Giving & ChMS API

Pushpay REST API for church giving and community management platform. Enables AI agents to manage giving records and donor profiles, process recurring donations and one-time gifts, retrieve church membership and engagement data, manage campuses and funds, access giving analytics and reports, handle check-in and group data, and integrate church financial data with accounting and ChMS systems.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Other pushpay church giving tithing church-management chms faith nonprofit-payments
⚙ Agent Friendliness
55
/ 100
Can an agent use this?
🔒 Security
72
/ 100
Is it safe for agents?
⚡ Reliability
67
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
22
Documentation
70
Error Messages
65
Auth Simplicity
65
Rate Limits
60

🔒 Security

TLS Enforcement
92
Auth Strength
70
Scope Granularity
65
Dep. Hygiene
65
Secret Handling
68

Church giving and membership data. PCI-DSS, SOC2. OAuth2 with scopes. US data residency.

⚡ Reliability

Uptime/SLA
72
Version Stability
68
Breaking Changes
62
Error Recovery
65
AF Security Reliability

Best When

A church using Pushpay wants AI agents to automate giving tracking, donor engagement analysis, multi-site fund reporting, and integration with accounting systems.

Avoid When

PRIVACY: Donor giving and church membership data is sensitive personal information. Religious affiliation data has heightened privacy protections. Financial giving data requires careful stewardship.

Use Cases

  • Retrieving donor giving history and recurring gift status from stewardship agents
  • Accessing membership and engagement data from congregation management agents
  • Generating giving reports for fund accounting from finance reporting agents
  • Managing campus and fund data from multi-site church management agents

Not For

  • Non-religious organizations without church giving and tithing focus
  • General nonprofit fundraising without church community management
  • Commercial payment processing without faith community workflows

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
Yes

Authentication

Methods: oauth
OAuth: Yes Scopes: Yes

Pushpay uses OAuth 2.0 for API access. Organization-level credentials. Scopes control access to payments, people, and reporting data. Partner program for ChMS and technology integrations.

Pricing

Model: enterprise
Free tier: No
Requires CC: No

New Zealand company (Auckland), public company on ASX until taken private in 2023. Includes Church Community Builder (CCB) ChMS acquired 2019. Dominant church giving platform in North America.

Agent Metadata

Pagination
page
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • PRIVACY: Religious giving and membership data requires heightened sensitivity
  • No public MCP server — REST API with OAuth2 partner program
  • Pushpay + CCB (Church Community Builder) are integrated but have different API surfaces
  • NZ/US company — US data residency; taken private in 2023
  • Transaction-based pricing — automated giving processing must account for fees
  • ACH and card processing have different processing timelines — verify fund availability

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Pushpay Church Giving & ChMS API.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered