FinRev Troubleshooting

When customers are connecting their exchange accounts to FinRev, or have previously completed the connection, there are a number of 'Authentication Errors' that can be produced.


There errors can be found under the 'Authentication Errors' tab under 'User management' when logged into your Admin account at https://finrev.trade

Below is an explanation of each of the errors that can be produced, and the action steps that need to be taken in order to solve the error.


Common FinRev Authentication Errors

Type2_Strike:

Cause: 

Random compliance audit from dYdX


Solution: 

Complete compliance check steps from dYdX


Guide:

https://help.finrev.trade/article/110-dydx-troubleshooting-guide


Unable to extract capital:


Cause: 

Upgraded to Unified account, V5 API on Bybit, or incorrect API permissions.


Solution: 

Create a new subaccount & resubmit API keys


Guide:

Create subaccount specific to exchange, then: https://help.finrev.trade/article/43-how-do-i-reconnect-my-api-with-finrev


STARK public/private mismatch:


Cause: 

Unknown error on the customer’s system or dYdX account


Solution: 

Follow troubleshooting steps on new browser to reconnect API


Guide:

https://help.finrev.trade/article/118-dydx-api-key-error-troubleshooting


API key is invalid:


Cause: 

Incorrect permissions or code copied into FinRev, upgraded to V5 API on Bybit.


Solution: 

Create a new subaccount & resubmit API keys


Guide:

Create subaccount specific to exchange, then: https://help.finrev.trade/article/43-how-do-i-reconnect-my-api-with-finrev


Unable to place order:


Cause: 

Ineligible to trade futures. Incorrect API permissions, or KYC not completed/rejected.


Solution: 

Complete KYC or move exchanges


Guide:

https://help.finrev.trade/article/94-how-to-connect-reconnect-bybit-api-with-finrev


FinRev Troubleshooting Session With Coaches

Below is a video of a FinRev troubleshooting sessions, where we discuss, in depth, the various common FinRev account errors & how to best troubleshoot them.


Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.