Closed marinaglancy closed 4 days ago
Screenshot of the price configuration for storage:
Hey @marinaglancy 👋
Thanks for taking the time to send in such a detailed issue. Setting a quantity limit against a price lets you specify the maximum and minimum units for an item when buying, but it doesn't require a customer to buy an item. In your example, it'll stop the customer from buying fewer than 50 units, but won't stop them removing the item altogether.
There's a few things you can do here that might help:
billed
to prevent quantity changes. Billed transactions cannot be changed, so the quantity stepper and delete icon for items aren't presented.ready
. You can use an eventCallback
to listen for checkout events, then send a request to the Paddle API to mark a transaction as billed
.Here's a quick screenshot of how overlay checkout looks for a billed transaction 👇
Stopping customers from removing an item like this is feedback that we've had before, so I chatted with the PM who heads up checkout to let them know it's something that you're looking for too. In the meantime, I'm going to mark this as a feature request and close the issue. Pop back and let us know how you get on with the suggested solutions, and feel free to reopen the issue if there's anything else we can do to help 😄
Thank you very much! Marking transaction as billed worked perfectly
What happened?
When calling checkout I add two items:
The price for storage has constraints that it has to be between 50 and 1000 (Gb).
At the checkout the user is able to change the quantity for storage within the allowed limits but is also able to completely remove this item. I do not want them to be able to remove it.
I can not find any setting that would prevent user from modifying the items at the checkout, even if I create a transaction using the API and pass the transaction id to the paddle.checkout.open() method
Steps to reproduce
What did you expect to happen?
No response
How are you integrating?
No response
Logs
No response