#mudassir.dev

1 messages · Page 1 of 1 (latest)

runic badgeBOT
covert loom
#

👋 happy to help

edgy cosmos
#

Yes

covert loom
#

PaymentLinks aren't meant to be customer-driven

#

instead you can use Checkout Sessions

#

which might be better suited for your use-case

edgy cosmos
#

I am using checkout sessions but the problem is users are paying with another email vs the one stored in our DB and in that case I am unable to find which user paid for what

#

So I want a way that when I send user a link and user pays it I should exactly know which link was this

#

so I can trigger my API

#

Hello?

covert loom
#

I understand

#

this is why I suggested using Checkout Sessions instead of Payment Links

edgy cosmos
#

How can I achieve that using check out sessions, can you elaborate

#

Unique Identifiers for each user

covert loom
#

you can pass in metadata in the Checkout Session

#

as another way to identify your customer in your DB

edgy cosmos
#

Is it a wise idea to create custom stripe checkout sessions for each user?

#

@covert loom

covert loom
#

yes why not?

edgy cosmos
#

Talking in terms of scale, we have hundreds of thousands of user.

covert loom
#

how are your customers getting into your Checkout flow?

edgy cosmos
#

Right now, we have a predefined checkout session link which we send to our user and they make the payment.

covert loom
#

what you can do instead is host a page on your website, and send a link to that page with whatever query params you want to your customers
when the customer visits that link, your backend code will generate a Checkout Session and automatically redirects the customer to the CHeckout Session

#

while creating the Checkout Session you will be able to add the metadata/client reference as you like