Wakes terminal with request for user to insert card.
Wake the terminal with a request for the user to insert the card. This call is SYNCHRONOUS, meaning the network call will stay open until the transaction is finished. The call will time out after only 60 seconds if the transaction is not completed, and you will not receive the response, unless you poll the GET transactions resource.
For this reason, we recommend using the charge/queue resource.
Timeouts
When a timeout occurs during a transaction because it is not completed on time, Stax creates a scheduled task to begin querying the terminal for the status of the transaction. The schedule waits 3 minutes after the timeout and queries the terminal for the transaction status every minute for the next hour. Once Stax receives a response from the terminal, the transaction will display in Stax. Until a response from the terminal is received or the schedule finishes.
Note: THE TRANSACTION WILL NOT DISPLAY IN Stax.
Synchronous vs Asynchronous
Both /terminal/charge and /terminal/charge/queue are valid solutions depending on your use case. If you want the transaction data immediately and are ok with a slower HTTP response, /charge is the method to use. If the transaction data is not immediately needed, you can get a quick HTTP response with /charge/queue.
For most use cases, we recommend charge/queue.