#arush-kapoor_code

1 messages · Page 1 of 1 (latest)

lyric pulsarBOT
#

đź‘‹ Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1402245075236552725

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

lime path
#

hi there!

#

I'm not sure I follow your question. do you want to use Link or not?

karmic atlas
#

Hey @lime path, yes we are looking into different ways we can integrate Link (for example, in Payment Element or in Express Checkout). I wanted to know if there is a way to integrate this type of Link, where the cardNumber and other input fields are our own

lime path
#

where the cardNumber and other input fields are our own
so you want to use Link when using the split card element?

#

if so, that feature is not publicly available. but you could reach out to Stripe support to see if your account is eligible to have access to this feature.

karmic atlas
#

Could you please explain, what you mean by split card element. In the screenshot which I have shared, the card number, expiry and cvv are all inside Stripe's iframe, is it possible for those input fields to be our own custom but we still use the same Stripe Link widget

lime path
#

in the code you shared you are using cardNumber, cardExpiry, etc.

#

we call this the "split card element".

karmic atlas
#

Thank you for clarifying, yes, we would like to implement Stripe Link in split card element where the card elements are ours and not of Stripe's

lime path
#

where the card elements are ours and not of Stripe's
I don't understand what that means, sorry.

#

are you using the Card Element or not?

karmic atlas
#
    style: elementStyles,
    classes: elementClasses,
  });
  cardNumber.mount('#example3-card-number');

  var cardExpiry = elements.create('cardExpiry', {
    style: elementStyles,
    classes: elementClasses,
  });
  cardExpiry.mount('#example3-card-expiry');

  var cardCvc = elements.create('cardCvc', {
    style: elementStyles,
    classes: elementClasses,
  });
  cardCvc.mount('#example3-card-cvc');

Instead of using Stripe’s pre-built Elements (which render Stripe-hosted iframes for cardNumber, cardExpiry, and cardCvc), is it possible for us to use our own custom input fields for these values—since we are PCI compliant—while still integrating with this specific implementation of Stripe Link?

lime path
#

oh, you are sending the raw card numbers directly to Stripe? you didn't mention that before.

#

in this case I don't think you can use Link no.

karmic atlas
#

So we will have to use Stripe's Split Card Elements if we want to use this Stripe Link implementation which is visible in the attached screenshot

lime path
karmic atlas
#

Link Auth element UX is different from the one shared in the screenshot, is there some exposed element which we can use for similar UX as in the screenshot?

lime path
#

no sorry