Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

image-20241202-202631.png

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

image-20241202-205424.png

Create a new Input Queue.

image-20241203-214444.png

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.

  • (blue star) indicates the transactions require manual approval.

Number of Transactions Currently Queued

The total number of transactions queued.

  • (blue star) indicates that automatic submission is not possible for X transactions in this queue.

Total Amount

The total amount of fiat queued.

image-20231229-164219.png

View the specified Output Queue.

image-20231229-164247.png

Submit all unlocked queued transactions immediately.

image-20231229-164330.png

Delete the specified Output Queue.

Details

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 unlock has

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

  • Approve: allow this queued transaction to be submitted during the next regular cycle of automatic queue handling.

  • Send Now: ignore the queue and any locks; approve and submit the transaction now.

  • Remove From Queue: do not submit the transaction now or ever.

  • View in Transactions: navigate to the transaction in the Transaction Log.

Last sent:

The last date+time a transaction was sent from this queue.

image-20231229-160038.png

Approve and submit all unlocked & pending transactions in this queue.

image-20241202-134936.png

Input Queue Settings

image-20241202-210604.png

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

image-20241202-211122.png

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

  • required when manual approval is enabled.

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.

See: https://generalbytes.atlassian.net/l/cp/Tkq1mFHy

Rule 2: Delayed Transactions

image-20241202-211400.png

Delay transactions

Send qualifying transactions after a set delay.

Delay By (seconds)

  • required when Delay is enabled.

The amount of delay before submitting the transaction to the network.

Minimum Cash Amount

  • required when Delay is enabled.

The transaction amount to qualify for the delay.

Rule 3: Delayed Batches by Timer

image-20241202-211620.png

Automatically send transactions from this queue in one batch every:

Submit the pending batch automatically on a time schedule.

Seconds

  • required when this rule is enabled.

Must be zero or higher.

Rule 4: Delayed Batches by Quantity

image-20241202-212049.png

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

  • required when this rule is enabled.

Must be greater than zero.


CAS - Crypto setting:
In crypto setting - SELL - there are two new dropdowns “Input Queue” and “Secondary Input Queue”

image-20241202-142704.png

“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).

  • No labels