SEP-6 SEP-24 SEP-31
Retrieve a transaction by its ID.
Params (1)
string
required
The unique identifier of this transaction.A unique transaction identifier.
Result
(get_transactionResponse)string
A unique transaction identifier.
integer
Protocol of the transaction.Available options:
6, 24, 31string
The kind of transaction that is desired.Available options:
undefined, receive, deposit, deposit-exchange, withdrawal, withdrawal-exchangestring
Processing status of the transaction.Available options:
pending_anchor, pending_trust, pending_user, pending_user_transfer_start, pending_user_transfer_complete, incomplete, no_market, too_small, too_large, pending_sender, pending_receiver, pending_transaction_info_update, pending_customer_info_update, completed, refunded, expired, error, pending_external, pending_stellarstring
Funding method used for transferring or settling assets.
string
DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.
object
The amount expected in the payment.
object
Amount expected/received by anchor.
object
The amount expected to be sent by anchor to user at end of transaction.
object
Description of fee charged by the anchor.
string
The id returned from a SEP-38 POST /quote response
string
Start date and time of transaction.
string
The date and time of transaction reaching the current status.
string
The date and time of transaction reaching completed or refunded status.
string
The date and time of receiving transfer.
string
Time and date by which user action is required.
string
Human readable explanation of transaction status
object
An object describing any on or offchain refund associated with this transaction.
object[]
string
The account being debited in the Stellar Network.
string
The account being credited in the Stellar Network.
string
A unique transaction identifier.
string
string
The memo type of the transaction in the Stellar network. Should be present if memo is not null.Available options:
id, hash, textstring
string
The memo type of the transaction in the Stellar network. Should be present if memo is not null.Available options:
id, hash, textstring
The domain of the client.
string
The IP address of the client requesting the transaction.
object
The Identification info of the sending and receiving customers. If they were created through SEP-12, this object should contain the SEP-12 customer
id. Otherwise, the account address of the customer.object
A object that identify end-user. For a SEP-12 customer, the
id field should be sufficient to fully identify the customer in the business’ Backend. For a SEP-31 Sending Anchor, the account and memo fields should be used. For a SEP-6 or SEP-24 Anchor, the account and memo fields should be used.Example
Example request to theget_transaction method.
Request