Arctic

[flat cloud]

hi! raw PaymentIntents are indeed just that, they don't have any API linkage to our other objects like Products or Prices.

So generally you either use some other Stripe integration, like CheckoutSessions(which use line_items that connect to Products) or Invoices(similar idea), or you use metadata(https://stripe.com/docs/api/metadata) on the PaymentIntents you directly create to store information about what the customer is purchasing.

[sharp moth]

the thing with using metadata is there will be different amoiunt of products each time

[flat cloud]

hmm, not sure I follow, what issue does that specifically result in?

[sharp moth]

and i think i asked this before and was told i cant put objects in metadata of payment intent

[flat cloud]

correct, it's just a string->string bag

you could like JSON stringify something and put that in. But really the idea would be you keep the stuctured data in your database and in Stripe you have metadata:{"my_order_id": "<unique identifier to lookup in my database>"}

[sharp moth]

hmm okay json stringifying actually sounds like a nice solution , imma try that thank you:)

or you think there could be a problem with that?

[flat cloud]

well you might run into the limits on the length of value

You can specify up to 50 keys, with key names up to 40 characters long and values up to 500 characters long.

[sharp moth]

okay not optimal :/

[sharp moth]

how long does it usually take until a paymentIntent is successful?

Im trying to figure out how i should build the payment confimation page

[fading spoke]

Hi 👋 jumping in as my teammate needed to step away. The rate at which a Payment Intent moves from processing to succeeded will vary depending on the type of payment method that is being used. Cards and other instant notification payment methods are pretty quick, but bank account debits can take days to process.