#JohnnyB
ornate ivy
timber cypress
Hi 👋
What do you mean here? The Payment Element is an element loaded onto your own webpage, not a Stripe hosted front-end. Do you mean Checkout? Could you explain your integration a little more?
icy steeple
Hello there
Let me show you
We use stripe to take payments over IVR (via twilio pay) and directly through you using something else, I guess it could be check out
When a customer selects to pay using payment link, we send them an SMS with the payment URL, and they click it to complete payment
is an example
you're right, we host it
apologies
we'd like to check with you if that link can be blocked from use after a certain period of time
we can nuke it, but also want to see if there's a way to disable payments on your side
timber cypress
Sorry I'm still not clear on what APIs you are using
Without that information it is difficult for me to provide a clear answer
icy steeple
Payment Element
timber cypress
Okay so that's the front-end. What are you using to instantiate it?
You can "disable" the Payment Element using JavaScript by updating the readOnly property to true: https://stripe.com/docs/js/elements_object/update_payment_element#payment_element_update-options-readOnly
But to be secure you would want to cancel whichever Intent you used to instantiate it on the server-side:
- Setup Intent: https://stripe.com/docs/api/setup_intents/cancel
- Payment Intent: https://stripe.com/docs/api/payment_intents/cancel
icy steeple
my team says it's Payment element
timber cypress
That's the front-end, as I said. Your server must create either a Setup Intent or a Payment Intent to instantiate it. However, in my comment above I provided a way you could handle either case.