# Stripe's SPT docs show a Resolve API for other processors

What a seller using another processor needs to take an agent's SPT, in preview. Our side proved a native agent payment at 5 of 140.

Source: https://agentdrives.com/notes/2026-10-16-stripe-spt-docs-add-a-resolve-api-for-third-party?via=md · Published 2026-10-16 · 140 products, driven 2026-10-01 to 2026-10-16

## What happened

Stripe's Shared Payment Token docs, as we fetched them on 16 Oct 2026, show how a seller takes an agent's token through a third-party processor. “Use the SPT Resolve API to retrieve network credentials and submit them to your payment processor.” ([source](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=seller&locale=en-US)) The page carries no date, and the API version in its payment examples is marked preview. Stripe says the API returns one of these credential types: fpan, network_token, agentic_token, dpan ([source](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=seller&locale=en-US)). It also says SPTs are available in the US, Canada, and select European countries ([source](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=seller&locale=en-US)). Source: [Stripe's Shared Payment Token docs](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=seller&locale=en-US).

## What our drives saw

As of 16 October 2026, 22 of 140 products we drove offer an agent-native way to pay (x402, MPP, Stripe Projects and similar), seen or paid. Our agent got as far as the payment step at 40 of 140.

Across all products we drove, 70 of 140 pay only through a card checkout a person does, and 49 of 140 offer only a card checkout an agent could finish with a card it was given.

[Stripe](/tools/stripe) itself is graded P3 in our drives: a billing API, or an agent payment rail seen but not paid. At Stripe, our agent reached the last step before paying and stopped there for a reason of ours.

## What it means

For owners who process cards outside Stripe: per Stripe's docs, you resolve an agent's SPT to network credentials and submit them to your own processor. You need a Stripe profile, and Stripe must create a credential configuration for your account first; without one, the Resolve API answers with a 400 error. “You can only resolve an SPT one time.” ([source](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md?agent-seller=seller&locale=en-US)) Without your PCI Attestation of Compliance on file with Stripe, Stripe encrypts the in-scope credentials with a key you can't decrypt, for example one your processor owns. If agents buy from you, settle the configuration and the PCI question with Stripe before you resolve SPTs.

For builders: an SPT is a grant on the customer's payment method, with limits the agent sets, such as currency, maximum amount and expiry. It helps only at a seller that accepts SPTs. At a product whose only checkout is one a person does, as at the P1 products above, an SPT doesn't get your agent through.

See [how we drive](/method) for what each pay grade means, and [the facts](/data/facts) for the full counts.

## What we don't know

The page has no date, so we can't say when the Resolve API became available. The docs don't name the processors that accept the resolved credentials. They don't say when the preview ends. Our payment facts count agent-native rails together, so we can't yet say how many of those products take SPTs.

## What we'll do

Nothing to drive yet. We watch for a product we drove that starts taking SPTs; when one does, we drive its payment step again and date the result on its page and on [the facts](/data/facts).