Charge (Queue)

Queues a card-present sale on the terminal rather than waking it immediately. Useful when multiple transactions need to be staged (e.g., busy lanes) or when the device is currently in use. Response mirrors /terminal/charge but processing begins only when the terminal becomes available.

Workflow:

1. Create queued charge.
2. Terminal processes queued items FIFO.
3. Poll status endpoint for each queued transaction.

Differences vs /terminal/charge:

• Terminal may return terminalservice.waiting until it dequeues.
• If queue is full returns a 422 or device-specific error.
• Cancellation before processing removes from queue.

Recommended Use: High concurrency environments; fall back to direct charge for immediate processing.

Security: ApiKeyAuth or EphemeralAuth required.

Polling: Same recommendations as charge; consider exponential backoff if many queued items.