CheckoutInput

  • The products on offer, each with its plans. With Stripe connected, a customer given and a single-use checkout offering only one plan (a product without plans counts as one, its default plan), the customer goes straight to paying for it on Stripe Checkout.

    Properties: 2
  • Where the customer goes once they have paid or started. Must be http or https. {CHECKOUT_ID} is replaced with the checkout's ID when it is created, and {CHECKOUT_SESSION_ID} with the session's ID when the customer finishes.

  • Where Stripe Checkout's back link sends a customer who leaves without paying. Must be http or https; takes the same placeholders. Default, successUrl.

  • Require a billing address on Stripe Checkout.

  • Ask for a phone number on Stripe Checkout.

  • ISO 4217 code to price the checkout in. Default, each plan's own currency.

  • Cards of your own content to show on the checkout page, returned as sent.

    Properties: 1
  • The customer the checkout is for, by Spondo Billing ID.

  • When the link stops working; must be in the future. Default, 24 hours from now.

  • The customer the checkout is for, by your ID (case-insensitive). A customer with this ID is created if you have none. Ignored when customerId is set. Leave both out and the customer gives a name and billing email on the checkout page, which creates them.

  • Your own key-value data, kept with the record and returned as sent.

    Properties: 1
  • Close the checkout once one customer completes it. A multi-use checkout stays active until it expires or you archive it, sends each customer through your hosted checkout page, and gives each customer who completes it their own order.

  • The message under it. Default, "This checkout is complete."

  • The heading the checkout page shows once the checkout is completed. Default, "You're all set".