#expensiveee

1 messages · Page 1 of 1 (latest)

clear shardBOT
queen nebula
#

"stripe": "^12.18.0",

grave plover
#

Daimmm, I'm way behind

#

Will try, thanks!

grave plover
#

Ok worked

#

Now I have another quesiton, is there a way to have customer statement descriptors ?

#

I'd have to create a payment intent first no?

queen nebula
#

Statement descriptors can be set at the account level and per payment, so if you want it to be per customer you'd need to set it per payment and track what the custom descriptor is per customer

grave plover
#

When saying statement descriptors, it's what's being shown on the bank statement of the customer correct?

queen nebula
#

Yes mostly, it is ultimately up to the bank what to show on the statement, so sometimes they ignore the statement descriptor that we send and use their own

grave plover
#

How do they define their own? That something you know?

#

Also, how do I have that on a payment-level?

queen nebula
#

Though it is unusual for customers to directly set that. Can you tell me more about your use case?

grave plover
#

No no I'm not looking for the customer to custom the descriptor, I wanna do it for payments

#

My question is, how can I do it if on checkout I don't have the statement_descriptor field?

#

I guess my question would be, how do I use a payment intent for a checkout session

#

Is it even doable

queen nebula
#

The checkout session create function has a payment_intent_data hash with a statement descriptor that you can set