BlendFi

On-chain monitoring and risk

Every USDT deposit is evaluated in real time before it is accepted. How it works, what it protects, what your integration observes.

BlendFi runs real-time on-chain monitoring on every USDT deposit before accepting it into the operation. Each on-chain transaction receives a risk score; deposits whose origin signals material risk are refused before settlement. This is a central piece of what makes BlendFi a safe ramp to use.

Why it matters

A crypto-fiat ramp without origin monitoring is an open path for illicit funds: mixers, sanctioned addresses, exploit flows, escrows tied to fraud. Once converted into BRL via Pix, those funds become fungible and the ramp operator carries the responsibility.

BlendFi runs an on-chain risk analysis pipeline before a conversion settles. The pipeline evaluates the provenance of the received USDT and assigns a risk score. Deposits above the acceptable risk threshold are automatically refused, before any Pix is dispatched.

What is evaluated

The analysis runs over the on-chain deposit transaction and over the source address history. Signals cover:

  • Sanctioned addresses (national and international sanctions lists).
  • Direct or indirect exposure to mixers (Tornado Cash and equivalents).
  • Links to addresses associated with exploits, reported scams, ransomware, or darknet markets identified by chain analysis providers.
  • Anomalous transfer patterns suggestive of laundering (peeling chains, characteristic fan-in / fan-out).

The signals combine into an aggregate risk score. The acceptance policy is configured per organization during onboarding, within bands aligned to BlendFi's regulatory profile.

What your integration observes

For your organization, the effect is direct and localized:

  • Accepted deposit (happy path, the vast majority of cases): the conversion follows the normal cycle and ends in completed once the Pix settles.
  • Refused deposit (risk): the conversion ends in failed with a specific failure_reason indicating risk-driven refusal. The exact code lands in the API reference once the catalog is updated.

You do not need additional code to benefit. Monitoring runs independently of your integration; the result arrives like any other conversion outcome, via webhook.

UX for refused deposits

When a deposit is refused for risk reasons, the end customer needs clear guidance: BlendFi cannot release the BRL for that transaction. Recommend that the customer contact your organization's support. Returning the USDT, when applicable, is handled case by case by BlendFi's operations team, with criteria aligned to the identified origin.

The differentiator

Other ramps process deposits without inspection, transferring operational risk to the partner. At BlendFi, on-chain monitoring is native to the platform:

  • Real time: the risk score is computed before settlement, not after.
  • Before the Pix: suspicious deposits never become BRL on the recipient.
  • Audit trail: every accept-or-refuse decision is recorded in the audit log.
  • Inherited compliance: your organization integrates with BlendFi and automatically inherits the source-of-funds control required by Brazilian regulation.

Next steps

Audit events

Every state change on every BlendFi resource is recorded in an immutable audit log. Why it exists, what it covers, what it guarantees for your organization.

Glossary

Alphabetical reference for every domain term used across the BlendFi docs.

On this page

Why it mattersWhat is evaluatedWhat your integration observesThe differentiatorNext steps