Scoutinternal

Ledn Custodial Withdrawal Requests

Ledn Custodial Withdrawal Requests

Problem

Ledn, a BitGo custody client, submits withdrawal requests on behalf of its end users. These requests arrive as individual support tickets (often in high volume) and require processing by the BitGo custody/operations team. The tickets follow a uniform pattern — titled "Ledn - Withdrawal Request" or "Ledn- Withdrawal request" — and are created in bulk, indicating a batch-processing workflow for custodial withdrawals. Based on the available ticket data, the problem descriptions and resolution details are largely absent, leaving resolution confidence at medium across all samples.

Diagnostics

  • Identify the client: Confirm the ticket subject references "Ledn" (sometimes misspelled as "Lednn") and contains "Withdrawal Request" or "Custodial Withdrawal Request."
  • Check Salesforce case reference: Each ticket maps to a Salesforce case (e.g., SF#00042166, SF#00082311). Verify the SF case number is present and valid.
  • Confirm ticket creator: All sampled tickets were created by the same agent ID (158009540847). Confirm the ticket originated from an authorized Ledn operations contact or internal BitGo agent handling the Ledn queue.
  • Batch context: These tickets arrive in large batches (429 total in this cluster). Check whether the request is part of a known bulk withdrawal processing cycle for Ledn.
  • Ticket content: Note that the 50 sampled tickets contain no problem description, no diagnostic notes, and no substantive resolution text. If the ticket body is empty or minimal, this is consistent with the pattern observed — the withdrawal details may reside in the linked Salesforce case or in an attached document rather than in the Freshdesk ticket itself.
  • Variant subjects to watch for: "Ledn - Withdrawal Request," "Ledn- Withdrawal request," "Ledn - Custodial Withdrawal Request," "Ledn- Withdrawal Requests" (plural), and occasional misspellings like "Lednn."

Resolution

Scenario: ledn-withdrawal-request-q4#standard-custodial-withdrawal

Trigger: A ticket arrives with subject matching "Ledn - Withdrawal Request" (or close variant), created by the known Ledn-queue agent, with withdrawal details in the linked Salesforce case.

Signals: Ledn, withdrawal request, custodial withdrawal, SF case, batch processing, Q4

Steps:

  1. Open the linked Salesforce case (the SF# in the ticket subject) to retrieve the full withdrawal details (asset, amount, destination address, any authorization documentation).
  2. Verify that the withdrawal request has been authorized per the standing Ledn custodial withdrawal procedures.
  3. Process the withdrawal through the BitGo custody operations workflow as defined for the Ledn account.
  4. Once the withdrawal transaction is submitted and confirmed, update both the Freshdesk ticket and the Salesforce case with the transaction status.
  5. Close the Freshdesk ticket.

Notes: - The source tickets contain no problem descriptions, diagnostic threads, or resolution details beyond a creation timestamp. All 50 samples show identical structure: same creator, same date (2026-02-09), medium resolution confidence, and empty content fields. The actual withdrawal parameters are presumed to reside in the linked Salesforce cases or attached files.

  • One ticket (SF#00045177) references a "New Ledn member" rather than a withdrawal; confirm whether such tickets require a different onboarding workflow before processing.
  • One ticket (SF#00163640) references a transfer from Binance to ledn.io and may be an inbound deposit inquiry rather than an outbound custodial withdrawal — route accordingly.
  • Due to the volume (429 tickets in this cluster), coordinate with the custody operations team if a bulk batch run is underway to avoid duplicate processing.

Related

  • policy-structure — Custodial wallet withdrawal policies and approval requirements may apply to Ledn withdrawal processing.
  • bitgo-global-regulated-entities-faqs — Travel Rule and compliance screening may be triggered for Ledn custodial withdrawals depending on jurisdiction and destination.
  • none identified for a direct Ledn-specific onboarding or operational runbook in the existing KB.