Manage deferred authorizations on mobile readers
Track offline queues and merchant exposure without confusing local acceptance with an acquirer approval.
Enable a deliberate offline policy
Deferred authorization can accept locally when a standalone sale cannot go online, but the card issuer has not approved funding. Gate its use with your merchant policy, amount limits and operator controls. This physical-reader capability does not apply to Tap to Pay.
Handle the callback
Register deferredAuthorization and answer with continueDeferredAuthorization. Only confirmed deferred attempts enter the pending queue.
Reconcile both queues
Use RequestQueueStatus to track counts, values and failed references. The documented pending window is 24 hours; declined submissions are retried at eight-hour intervals during that window. Unresolved attempts move to the failed queue. Implement review and recovery using the same UserReference, not a new sale.
Account for reporting differences
Unsubmitted offline attempts are absent from gateway reports. Repeated submissions can produce multiple requests with one reference. Compare local queue records with gateway results and preserve uncertainty until resolved. Hardware execution of this workflow has not been tested here.