GetP2PTransactions
How it works
Use this function to get essential information on the P2P transactions which match the filtering rules.
-
The supported filtering rules are:
- a list of wallets ← the function will return transactions that belong to these wallets
- a list of transaction Ids ← the function will return transactions whose id appeared in this list
- a transaction id start ← the function will return transactions whose id is greater than this start id
- a transaction id end ← the function will return transactions whose id is smaller than this end id
- a start date ← the function will return transactions that were created after this start date
- an end date ← the function will return transactions that were created before this end date
-
You can also combine multiple filters (AND conditions) ← the function will return P2P transactions matching all of your filters
-
All filters are optional but you will have to specify (use) at least one of them.
-
There is a limit to the returned result.
- we will return at most 25000 matching transactions (this number might be different in your Environment)
- in case exceeding this limit, the flag "Complete" (in our response) will be set to 0 to indicate that there is at least one other P2P transaction matching the filtering rules but not included in this response.
- Reciprocally, if the flag Complete is set to 1, then it indicates that all the matching P2P transactions are in the response.
- If you want to increase this limitation, please contact [email protected]
XML
<GetP2PTransactions>
<wallets>
<string>string</string>
<string>string</string>
</wallets>
<transactionsIds>
<long>number</long>
<long>number</long>
</transactionsIds>
<transactionIdStart>long</transactionIdStart>
<transactionIdEnd>long</transactionIdEnd>
<startDate>string</startDate>
<endDate>string</endDate>
<wlLogin>string</wlLogin>
<wlPass>string</wlPass>
<language>string</language>
<version>string</version>
<walletIp>string</walletIp>
<walletUa>string</walletUa>
</GetP2PTransactions>
<?xml version="1.0" encoding="utf-8"?>
<GetMoneyTransactionsResult>
<COMPLETE>int</COMPLETE>
<COUNT>long</COUNT>
<TRANS>
<HPAY>
<ID>string</ID>
<DATE> string </DATE>
<SEN> string </SEN>
<REC> string </REC>
<CRED> string </CRED>
<DEB> string </DEB>
<MSG> string </MSG>
<STATUS> string</STATUS>
<SCHEDULED_DATE>string</SCHEDULED_DATE>
<IS_FEE>string</IS_FEE>
<FEE_REF>string</FEE_REF>
</HPAY>
...
<HPAY>
...
</HPAY>
</TRANS>
</GetMoneyTransactionsResult>
JSON
{
"wallets": ["string", "string"],
"transactionsIds": [number, number],
"transactionIdStart": number,
"transactionIdEnd": number,
"startDate": "string",
"endDate": "string",
"wlLogin": "string",
"wlPass": "string",
"language": "string",
"version": "string",
"walletIp": "string",
"walletUa": "string"
}
{
"COMPLETE": 0 or 1,
"COUNT": number,
"TRANS":[
{
"ID":"string",
"DATE":" string ",
"SEN":" string ",
"REC":" string ",
"DEB":" string ",
"CRED":" string ",
"MSG":" string ",
"STATUS":" string ",
"SCHEDULED_DATE":"string",
"IS_FEE": "string",
"FEE_REF": "string",
},
...
]
}
}
Request Input Description
| Item | Description | Mandatory | Format | Example |
| wallets | A list of wallets' external IDs: take transactions that belong to these wallets | No | [char(100)] | ["marketplace", "abc"] |
| transactionsIds | A list of transactions IDs: take transactions whose ID appeared in this list | No | [number, number..] | [89, 90, 91] |
| transactionIdStart | An integer: Take transactions that have a greater transaction ID (>=) | No | int | 100 |
| transactionIdEnd | An integer: Take transactions that have a lower transaction ID (<=) | No | int | 1000 |
| startDate | A date: Take transactions that were created after this date (>=) | No | "dd/MM/yyyy HH:mm:ss" | "14/01/2018 00:00:00" |
| or "yyyy-MM-dd HH:mm:ss" | "2018-01-14 00:00:00" | |||
| or epoch value | "1545311351" | |||
| endDate | A date: Take transactions which were created before this date (<=) | No | (same as start date) |
Response Output Description
| Item | Description | Example |
|---|---|---|
| COMPLETE | 1 = All matching transactions are in the response 0 = There is at least one transaction not included in the response | |
| COUNT | Transactions number in the response | |
| HPAY | Money-In/Out | |
| ID | P2P Transaction ID | 255 |
| DATE | Transaction Date | 10/9/2011 18:09 |
| SEN | Wallet Sender | capital01 |
| REC | Wallet Receiver | project01 |
| DEB | P2P Amount | 15 |
| CRED | P2P Amount (same as DEB) | 15 |
| MSG | Comment | Order number 245776 |
| STATUS | 3: success | 3 |
| 5: pending | ||
| others: error | ||
| SCHEDULED_DATE | An execution date for delayed P2P | 12/31/2015 |
| IS_FEE | Indicates if the P2P is a fee or a commission | 78956 |
| FEE_REF | Origin of the Money-In/Out transaction | 4567 |
Known Issue!
In the response, you might see more fields than in this documentation, the value of these additional fields is always null. Please ignore them. It means that you would ignore all the fields in the response which are not in this documentation. We will clean them up in the future.
Examples
XML
JSON
