get transaction hashes by payment id: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (→Description) |
||
| Line 16: | Line 16: | ||
== Description == | == Description == | ||
* This is JSON version of [[get_transaction_hashes_by_payment_id.bin]] and uses same structs as the binary version | * This is JSON version of [[get_transaction_hashes_by_payment_id.bin]] and uses same structs as the binary version. | ||
== Notes == | == Notes == | ||
* Payment ID is passed as array of 8-bit integers, instead of hexadecimal string | * Payment ID is passed as array of 8-bit integers, instead of hexadecimal string | ||
* Transaction hashes are returned as array of 8-bit integers, instead of hexadecimal string | * Transaction hashes are returned as array of 8-bit integers, instead of hexadecimal string | ||
Revision as of 06:15, 23 March 2020
Input
| Argument | Mandatory | Description | Format |
|---|---|---|---|
| paymentId | yes | Payment ID | Hash |
Output
| Argument | Description | Format |
|---|---|---|
| transactionHashes | List of transaction hashes | array |
| status | Status of request, "OK" if successful | string |
Description
- This is JSON version of get_transaction_hashes_by_payment_id.bin and uses same structs as the binary version.
Notes
- Payment ID is passed as array of 8-bit integers, instead of hexadecimal string
- Transaction hashes are returned as array of 8-bit integers, instead of hexadecimal string