Stripe Manage Stripe payments, billing, catalog, and finance resources
Stripe is a payments and billing platform used to manage one-time payments, subscriptions, invoices, product catalogs, refunds, balances, and dispute workflows. In Agent Forge, the Stripe block gives your workflows and agents a broad admin surface over the most common operational parts of the Stripe API.
With Stripe in Agent Forge, you can:
Manage customers and payment objects : Create and look up customers, Payment Intents, Checkout Sessions, charges, and refunds.Run billing workflows : Create invoices and subscriptions, update them over time, finalize and pay invoices, and handle recurring billing actions from automated workflows.Control your commerce catalog : Manage products, prices, payment links, coupons, and promotion codes directly from your agents.Monitor finance and support flows : Inspect account balance data, review balance transactions, and work disputes from within a workflow.
This makes Stripe useful for revenue operations, support tooling, internal finance automation, and agent-driven commerce flows where you need secure access to your Stripe account without building a custom backend for each action.
Use the Stripe block when you want a workflow step or agent tool to call Stripe directly with a secret API key.
Enter a Stripe secret key in the secretKey field.
Use a test key such as sk_test_... in development and a live key such as sk_live_... only in production.
Optionally set stripeVersion if you want to pin requests to a specific Stripe API version.
List and search operations use dedicated filter fields such as limit, startingAfter, endingBefore, page, and query.
Retrieve and action operations use the relevant Stripe object ID field, such as customerId, paymentIntentId, invoiceId, or subscriptionId.
Create, update, and action-heavy operations use the data field, which must contain a JSON object.
Agent Forge converts the data object into Stripe-compatible application/x-www-form-urlencoded requests for you.
Use Stripe when you want to:
create a Checkout Session or Payment Intent from a workflow
search customers, invoices, subscriptions, or charges
update billing records from internal operations
build agent tools that can reason over Stripe state and take follow-up actions
Parameter Type Required Description secretKeystring Yes Stripe secret API key stripeVersionstring No Optional Stripe-Version override datajson Varies JSON object payload for create, update, or action operations querystring Search only Stripe Search Query Language expression limitnumber No Max records to return for list and search endpoints startingAfterstring No Forward pagination cursor for list endpoints endingBeforestring No Reverse pagination cursor for list endpoints pagestring No Search pagination cursor for Stripe search endpoints
Tool Purpose stripe_create_customerCreate a customer stripe_get_customerRetrieve a customer by ID stripe_list_customersList customers with pagination stripe_update_customerUpdate an existing customer stripe_search_customersSearch customers with Stripe query syntax
Tool Purpose stripe_create_productCreate a product stripe_get_productRetrieve a product by ID stripe_list_productsList products stripe_update_productUpdate a product stripe_search_productsSearch products stripe_create_priceCreate a price stripe_get_priceRetrieve a price by ID stripe_list_pricesList prices stripe_update_priceUpdate a price stripe_search_pricesSearch prices stripe_create_couponCreate a coupon stripe_get_couponRetrieve a coupon stripe_list_couponsList coupons stripe_create_promotion_codeCreate a promotion code stripe_get_promotion_codeRetrieve a promotion code stripe_list_promotion_codesList promotion codes
Tool Purpose stripe_create_checkout_sessionCreate a Checkout Session stripe_get_checkout_sessionRetrieve a Checkout Session by ID stripe_list_checkout_sessionsList Checkout Sessions stripe_expire_checkout_sessionExpire an open Checkout Session stripe_create_payment_intentCreate a PaymentIntent stripe_get_payment_intentRetrieve a PaymentIntent by ID stripe_list_payment_intentsList PaymentIntents stripe_confirm_payment_intentConfirm a PaymentIntent stripe_capture_payment_intentCapture a PaymentIntent stripe_cancel_payment_intentCancel a PaymentIntent stripe_search_payment_intentsSearch PaymentIntents stripe_get_chargeRetrieve a charge by ID stripe_list_chargesList charges stripe_search_chargesSearch charges stripe_create_refundCreate a refund stripe_get_refundRetrieve a refund by ID stripe_list_refundsList refunds
Tool Purpose stripe_create_invoiceCreate an invoice stripe_get_invoiceRetrieve an invoice by ID stripe_list_invoicesList invoices stripe_update_invoiceUpdate an invoice stripe_finalize_invoiceFinalize an invoice stripe_pay_invoicePay an invoice stripe_void_invoiceVoid an invoice stripe_send_invoiceSend an invoice stripe_search_invoicesSearch invoices stripe_create_subscriptionCreate a subscription stripe_get_subscriptionRetrieve a subscription by ID stripe_list_subscriptionsList subscriptions stripe_update_subscriptionUpdate a subscription stripe_cancel_subscriptionCancel a subscription stripe_search_subscriptionsSearch subscriptions
Tool Purpose stripe_create_payment_linkCreate a payment link stripe_get_payment_linkRetrieve a payment link by ID stripe_list_payment_linksList payment links stripe_update_payment_linkUpdate a payment link
Tool Purpose stripe_get_balanceRetrieve Stripe balance data stripe_list_balance_transactionsList balance transactions stripe_get_disputeRetrieve a dispute by ID stripe_list_disputesList disputes stripe_update_disputeUpdate a dispute stripe_close_disputeClose a dispute
{ "name" : "Jane Doe" , "email" : "jane@example.com" , "metadata" : { "workspaceId" : "ws_123" } } { "amount" : 2500 , "currency" : "usd" , "customer" : "cus_123" , "automatic_payment_methods" : { "enabled" : true }, "metadata" : { "orderId" : "order_123" } } status:'open' AND metadata['workspaceId']:'ws_123'
Category: tools
Type: stripe
Stripe processes one object per request, so batch-style updates should be modeled as repeated workflow steps rather than one bulk call.
Stripe request bodies are form-encoded under the hood, even though you enter structured JSON in the block UI.