When the Reader is disconnected (by turning off Bluetooth on the iPad) while waiting for a card to be tapped, the reader error appears full screen. A correct behavior would be to appear in split screen, the same way as before initiating the payment.
When the Reader is disconnected (by turning off Bluetooth on the iPad) while processing payment or payment success we can get into weird states. Although these states seem functional and after re-connection, we transition to a payment state, we could make improvements for even more solid error handling.
– p91TBi-c11-p2#comment-12991
When the reader gets disconnected, we could move back to the checkout stage.
However, if we do that from the Order Completed screen, or even the processing screen we risk people using a paid order a second time.
If they do that (change the contents and check out again) the order will succeed without a card being tapped.
This means we'd be risking merchants giving products away for free, if they got confused by this.
We should fix this in our architecture, by taking the post-card tap stages of payment out of TotalsView, into a new view. By doing that, we can have separate, simpler handling for reader disconnection on these screens.
dangermattic
commented
1 week ago
Description
When the reader gets disconnected, we could move back to the checkout stage.
However, if we do that from the Order Completed screen, or even the processing screen we risk people using a paid order a second time.
If they do that (change the contents and check out again) the order will succeed without a card being tapped.
This means we'd be risking merchants giving products away for free, if they got confused by this.
We should fix this in our architecture, by taking the post-card tap stages of payment out of TotalsView, into a new view. By doing that, we can have separate, simpler handling for reader disconnection on these screens.