Payment processing

Detect user deposits, process transfers, and handle stablecoin payments with compliance.

Payment processing involves detecting incoming deposits, executing outbound transfers, and meeting compliance requirements. This topic explains deposit detection, stablecoin transfers, and compliance integration.

What you need

Wallets for receiving deposits
A webhook endpoint for receiving deposit notifications

Components to configure

Deposit deduction

Detect incoming transactions to your wallets by using /guides/developers/webhooks for notifications in real time or by querying wallet history using /guides/developers/displaying-balances. Key considerations:

Confirmed events: The wallet.blockchainevent.detected webhook fires only after IBM Digital Asset Haven processes the network-specific confirmation delay. See /networks/index.
Duplicate handling: Webhook events may be delivered more than once. Use idempotency keys to avoid processing the same event twice.
Reconciliation: Run periodic jobs to identify any missed events or delayed confirmations.

Compliance integration

AML and KYT screening: Screen outbound transactions for sanctions and risk by using the Chainalysis integration.
Travel rule: For transfers above regulatory thresholds, exchange originator and beneficiary information through travel rule integration.

Example: Deposit flow

A typical deposit processing flow is shown below.

Because IBM Digital Asset Haven waits for the confirmation delay before sending the webhook, you can credit users as soon as you receive the event.