#avery-terminal-decline

1 messages · Page 1 of 1 (latest)

scenic heronBOT
drifting oar
#

Hey sorry about the delay, but I'm not seeing any payment attempts on that payment intent

#

Do you have specific request logs you're seeing for this decline?

#

Or how does it manifest for you?

slender acorn
#

It just declines on the reader

#

Just automatically saying declined

#

Want me to get a photo?

drifting oar
#

Yea sure, but have there been any other changes compares to what worked previously?

slender acorn
#

Not really anything big

#

Maybe my colleciton method is weird

drifting oar
#

Can you share the reader serial number?

#

I can check if the reader logs reveal anything

slender acorn
#

Sure

#

SDR706250001017

drifting oar
#

The only think I'm seeing is a number of invalid currency errors -- is it possible you're triggering something with an incorrect currency?

#

The PI you shared was using usd which makes that error unexpected, to me

slender acorn
#

yeah I saw that but it should be good

#

is there a way to start a collect with a different currency?

drifting oar
#

Not that I am aware of, but that error seems to be happening repeatedly

slender acorn
#

Hmm let me try again and see if you see it

#

Alright just sent one and got an error

#

pi_3Of7HnAcqRxm04BK1TYZsM4u

drifting oar
#

Are there any other logs from the reader side you can share, and where you able to get that image/recording of what happens?

slender acorn
#

Dev logs look fine to me

#
2024-02-01 15:55:13.943  2969-3209  StripeTerminal          co.frostbyte.driposreader            I  class=TerminalStatusManager message=waitForInput.
2024-02-01 15:55:13.949  2969-3209  StripeTerminal          co.frostbyte.driposreader            D  class=RemoteReaderAdapter message=collectPaymentMethod
2024-02-01 15:55:13.950  2969-3209  StripeTerminal          co.frostbyte.driposreader            I  class=HandoffReaderController message=startPaymentCollection intentId=pi_3Of7HnAcqRxm04BK1TYZsM4u updatePaymentIntent=false enableCustomerCancellation=false
2024-02-01 15:55:13.952  2969-3209  StripeTerminal          co.frostbyte.driposreader            D  class=AidlRpcClient message=makeRequest service=HANDOFF_SERVICE method=COLLECT_PAYMENT_METHOD requestId=4
2024-02-01 15:55:13.953  2969-2969  StripeTerminal          co.frostbyte.driposreader            D  class=HandoffReaderController message=startReader componentName=ComponentInfo{co.frostbyte.driposreader/co.frostbyte.driposreader.MainActivity} isMainThread=true isFinishing=false isDestroyed=false isActivityTransitionRunning=false isChangingConfigurations=false isChild=false
drifting oar
#

And what does the reader flow look like?

slender acorn
scenic heronBOT
slender acorn
#

Do any of the listeners have more granular logs with why a decline happened

#

Assuming since they are client side not server side we don't get passed much

drifting oar
#

We're looking into the device logs to see if anything else stands out

scenic heronBOT
#

avery-terminal-decline

drifting oar
#

How long ago did this test card start failing? And nothing else about the integration changed?

#

Do you have another test card to try?

slender acorn
#

I upgraded the integration to the 3.x

#

I was on 2.x but I am using the same code from tutorial

#

Different card declines as well

drifting oar
#

Ok the 3.x SDK is new, gotcha

#

Can you share any more about the code paths being hit in your integration when this happens?

slender acorn
#
        CollectConfiguration collectConfiguration = new CollectConfiguration.Builder().build();
        Cancelable cancelable = Terminal.getInstance().collectPaymentMethod(paymentIntent,
                new PaymentIntentCallback() {
                    @Override
                    public void onSuccess(PaymentIntent paymentIntent) {
                        callback.onSuccess(paymentIntent);
                    }

                    @Override
                    public void onFailure(TerminalException exception) {
                        callback.onFailure(exception);
                    }
                }, collectConfiguration);
#

The createPaymentIntent is working

#

This is the only failing part I have

drifting oar
#

and the onFailure is called here?

slender acorn
#

Nope it's not even called I believe

#

I can log aagain

#

It does not get called unless I exit out of the Stripe Collect screen

sand glen
#

👋 Stepping in for my teammate. Since this is fairly complex, we'll need to work on this over email instead. This way we can continue to test with any code you share and report back on our findings. Could you open a case with our Support team and let me know when the case has been opened? https://support.stripe.com/contact/

slender acorn
#

Can we work this over slack?

#

I have a terminal channel they just are not messaging me back

sand glen
#

In your case, please mention that you were working with support engineers on Discord and include some of the PI and request IDs from this thread so I can quickly find your case.

#

No, we can't work on this over Slack. Could you clarify what you mean by "have a terminal channel"? Do you already have a contact at Stripe?

slender acorn
#

I am in a Slack channel with the Stripe Terminal team

#

Just search up Dripos on your slack connect

sand glen
#

Ah, gotcha. I recommend continuing to nudge there and I can still retrieve your support case so we don't lose the context from this conversation

slender acorn
#

Awesome ty

sand glen
#

@slender acorn I see you're offline so not sure if you'll get this. I don't see your support case yet. As mentioned, when you file it, please mention some of the IDs you included above (including the reader serial number), as well as the fact that you were chatting with our team in Discord.