#mubashar-3DS-statement-descriptors
leaden prairie
fallen cairn
Mark here (I work at Locally with Mubashar) following along.
leaden prairie
Hi there 👋 we don't have any control over the information displayed within the modal/popup during a 3DS/SCA authentication flow, this is all controlled by the issuing bank, so I don't think there is a way to have that be a non-zero amount if you're using Setup Intents.
Statement descriptors are also tricky as it's ultimately up to the card issuer what information they put on the statement, but do you have the ID of the Payment Intent that is associated with the payment shown in that statement?
fallen cairn
Yes it's pi_3KP1rzGNWtoZCM791uyjOvRa
leaden prairie
Thank you, pulling that up
Ah sorry, I overlooked that you were asking about the $0.00 line, do you have the ID of the Setup Intent that corresponds with that line?
fallen cairn
@grand cairn is that something you have?
leaden prairie
Looking at that payment intent, I see that you're specifying the statement_descriptor and it doesn't look like on_behalf_of is being used, so I'd like to compare that to how you're creating the setup intents.
grand cairn
Hey @leaden prairie ,
on_behalf_of is being used with SI. Can you also assist, where I can list SIs?
leaden prairie
You can use this endpoint to list setup intents, there are also a couple filter options that will let you do a more targeted search:
https://stripe.com/docs/api/setup_intents/list
grand cairn
I have found the SI. It's https://dashboard.stripe.com/setup_intents/seti_1KP1mzAAKdQR3wItxLiXKzHl
@leaden prairie do you need anything else?
short acorn
Hey there, I'm looking into this still (working with toby)
grand cairn
Okay NP.
short acorn
Still looking into this, but can you tell me more your payment flow and the use of setup intents up front?
We spoke about this a bit last week: if you're aware of a specific amount (as part of a first payment) then you likely want to use a payment intent instead. You can use setup_future_usage to save the payment method for future use:
https://stripe.com/docs/payments/save-during-payment?platform=web#web-create-payment-intent
fallen cairn
Hey @short acorn Mubashar may have tapped out for the evening so I can take over for him
Our cart is for Buy Online, Pickup In Store. When the order is placed, we authorize the shopper's credit card, but we don't charge until the store receives the order and confirms that they have it in-stock.
We use Setup Intent because sometimes the orders can be multiple products, so this way, we set up the shopper's payment details once instead of having to do it individually for each item.
Is this understanding correct? We are under the impression that if we only used payment intents, each item in the cart would have to have the payment details saved individually, including the 3D Secure/SCA two-factor step.
Btw, we create separate payment intents per product in the cart because for example, sometimes a store will receive an order for two products, but can only confirm one item and not the other. This way then can confirm one and reject the other.
short acorn
This is not quite accurate, you can use the setup_future_usage approach in the docs linked above to allow you to create multiple payments for the payment method after authenticating once
Note that with 3DS auth for future payments (whether by setup intent or payment intent) is always subject to potential auth challenges again in future
You'll need to determine the best flow for your business/customers, but one I've seen used as a customer than can be effective is authorizing for the full order amount up front, but with delayed capture. Docs: https://stripe.com/docs/payments/capture-later
You have 7 days to capture up to that amount. If the full order is fulfilled within 7days, you just capture the entire payment. If some items are unavailable, you can capture less by specifying amount_to_capture: https://stripe.com/docs/api/payment_intents/capture#capture_payment_intent-amount_to_capture
If items are delayed, you can capture less and create future payment intents using the same PM. The customer may need to authenticate again if the bank asks for it, but this is already true with the setup intent, too.