Butterpayments

Butter Payments is a payment recovery and involuntary-churn platform that uses machine learning to recover revenue from failed subscription payments. Its Recover product ingests real-time transaction and payment-method events, optimizes retry timing, and reports outcomes back to merchants via HMAC-SHA256 signed webhooks; Dispute (powered by Verifi) intercepts chargebacks and runs Rapid Dispute Resolution; PaymentScore identifies recoverable failed payments; and a PCI DSS Level 2 Card Vault secures card data behind a secure-iframe element. Butter integrates turnkey with Stripe Billing, Braintree, and Recharge, or directly through the Recover Enterprise API.

Butterpayments publishes 1 API on the APIs.io network. Tagged areas include Company, Payments, Payment Recovery, Subscription, and Dunning.

The Butterpayments catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Butterpayments’ developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, authentication, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub

44.8/100 developing ▬ flat Agent 20/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Payments Payment Recovery Subscription DunningInvoluntary ChurnDispute PreventionChargebacksCard VaultFintech Machine-Learning

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 44.8/100 · developing

Contract Quality 8.8 / 21

Developer Ergonomics 10.9 / 17

Access Clarity 6.7 / 17

Operational Transparency 0.9 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 7.7 / 15

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/butterpayments: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Recover Enterprise API

Source-agnostic payment-event ingestion API for payment recovery. Merchants POST standardized successful and failed payment events and payment-method updates; Recover optimizes ...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Butterpayments Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Butterpayments Authentication

apiKey/http/hmac · 5 schemes

SECURITY

Butterpayments Domain Security

TLSv1.2 · DNSSEC · DMARC

SECURITY

Butterpayments Trust Center

SOC 2 Type 2, HIPAA, PCI DSS Level 2

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

Webhooks

Components

DataModel

Conformance

Access & Security 4

Authentication, authorization, and security posture

Authentication

Compliance

TrustCenter

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: butterpayments
name: Butterpayments
description: Butter Payments is a payment recovery and involuntary-churn platform that uses machine learning to recover revenue
  from failed subscription payments. Its Recover product ingests real-time transaction and payment-method events, optimizes
  retry timing, and reports outcomes back to merchants via HMAC-SHA256 signed webhooks; Dispute (powered by Verifi) intercepts
  chargebacks and runs Rapid Dispute Resolution; PaymentScore identifies recoverable failed payments; and a PCI DSS Level
  2 Card Vault secures card data behind a secure-iframe element. Butter integrates turnkey with Stripe Billing, Braintree,
  and Recharge, or directly through the Recover Enterprise API.
url: https://raw.githubusercontent.com/api-evangelist/butterpayments/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://cdn.prod.website-files.com/6570760e6e7b5aa59f8f2452/657b7105d992d17f87a2d0e2_hero-img-m.avif
x-type: company
x-source: vc-portfolio
x-backed-by:
- norwest-venture-partners
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Payments
- Payment Recovery
- Subscription
- Dunning
- Involuntary Churn
- Dispute Prevention
- Chargebacks
- Card Vault
- Fintech
- Machine-Learning
tags_raw:
- Company
- Payments
- Payment Recovery
- Subscriptions
- Dunning
- Involuntary Churn
- Dispute Prevention
- Chargebacks
- Card Vault
- Fintech
- Machine Learning
apis:
- name: Recover Enterprise API
  description: Source-agnostic payment-event ingestion API for payment recovery. Merchants POST standardized successful and
    failed payment events and payment-method updates; Recover optimizes retry timing and reports retry outcomes and end-of-dunning
    back through signed webhooks.
  humanURL: https://docs.services.butterpayments.com/api-reference
  baseURL: https://api.butterpayments.com
  tags:
  - Payments
  - Payment Recovery
  - Dunning
  properties:
  - type: APIReference
    url: https://docs.services.butterpayments.com/api-reference
  - type: Authentication
    url: authentication/butterpayments-authentication.yml
  - type: Webhooks
    url: asyncapi/butterpayments-webhooks.yml
  - type: DataModel
    url: data-model/butterpayments-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/butterpayments-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://butterpayments.com
- type: DeveloperPortal
  url: https://docs.services.butterpayments.com/
- type: Documentation
  url: https://docs.services.butterpayments.com/
- type: APIReference
  url: https://docs.services.butterpayments.com/api-reference
- type: GettingStarted
  url: https://docs.services.butterpayments.com/integration-guide
- type: Blog
  url: https://butterpayments.com/blog
- type: Support
  url: https://butterpayments.com/faq
- type: Pricing
  url: https://butterpayments.com/pricing
- type: TermsOfService
  url: https://butterpayments.com/terms-of-use
- type: PrivacyPolicy
  url: https://butterpayments.com/privacy-policy
- type: Authentication
  url: authentication/butterpayments-authentication.yml
- type: Conventions
  url: conventions/butterpayments-conventions.yml
- type: Webhooks
  url: asyncapi/butterpayments-webhooks.yml
- type: Components
  url: components/butterpayments-components.yml
- type: Sandbox
  url: sandbox/butterpayments-sandbox.yml
- type: DataModel
  url: data-model/butterpayments-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/butterpayments-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/butterpayments-llms.txt
- type: Conformance
  url: conformance/butterpayments-conformance.yml
- type: Compliance
  url: https://security.butterpayments.com/
- type: TrustCenter
  url: security/butterpayments-trust-center.yml
- type: DomainSecurity
  url: security/butterpayments-domain-security.yml
- type: WellKnown
  url: well-known/butterpayments-well-known.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/butterpayments"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/butterpayments/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/butterpayments/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.