The stellar or muxed account ID of the user that wants to deposit.
This is where the asset token will be sent. Note that the account
specified in this request could differ from the account authenticated
via SEP-10.
(optional) The amount of the asset the user would like to deposit with
the anchor. This field may be necessary for the anchor to determine
what KYC information is necessary to collect.
The code of the on-chain asset the user wants to get from the Anchor
after doing an off-chain deposit. The value passed must match one of the
codes listed in the /info response's deposit object.
(optional) The ISO 3166-1 alpha-3 code of the user's current address.
This field may be necessary for the anchor to determine what KYC
information is necessary to collect.
(optional) id of an off-chain account (managed by the anchor) associated
with this user's Stellar account (identified by the JWT's sub field).
If the anchor supports SEP-12, the customerId field should match the
SEP-12 customer's id. customerId should be passed only when the off-chain
id is know to the client, but the relationship between this id and the
user's Stellar account is not known to the Anchor.
(optional) Value of memo to attach to transaction, for hash this should
be base64-encoded. Because a memo can be specified in the SEP-10 JWT for
Shared Accounts, this field as well as memoType can be different than the
values included in the SEP-10 JWT. For example, a client application
could use the value passed for this parameter as a reference number used
to match payments made to account.
(optional) A URL that the anchor should POST a JSON message to when the
status property of the transaction created as a result of this request
changes. The JSON message should be identical to the response format
for the /transaction endpoint.
(optional) Type of deposit. If the anchor supports multiple deposit
methods (e.g. SEPA or SWIFT), the wallet should specify type. This field
may be necessary for the anchor to determine which KYC fields to collect.
(deprecated, optional) In communications / pages about the deposit,
anchor should display the wallet name to the user to explain where funds
are going. However, anchors should use client_domain (for non-custodial)
and sub value of JWT (for custodial) to determine wallet information.
(deprecated,optional) Anchor should link to this when notifying the user
that the transaction has completed. However, anchors should use
client_domain (for non-custodial) and sub value of JWT (for custodial)
to determine wallet information.