#rahul_86583
1 messages ยท Page 1 of 1 (latest)
Hey there, the docs don't indicate anything specifically necessary for this so I'd expect the amount to be shown as in the examples when you call collectPayment
You say the actual collection works as expected and the payment is successful?
Can you share an example payment intent ID?
What version of the SDK are you using and can you share snippets showing how you initialize, connect to the reader, and call collect payment?
Here is PaymentIntent Id : id=pi_3NacCDB7qaunkkSG1r5Dgnqs
I'm using the latest sdk version as mentioned in the docs:
implementation "com.stripe:stripeterminal-localmobile:2.22.0"
implementation "com.stripe:stripeterminal-core:2.22.0"
Hey there ?
I'm here, i was waiting for snippets showing those other pieces of your integration
Also you mention using a "simulated" reader, but our simulated readers in the SDK have no UI so something doesn't align here
Can you explain more about what/how you're connecting when you share those snippets?
val config = DiscoveryConfiguration(
timeout = 0,
discoveryMethod = DiscoveryMethod.LOCAL_MOBILE,
isSimulated = true,
locationId
)
discoverCancelable =
Terminal.getInstance().discoverReaders(config, object : DiscoveryListener {
override fun onUpdateDiscoveredReaders(readers: List<Reader>) {
CoroutineScope(Dispatchers.Main).launch {
try {
val readersArray: ArrayList<Reader> = ArrayList()
readers.forEach {
if (it.deviceType == DeviceType.COTS_DEVICE) {
readersArray.add(it)
}
}
if (readersArray.isNotEmpty()) {
delay(500)
connectTapToPayReader(readersArray[0])
}
} catch (e: Exception) {
e.printStackTrace()
}
}
}
}, object : Callback {
override fun onFailure(e: TerminalException) {
e.printStackTrace()
//
// mContext.showShortToast("Failed At discoverReadersAction")
Log.v("TERMINAL_READER", "Failed At discoverReadersAction")
}
override fun onSuccess() {
println("discoverReaders succeeded")
Log.v("TERMINAL_READER", "discoverReaders succeeded")
}
})
Ok, then there is no UI, so what are you referring to about the display then?
Note that the simulated reader does not provide a UI. After connecting to it in your app, you can see it working when calls to the Stripe SDK or API succeed.
https://stripe.com/docs/terminal/references/testing#simulated-reader
After call Terminal.getInstance().collectPaymentMethod
The SDK opens a screen which I attached above,
And I want to refer again that I'm Implementing TapToPay
Please see the above image I think there is some misunderstanding, Please Help
And the doc you refer, I think is for physical reader, But I try to simulate Android TapToPay which works and also shows an UI for Collect card data, The only problem I've that it not showing amount.
Thank You!
Ok, looking into this more
Thanks
When you call this, is the simulated reader automatically presenting the card for you successfully, causing this to be dismissed?
Also, do you get the expected complete UI on a real device?
It appears as it shows in above image, and when I Click on TAP TO SIMULATE PAYMENT it get dismissed and payment get success, and if I click on below cross button then it dismissed and payment get Canceled.
No I'm not getting the complete UI as mentioned in the doc
I think this is just a minimal UI used for the tap to Pay simulation, but I agree our docs should make this more clear, and ideally include the amount etc
Are you having any issues with the UI on a real device?
I can file feedback about this simulator UI and the docs to improve things
But it sounds like both the success and cancel flows to in fact work, and the issue is limited to a UI that looks to be incomplete
Yes payment flow is working fine and yes issue is with UI only
And what about when you're not using the simulated reader?
As of now I only tested this in simulated mode.
Ok, thanks for confirming
๐ Let us know if you get a chance to test on a real device and are seeing similar UI issues
Sure ! and how I know when There is some update regarding this issue.
Thank You!
And Yes I'm testing it in a real device with simulated option true for TapToPay
Are you running in "debug" build target? If so, you can build your app against "release" build target and test it with the non-simulated reader
At present I can't test with non-simulated reader,
When I will test with non simulated reader will update you.
Okay ๐