#nyckid80-obo-payment-link

1 messages ยท Page 1 of 1 (latest)

slate acorn
#

Hi ๐Ÿ‘‹ can you share the ID of the Payment Link that you created (starts with plink_ and the ID of the Checkout Session that it spawned which raised the error you referenced (starts with cs_test_ or cs_live_)?

craggy jewel
#

plink_1LUboYKXseKUVU9Sh2a7O0Xy

#

cs_test_a1IC9VJzVaupMXq0Ge7XcXg3HYADzMU8Km0sE0n5jXqX5SDITGy1jWVL34#fidkdWxOYHwnPyd1blpxYHZxWjA0TUJRfGZOXXZgTlBTUDxWZ2ROU0NMMUxfY21hYVRnXUdGXUhWal9IdDVtYnZDRGE9ZkNVVVNNYlZrb21hVF19Vm08QjJETDFIdH9JY0dAM2BrM0tcbj1SNTUwUGB3XFZ3aCcpJ3VpbGtuQH11anZgYUxhJz8ncWB2cVo1NWI1NDw3XzA9aTE0XFRkQEIneCUl

#

sry i can also send you the req if thats easier

slate acorn
#

Thank you for those, so far everything looks normal and the associated requests that I'm seeing are showing a successful status. Just want to make sure I'm understanding correctly, it's when the customer tries to subscribe that the error is encountered?

craggy jewel
#

literally bounces back as an error above the subscribe button

slate acorn
#

Thank you! Wanted to make sure I was looking in the right place.

craggy jewel
#

yup no worries

#

but the thing is the on_behalf_of works from the branding perspective

#

ie uploaded a logo and icon just as a test

#

and when the payment link is created it shows as the branded page so i'm almost there. i upgraded to the latest api version before attempting this

#

this is all in test mode btw

proud briar
#

๐Ÿ‘‹ toby has to head out soon so I'm also going to start taking a look

craggy jewel
#

i love that you guys use discord

#

i had this stupid grin on my face when i logged in and realized you guys had a legit discord where you were actually helping devs

#

it will subside

#

hopefully

proud briar
#

i'm still trying to reproduce on my end (the first thing I tried didn't work) - give me a bit longer to pinpoint what exactly is different about our requests

craggy jewel
#

thats the actual link that gets created it took the a logo,icon i uploaded for the test connected account

proud briar
#

Finally narrowed it down - I was testing w/ one-time prices before, but I can reproduce when I use recurring prices/subscriptions. Let me raise this with some folks and give you an update soon

craggy jewel
#

no worries do you think this is supposed to work for subscriptions?

#

the payment links docs make clear reference to subscriptions in the parameters

#

so i assume its a bug

proud briar
#

Yeah there's a weird disconnect here where PaymentLinks allows for a top-level on_behalf_of parameter, but Subscriptions doesn't public support on_behalf_of.

craggy jewel
#

ok will wait to hear verdict

craggy jewel
proud briar
#

we're still looking into it ๐Ÿ™‚

craggy jewel
#

k ty

proud briar
#

Circling back - we believe the bug here is that you shouldn't be able to create a Payment Link for a recurring price w/ the top-level on_behalf_of set. We're working on fixing it, but for now I'd recommend removing on_behalf_of from your payment link creation request.

#

If you do need on_behalf_of with Subscriptions, I'd recommend writing in to support (https://support.stripe.com/contact) to see what they recommend as there may be some workarounds

craggy jewel
#

is that something that will be allowed down the road

proud briar
#

I don't think there are any confirmed plans to allow this, but if it's something you need definitely write in so they can see if you qualify for workarounds that allow you to do this

craggy jewel
#

ok understood

#

its weird because the idea of affiliate links for recurring subscriptions should exist

#

feels like a gap in functionality rather than something that shouldn't be allowe

#

d

proud briar
#

I know it's odd (there are reasons for this, but support should be able to clarify)

craggy jewel
#

ok will try with them

proud briar
#

๐Ÿ‘ I'm going to archive this thread now, but if you need anything else feel free to ask in the main channel