Skip to main content
Complete these checks before production traffic reaches your integration. Most teams review them with their Rhino.fi account manager in a launch call. Items marked Required are needed for the integration to work correctly; items marked Recommended are best practice.
Trial accounts should not be used for production. To go live, contact our sales team at partnerships@rhino.fi to set up a production account.

​
Account

  • (Recommended) Your project is on a production account, set up with our sales team. Trial accounts should not be used for production traffic. A subscription gives you production-level limits and enterprise pricing, instead of the trial’s test limits and per-transaction fees.

​
Security

  • (Required) Secret keys are used only server-side and stored in a secrets manager. See Authentication.
  • (Recommended) Production secret keys have an IP allowlist.
  • (Required from 9 November 2026) SDA search and webhook event history are called from your backend with a secret key. Public keys are rejected from 9 November 2026.
  • (Recommended) Your webhook endpoint verifies every signature and rejects unsigned requests.
  • (Recommended) You have a process to rotate API keys in the Rhino.fi Console, with an owner assigned.

​
Reliability

  • (Required) JWTs are refreshed before they expire. Requests that return 401 are retried once with a fresh token.
  • (Recommended) Every 4xx and 5xx response is logged with its error code. See Errors.
  • (Recommended) 503 responses and network failures are retried with exponential backoff.
  • (Recommended) Your system recovers missed webhook events after an outage.
  • (Recommended) Customer balances are credited on EXECUTED. Crediting earlier is a risk decision for your team.

​
Smart Deposit Addresses

  • (Recommended) Your project is on a subscription, which sets production SDA limits to cover your expected volume. See Limits.
  • (Recommended) Each SDA lists every EVM chain that supports SDAs, so deposits on the wrong network are still settled.
  • (Recommended) Your customer UI shows the supported tokens and the minimum and maximum deposit amounts.
  • (Recommended) You have agreed a refund process with your account manager, or have decided to use refundAddress.
  • (Recommended) DEPOSIT_ADDRESS_BRIDGE_REJECTED and DEPOSIT_ADDRESS_BRIDGE_DELAYED events alert your support team.

​
Bridge transfers

  • (Required) Same-chain swaps follow the calldata flow, not the bridge deposit. See Same-chain swaps.
  • (Required) Token amounts are converted with parseUnits, or your language’s equivalent, never with floating-point math.
  • (Required) Quotes are committed before expiresAt, and before the deposit is sent.

​
Operations

  • (Recommended) Your team has subscribed to the Rhino.fi status page.
  • (Recommended) You have run at least one small transaction end to end on mainnet for every chain and token pair you will offer.
  • (Recommended) Your support team knows how to find a transaction by quote ID (quoteId), deposit hash or withdrawal hash.
  • (Recommended) Support contacts are agreed with your Rhino.fi account manager.

​
Need help?

Contact your Rhino.fi account manager, or email partnerships@rhino.fi for commercial questions.