![]() ![]() If you have multiple pricing tables, the rate limit is shared. Rate limit-The pricing table has a rate limit of up to 50 read operations per second.It doesn’t currently support adding an intermediate step (for example, asking the customer to create an account on your website before checking out). Account creation-The pricing table call-to-action takes customers directly to checkout.You can only configure three unique pricing intervals across all products. Product and price limits-You can configure the pricing table to display a maximum of four products, with up to three prices per product.Other advanced pricing models aren’t supported. Business models-The pricing table supports common subscription business models like flat-rate, per-seat, tiered pricing, and trials.Invalid values are silently dropped and your pricing table will continue to work as expected. client-reference-id can be composed of alphanumeric characters, dashes, or underscores, and be any value up to 200 characters. This can be an authenticated user ID or a similar string. When the property is set, the pricing table passes it to the Checkout Session’s client_reference_id attribute to help you reconcile the Checkout Session with your internal system. The web component supports setting the client-reference-id property. For more information, see the guide for fulfilling orders after a customer pays. Make sure to listen to additional webhooks if you enable payment methods like bank debits or vouchers, which can take 2-14 days to confirm the payment. When a payment is completed using Checkout, Stripe sends the webhook that you can use for fulfillment and reconciliation. The pricing table component uses Stripe Checkout to render a prebuilt, hosted payment page. When a customer purchases a subscription, you’ll see it on the subscriptions page in the Dashboard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |