#Hari - invalid shipping address
north shale
how do i get request Id
north shale
Apple pay is giving this error. We haven't changed anything
we are using stripe hosted checkout
quasi geode
Can you send the request ID for that checkout session
spiral star
jovial dome
Hello! I'm taking over and catching up now...
spiral star
cs_live_b1DyGAbC6gX5hz8P1NsWBtLS9s5Zv7X1ZVFWE44iD0MXAFXWujeSLeWURk
is this the request ID you looking for.
jovial dome
Yep, that will work, let me take a look...
I think this is an issue on our end, we're looking into it now. When did you first notice this happening?
spiral star
Since Friday evening
jovial dome
Thanks. We're investigating now!
spiral star
Thank You🙏
spiral star
https://checkout.stripe.com/pay/cs_live_b1DyGAbC6gX5hz8P1NsWBtLS9s5Zv7X1ZVFWE44i...
I just used this and made payment with google pay. That went through. So the issue is only with apple pay
jovial dome
Yep, we've confirmed it's only Apple Pay that's impacted.
Will you give it another try now and see if it works as expected?
jovial dome
Oh, I should have said that you'll need to reload Checkout and then try again.
Does reloading and trying again still not work?
jovial dome
Can you give me the ID of the new session that's not working?
jovial dome
Hang on, that session has different parameters and you're requesting a shipping address. Can you create a session with the same parameters as before?
spiral star
spiral star
Hang on, that session has different parameters and you're requesting a shipping ...
Its exactly the same code for test v/s prod. .. how do we request a shipping address
jovial dome
Hang on, let's back up. The first Checkout Session you created did not have shipping_address_collection set, but this latest one does.
Why did that change?
spiral star
This is the test environment.. we havent set this . can you check if Stripe test checkout is doing on its own
YEs the prod one is working
Thanks a lot
jovial dome
You're doing it in your Node code. Have a look at this request: https://dashboard.stripe.com/test/logs/req_WnafY1NqabZtAk
spiral star
We are not doing anything different for test vs prod.
we have exactly the same code and the same method
just the initialization is different
jovial dome
That's not what I'm seeing. Compare to this request: https://dashboard.stripe.com/logs/req_99Aq95KX7DMyFi
You're not setting shipping_address_collection there.
spiral star
Yeah I saw in the request payload.
I dont think its in code.
there is another bug in the test environment can you check on your side
jovial dome
Those requests are coming directly from your code.
It's not happening on our end.
To clarify, the invalid shipping address issue you originally reported was an issue on our end that we just fixed. The fact that you're specifying shipping_address_collection in test mode is something you're doing on your end.
spiral star
Makes sense.
What I am saying is there is chance the request could have default values. And if we dont set anything those default values would take over.
That is my hunch of whats happening
can you confirm in the stripe module of a bad push
I am pretty certain you will find something messsy there.
I will get back to this thread in 30 mins. leave it open.
Trust me you will find something on our side. I have written this code. and till this time I didnt know about "shipping_address_collection"
jovial dome
What I am saying is there is chance the request could have default values. And if we dont set anything those default values would take over.
That is my hunch of whats happening
That is not what's happening.
Can you share the code that's creating this request?
Would be happy to help you debug it.
jovial dome
@spiral star You still around? Anything else I can do to help?
worn stirrup
opened!
spiral star
Thanks
session = await stripe.checkout.sessions.create(
{
payment_method_types: ['card'],
line_items: line_items,
mode: 'payment',
payment_intent_data: {
application_fee_amount: applicationFeeAmount,
metadata: metadata,
},
success_url:
endpoint +
'?stripeRedirect=success&id={CHECKOUT_SESSION_ID}&' +
successparams,
cancel_url:
endpoint + '?stripeRedirect=receipt&' + cancelparams,
metadata: metadata,
},
strAcc
);
This is the code which is creating the checkout session for both prod and test flow
@worn stirrup : context for you is when we are doing stripe hosted checkout and using apple pay, it is defaulting to "shipping_address_collection"
worn stirrup
Are you sure there can't be any other place in your code that would set shipping_address_collection? While it could be possible for us to have default values, they wouldn't show up in the request body unless they were explicitly set by you in the code. From the requests that you've shared like req_WnafY1NqabZtAk there's no way for shipping_address_collection to be included in the request body unless you sent it to us
spiral star
I am pretty certain we are not setting up shipping_address_collection
can you send me how to set it : shipping_address_collection.
you think of anything else, that can go wrong.
const stripe = require('stripe')(stripeToken, {
apiVersion: '2020-08-27;us_bank_account_beta=v2',
});
apiVersion: '2020-08-27;us_bank_account_beta=v2',
});
Let's back up for a minute here (since my concern right now is that the code you're looking at doesn't match the code that's generating Checkout Sessions for you). Can you modify your test code to set payment_intent_data.desctiption: 'testing' and then send over the Checkout SEssion that gets created?
spiral star
we are using initializing the stripe module...as above.. do you see that as an issue.
worn stirrup
No, that wouldn't be the issue - can you try what I suggested?
spiral star
cs_test_b1WtK7acHzlhmyy53R7kGuB4zEo6lNJ9auLGeYJS0heL6fTuxwnYlhRzGn
Yes it worked this time
do you see desctiption
worn stirrup
Yup I see it! Awesome, that lines up with the code you sent over earlier. Does apple pay work with this one?
spiral star
yes
I still dont know the root cause.
but will take it .. things are working.
thanks to you and Rubeus
One last thing. Rubeus fixed an issue with apple pay in prod env on the Stripe side.
We had this issue since Friday and raised it here and on support.stripe twice. But the support was not helpful
What is the best place to raise an issue over weekend if we ascertain issues with some flows
worn stirrup
I'm sorry support wasn't more helpful - while you can always try asking here, there isn't guaranteed staffing in this channel over the weekend which is why we recommend going to support.