Skip to main content
Every scenario resolves on its own. You force a scenario on the deposit that creates the onramp, the onramp reaches the status you asked for, and 3 minutes later it moves to its true terminal status, FIAT_RETURNED. No follow-up API call is needed.
Magic values are sandbox only. In production, sandboxScenario is rejected with a 400.

Magic values

Onramps funded by a USD virtual account are created by the deposit itself, so onramp magic values are passed on the sandboxScenario field of the simulate a deposit to a virtual account endpoint rather than on an onramp create request. The following table outlines the magic values and their effects on the onramp the deposit creates: Both resolve to FIAT_RETURNED 3 minutes after reaching the status they force, with a webhook for the change. The onramp moves straight there, and FIAT_RETURNED is terminal. The fiat is returned to the sender’s bank account as part of the return.

Example request

Coverage

Onramp magic values are wired into USD onramps, triggered from the virtual account deposit that creates them, and both resolve to FIAT_RETURNED. This is available regardless of which rail funded the deposit. Values that are not listed above either fall through to the standard sandbox behavior or return an error.

Getting help

  • 📧 Email: support@hifi.com
  • 💬 Slack: Message us in our shared Slack channel