...
An Input Queue
Add new Input Queue
...
is used when an Operator wants more control over outgoing fiat. For example: to manually approve all SELL transactions that are above some arbitrary limit, or where a SELL might be legally required to have a holding period of some sort.
Dashboard
| Create a new Input Queue. |
...
Name | Description |
|---|---|
Crypto Currency | The coin involved in the SELL being queued. |
Crypto Settings | The Crypto Setting using the Queue. |
Organization | The Organization that owns the Queue. |
Transactions Waiting for Approval | The number of transactions queued - but waiting for approval.
|
Number of Transactions Currently Queued | The total number of transactions queued.
|
Total Amount | The total amount of fiat queued. |
View the specified Output Queue. | |
Submit all unlocked queued transactions immediately. | |
Delete the specified Output Queue. |
...
Transactions pending
RID | The transaction Remote ID (RiD). Click to see the related transaction. |
Terminal | The BATM at which the transaction was created. Click to see the Terminal details. |
Crypto Settings | The related Crypto Setting. Click to see the setting. |
Added | The date+time the transaction was added to the queue. |
Delayed Until | The date+time the transaction will be automatically submitted. |
Locked Until | The date+time the transaction will be unlocked for queue processing. Transactions may be locked to comply with government mandated refund periods. A transaction cannot be submitted until the lock has expired. |
Fiat Amount | The fiat amount of the transaction. |
Crypto Amount | The crypto amount of the transaction. |
Crypto Address | The target wallet used in the transaction. |
State | The state of this transaction in the queue. |
Actions |
|
Last sent: | The last date+time a transaction was sent from this queue. |
Approve and submit all unlocked & pending transactions in this queue. |
...
Settings/Details/Rules
Input Queue Settings
...
Name* (required) | Describe the Queue in the Name. |
Organization* (required) | Assign an Organization to “own” the queue. |
Crypto Currency* (required) | Select the Crypto Currency that applies. |
Configuration Cash Currency | Optional fiat assignment for evaluation in Rules (below). |
Rule 1: Manual Approval?
...
Require manual approval | Batches must be manually approved when the transaction amount exceeds the amount specified. Transactions below this amount will be sent immediately (not queued).
|
Minimum Cash Amount
| The minimum transaction amount that demands manual approval (e.g. large transactions that might exceed your fiat capacity). |
For all transactions identified as Suspicious by a Scoring Provider | When using a Scoring Provider, check this box to hold all suspicious transactions. |
Rule 2: Delayed Transactions?
...
Delay transactions | Send qualifying transactions after a set delay. |
Delay By (seconds)
| The amount of delay before submitting the transaction to the network. |
Minimum Cash Amount
| The transaction amount to qualify for the delay. |
Rule 3: Delayed Batches (by Timer)?
...
Automatically send transactions from this queue in one batch every: | Submit the pending batch automatically on a time schedule. |
Seconds
| Can be zero or higher. |
Rule 4: Delayed Batches (by Quantity)?
...
Automatically send transactions from this queue in one batch when number of transactions is higher than: | Post the batch immediately when X transactions have accumulated (ignores time delays). |
Number of transactions
| Must be greater than zero. |
...
Related Crypto Settings
Crypto Settings (SELL) displays these 3 related settings:
“Input Queue” and
“Secondary Input Queue”, and
Transaction unlock delay (normally hidden).
...
Select the new “Input Queue” as desired. The Transaction unlock delay setting will appear.
The “Secondary Input Queue” - only works with custom server extensions,
implementing the method: overrideInputQueueInsertConfig
Transaction unlock delay: defines the length of time (in minutes) that a transaction stays in the locked state (🔒 lock icon). Locked transactions in the queue cannot be submitted.
Default: 0 (no delay).