#andy-pricingtable-customerid

1 messages · Page 1 of 1 (latest)

acoustic zodiacBOT
rigid sail
#

Good question, checking in to this now

#

I'm not seeing a documented way to do this. Would you mind passing customer="cus_1234" like you would pass in the customer email? It is possible that there is an undocumented parameter there. Otherwise I can look a bit deeper

sterile sun
#

Sorry it's taking a minute while i spin up my app. Have a package conflict I gotta resolve first.

#

It created a new customer sucessfully, but assigned customer_id="cus_NA9bcCdSEx4RN0"

rigid sail
#

To be clear, you assigned cus_NA9bcCdSEx4RN0 but it basically ignored that?

sterile sun
#

Subscribing a second time did in fact create a second brand new customer as well.

rigid sail
#

Gotcha. That makes sense, I will look again to see if there is some other way to achieve this.

sterile sun
#

Correct.

#

It did not add the second subscription to this customer but created another unique customer.

image.png
rigid sail
#

Gotcha. Thank you for testing. I am still looking in to this. Unfortunately subscriptions can't really be transferred between customer objects either which could make workarounds a bit complicated.

#

So unfortunately I have confirmed that this is not currently possible but is a very heavily requested feature. I will add your interest to that feedback to hopefully push it along further

#

In the meantime I don't think there are any particularly great workarounds that involve the pricing table. The best thing I can think of would be to listen for webhook events, check if you already have a customer with that email, delete the subscription that was just created, and create a new subscription on the old customer with a 1 cycle off coupon or something.

#

So it might make sense to do that, or it might make sense to hold off on using the pricing table and more or less make four checkout session links and your own custom pricing table. Customers can definitely be re-used with normal Checkout sessions

sterile sun
#

Thank you for looking into it and getting that confirmation for me.

#

Also thank you for the additional advice. You are correct that I want a "pricing table" feel for the user. I'll likely stick with what I have for now, knowing that in the future I may have to create proper checkout sessions likely you suggested.

rigid sail
#

Yeah, sorry we don't have better options today

#

Would you be able to send me your account ID (acct_1234...) It will help me file feedback here

sterile sun
#

I stepped away for a minute. Sorry, I'll get it to soon.

spark plume
#

andy-pricingtable-customerid

sterile sun
#

acct_1M9FkHLmxGS25FUi