#JulesR-terminal
1 messages · Page 1 of 1 (latest)
when we send the charge amount, ie a payment request to the terminal for $100, how long before it times out before a card is swiped to complete the transaction. ie if waiter rings up the order and walks out to a patio with the terminal, how long before it would time out?
More specifically, is it this step you are talking about? https://site-admin.stripe.com/docs/terminal/payments/collect-payment#collect-payment
I don't think there is a timeout if the reader still stay connected to the sales application (aka SDK)
If they are disconnected somehow, I think you should generate a new PaymentIntent
thanks, this is the question i had. so if it takes 10 mins to walk to the person's table on the deck, it will not drop the sale?
To clarify, you are asking how long after you call collectPaymentMethod() it will take before a Timeout occurs?
Yes
We don't have a published amount of time... really the best thing to do here would be to test it out yourself to get a sense of the Timeout.
Next question: what is the best way to test what BUSINESS NAME the credit card statement will show for the sale to the buyer, while in test mode. We will have connected accounts and want to make sure it shows the right business name on the card statement, for the right account, so buyer from storeA does not see either our company VinesOS or StoreB name
You want to look at the calculated_statement_descriptor on the charge: https://stripe.com/docs/api/charges/object#charge_object-calculated_statement_descriptor
That is what we will pass to the card networks and the issuer.
Important to note that issuers can always show whatever they want and sometimes they show incorrect SDs
Issuers sometimes try to use more "common" names for businesses and have their own logic of how they display Statement Descriptors to try and make the SD more customer friendly. So it is possible that it isn't exactly what you set, though it almost always should be.
how do we test it?
You ensure the calculated_statement_descriptor is exactly what you want it to be.
when i set that on test mode on the connect account it does not save it
Not sure what you mean by that?
The calculated_statement_descriptor is on a charge-by-charge basis
Okay that is the Accounts Payout SD
Which is totally different
ok, where is it set for each account
That is the Payout SD for your Connected Account
Is for the charges themselves from end-customers
What is your new question?
THanks, is it possible to just keep this open for me for 24 hrs?
Tyring to launch and have various questions, want to have this trail here.
THis is for customers buying from our clients, the stores, we want statement to reflect the store not us
We can keep re-opening this thread for you but we typically like to close threads after an hour or so of inactivity because it can be hard to manage when many threads are open.
Catching up, one moment.
Hey @unkempt moon! I'm hopping back on here so I'll take this back over. As @cloud girder noted, it is hard to leave threads open because of the clutter that it entails. Just ask whomever is on to re-open or state a new question when you come back around. I'll leave your thread open for a bit now though.
In terms of the above, you want to set the https://stripe.com/docs/api/accounts/update#update_account-settings-payments-statement_descriptor on your Connected Accounts to control what the end-customers will see on their credit card statements.
i have two responses: so for connected accounts or OUR customers, ie STORE-A , when customer A BUYS from STORE A, what they will see on bank statement is set WHERE:
set the https://stripe.com/docs/api/accounts/update#update_account-settings-payments-statement_descriptor on your Connected Accounts to control what the end-customers will see on their credit card statements.
Y u want to look at the calculated_statement_descriptor on the charge:
Important to note that issuers can always show whatever they want and sometimes they show incorrect SDs
https://stripe.com/docs/api/charges/object#charge_object-calculated_statement_descriptor
On this? TO confirm: https://stripe.com/docs/api/accounts/update#update_account-settings-payments-statement_descriptor on your Connected Accounts to control what the end-customers will see on their credit card statements.
Yep you got it.
If you set the https://stripe.com/docs/api/accounts/update#update_account-settings-payments-statement_descriptor on your Connected Accounts then that will set the default SD that will be used assuming your Connected Accounts are the Merchant of Record (are you using Direct charges or on_behalf_of)?