#.stevenp

1 messages · Page 1 of 1 (latest)

spare boltBOT
karmic gull
#

Hi there, can you tell me exactly what is not working?

fast atlas
#

When I install from that URL it takes me to:
https://api.chargeblast.io/callback_stripe?user_id=xxx&account_id=xxx&install_signature=****&stripe_user_id=yyy

instead of

https://api.chargeblast.io/callback_stripe?user_id=xxx&account_id=xxx&install_signature=****&stripe_user_id=yyy?customer=query_string=XXXX as I would expect

karmic gull
#

ok so the customer=query_string=XXXX is missing, am I right?

fast atlas
#

yes, thats correct

#

it looks like when stripe generates the callback url, it appends its own query strings and overwrites any query params that are passed in in the original redirect uri field

karmic gull
#

It looks like this is what is happening.

fast atlas
#

indeed. anything that can be done to fix this, or is it a bug on Stripe's side basically?

karmic gull
#

If you think it's something that make Stripe product better, you can write in to Stripe support and let them know about it https://support.stripe.com/contact/email

fast atlas
#

ahh well i just need to pass specific user info back to my backend during the callback url for the installation link. how would i do this?

#

i cannot either do it like this: redirect_uri=https://api.chargeblast.io/callback_stripe/{{ CUSTOMER_UID }} as that is blocked via Stripe, since you can't do a wildcard allowed Redirect URI

karmic gull
#

Ok, it looks like there's no way to append extra params to the redirect_url at this moment.

fast atlas
#

ok interesting. so what i could do is send the user to a temporary front end url which has customer uid cookied and then redirect back to the backend url with the params appended

#

quite hacky but coudl be done

spare boltBOT