Commercial operations and calculations

Process a scheduled payment

Collects a scheduled payment with Stripe PaymentIntents.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Minor-unit amount, payment method, due-date gate, native idempotency and reconciliation status.

What to customize

Use fixed Stripe API origin and set timeout.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "{\"amount\":1250,\"currency\":\"usd\",\"paymentMethodId\":\"pm_demo\",\"customerId\":\"cus_demo\",\"idempotencyKey\":\"contract-42-installment-1\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "dry_run",
    "output2": "",
    "output3": "provider call suppressed"
  }
}

Returned fields

output1: status
output2: provider ID
output3: details

What changes when it runs

Creates and confirms one Stripe PaymentIntent in live mode.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe