#joe-transaction-error

1 messages · Page 1 of 1 (latest)

true sentinel
#

@small bramble we're not really the right people to help with account specific error. Also this is not really a Stripe error

small bramble
#

I thought it was an error because the finalizePayment method (iOS) returns annulled with that message but the customer is charged

#

returns "Failed" sorry

#

*confirmPayment method

true sentinel
#

Happy to try and have a look in that case but I will need way more information

small bramble
#

sure

#

which kind of informations do you need?

true sentinel
#

I need exact code, what call you make, what error you get back and an exact transaction and I can have a look

small bramble
#

Object-c

#

Method: [paymentHandler confirmPayment:paymentIntentParams withAuthenticationContext:self completion:^(STPPaymentHandlerActionStatus status, STPPaymentIntent *paymentIntent, NSError *error) { ..... } ]

#

status value was "STPPaymentHandlerActionStatusFailed"

#

Error number 7

#

ErrorDescription: "There was an unexpected error -- try again in a few seconds"

#

a transaction id is pi_3LRKBED8KdtqZOJf0Jm17Jxa (there are severals)

#

the user was charged

#

we have done about a thousand transactions in five days, and a few dozen of them have had this problem

opaque bobcat
#

hey, having a look. So at least on our end, this payment succeeded completely, so it's unclear why the SDK might report a problem with it(as I mentioned earlier, having your app dump the full error would help)

small bramble
#

on 4th August there will be another event (we manage music festivals). I will log all the nserror dump this time. It's the best I can do at this moment

opaque bobcat
#

yep, looking too at what I can find in our logs

#

you are using a slightly older version of our library(from May 2021) so it might be a client-side bug we have since fixed, doing some investigation

small bramble
#

I will updated the SDK too. Hope that apple will be fast as soon as possibile to publish the updated. I'm preparing a new build right now.

#

I would like to remark that I have done thousands (but really a thousands and thousands) tests in the test enviroment and I have never ever had this error

#

I have checked, the SDK looks like it's the lastest one, 22.6.0

opaque bobcat
opaque bobcat
small bramble
#

this is the current podfile.lock for the stripe part:

#
  • Stripe (22.6.0):
    • Stripe/Stripe3DS2 (= 22.6.0)
    • StripeApplePay (= 22.6.0)
    • StripeCore (= 22.6.0)
    • StripeUICore (= 22.6.0)
    • Stripe/Stripe3DS2 (22.6.0):
      • StripeApplePay (= 22.6.0)
      • StripeCore (= 22.6.0)
      • StripeUICore (= 22.6.0)
    • StripeApplePay (22.6.0):
      • StripeCore (= 22.6.0)
    • StripeCore (22.6.0)
    • StripeUICore (22.6.0):
      • StripeCore (= 22.6.0)
#

yes, build 3.0.4 is the

opaque bobcat
#

oh yeah

small bramble
#

latest version of the app

opaque bobcat
#

sorry, I misread the logs, you were indeed using 22.6.0 on that PaymentIntent, my bad.

small bramble
#

that is compiled with 22.6.0 version

#

👍

opaque bobcat
#

hmm ok. Then yeah I'm not sure what could be causing this. On our backend logs, that payment ran through 3D Secure and it completed and the customer was charged.
Can you share the exact code of your app's ViewController that uses the SDK and the part that logs the error you mention?

small bramble
#

here? there is some code tag? or it's ok to past the code here?

opaque bobcat
#

you can post code inside 3 ` symbols

like this
small bramble
#

test

#

this is the complete method

opaque bobcat
#

so the error we're discussing is the one being handled in case STPPaymentHandlerActionStatusFailed ?

small bramble
#

yep

#

later I would like to ask one thing

opaque bobcat
#

fair enough! unfortunately I have no pointers or other suggestions right now.
I'd need you to log and dump the complete NSError from that code and let us know what it contains the next time this problem happens. i.e. dump the userInfo of that NSError.

small bramble
#

I will do. One thing: there is something I can do to check again when I'm into the STPPaymentHandlerActionStatusFailed case?

#

I mean, if I catch error number 7 I can do some sort of calls to check again?

#

so even if I encounter this error I will call you again

opaque bobcat
#

as in can you add any other code to help? I don't think so. For now we just need more of the client side logs since everything on the backend seems successful.

small bramble
#

I was thinking a call like "hey stripe, can you please give me informations about this transaction id?" 🙂

opaque bobcat
#

if we had the ID of a PaymentIntent pi_xxx that had the problem and a full dump of the error object there might be enough to go on.

#

For what it's worth, did the customer actually complain or notify you of this or are you just looking at logs? Because this error can also happen for just generic connection problems like the phone losing internet connection I believe. So at scale when you have many payments, it's possible this might happen I think(though I'm not 100% sure).

#

either way, the payment succeeds and you'd use webhooks on your backend server to fulfill the customer order

small bramble
#

The transaction I'm looking for comes for customer complains.... maybe there are others that I don't know at this moment.

#

I know, there are other error 7 .... that aren't charged in my logs

#

some of them run away and get charged 😅

#

we are processing refunds in these cases

opaque bobcat
small bramble
#

all clear. Looking at the current flow I don't know if I will be able to write something in two days that use the weekhooks ... specially if I have to modify the app and send it to apple