Subscription Billing & Revenue Management › Payment Collection & Dunning

Payment Collection & Dunning

BC-4250.40 Level 2 Software & Technology 78 providers 113 API surfaces 25 rated strong or better

Payment-method management, payment authorisation, dunning, and involuntary churn recovery.

Payment Collection & Dunning (BC-4250.40) is a level-2 business capability under Subscription Billing & Revenue Management in the Software & Technology model. The catalog holds 113 API surface(s) from 78 provider(s) that can perform some part of it, 25 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Payment Method Management BC-4250.40.10

Capture and stewardship of customer payment methods and tokens.

no catalog coverage

Payment Authorisation BC-4250.40.20

Authorisation and capture of recurring payments through payment processors.

no catalog coverage

Dunning Workflow BC-4250.40.30

Automated dunning sequences for failed payments and ageing balances.

no catalog coverage

Involuntary Churn Recovery BC-4250.40.40

Recovery of subscriptions lost due to expired cards, hard declines, and similar payment failures.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 12 Complete, well-documented, and agent-ready
XquikGuest WalletsSubscribe2 APIs88.7OptimizelyPaymentauthentication1 API80.8TelnyxAutoRechargePreferences1 API79.6TabbyPayments1 API77.1Microsoft AzurePaymentMethods1 API76.2LeadpingPaymentMethods1 API74.9DrippayDunning1 API72.0NetlifypaymentMethod1 API71.5ClerkPayment AttemptsPayment Methods2 APIs71.4PAY.JPCharges1 API70.8DocusignPayments1 API69.8Hint HealthPaymentMethod1 API69.0
Strong 13 Solid coverage with minor gaps
NexGen CloudPaymentauto-topup2 APIs65.9PayMongoPayment IntentsPayment Methods2 APIs65.2Commerce Layerpayment_methodspaypal_payments2 APIs65.1KoyebPaymentMethods1 API63.5TelrRemote1 API62.6SolvimonpaymentMethodspaymentSchedulespayments3 APIs60.7AppDirectAppResellerPaymentMethodPaymentPayment MethodsPaymentInstrument4 APIs58.0LaserDataPayments1 API58.0ParlayAPIBilling1 API57.8Altimate AIPAYMENT1 API55.4OpenRelayBilling1 API55.1BuiltWithMppx1 API54.9RainforestPayinsPayment Methods2 APIs54.3
Developing 25 Usable, with meaningful gaps to close
DealHubPayments1 API54.2FermyonPayments1 API53.8SAP BRIM (Billing and Revenue Innovation Management)Balances1 API53.5RapidataPayment1 API52.9SpreedlyPayment MethodsPurchaseTransactions3 APIs52.4CobotSpace Payment Method1 API51.7MTN Grouppayment methods1 API51.6Red Hat 3scalePayment Transactions1 API51.0CSG SystemsPayment MethodsTransactions2 APIs50.5AmazonCharges1 API48.9Elastic PathDunning Rules1 API48.9TessellPayment1 API48.7KushkiPre-Authorization1 API48.6ChargebeePayments1 API48.5Akash NetworkPayment1 API47.5KalturahouseholdPaymentGatewayhouseholdPaymentMethod2 APIs47.4CodagBilling1 API47.0PrimerPayment Methods APIPayments API2 APIs46.7Unlock ProtocolPurchase1 API45.9ZeroSettleCheckout1 API45.7KumospacePayments1 API45.2AivenOrganizationPaymentMethodPayment2 APIs44.8SmokeballSubscription Payments1 API42.5EBANXPayments1 API41.2Packet HostPaymentMethods1 API40.5
Thin 27 Limited public surface area
MetronomePayments1 API38.9BraintreePayment MethodsTransactions2 APIs38.7ChargeDeskGateway1 API38.2PaidyPayments1 API37.8NetBirdCheckout1 API37.3ReachwarePayments1 API36.9EquinixPaymentMethods1 API36.6ZuoraCustom Payment Method TypesPayment AuthorizationPayment Gateway ReconciliationPayment Method Updater8 APIs36.3Visa AcceptanceCapturesPayments2 APIs35.9Dodo PaymentsCheckout SessionsPayments2 APIs34.9AbacatePayPix QR Code1 API34.7KOMOJUPaymentsSessions2 APIs34.4Lemon SqueezyCheckouts1 API34.0PayPayPayment1 API33.8TabsPayments1 API33.6WhopPayments1 API33.2RechargeChargesPayment Methods2 APIs33.1OrdwayPayment RunsPayments2 APIs32.7Tap PaymentsCharges1 API32.4ADROPayments1 API31.5CreemCheckouts1 API31.4CacheflowPayment MethodsPaymentsTransfers3 APIs29.3PickerpaymentezstripePay2 APIs28.5Pin PaymentsCharges1 API28.2EventEdge OracleOne-Time PaymentsRecurring Payments2 APIs27.6OpenpayCardsCharges2 APIs27.6Forithmuspayments1 API26.9
Emerging 1 Early or largely undocumented
Lit ProtocolBilling1 API20.7
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Payment Collection & Dunning. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →