{
  "id": "evt_dep000",
  "type": "deposit.pending",
  "data": {
    "depositId": "dep_xyz789",
    "sideshiftAccountId": "acct_a1b2c3d4e5f6",
    "amountCents": 10000,
    "feeCents": 320,
    "netAmountCents": 9680,
    "currency": "usd",
    "paymentId": "pay_abc123",
    "status": "pending"
  },
  "timestamp": "2026-03-13T12:28:00.000Z"
}

Depositpending

Sent the moment a deposit is initiated — before the underlying payment has settled.

Fires on two funding paths:

Escrow-mode checkout — when one of your users funds your wallet via the embedded checkout. data.sideshiftAccountId is the depositing user.
Self top-up — when you (the integrator) fund your own wallet through SideShift wallet top-up. data.sideshiftAccountId equals your own integrator companyId; data.metadata.source = "wallet_topup".

Use this to mark the deposit as in-flight in your internal ledger so subsequent reconciliation has a head start before the final deposit.confirmed event arrives. The deposit is not yet credited to the wallet at this point.

WEBHOOK

deposit.pending

{
  "id": "evt_dep000",
  "type": "deposit.pending",
  "data": {
    "depositId": "dep_xyz789",
    "sideshiftAccountId": "acct_a1b2c3d4e5f6",
    "amountCents": 10000,
    "feeCents": 320,
    "netAmountCents": 9680,
    "currency": "usd",
    "paymentId": "pay_abc123",
    "status": "pending"
  },
  "timestamp": "2026-03-13T12:28:00.000Z"
}

Authorizations

x-api-key

string

header

required

Your SideShift Connect API key (sk_live_* or sk_test_*). Generate from Settings → Connect.

Body

application/json

string

Unique event ID

type

string

Example:

"deposit.pending"

data

object

Show child attributes

timestamp

string<date-time>

Response

200

Webhook acknowledged

⌘I