Stripe · Arazzo Workflow

Stripe Set Up Future Payment

Version 1.0.0

Create a SetupIntent to save a payment method for future off-session use, then confirm it.

1 workflow 1 source API 1 provider
View Spec View on GitHub CommerceFinancial-ServicesFintechPaymentsT1ArazzoWorkflows

Provider

stripe

Workflows

setup-future-payment
Save a payment method for future off-session charges via a confirmed SetupIntent.
Creates a SetupIntent for off-session usage attached to the supplied customer and payment method, then confirms the SetupIntent to complete any required SCA/3DS authorization and persist the payment method for later charges.
2 steps inputs: customer, description, paymentMethod, returnUrl outputs: paymentMethod, setupIntentId, status
1
createSetupIntent
Create a SetupIntent flagged for off-session usage, bound to the customer and payment method that will be saved.
2
confirmSetupIntent
Confirm the SetupIntent to trigger any required SCA/3DS authorization and save the payment method for future off-session charges.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Stripe Set Up Future Payment
  summary: Create a SetupIntent to save a payment method for future off-session use, then confirm it.
  description: >-
    The canonical Stripe pattern for collecting permission to charge a payment
    method later without the customer present. The workflow first creates a
    SetupIntent flagged for off-session usage and bound to a customer and payment
    method, then confirms it so any required SCA/3DS authorization is triggered
    and the payment method is saved for future charges. Each step spells out its
    form-encoded request inline so the flow can be read and executed without
    opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: setupIntentsApi
  url: ../openapi/stripe-setup-intents-api-openapi.yml
  type: openapi
workflows:
- workflowId: setup-future-payment
  summary: Save a payment method for future off-session charges via a confirmed SetupIntent.
  description: >-
    Creates a SetupIntent for off-session usage attached to the supplied customer
    and payment method, then confirms the SetupIntent to complete any required
    SCA/3DS authorization and persist the payment method for later charges.
  inputs:
    type: object
    required:
    - customer
    - paymentMethod
    properties:
      customer:
        type: string
        description: ID of the Customer the payment method is being saved for (e.g. cus_...).
      paymentMethod:
        type: string
        description: ID of the PaymentMethod to save for future use (e.g. pm_card_visa).
      returnUrl:
        type: string
        description: URL to redirect the customer to after any required authentication (e.g. https://example.com/setup/complete).
      description:
        type: string
        description: Optional description for the SetupIntent.
  steps:
  - stepId: createSetupIntent
    description: >-
      Create a SetupIntent flagged for off-session usage, bound to the customer
      and payment method that will be saved.
    operationId: PostSetupIntents
    requestBody:
      contentType: application/x-www-form-urlencoded
      payload:
        customer: $inputs.customer
        payment_method: $inputs.paymentMethod
        usage: off_session
        description: $inputs.description
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      setupIntentId: $response.body#/id
      status: $response.body#/status
      clientSecret: $response.body#/client_secret
  - stepId: confirmSetupIntent
    description: >-
      Confirm the SetupIntent to trigger any required SCA/3DS authorization and
      save the payment method for future off-session charges.
    operationId: PostSetupIntentsIntentConfirm
    parameters:
    - name: intent
      in: path
      value: $steps.createSetupIntent.outputs.setupIntentId
    requestBody:
      contentType: application/x-www-form-urlencoded
      payload:
        payment_method: $inputs.paymentMethod
        return_url: $inputs.returnUrl
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/status
      paymentMethod: $response.body#/payment_method
      nextAction: $response.body#/next_action
  outputs:
    setupIntentId: $steps.createSetupIntent.outputs.setupIntentId
    status: $steps.confirmSetupIntent.outputs.status
    paymentMethod: $steps.confirmSetupIntent.outputs.paymentMethod

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/stripe-setup-future-payment-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.