The API that fits your SaaS.

Choose hosted or SDK checkout, connect subscription authorization and reconcile events.

Connect payment, payout and verification APIs through Cashfree’s agent stack.

Sandbox and Postman workflows support API and payment-flow testing.

Your team owns tax obligations, entitlement rules and subscription product logic.

Set up a product catalog, billing rules and a payment gateway; map subscription and invoice states into your app.

Data, onboarding and billing operations; OAuth or API-key authentication. Available tools depend on enabled server toolsets.

Move test-site billing through time to exercise subscription changes and renewals.

Chargebee manages billing workflows. Your selected gateway and tax setup remain separate integration choices.

Use checkout and a framework adapter; keep customer and subscription state synchronized.

Use the API or CLI from your own agent adapter; official MCP support is not confirmed here.

Sandbox keys and test cards let you exercise checkout without live payments.

The MoR handles supported transaction taxes; you still wire license or application access.

Connect Stripe, create products and connect purchases to newsletter automations.

Tools include Commerce products and purchases; this is not a general SaaS metered-billing engine.

Kit documents refunding a purchase or using a zero-price discount to test the purchase flow.

Kit runs product and email workflows; you configure the connected payment account and seller obligations.

Create subscription products, use hosted checkout and map store events to your users.

A custom agent can call the API. An official MCP offering was not verified in this review.

Use separate test data and manually simulate subscription or order webhooks.

Payment and supported sales-tax handling are bundled; your app still owns access, usage capture and customer mapping.

Choose payment links or a custom integration; confirm the required recurring-payment API scope.

Connect an assistant to query balances, inspect payments and create payment links.

Verified businesses can use a separate sandbox dashboard and API key for end-to-end dummy payments.

You own product access, tax obligations and billing rules around the payment service.

Establish customer mandates and recurring payments. Build advanced plan-change and billing logic around that flow.

OAuth-based MCP for account operations, plus a toolkit for custom agents. Check which write actions are supported.

Use changePaymentState for recurring test payments, refunds and chargebacks.

You remain the seller. Your team owns advanced billing rules and access control alongside mandate/payment handling.

Configure plans, authorization and checkout, then handle subscription events and access.

Local and remote options expose payment operations; available tools depend on deployment.

Exercise payment and subscription flows in test mode with separate credentials.

You own taxes, access and billing policies around gateway and mandate behavior.

Connect Checkout, Billing, webhook handling and your app’s access rules. Tax services are separate.

OAuth or agent API keys; API read/write tools and integration planning. Limit permissions to the task.

Advance billing clocks to exercise renewals, trials and lifecycle events.

You own the seller relationship, access policy and tax workflow; Stripe supplies billing and payment components.

Publish products or memberships; API and notifications connect sales to your own application.

A custom integration can use the API; official MCP support is not confirmed here.

Test the product purchase and fulfillment path; this is not a billing time-travel environment.

Gumroad handles its supported checkout tax obligations; custom SaaS entitlements remain in your app.

Configure products, content and checkout in the platform instead of building a billing backend.

Podia explicitly offers no public API or webhooks; use its supported Zapier integrations.

Verify purchase, membership access and cancellation through the hosted product workflow.

Podia handles course and community access; payment configuration and seller tax obligations remain relevant.

Connect gateways, plans and recovery rules, then reconcile Recurly states with your application.

Build around the API and verify current state after notifications. An official MCP offering was not verified.

The documented dunning test moves the next renewal to one hour ahead. This differs from a general time-travel API.

Subscription and dunning automation reduce manual work; gateway configuration, access and tax responsibilities still need an owner.

Configure products and a payment gateway rather than implementing a full billing API.

Do not assume storefront automation provides subscription-management tools for an agent.

Test gateway connection, checkout and digital delivery through the platform workflow.

Sellfy provides selling and delivery tools; you remain responsible for your seller and tax setup.

Connect products, delivery and your payment gateway; use the developer API for custom workflows.

Developer endpoints can support custom automation; official MCP tooling is not confirmed here.

Verify purchase notifications and delivery alongside the connected gateway’s test workflow.

You configure the payment provider and keep responsibility for tax and application access rules.