#newt-link-details
1 messages ยท Page 1 of 1 (latest)
Hello! I'm not sure I follow the question unfortunately. Can you provide more context about "retrieved by link", especially your exact integration path and which part of the code you are referring to
newt-link-details
We have a "Virtual Terminal" component that our clients use for processing payments, both internally (backend) and externally (external portals). Our Terminal has been using the Card element but we are planning to move away from it and migrate to the Payment Element.
Terminal with a capital T is our in-person payments product so that's... tricky
Wait
But okay you used CardElement and now are using PaymentElement. But what's the blocker/problem
Not Stripe Terminal. We also use that one in one of our mobile apps.
But let's try to separate the Stripe Terminal and our Virtual Terminal.
The Virtual Terminal I am talking about is using the Card Element and we will try to use the Payment Element.
So, we would like to use Link now that we are moving to the Payment Element.
But our terminal already has fields managed by our logic both for the Shipping and the Billing information.
We would like to keep using those so, would it be possible to use Link in a way that integrates with these fields on our side?
One way that could happen is that after the use authenticates with Link the customer information that is loaded could be received on our side so that we could fill in our fields with it.
Do you think that will be possible?
Does that make sense?
Unfortunately not really
Can we ignore your app for a sec, I don't really grasp the vocabulary you're using. Let's focus on the Stripe products. What are you using, what have you tried, what does your code look like, and what's the problem
What we would like to do is to use Link for loading billing / shipping information and but then autofill our own fields instead of using Stripe's Address element.
Is that possible?
For shipping address no that's impossible as far as I know, you can't extract a shipping address from Link (I don't even think that can be configured today)
Got it
So, if we provide Link support we will need to use the Address Element from Stripe
is that correct?
Not really no
Sorry I'm still really struggling with your approach right now. You mentioned migrating from CardElement to PaymentElement. Are you saying you are not using Link in CardElement at all? Because it is supported
We are not using Link in Card Element at all
You got that right
We know we could support it on Card Element but we want to move to Payment Element not because of Link but because the Card Element is marked as legacy and we think it might get deprecated sooner rather than later.
So, we decided to start planning our migration to the Payment Element.
Okay, so what have you tried exactly in Test mode, where are you at with the overall testing? I'm still only following half of the issue. Are you planning to disable address collection in PaymentElement and always have your own? Are you planning something else?
Are you going to do only card and Link? Or other payment methods?
This is how our Terminal looks today. The first square shows you the Card Element. The second square shows our contact information fields which are used for billing and shipping. As you can see there, we managed to make it work in a way were we are only using the Card Element for credit card collection.
Are you planning to disable address collection in PaymentElement and always have your own?
We are exploring that idea. Hopefully, yes.
(I'm really nitpicky but I highly recommend you avoid using capital letters for things like Terminal if you don't mean ours. I know what you mean now but you're going to hit this with everyone on my team)
Are you going to do only card and Link? Or other payment methods?
ACH too with other methods coming in the future.
Okay so you plan to fully disable all billing details collection since depending on the payment method Stripe will require that information inside PaymentElement by default
You'll need to disable this fully using https://stripe.com/docs/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails
I am sorry. I will try to use the small case for our terminal but the images will still have our terminal named in Uppercase.
yeah the images are fine!
What is your overall integration path? Which exact doc are you following? There are multiple ways to integrate PaymentElement.
What is your overall integration path?
I am trying to decide that. We are still exploring the options.
Which exact doc are you following?
We are reviewing them all to find the best path forward.
There are multiple ways to integrate PaymentElement.
Yes, we are aware of that.
lol
Have you tried anything or are you really just looking at docs? Trying to figure out where you are at. If you tried nothing yet, I can fiddle a bit with this on my end
Have you tried anything or are you really just looking at docs?
We implemented a PoC like a year ago and got the Payment Element working within our terminal. We dropped with PoC because there were some limitations with the Payment Element that we didn't want to deal with back then. Now we have more time and since the Card Element is already legacy, we will try to tackle them.
sounds good
Now, that PoC was lost in time so I am starting from scratch. I do know the Payment Element a bit from that previous PoC, but I am open to any suggestions on the best path forward.
Let me pair with my team for a bit (Discord is really busy)
Hi, @crisp ingot
Thank you, Sir
Sure! Things are calming down a bit and someone on my team is making progress, I'll share more details once we have them
@crimson dawn okay sorry this is a lot harder than it should. Are you fine with simply collecting your own billing/shipping address entirely and ignoring the one already in Link?
I was exploring the idea of being able to collect our shipping / billing info by integrating with Link.
Okay so that should just work by default then
If that's not possible, then we may not support link
You have your own address form and you collect that, it works the same as a card
Got it
without Link, no problem
but with Link?
can we still use Link to populate our address form?
๐
I'm sorry we seem to talk a bit past each other
I was asking if you were fine with not extracting the billing details from Link but it seems the answer is no you are not fine with that is that correct?
You absolutely want to extract the existing billing details from the saved details inside of Link?
I'm asking because I think this is impossible but I want to make sure I understand your end goal here
Yes, I was trying to extract the billing details from the saved details inside Link. But if you tell me that's not possible, then we may need to think about how we can support Link in some other way.
yeah that is not possible in that case. But technically that means it makes Link/card a lot easier for you since they work the same way and you ask for the real/full billing/shipping details
I paired with a colleague and there's no way to extract the full billing details from Link otherwise (it'd be bad if there was a way without an action from the customer)