Proposal: Deposit Gateway, receiver-side attribution and settlement for pooled deposits
SubmittedPR- SIG
- financial-workflows-composability
- Champion
- —
- Author org
- Ask
- source pending
Abstract
Exchanges, custodians and payment processors on Canton receive customer deposits into shared parties and rely on a memo to know which customer to credit, and across seven exchanges on MainNet about one deposit in 79 arrives with a missing or malformed memo that staff must resolve by hand. Deposit Gateway is an Apache-2.0 Rust service that a receiver runs beside its own validator. Deposit Gateway checks each incoming deposit against the receiver's rules and optional decision endpoint, then accepts or rejects two-step transfers, returns deposits that already settled through a preapproval less a configurable fee, holds the rest in a review queue, and reports every outcome through signed webhooks. It is built on the token standard, needs no changes to sender wallets, Canton or Splice.
Milestones
No milestones recorded.
- % of approved-to-date
- —
- % if all RFV pass
- —
RFV scenario unavailable — using approved-to-date as denominator (degraded mode).
- Ask (CC)
- amount pending
Comments by org
No public reasons documented.
View discussion on GitHub