Approval-gated Chargebee hosted checkout creation workflow. It reads customer and item-price context, then creates one hosted checkout page through recued-core.chargebee.hosted_page.checkout.create using Chargebee's documented checkout_new_for_items form-encoded body. It does not directly create subscriptions, update subscriptions, manage payment sources, collect invoices, acknowledge hosted pages, or call arbitrary Chargebee endpoints.

How it works 9 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (9 steps)

■ target_customer_id trim

Trim whitespace from setting customer id

■ target_item_price_id trim

Trim whitespace from setting item price id

■ encoded_checkout_body trim

Trim whitespace from setting checkout body

■ checkout_reason trim

Trim whitespace from setting reason

■ customer ?

■ item_price ?

■ has_body compare

Check if encoded checkout body has data

■ hosted_checkout ?

skip: step.has_body not_equal true

■ card to_summary

Format results as a summary card

Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

reason setting =

chargebee setting =

customer id setting =

checkout body setting = customer[id]=customer-001&subscription_items[item_price_id][0]=example-plan-USD-monthly&subscription_items[quantity][0]=1&redirect_url=https%3A%2F%2Fexample.com%2Fchargebee%2Fsuccess&cancel_url=https%3A%2F%2Fexample.com%2Fchargebee%2Fcancel

item price id setting =