Skip to main content
POST
transfer.crypto_deposit.completed
Triggered when a crypto deposit is COMPLETED and funds are available on platform.
Webhook payloads contain only event metadata. Use the Get Event API with the event ID to retrieve full details.

​
Event Object Structure

The Get Event API returns a transfer_status_change object with transfer status details.

Body

application/json

Webhook payload containing event metadata. Use the event ID with the Get Event API to retrieve full details.

The webhook payload structure sent to your endpoint

​
id
string<uuid>
required

The event identifier used to query the Events API for full details

​
type
enum<string>
required

The type of event that occurred

Available options:
identity.documents_required,
identity.approved,
identity.denied,
identity.disabled,
identity.kyc_refresh.started,
identity.kyc_refresh.completed,
identity.kyc_refresh.expired,
orchestration.processing,
orchestration.completed,
orchestration.failed,
transfer.crypto_deposit.pending,
transfer.crypto_deposit.completed,
transfer.crypto_deposit.failed,
transfer.crypto_withdrawal.pending,
transfer.crypto_withdrawal.completed,
transfer.crypto_withdrawal.failed,
transfer.act_deposit.pending,
transfer.act_deposit.completed,
transfer.act_deposit.failed,
transfer.act_withdrawal.pending,
transfer.act_withdrawal.completed,
transfer.act_withdrawal.failed
​
source
enum<string>
required

Always 'com.paxos'

Available options:
com.paxos
​
time
string<date-time>
required

When the event occurred, RFC3339 format

​
object
enum<string>
required

Always 'event'

Available options:
event

Response

200

Webhook successfully received