SEP-6 SEP-24 SEP-31
Retrieve a transaction by its ID.
Params (1)
Result
(get_transactionResponse)The kind of transaction that is desired.Available options:
undefined, receive, deposit, deposit-exchange, withdrawal, withdrawal-exchangeProcessing 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_stellarThe memo type of the transaction in the Stellar network. Should be present if memo is not null.Available options:
id, hash, textThe memo type of the transaction in the Stellar network. Should be present if memo is not null.Available options:
id, hash, textThe 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.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