An 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 in the queue. |
Crypto Settings | The Crypto Setting that triggered the queue. |
Organization | The Organization that owns the Queue. |
Transactions Waiting for Approval | The number of transaction 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. |
Details
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). |
Sending Rules
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
| Must 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. |
CAS - Crypto setting:
In crypto setting - SELL - there are two new dropdowns “Input Queue” and “Secondary Input Queue”
“Input Queue” - no need for extra server extensions
“Secondary Input Queue” - works only with custom server extensions - extension method overrideInputQueueInsertConfig.
When some “Input Queue” is set in crypto setting - new row “Transaction unlock delay” will appear. This works same as for BUY “Output Queue”. This defines number of minutes for how long transaction stays in locked state (lock icon) in the queue before it is possible to send it. Default value is 0 (no delay).