#amy_api

1 messages · Page 1 of 1 (latest)

covert micaBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1226813524634894347

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

violet tapirBOT
forest ivy
#

We want to make a terminal payment, the card machine to pay, but after the creation of paymentIntent, the card keeps stuck, no response

#

pi_3P3DGA04cT6YoXkE0TyEYkTt

bleak lintel
#

hi! what model of Terminal reader is it? what type of integration are you using(bluetooth/internet/server-driven)?

forest ivy
#

wisepad

#

bluetooth

bleak lintel
#

what does your code look like?
do you discover and connect successfully to the reader?
what's the serial number of the reader?
what client are you using(iOS/Android/RN) and what version of the library?

forest ivy
#

We create paymentIntent on the server, and then the device side to start the swipe, there is a problem, but the Android device side to create paymentIntent, and then swipe the card to pay the normal payment. Why is that?

bleak lintel
#

I don't know, I would need a lot more information to investigate.

forest ivy
#

now the wisePad 3 show Authorising

#

Ok, what information do you need while I gather it

#

serial number:WPC323207048515

#

Android

bleak lintel
#

what does your code look like?
do you discover and connect successfully to the reader?
what version of the stripe-terminal-android library?

forest ivy
#

2.23.1

#

The server code is as follows:
params =
PaymentIntentCreateParams.builder()
.addPaymentMethodType("card_present")
.setAmount(Long.valueOf(amount))
.setCurrency(currency)
.setCaptureMethod(PaymentIntentCreateParams.CaptureMethod.MANUAL)
.build();

#

The server sdk version 22.0.0

#

Or is there any guidance for us? What do you refer to for the docking document?

bleak lintel
#

what does your frontend code look like?
do you discover and connect successfully to the reader?

forest ivy
#

Integrated document

forest ivy
#

Do you understand my side of the problem? Is to create paymentIntent can be created by the client, can also be created by the server, but my side of the server is created, the client pos machine swipe card is unsuccessful, why?

bleak lintel
#

I don't know, I would need a lot more information to investigate.

#

what does your frontend code look like?
do you discover and connect successfully to the reader?

forest ivy
#

Yes, I have been able to adjust the pos machine, but there has been no reply after swiping the card.

#

val cancelable = Terminal.getInstance().collectPaymentMethod(paymentIntent,
object : PaymentIntentCallback {
override fun onSuccess(paymentIntent: PaymentIntent) {
// Placeholder for confirming paymentIntent
}

override fun onFailure(exception: TerminalException) {
// Placeholder for handling exception
}
})

#

Step 2 No success or failure response is received here

bleak lintel
#

sorry but I really need to see the complete code and much more information. Add logs and breakdpoints to the code and figure out how far execution gets and what SDK functions you call succesfully and which ones might have issues.

forest ivy
#

pm_1P3CUJ04cT6YoXkEqMV0soTL this one is successed

#

pi_3P3CWj04cT6YoXkE0oSeInNf this one is fail

#

There is no success or failure feedback after the call, but the pos machine can enter the card page and load the card.

#

pi_3P3CUC04cT6YoXkE07KxGT1M this one is successed. the same to the pm_1P3CUJ04cT6YoXkEqMV0soTL.

#

No callback is entered and no log is generated. Breakpoints are useless

bleak lintel
#

well no, it's not useless. You need to get to a solid understanding of what exact code is executing and which SDKs are being called and which specific function might be called and having an issue. You need to get that technical detail so we can start debugging anything, because unfortunately sentences like "There is no success or failure feedback after the call, but the pos machine can enter the card page and load the card." are meaningless(for example, you say "the call", what call is that?)

bleak lintel
#

there are multiple calls and sections in step 2. What does your code that you wrote look like ( the complete full code) and through the logs/breakpoints you're using, what parts execute and which parts don't, what results and callbacks are returned etc.