Skip to main content
Once the integration is connected in Marketplace, Stripe is available in your workspace for use inside your flows and AI Agents.
First time implementing a charge? Follow the Tutorial: Implementing your first charge from WhatsApp guide first, which takes you step by step from zero to production.

​
Three usage modalities

Embedded WebView

Payment button with WebView checkout

Native in chat

Card capture in conversation

Advanced tools / MCP

Full API access via MCP
This page covers all three modalities. Use the cards to go directly to the one you need.

​
Embedded WebView

This is the recommended modality to start with. The user receives a link or payment button that opens the Stripe checkout in a WebView inside WhatsApp.

​
Add the node to the Canvas

1

Locate the integration in Marketplace

In the left sidebar of Brain Studio, open the Marketplace folder.If the integration is correctly connected, you will see Stripe listed as an available provider.
Stripe visible in the Marketplace folder inside the Brain Studio sidebar
2

Drag the node to the Canvas

Drag Stripe from the sidebar into your flow on the Canvas.When you drop it, the node block will be created with its available outputs.
Stripe node added to the Canvas showing its outputs
3

Open the configuration panel

Select the node on the Canvas to open its configuration panel on the right side.From there you can complete the inputs and review the available outputs.

​
Configure the node in Canvas

​
Save result as
string
Defines the name of the variable where Brain Studio will store the complete JSON response from the node.
Useful if you want to use the response later (logs, validations, traceability, or flow decisions).
​
Payment type
string
default:"payment"
Defines the type of charge.Available values: payment (one-time payment), subscription (subscription)
If nothing is selected, payment will be used.
​
Environment
string
required
Defines the execution environment for the payment.Available values: Test, Production
Must match the API Key you used to install Stripe in Marketplace (Test vs Live).
​
Payment button expiration [minutes]
number
Defines how long the payment button is valid from the moment it is sent to the user.Available values: 10, 20, 30, 60
​
Currency
string
required
Currency for the charge.
The available currency depends on the country and configuration of the connected Stripe account.
​
Payment reason
string
required
Descriptive text for the charge (for example, order number or product/service description).
Ideally use it with flow variables so it aligns with the conversation context.
​
Payment metadata
string
Additional information for traceability or internal reference.
You can use it for correlation with your order, reconciliation, or payment audit.
​
Buyer email
string
required
The buyer’s email. It must have been collected previously in the flow and passed here as a variable.
​
Customize payment button text
boolean
default:"false"
If you select Yes, additional fields are enabled to customize the message that accompanies the payment button.Fields enabled when activated:
  • Header (required)
  • Body (required)
  • Footer (required)
When this option is active, you can fully modify the message the user will see before opening the checkout.
​
Header
string
Title of the message that accompanies the payment button.
​
Body
string
Main text of the message that accompanies the payment button.

​
Native in chat

Stripe can also operate with a native card payment experience inside the chat.
This modality requires special enablement. If you want to activate it, contact us at [email protected].

Payments – Card payment (technical documentation)

Technical reference for implementing the native experience.

​
Advanced tools / MCP

In addition to Canvas usage via native tools, Stripe exposes a set of advanced tools that can be used in more technical implementations or custom flows. These tools allow you to interact directly with Stripe services from your flow.
Creates a new customer record in your Stripe account.Customers can be associated with:
  • Payment methods
  • Subscriptions
  • Invoices
Useful for:
  • Registering a customer before processing payments
  • Implementing subscription models
  • Managing payment history per customer
Creates a PaymentIntent in Stripe.
  • The amount is sent in cents (example: 15000 = $150.00)
  • Returns:
    • client_secret
    • payment_intent_id
Useful for:
  • Initiating a payment from a customer
  • Custom integrations
  • Advanced payment cycle control
Gets the current status of a payment by:
  • PaymentIntent ID
  • Charge ID
Returns details such as:
  • Status
  • Amount
  • Payment method
  • Receipt URL
Useful for:
  • Verifying if a customer completed the payment
  • Implementing additional validations
  • Post-transaction queries
Lists recent balance transactions in the Stripe account:
  • Charges
  • Refunds
  • Transfers
  • Payouts
Supports:
  • Date filter (Unix timestamps)
  • Pagination
Useful for:
  • Reviewing recent activity
  • Accounting reconciliation
  • Movement audit
Processes a full or partial refund of a charge or PaymentIntent.Available options:
  • Specific amount (for partial refunds)
  • Reason (duplicate, fraudulent, requested_by_customer)
Refunds usually appear in the customer’s account within 5–10 business days.Useful for:
  • Post-sale management
  • Cancellations
  • Return policies