Take payments with Stripe

Stripe is AnythinkPay's web and non-digital-mobile payment rail, run through Stripe Connect: your project's own Stripe account, connected to Anythink's platform account. Money settles directly to you, minus Stripe's fees and Anythink's platform fee — Anythink never holds customer funds.

For the subscription concepts (plans, statuses, trials), see Create plans and manage subscriptions. This page covers Stripe specifically: connecting your account, one-off payments, saved payment methods, and webhooks.

Connect your Stripe account

In the Anythink dashboard

1. Go to Settings › Payments, Stripe tab.
2. Select Connect Stripe, choose Individual or Company, enter your country and business email.
3. Complete Stripe's own onboarding form (business details, bank account) in the tab it opens.
4. Back in Anythink, the page shows Onboarding complete, Charges enabled and Payouts enabled once Stripe confirms each. If Stripe flags your account (for example asking for more verification), the page shows Account Disabled or Action Required by with the deadline Stripe gave.

With the CLI

anythink pay connect     # creates the Connect account, opens onboarding
anythink pay status      # shows onboarding / charges / payouts state

With an AI assistant (MCP)

Note: As with the rest of AnythinkPay, pay isn't proxied by the hosted cli MCP tool — only a locally running CLI (anythink mcp) exposes it. Locally, ask your assistant to run pay connect and pay status.

Test mode

Onboard with Stripe in test mode (the default for a new Connect account until you complete Stripe's live activation) and use Stripe's test cards — 4242 4242 4242 4242, any future expiry, any CVC — for both subscriptions and one-off payments. No real charge happens, and Stripe's dashboard shows the payment under its own Test mode toggle.

Note: Stripe Connect onboarding and webhook delivery can't be exercised without a real (test-mode) Stripe account and its webhook signing secret — this documentation pass verified everything up to that point (plan creation, subscription creation locally) and confirmed the shape of these endpoints from source, not against live Stripe test mode.

One-off payments

A one-off payment isn't tied to a plan — you set the amount and description directly.

In the Anythink dashboard

1. Go to AnythinkPay › Payments and select New payment (or trigger one from your app's checkout flow — most projects create payments from their own code, not the dashboard).
2. Set Amount, Currency, Description, and optionally line items.
3. The customer completes a Stripe Checkout session; the payment's Status updates from the webhook once it settles.

With the CLI

anythink fetch /integrations/anythinkpay/payments --method POST --body \
  '{"type":"one_off","amount":25.00,"currency":"gbp","description":"Event ticket","customer_email":"test@user.com"}'

anythink pay payments --page 1 --limit 25

pay payments lists recent payments in a table (id, amount, status, description, date); creating one is a fetch call since there's no dedicated anythink pay create command.

With an AI assistant (MCP)

List the last 10 AnythinkPay payments for this project.

Direct charges (saved payment method)

For a subscriber who's already saved a card, POST /integrations/anythinkpay/payments/charge-payment-method charges it directly without a new Checkout session — pass the saved payment_method_id, amount and currency; idempotency_key is optional and prevents duplicate charges on retry.

Payment methods

Saved cards live against a Stripe customer, keyed by the subscriber's email.

In the Anythink dashboard

A subscriber's payment methods show on their subscription's detail page. There's no separate global payment-methods screen in the dashboard today — see them via the API or CLI instead.

With the CLI

anythink pay methods

── Payment Methods (2) ───────────────────────────────
  ID         Type   Brand  Last4  Expires
  pm_1a2b3c… card   visa   4242   12/2027

With an AI assistant (MCP)

List saved payment methods on this project.

To let a subscriber add a card without an immediate charge, create a SetupIntent: POST /integrations/anythinkpay/payment-methods/setup-intent. Removing one is DELETE /integrations/anythinkpay/payment-methods/{id}.

Payment options and platform routing

GET /integrations/anythinkpay/payment-options?platform=ios&storefront=GBR tells your app which provider(s) to offer for a given platform and (for iOS) App Store storefront, so you don't hardcode the Stripe-vs-Apple decision client-side:

• Android, web, and anything that isn't ios always get stripe_web.
• iOS gets Apple in-app purchases if the project has Apple IAP configured — except for storefronts where Stripe supports digital subscriptions directly (the US and most of the EU), which prefer stripe_web and fall back to apple as a second option.
• If Apple IAP isn't configured for the project at all, iOS falls back to stripe_web regardless of storefront.

{ "primary_provider": "stripe_web", "providers": ["stripe_web"], "web_checkout_allowed": true, "storefront": "GBR" }

This behaviour was confirmed against a local project with no Apple IAP configured: every platform and storefront combination returned stripe_web only, matching the fallback rule above.

Platform fees

Settings › Payments › Fees & Calculator shows your current platform fee configuration and a calculator for a given amount. The same data is available as:

GET /integrations/anythinkpay/stripe-connect/fees
GET /integrations/anythinkpay/stripe-connect/stripe-fees
POST /integrations/anythinkpay/stripe-connect/fees/calculate

fees is Anythink's platform fee configuration (what Anythink takes); stripe-fees is Stripe's own processing fee schedule; fees/calculate runs both against a given amount so you can show a subscriber or your own reporting the net payout before it happens.

Webhooks

Stripe webhooks go to AnythinkPay's payments service (verified against your project's Stripe webhook signing secret), not to your project directly. It handles:

After a payment succeeds or fails, the AnythinkPay payments service relays a PaymentSucceeded or PaymentFailed event to your project, which a workflow can act on — see Payments recipes for a worked example that emails and pushes on this event.

Limit: The webhook handler tolerates Stripe API version drift for the event types above, but an event type it doesn't recognise returns 200 with a "not supported" message rather than failing — Stripe won't retry those, so don't rely on an unlisted event type ever being processed.

Permissions

Next steps

How payments and subscriptions work