#morteza_api
1 messages · Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- morteza_issuing-web, 19 hours ago, 40 messages
- morteza_api, 1 day ago, 34 messages
- morteza_api, 1 day ago, 33 messages
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1260229815642886297
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
Can you say more or share an example of what you mean?
this is the ui for my app
the cards screen is actually a webview which uses issuing elements to show card details
but the modal is in app side
I need to somehow trigger copy card number for example
from app in the webside
in othe words I need to trigger issuingCardCopyButton loaded in webside from the app
is it possible ?
As far as I know, no that is not possible/supported
https://docs.stripe.com/issuing/elements#adding-a-copy-button
const cardPinCopy = elements.create("issuingCardCopyButton", {
toCopy: "pin",
style: {
base: {
fontSize: "12px",
lineHeight: "24px",
},
},
});
cardPinCopy.mount("#card-pin-copy");
this is how I've rendered copy pin , how can I get it from the dom and trigger click on it
these are rendered inside an iFrame
You can't
We restrict the copy functionality to Stripe’s PCI-compliant <iframe>.
By design your application is meant to not be able to access that
That may be necessary, yes, so that you can use the copy button for the user to tap