Create Test Token: Stripe action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Card Number card_number	string	Required	Card Number. e.g. "4242424242424242"
Exp Month exp_month	string	Required	Exp Month. e.g. "12"
Exp Year exp_year	string	Required	Exp Year. e.g. "2025"
CVC cvc	string	Required	CVC. e.g. "123"

Sample request

{
  "card_number": "4242424242424242",
  "exp_month": "12",
  "exp_year": "2025",
  "cvc": "123"
}

Returns

{
  "id": "tok_abc",
  "card": {
    "brand": "Visa",
    "last4": "4242"
  },
  "type": "card"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Test Token.

What does the Create Test Token action do in Stripe?

Creates a test card token (for testing only). In production, Stripe.js or Stripe Elements creates the token client-side to keep PCI scope minimal.

What inputs does Create Test Token require?

Required: Card Number, Exp Month, Exp Year, CVC. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Stripe returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Test Token support batch operations?

Yes. Run Create Test Token inside a Loop node to process arrays. Tiny Command handles Stripe's rate limits automatically so you don't have to throttle manually.

More actions