Finrax API
HomeChangelogIntegration GuideResources
HomeChangelogIntegration GuideResources
  1. Callbacks
  • Getting Started
    • Introduction
    • Environments
    • Errors
    • Authorization
      • API Key Management
      • Signature
      • Code Snippets
  • Payments and Withdrawals
    • Crypto Payments
      • Fetch payment by ID
      • 🔒Fetch payments
      • Submit crypto payment
      • Request crypto payment
    • Fetch withdrawals
      GET
    • Fetch withdrawal metadata
      GET
    • Request crypto withdrawal
      POST
    • Fetch whitelisted addresses
      GET
    • Whitelist an address
      POST
    • Fetch crypto withdrawal approval by ID
      GET
    • Fetch business by ID
      GET
    • Fetch business balance
      GET
    • Unwhitelist an address
      DELETE
  • Callbacks
    • Deposit received notification
    • Withdrawal broadcast notification
    • Withdrawal approved/rejected notification
  • Address validation
    • Validate address
      GET
    • Validate address and destination tag
      GET
  • Rates and metadata
    • Fetch market rates
      GET
    • Fetch fiat rates
      GET
    • Fetch deposit rates
      GET
    • Fetch all currencies
      GET
  1. Callbacks

Deposit received notification

Once the end-user sends funds from their wallet, transaction-specific events will be broadcasted on the blockchain. We listen for such blockchain events and will send them to you via an endpoint provided by you when creating your business through the dashboard.
Based on our instant deposit feature an event will be sent to you as soon as we see a new deposit transfer broadcasted on the designated wallet address. At this stage, the status of the transaction is still UNCONFIRMED We run an internal probabilistic algorithm to help us identify double spent attempts or illicit transactions. If we detect such a case we won't propagate this event to you systemically and will instead contact you about it. Note that only UTXO-based coins (BTC, LTC, BCH etc.) have such an event, whereas account-based coins (ETH, ERC20, XLM, XRP) don't.
If the deposit doesn't meet our instant deposit conditions a notification will be sent once the transaction is added in a block and there is 1 blockchain confirmation.
This callback notification is sent on your depositReceivedCallbackUrl endpoint.
The networks of some coins like XRP and XLM are extremely fast. It takes literally ~1 second to verify and confirm a transaction once it is broadcast on the network.
On average a Bitcoin transaction to be included in a block requires ~15 minutes. By using Finrax you'll be able to credit Bitcoin deposits in less than 10 seconds.

Schema#

ParameterTypeDescription
actualDepositAmountnumberActual amount deposited in cryptocurrency (depositCurrency) by the end-user. Can be different than the expectedDepositAmount
actualDisplayAmountnumberActual amount deposited in displayCurrency currency (e.g.EUR, USD, GBP, TRY etc..)Can be different than expectedDisplayAmount
clientPaymentIdstringUnique payment identifier provided by the merchant in the request body of POST /payments
depositCurrencystringCryptocurrency that has been deposited
settlementAmountnumberAmount deposited in settlementCurrency
settlementCurrencystringThe currency in which the merchant's account was credited because of the deposit (can be either fiat or cryptocurrency)
depositIdstringUnique Finrax deposit identifier UUID
onChainFeenumberBlockchain cost for this deposit paid by the end-user
depositAddressstringYour unique blockchain address supplied by Finrax where the deposit was received.
fromAddressstringThe blockchain address from which the payment originated.
transactionIdstringUnique blockchain transaction ID of the deposit
displayCurrencystringThe fiat currency chosen for display (denomination) purposes
expectedDepositAmountstringAmount in cryptocurrency to be deposited to fulfil the required amount in displayCurrency
displayServiceFeenumberFinrax commission in displayCurrencyfor the concrete deposit
settlementServiceFeenumberFinrax commission in settlementCurrencyfor the concrete deposit
expectedDisplayAmountnumberAmount in displayCurrency requested for this payment
networkstringThe network on which this deposit occurred
expirationTimenumberTimeframe at which the payment link against which this deposit was received expires
paymentIdstringUnique Finrax payment identifier UUID
paymentReceivedAtnumberTimestamp when the payment was received UNIX
paymentRequestedAtnumberTimestamp when the payment was requested UNIX
statusstringCan be only CONFIRMED.
rateTypestringRate type of the deposit (FIXED or FLOATING). Depends on the payment rate type and the time frame within which the deposit was created by the end-user. Fixed vs Floating rates.
Modified at 2024-07-04 10:42:04
Previous
Unwhitelist an address
Next
Withdrawal broadcast notification
Built with