#jarcher
1 messages ยท Page 1 of 1 (latest)
Are you encountering errors or what do you mean by
aren't allowing us to use
And do you have specific example you can share of using this previously with success?
yeah let me grab the error message
And a snippet of your code where you set this would be helpful too
Here
Here's the code snippet : let payment_intent_data: Stripe.PaymentIntentCreateParams = { amount: Math.round(order.cart.cardCheckout.total), application_fee_amount: order.cart.cardCheckout.applicationFee, currency: order.currency.toLowerCase(), customer: customerID, description: order.paymentIntentDescription || `Order #${order.orderNumber}`, metadata: { TaxAmount: order.cart.cardCheckout.taxes, pendingOrderId: order.id, pendingOrderCollection: "ordersPending", ...metadata, }, setup_future_usage: "off_session", capture_method: "manual", payment_method_types: ["card_present"], };
Ok, and you encounter errors when you do this?
Yes, sorry taking a minute to get to a state of reproducing
Of course now it won't reproduce.. even without the error, I am expecting the card to be sved to the client's profile, but it's not
this is the payment intent: https://dashboard.stripe.com/acct_1H0ZfEFSRlrDjPli/payments/pi_3MygeqFSRlrDjPli0z3Jd1IC
Hmm ok yea I don't see any generated_card within the charge payment_method_details as specified here
https://stripe.com/docs/terminal/features/saving-cards/save-after-payment?terminal-sdk-platform=ios
We're looking into this - please bear with us
Hello, we are still looking in to this. It is currently looking like the issue is that our PaymentIntent + setup_future_usage flow may not work with contactless payments
okay gotcha -- I found the error message from earlier as well
We're not getting this anymore, but it was an issue on monday for the same type of payment:
````setup_future_usagecannot be used with one or more of the values you specified inpayment_method_types. Please remove setup_future_usageor remove these types frompayment_method_types`: [card_present]```
Was that just an artifact and you fixed the bug?
cc @naive rapids
Whoops apologies I missed this. Good question. I will check with my colleagues and get back to you
Do you have the ID of the related payment intent there (pi_1234)?
No I don't recall, sorry. I don't think it even generated a payment intent
cc @naive rapids
it wouldv'e just failed
Hi there ๐ taking over, as my colleague needs to step away
Still working with colleagues to get a better idea of what's going on. Will circle back once I have something substantive
Okay thanks! I ended up turning of "setup_future_usage" for terminal payments. But I'd like to turn it back on. It seems like it works now, but can I expect it to work in the future?
Still getting current state. I'll let you know if that seems likely once we have more to share
๐ @cursive stone as far as we can tell this payment was made using Apple Pay.
Card details shared via Apple Pay on Terminal can not be saved
Sorry for the long delay, multiple of us looked but assumed it was not Apple Pay when it turns out it was so it's all expected
okay thanks @fluid finch . how bout his error message that we were getting on monday? ````setup_future_usagecannot be used with one or more of the values you specified inpayment_method_types. Please remove setup_future_usageor remove these types frompayment_method_types`: [card_present]```
can you find a concrete example? I'm looking at that now that I see your question was different (we only looked at "why didn't this card save" for the past hour)
both questions were relevant, so I super appreciate an answer to the first one.
I don't have a concrete example, because the payment intent would fail to be created
I'm unable to reproduce it right now, but we were getting this error on monday (and over the weekend)
sure but every request that fails returns a clear error with a request id in it req_123 so I'm asking if you have one. You used Connect so it's tough to find them. If you don't, any chance you know which account it happened on?
okay good point, I'll look!
okay thanks. there was one with acct_1MWk0hB28EKEehc3 ~ 4pm PT on Monday April 17th. 2023
yeah so that account is the one where you've had errors for a week and it's based in Canada where this feature isn't public so I assume it's related to that, but I'm looking
ahh so terminal just isn't live in Canada?
whoops.. we shipped them a reader b/c they couldn't order one ๐
Terminal is live. The feature to save cards is US only per the docs https://stripe.com/docs/terminal/features/saving-cards/save-after-payment?terminal-sdk-platform=ios (see at the top)
I'm digging internally, this will take a while again unfortunately
@fluid finch okay this is enough for us to just turn off this feature for Canadian accounts
no need to keep digging
appreciate your support
@cursive stone it should just work for you
like clearly it works today, I don't really get why it failed earlier this week. I'm still digging for a bit and otherwise you should ask support to escalate
@cursive stone yeah I'm sorry I can't get any details from this. I'd recommend contacting our support team to ask to escalate https://support.stripe.com/contact sorry about the hassle here