Held until reviewed
An outgoing transfer isn’t forwarded to the provider until the review result is back. An incoming deposit shows as pending until it clears.
AML & Transaction Monitoring
AML & Transaction Monitoring (KYT)
FinHost screens every crypto deposit and withdrawal against SumSub’s Know-Your-Transaction checks before it reaches the provider or settles. Held transactions land on a dedicated queue, and manual returns are tracked with an on-chain hash.
- Webhook-driven decisions
- Pending & Failed AML queues
- Manual returns with on-chain proof
←Transaction
◎ Crypto withdrawal1,000.00 USDT
Payment methodCrypto withdrawal
SumSub reviewGREEN
- AML status
- aml_confirmed
- Transaction status
- Pending_provider
- Webhook
- applicantKytTxnApproved
Built for compliance teams
Every crypto transfer, screened before it moves
Screening runs on both directions, independent of manual review, and every decision is traceable back to the webhook that made it.
One webhook, one decision
The first review result that arrives is the one that counts, so a transaction is never re-decided out from under itself.
Traceable after the fact
Every screened transaction carries its AML status, risk score, and a direct link to the SumSub record behind it.
Turning it on
Four steps to a working KYT setup
The same sequence works for sandbox testing and for production, with rules tuned differently for each.
- 01
Add the KYT webhook
Every relevant webhook type, no source keys specified, with automatic resend for failed deliveries.
- 02
Create a monitoring token
Scoped to transaction-monitoring permissions only, also without a source key attached.
- 03
Configure the rules
Start by holding everything in sandbox, then test automatic approval and automatic rejection as separate cases.
- 04
Add Slack notifications
Optional. A dedicated webhook for on-hold transactions, routed straight to a compliance channel.
Pending in AML
Every stuck transaction, in one table
A dedicated tab lists every transaction currently on hold, across individuals and corporates, incoming and outgoing, fiat and crypto alike.
- Remitter and recipient shown by name, company, or wallet address
- Risk score pulled directly from the screening provider
- A one-click link to the matching record in SumSub
- A View button opens full transaction details from the same row
Pending in AMLFailed AML
↑ TXN-8825 · OutgoingAML pending
Oliver Smith → BTC Account
1,000.0090 USDTRisk: Medium
View in SumSub
If a transfer fails
Reversed deliberately, never assumed
A failed transaction doesn’t just disappear from view. It’s either cleared automatically or held until someone confirms the funds actually went back.
Transaction details · Crypto withdrawalConfirmed
- AML status
- aml_confirmed
- Transaction status
- Pending_provider
- Risk score
- Low
- Reviewed via
- applicantKytTxnApproved
Cleared automatically
A clean review result lets the transfer proceed without anyone touching it by hand.
Manual return required
A failed deposit that already settled needs a team member to send the funds back and record the on-chain hash before it’s marked returned.
PendingConfirmedFailedReturned
Two back office tabs
Pending and failed transactions live in different places
Each tab exists for a different decision a compliance team needs to make.
Pending in AMLFailed AML
ShowsTransactions currently on holdRejected transactions not yet returned
Typical actionApprove or reject in SumSubMark as returned with a transaction hash
Auto-resolved casesNone. Every row needs a decisionProvider-side auto-returns are excluded already
Risk data shownRisk score from SumSub, with a direct linkFailure reason saved with the transaction
FAQ
AML and transaction monitoring, explained
What shows up in the Pending in AML queue?
Every transaction currently on hold, with its payment method, direction, remitter and recipient, total amount, AML status, risk score, and a direct link to the matching SumSub record.
What happens to a transaction already rejected on the provider’s own side?
It’s excluded from the Failed AML tab entirely. The system records it as automatically returned, with a note explaining why, rather than asking an admin to confirm something that already happened.
How does an admin mark a transaction as returned?
By entering the on-chain transaction hash of the return. The hash is required, so a return can’t be recorded without proof it actually took place.
Is manual review the same setting as AML screening?
No. They’re controlled separately. Enabling or disabling manual review doesn’t turn AML checks on or off.