Hi there,
I am using the installed Stripe package and the Vendr Checkout Package.
I can now finish a transaction and everything seems to be working fine.
However, as seen on the picture below, Stripe doesnt recognize the Address.
The same can be seen in the event data, as well as the email address from the purchase is set to NULL.
However, when looking at the logs under the developers section in Stripe I can see that Stripe receives the right data just fine
I am not sure, if it is because I am in test mode that Stripe doesnt recognize the address, or if it is because I need to configure Stripe, or if it is the Stripe Package that is posting it with the wrong ID's...
I believe the address gets associated with an attached customer in stripe so you’d need to click through to the customer object to see the address in stripe.
I’m not sure what that address on the payment is meant to be nor how it’s populated. We pass all the details the docs say we need to pass.
Hi Matt,
Thanks for the quick reply!
Yes, I can see the address gets posted with the attached customer.
I have been in contact with Stripe to ask what the address's function on the payment is. They informed me that it is only for AVS (Address Verification Service), and send me this link https://stripe.com/docs/disputes/prevention/verification#avs-check
While the feature is not necessary, it is a nice to have.
Is this in the pipeline for future updates?
If so, then I would not focus anymore on this, for now :)
Hi again,
I see the issue with the lack of documentation.
However, since we are currently re-building our site from scratch using umbraco and Vendr, I do have access to our old site and the Stripe solutution used. AVS works fine with the old solution and it recognizes the address. If you want to, I can send you some of the log files of the old solution?
If you could check where and how you are passing the address that could be handy. I'm guessing you won't be using the Stripe checkout API's though as it's finding how to supply them as part of this.
Regardless, it could be useful so sure, if you can find how it's passed, but all means let me know.
I am not sure if I can get access to the source code of the old site, but I have the paymentintents logs and the paymentintents"ID"confirm logs.
Do you have an email I can send the logs to?
Ok, after a conversation with Stripe on twitter (https://twitter.com/mattbrailsford/status/1285884864919674882) I think the only way we can force this address collection is to update the payment provider to set the billing_address_collection API option to be required. This then forces Stripe to collect a billing address which I think is then what gets stored against the payment method.
The problem with this is that this forces Stripe checkout to display billing address fields which are required but we have no way of pre-filling them with data we have already collected and so it requires the user to fill in the billing address twice.
From my conversation with Stripe, I don't think there is any way we can achieve sending the address from our end without going full on custom Stripe integration, which I really don't want to do as it's a nightmare to maintain (I know this because this is the approach we followed in TC).
If there is no way to achieve this with Stripes Checkout solution, then I'm going to have to say this is not possible and if you need that facility, then you'll need to implement a custom solution. I think there are plenty of other validation rules in Stripe which should give you plenty of protections, and it may very well be possible to state at an account level that you want to collect billing address such that the fields are displayed during checkout, but we don't want that to be the default in the payment provider.
For now then I'm just going to have to say the provider is as it is as it's the best solution we can achieve with the current Stripe Checkout API options.
Hi Matt,
Alright, thank you for coming back and telling me :)
I will just stick with the solution provided by you guys!
A second quick question. Have you been able to use the webhook with Stripe and the Stripe package provided by you? I get an errror 400 everytime, and not really sure why.
Yea, we use the Stripe provider on the Vendr.net site and it's all working as expected. If you are having problems, if you could raise is a separate issue that would be great.
Using Stripe with Vendr Checkout Package
Hi there, I am using the installed Stripe package and the Vendr Checkout Package. I can now finish a transaction and everything seems to be working fine. However, as seen on the picture below, Stripe doesnt recognize the Address.
The same can be seen in the event data, as well as the email address from the purchase is set to NULL.
However, when looking at the logs under the developers section in Stripe I can see that Stripe receives the right data just fine 
I am not sure, if it is because I am in test mode that Stripe doesnt recognize the address, or if it is because I need to configure Stripe, or if it is the Stripe Package that is posting it with the wrong ID's...
Any ideas on how to fix this?
Hi Victor
I believe the address gets associated with an attached customer in stripe so you’d need to click through to the customer object to see the address in stripe.
I’m not sure what that address on the payment is meant to be nor how it’s populated. We pass all the details the docs say we need to pass.
/Matt
Hi Matt, Thanks for the quick reply! Yes, I can see the address gets posted with the attached customer. I have been in contact with Stripe to ask what the address's function on the payment is. They informed me that it is only for AVS (Address Verification Service), and send me this link https://stripe.com/docs/disputes/prevention/verification#avs-check
While the feature is not necessary, it is a nice to have. Is this in the pipeline for future updates? If so, then I would not focus anymore on this, for now :)
Hey Victor,
The main thing really is knowing where this actually needs supplying. I've got a feeling it needs supplying as the shipping details on the payment intent object
https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-shippinghowever annoyingly in the docs this doesn't indicate this is required for AVS so I'd need clarity on this.If that is the case then we can look to extend this part
https://github.com/vendrhub/vendr-payment-provider-stripe/blob/dev/src/Vendr.PaymentProviders.Stripe/StripeCheckoutPaymentProvider.cs#L269to include the shipping address details, although we'll need some more settings to allow it to know which order properties contain the shipping address.I could probably do with getting some clarity from Stripe as to whether this is the case and that is what that address field is for.
Hi again, I see the issue with the lack of documentation. However, since we are currently re-building our site from scratch using umbraco and Vendr, I do have access to our old site and the Stripe solutution used. AVS works fine with the old solution and it recognizes the address. If you want to, I can send you some of the log files of the old solution?
If you could check where and how you are passing the address that could be handy. I'm guessing you won't be using the Stripe checkout API's though as it's finding how to supply them as part of this.
Regardless, it could be useful so sure, if you can find how it's passed, but all means let me know.
/Matt
I am not sure if I can get access to the source code of the old site, but I have the paymentintents logs and the paymentintents"ID"confirm logs. Do you have an email I can send the logs to?
Hi Victor,
Sure, you can email us on [email protected]
/Matt
I have sent all logs, which seemed relevant, to the email address listed above :)
Ok, after a conversation with Stripe on twitter (https://twitter.com/mattbrailsford/status/1285884864919674882) I think the only way we can force this address collection is to update the payment provider to set the
billing_address_collectionAPI option to berequired. This then forces Stripe to collect a billing address which I think is then what gets stored against the payment method.The problem with this is that this forces Stripe checkout to display billing address fields which are required but we have no way of pre-filling them with data we have already collected and so it requires the user to fill in the billing address twice.
From my conversation with Stripe, I don't think there is any way we can achieve sending the address from our end without going full on custom Stripe integration, which I really don't want to do as it's a nightmare to maintain (I know this because this is the approach we followed in TC).
If there is no way to achieve this with Stripes Checkout solution, then I'm going to have to say this is not possible and if you need that facility, then you'll need to implement a custom solution. I think there are plenty of other validation rules in Stripe which should give you plenty of protections, and it may very well be possible to state at an account level that you want to collect billing address such that the fields are displayed during checkout, but we don't want that to be the default in the payment provider.
For now then I'm just going to have to say the provider is as it is as it's the best solution we can achieve with the current Stripe Checkout API options.
/Matt
Hi Matt, Alright, thank you for coming back and telling me :) I will just stick with the solution provided by you guys! A second quick question. Have you been able to use the webhook with Stripe and the Stripe package provided by you? I get an errror 400 everytime, and not really sure why.
Hi Victor,
Yea, we use the Stripe provider on the Vendr.net site and it's all working as expected. If you are having problems, if you could raise is a separate issue that would be great.
/Matt
is working on a reply...