#Sibu John

1 messages · Page 1 of 1 (latest)

stray locustBOT
sleek nimbus
#

Hi let me check with a colleague really quick

#

What's the serial number on that reader?

keen mauve
#

WSC513142028959

sleek nimbus
#

Thanks

#

Ok so my colleague said this is actually expected that the reader will show as online for about 2 min after powering off. We don't continuously poll the device every second and wait those 2 minutes to help with blips where the reader is still online but not connected.

keen mauve
#

Okay..

sleek nimbus
#

Also the person initiating the payment flow can easily check if the reader is on or not prior to starting the flow. We don't support unmonitored terminal integrations anyway.

keen mauve
#

Okay..

We were trying to integrate the same for subscriptions
I believe the subscription are not deducting any amount while presenting the card
The reader just collects the card information only

How do we test different scenarios for a card failures

For one time payment, we have test amounts like 1.02, 1.03, 1.55, 1.65, etc

How about subscription? To test different failures?

sleek nimbus
#

How are you collecting payment for subscription?

#

Which guide are you following?

#

You should be able to create a subscription for the same test amounts

#

Not 100% sure if it works the same as with payment intents off the top of my head though

keen mauve
#

To proceed a subscription, we initiates a request to create a subscriptionIntent first
Then waits for the card to be presented
This time no amount is going to be deducted from the card, but collects only the card information

My need is to make the card to fail to test different test scenarios
We have test card, which always accepts the card for subscription since it's not deducting any amount
We tried all those test amounts, but card accepts at once

sleek nimbus
#

Ok let me check with a colleague

#

Ok so this isn't possible unfortunately

#

The amount testing is just for 1-time payment intents