TestingOps.ai

MCP tools for agents · MCP tool for agents

Stripe and TestingOps: sandbox payment checks for checkout tests

Connect Stripe's MCP server with a sandbox key and TestingOps agents can look up the payments, customers and disputes your checkout tests create.

  • MCP tool for agents
  • Available
Request a demo Stripe MCP server
Connection
MCP tool for agents
Writes back
Only after a person approves
Last checked
7 Nov 2026

In short

Stripe and TestingOps in short

The Stripe connection is an MCP tool for TestingOps agents: you paste a restricted key from a Stripe sandbox, created for agent access, and agents can call Stripe's MCP server with it.

Agents can then check the Payment Intent a checkout case created, the test customer it used or a dispute fixture, to confirm what Stripe recorded rather than only what the screen showed.

Use sandbox keys only: TestingOps does not reject a live key, so the sandbox rule is guidance you apply when you create the key.

What it does

What it does for your testing

  1. 1

    Payment results checked at Stripe

    Input
    A checkout case that ends with a payment
    TestingOps
    Agents can look up the Payment Intent in your sandbox and compare amount, currency and status with the case
    Output
    A payment check against Stripe's record, not only the confirmation screen
  2. 2

    Test customers and disputes inspected

    Input
    Sandbox customers and dispute fixtures
    TestingOps
    Agents can read a customer's saved payment methods or a dispute's state
    Output
    Preconditions confirmed before payment-related cases run
  3. 3

    Writes only with permission and approval

    Input
    A call through Stripe's write tool
    TestingOps
    TestingOps asks for approval first, and the key's permissions decide whether Stripe accepts it
    Output
    Sandbox changes through that tool only after an approved, reviewed call

Step by step

How it works

  1. Create a sandbox restricted keyIn a Stripe sandbox, create a restricted key for agent access (when Stripe asks what the key is for, choose Authorizing agent access to your account) with Read on the resources agents may see and None elsewhere.
  2. Connect it in TestingOpsPick Stripe under Extra tools your agents may use in Integrations → API & MCP, paste the key into Stripe restricted key and select Connect.
  3. Reads open, writes ask firstStripe's read tools are open to agents. A call through a write tool such as stripe_api_write waits for approval, and with a Read-only key Stripe refuses writes anyway.
  4. Agents check payments during a taskWhen a case involves a payment, an agent can look it up in your sandbox through TestingOps; the key stays on the TestingOps server.

From December 2026 Stripe's MCP server accepts only agent-tagged restricted keys; a plain restricted or secret key then gets a 401.

Connect

Setup

  1. In the Stripe Dashboard, switch to a sandbox, open Developers → API keys and select Create restricted key.
  2. When Stripe asks what the key is for, choose Authorizing agent access to your account and give it a name such as TestingOps agents.
  3. Set Read on the resources agents may see (Customers, Payment Intents, Disputes…) and None elsewhere, select Create key, complete the two-factor check and copy the key (rk_test_…).
  4. In TestingOps, as customer admin, open Integrations → API & MCP, pick Stripe under Extra tools your agents may use (outgoing, over MCP), paste the key into Stripe restricted key and select Connect.

Documentation: Stripe MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → Stripe

Use cases

Use cases

Verify a checkout end to end

Trigger
A checkout case completes on screen
Uses
The Payment Intent in your Stripe sandbox
Agent activity
Can look up the latest Payment Intent for the test customer and compare it with the case
Result
A payment check at Stripe as part of the analysis
Condition
The key needs Read on Payment Intents

Explain a declined test payment

Trigger
A payment step fails with a decline
Uses
The Payment Intent and its last error
Agent activity
Can read why Stripe declined the test payment
Result
A decline explained by the test card used, or a defect if the app handled it wrongly

Check a dispute flow

Trigger
A case covers how the app shows disputed payments
Uses
Dispute fixtures in the sandbox
Agent activity
Can read the dispute's state before the case runs
Result
Cases that start from a known dispute state
Condition
The key needs Read on Disputes

Capabilities

Capabilities and limits

What is read

What the restricted key allows in your sandbox, for example Customers, Payment Intents and Disputes

What is produced

Payment checks and explanations in agents' analysis; nothing is stored in TestingOps by the tool itself

Where it can write

  • Only what the key permits: with Read-only permissions Stripe refuses writes
  • Calls through Stripe's write tool ask first in TestingOps; refunds and outbound payments also need a person's confirmation in Stripe
  • Stripe's money transfer and currency conversion tools count as writes and ask first in TestingOps; Stripe also asks a person to confirm them

How it connects

Stripe's hosted MCP server (https://mcp.stripe.com) with the restricted key in the Authorization header

Account and permissions

  • A restricted key (rk_test_…) from a Stripe sandbox, tagged for agent access
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • Sandbox-only is guidance: TestingOps does not block a live key, so create the key in a sandbox
  • From December 2026 Stripe accepts only agent-tagged restricted keys on its MCP server
  • Write approvals are answered on the request by people in your organisation with Manage integrations rights, or by the TestingOps team
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

An online shop tests checkout against a Stripe sandbox. The QA lead creates a restricted key in the sandbox with Read on Customers and Payment Intents and connects Stripe in TestingOps.

When the pay-with-saved-card case passes on screen, the agent can look up the Payment Intent and sees it is still waiting for capture, so the analysis asks whether the shop captures payments later or misses a step.

Frequently asked questions

Does TestingOps stop us from using a live key?

No. The guidance is a sandbox key, and the field expects rk_test_…, but TestingOps does not reject a live key. Create the key in a sandbox.

Can agents create test payments?

Only if the key has write permissions, and each call through Stripe's write tool asks first in TestingOps. With the Read-only key from the setup steps, Stripe refuses writes.

What changes in December 2026?

Stripe's MCP server will accept only agent-tagged restricted keys. A key created with Authorizing agent access to your account, as in the setup, is tagged that way.

Who approves a write call?

Someone in your organisation with Manage integrations rights, on the request the agent is working on; the TestingOps team can approve it too. Tools that delete also need the TestingOps team's formal approval, and refunds and outbound payments also need a person's confirmation in Stripe.

Next step

Request a demo to see agents check sandbox payments after your checkout cases.

Request a demoMore mcp tools integrations