TriodeOfficial

[tiny stone]

Unfortunately there's no way to prevent that behaviour right now: Payment Links will always create a new Customer object when required (which is true for Subscription scenarios)

You likely want to switch to using Checkout directly, where you can re-use cus_xxx IDs: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout#handling-existing-customers

[wooden wave]

Ok. So I do need to implement my own checkout page which does the logic I'm thinking about?

[tiny stone]

Depends what you mean by 'checkout page'. You can leverage Checkout Sessions directly (which Payment Links just wrap), like I linked

That will allow you to pass existing Customer objects if you have them

[wooden wave]

OK i'll take a close look.