get transaction hashes by payment id: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Input == {| class="wikitable" ! Argument !! Mandatory !! Description !! Format |- | paymentId || yes || Payment ID || Hash |} == Output == {| class="wikitable" ! Argu...") |
No edit summary |
||
| Line 14: | Line 14: | ||
| status || Status of request, "OK" if successful || string | | 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. This means some values need to be converted if passed to methods expecting strings instead of arrays of 8-bit integers. | |||
== 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 | |||
Revision as of 01:31, 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. This means some values need to be converted if passed to methods expecting strings instead of arrays of 8-bit integers.
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