Table of Contents

Pricing

Internal pricing

The internal price in Nexus can be defined by selecting a primary and secondary crypto exchange and calculation settings like an artificial bid/ask spread and delay period. Nexus is always connected with a set of reference exchanges to read and validate actual exchange prices in real-time. If exchanges are not accessible or if market prices do not converge (like in times of very high market volatility or during incidents on individual exchanges), the system can automatically ban specific exchanges. As a result the internal pricing function can switch from the primary to the secondary exchange or even (temporary) halt all trading in the specific crypto.

Depending on the setting of the delay period and the artificial bid/ask spread, you can mitigate for short term price fluctuations and exchange fee costs. When using internal pricing the customers can be allowed to fix a price before actual transaction execution.

External pricing

When using external pricing all transactions are back-to-back executed on a specific exchange and the crypto transaction price is defined as the weighted average price of the realized trade. All customer transactions can be linked with an order Id to a specific trade on an exchange. With external pricing the customer can be provided with an estimate of the expected trade price, but the actual external price is set only after the trade has been executed on the crypto exchange.

Available Crypto Prices

Exchange Currency Cryptos
BitFinex EUR BTC, ETH, XLM, EOS
USD BTC, ETH, BCH, LTC, XLM, XRP, EOS, ALGO, USDT, ADA, DOT, LINK
Bitstamp EUR BTC, ETH, BCH, LTC, XRP, XLM, LINK, USDT
USD BTC, ETH, BCH, LTC, XRP, XLM, LINK, USDT
CEXio EUR BTC, ETH, BCH, LTC, XRP, XLM, ADA, LINK, USDT
USD BTC, ETH, BCH, LTC, XRP, XLM, ADA, LINK, USDT
CoinbasePro EUR BTC, ETH, BCH, LTC, XLM, XRP, EOS, DOT, ADA, LINK, USDT
USD BTC, ETH, BCH, LTC, XLM, XRP, EOS, DOT, ADA, LINK, USDT
Kraken EUR BTC, ETH, BCH, XLM, LTC, XRP, EOS, DOT, ADA, LINK, USDT
USD BTC, ETH, BCH, XLM, LTC, XRP, EOS, DOT, ADA, LINK, USDT

Payment methods

Several payment methods are supported within Nexus, in order to offer you a comprehensive range of options that you can offer also to your customers. The payment method called Generic is the one that allows the most flexibility, since it allows you to use your own process to manage these payments and then return the status of the operation, so that it can be recorded in Nexus. However, other payment methods are available:

  • Bank transfer
  • iDEAL
  • Sofort
  • Crypto
  • Giropay
  • Instant
  • Mybank
  • MisterPay

Send delay

Send delay functionality is only available in the Broker Model and can be configured per payment method to affect the crypto sent delay period of a buy transaction. As soon as the buy transaction is created with a status "Initiated", and there was a successful payment linked to it, we check whether it meets the necessary conditions to be delayed. If it should, we update its status to "SendDelay". Only after the configured delayed period has passed we continue with sending the crypto-currency amount of the transaction, by changing the status of the transaction to "sending". During this delayed period the transaction's crypto-currency amount is locked in the Nexus hot wallet, in order to guarantee the delivery to the customer.

Send delay functionality can be configured to apply to all transactions that are linked to that payment method, in two different ways:

  • Transactions which's customer's bank's country matches a specific country.
  • Transactions which's customer's bank account or bank filter (for example "NL??SNSB*") matches a specific bank account.

Multiple rules can be configured per payment method, for different countries and bank accounts, each with their own set of properties. For each rule, you can set the delay in hours or whether the transaction should be delayed until it is settled or not, and if so, the maximum allowed unsettled amount. Send delay functionality can be created, edited and deleted, but note that existing configuration's bank filter and country fields cannot be edited and if changes are needed in these fields, you have to delete and recreate the configuration.

Note that country specific send delay configuration is trumped by bank account specific send delay configuration.