Sep06Deposit Request
Request to initiate a programmatic deposit with a Stellar anchor.
A deposit occurs when a user sends an external asset (fiat via bank transfer, crypto from another blockchain, etc.) to an anchor, and the anchor sends an equivalent amount of the corresponding Stellar asset to the user's account.
Unlike SEP-24's interactive flow, SEP-6 deposits are fully programmatic - all required information must be provided in the API request.
Constructors
Properties
Issuer of the asset. Required when multiple assets share the same code.
Set to true if the client supports receiving funds via claimable balances. Allows deposits to accounts without a trustline.
ISO 3166-1 alpha-3 code of the user's current address. May be necessary for the anchor to determine KYC requirements.
SEP-12 customer ID if the off-chain account is already known to the anchor but not linked to this Stellar account.
Email address of the depositor. The anchor may use this to send status updates about the deposit.
Additional fields required by the anchor beyond the standard parameters. Keys should match field names from the /info response.
Method of funding the deposit (replaces deprecated type field). Values come from the /info endpoint's funding_methods for the asset.
ID of the chosen location for cash drop-off, if applicable.
URL where the anchor should POST transaction status updates. The callback message format matches the /transaction endpoint response.
Deprecated: Use client_domain in SEP-10 JWT instead. Name of the wallet application for display purposes.