Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Stripe Payments (BYOK) — connector documentation

  • MCP endpoint: https://byok-stripe-payments.connectorbay.com/mcp
  • REST API: POST https://byok-stripe-payments.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-stripe-payments.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Stripe Payments restricted API key with read permissions only (starts with rk_live_ or rk_test_), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-stripe-payments.connectorbay.com/health · Tool schemas: https://byok-stripe-payments.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-stripe-payments · agent@connectorbay.com

What Stripe Payments (BYOK) is for

Stripe Payments (BYOK) lets an AI assistant read your own Stripe Payments data through the Stripe Payments API with a key you supply (restricted API key with read permissions only (starts with rk_live_ or rk_test_)). Read-only: 11 tools (list_payment_intents, get_payment_intent, list_refunds, get_refund, list_disputes, get_dispute, list_checkout_sessions, get_checkout_session, list_checkout_session_line_items, list_payment_method_configurations, list_payment_method_domains). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.stripe.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Stripe Payments. Stripe Payments and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which payments are stuck in requires_payment_method?"
  • "What is the status of payment intent pi_3MtwBwLkdIwHu7ix28a3tqPa?"
  • "What refunds did I issue for charge ch_3MmlLrLkdIwHu7ix0snN0B15?"
  • "Did refund re_3MtwBwLkdIwHu7ix2DWUaZs8 succeed?"
  • "Which disputes need a response and by when?"
  • "When is the evidence for dispute dp_1MtwBwLkdIwHu7ix due?"

What it does

  • list_payment_intents: List PaymentIntents (one per attempt to collect a payment), newest first, with status, amount, currency and latest charge. Amounts are in the smallest currency unit. Works with a restricted key that has read access to this resource only.
  • get_payment_intent: Get one PaymentIntent by id: status, amount, amount received, currency, capture method and latest charge. Works with a restricted key that has read access to this resource only.
  • list_refunds: List refunds with amount, currency, status, reason and the charge or PaymentIntent refunded. Amounts are in the smallest currency unit. Works with a restricted key that has read access to this resource only.
  • get_refund: Get one refund by id: amount, status, reason, failure reason and receipt number. Works with a restricted key that has read access to this resource only.
  • list_disputes: List disputes (chargebacks) with amount, reason, status and the evidence deadline. Evidence text and customer details are not returned. Works with a restricted key that has read access to this resource only.
  • get_dispute: Get one dispute by id: amount, reason, status and evidence deadline and submission state. Evidence text and customer details are not returned. Works with a restricted key that has read access to this resource only.
  • list_checkout_sessions: List Checkout Sessions with status, mode, payment status, totals and the PaymentIntent or subscription they created. Customer details and addresses are not returned. Works with a restricted key that has read access to this resource only.
  • get_checkout_session: Get one Checkout Session by id: status, mode, payment status, totals and the linked PaymentIntent or subscription. Customer details are not returned. Works with a restricted key that has read access to this resource only.
  • list_checkout_session_line_items: List the line items of one Checkout Session with description, quantity, amounts and currency. Works with a restricted key that has read access to this resource only.
  • list_payment_method_configurations: List payment method configurations (which payment methods are offered) with name, default flag and whether card and link are available. Works with a restricted key that has read access to this resource only.
  • list_payment_method_domains: List domains registered for wallet payments with enabled flag and the status of Apple Pay, Google Pay and Link on each. Works with a restricted key that has read access to this resource only.

BYOK key

You bring your own Stripe Payments restricted API key with read permissions only (starts with rk_live_ or rk_test_) (https://dashboard.stripe.com/apikeys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.stripe.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Stripe Payments API (api.stripe.com) with a BYOK key; documentation: https://docs.stripe.com/api/payment_intents. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Stripe Payments. Stripe Payments and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Stripe Payments account.

Built for: Worldwide. Languages: English.