Pricing

The Donations SDK ships in two pricing tiers. Both tiers ship with the same browser embed, server SDKs in TypeScript/Node and Python, signed webhooks, sandbox keys, and PCI SAQ A scope — only the per-donation rate structure and monthly platform fee differ.

Flat-rate processing is the default for churches that already subscribe to the 1st Flock Finance product. The tier carries no additional monthly fee — donation processing is included in the Finance subscription — and applies a single, predictable rate to every donation regardless of card type. This is the right tier for low- and mid-volume programs that want one number on a budget line.

Interchange + markup ("cost-plus") is the right tier for high-volume programs. The underlying card-network interchange cost is passed straight through to your church with no markup, and a transparent platform markup is billed on top. Because card-network interchange varies by card type (consumer credit vs debit vs commercial), high-volume programs typically save several basis points compared to the flat tier — at the cost of a small monthly platform fee and a slightly less predictable per-donation total.

The widget below shows the live rates pulled from the 1st Flock pricing API. Numbers are never cached client-side longer than five minutes, so admin edits to the cost-plus markup configuration propagate to this page within minutes — never a deploy. If the pricing API is unreachable, the widget falls back to a "Contact sales" prompt rather than display a stale or hardcoded number.

Choosing a tier

The decision is almost entirely about volume. A program processing under roughly $10,000 a month in donations will usually come out ahead on the flat tier — the predictable monthly cost is a wash against the slightly higher per-transaction rate. A program processing $50,000 or more a month will usually come out ahead on the interchange-plus tier — the savings on every transaction more than cover the small monthly platform fee. The middle band depends heavily on the specific mix of card types your donors use.

If you are not sure which tier fits, contact sales and we will run the numbers against your last 90 days of donation history. Switching tiers later is also a single click in the donations subscription hub — there is no annual commitment on either tier.

What the rates cover

Both tiers cover identical capability:

• Browser embed — the <flock-donate> web component plus the React <FlockDonate> wrapper, with all seventeen configuration attributes available on every tier.
• Server SDKs — TypeScript/Node and Python clients, each with the full surface (donations, refunds, recurring schedules, signed-webhook helpers, synthetic-event triggers for integration tests).
• Signed webhooks — nine event types, HMAC-SHA256 signatures, 5-minute replay window, exponential-backoff redelivery on failure, constant-time verifier in every SDK.
• Sandbox mode — pk_test_… / sk_test_… keys route every call to the sandbox cluster; identical wire format and webhook events; no real money moves.
• PCI SAQ A scope — donor card data is tokenised inside an isolated iframe before it ever reaches your code.

Note: ACH uses a different per-transaction rate from card donations — see the rate breakdown above for the current ACH and card rates. Recurring schedules don't add surcharges over one-time gifts on either tier. Live numbers in the widget below are read from the API on every page load (five-minute browser cache). If they appear blank or you see a "Contact sales" prompt, the pricing service is temporarily unreachable — refresh the page in a minute or email sales.