GetMoneyTransactions: Retrieve a List of Money-in/out Transactions
How it works
Use this function to get essential information of the 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 list of the merchant tokens (wktoken) ← the function will return transactions whose merchant id (wktoken) appeared in this list
- a start date ← the function will return transactions that were created after this start date
- a end date ← the function will return transactions that were created before this end date
- You can also combine multiple filters (AND condition) ← the function will return 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 returning result.
- we will return at most 5000 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 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 transactions are in the response.
- If you want to change this limitation, please contact support@lemonway.com
Request
XML
<GetMoneyTransactions>
<wallets>
<string>string</string>
<string>string</string>
</wallets>
<transactionsIds>
<long>number</long>
<long>number</long>
</transactionsIds>
<merchantTokens>
<string>string</string>
<string>string</string>
</merchantTokens>
<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>
</GetMoneyTransactions>
JSON
{
"wallets": ["string", "string"],
"transactionsIds": [number, number],
"merchantTokens": ["string", "string"],
"transactionIdStart": number,
"transactionIdEnd": number,
"startDate": "string",
"endDate": "string",
"wlLogin": "string",
"wlPass": "string",
"language": "string",
"version": "string",
"walletIp": "string",
"walletUa": "string"
}
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] |
merchantTokens | A list of merchant token (wkToken given in MoneyInWebInit) | No | [char(50)] | ["312232", "command10"] |
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" or "yyyy-MM-dd HH:mm:ss" or epoch value | "14/01/2018 00:00:00" "2018-01-14 00:00:00" "1545311351" |
| endDate | A date: Take transactions which was created before this date (<=) | No | (same as start date) |
Note
You have to fill in at least one parameter
Answer
XML
<?xml version="1.0" encoding="utf-8"?>
<GetMoneyTransactionsResult>
<COMPLETE>int</COMPLETE>
<COUNT>long</COUNT>
<TRANS>
<HPAY>
<ID>string</ID>
<TYPE> string </TYPE>
<DATE> string </DATE>
<SEN> string </SEN>
<REC> string </REC>
<CRED> string </CRED>
<DEB> string </DEB>
<COM> string </COM>
<MSG> string </MSG>
<INT_STATUS> string</INT_STATUS>
<INT_MSG>string</INT_MSG>
<MLABEL>string</MLABEL>
<SCHEDULED_DATE>string</SCHEDULED_DATE>
<ORIGIN_TRANSACTION>string</ORIGIN_TRANSACTION>
<MTOKEN>string</MTOKEN>
<METHOD>string</METHOD>
<CARD_ID>string</CARD_ID>
<IS_CHARGEBACK>string</IS_CHARGEBACK>
</HPAY>
...
<HPAY>
...
</HPAY>
</TRANS>
</GetMoneyTransactionsResult>
JSON
{
"COMPLETE": 0 or 1,
"COUNT": number,
"TRANS":[
{
"ID":"string",
"TYPE": "string"
"DATE":" string ",
"SEN":" string ",
"REC":" string ",
"DEB":" string ",
"CRED":" string ",
"COM":" string ",
"MSG":" string ",
"INT_STATUS":" string ",
"INT_MSG":"string",
"MLABEL":"string",
"SCHEDULED_DATE":"string",
"ORIGIN_TRANSACTION": "string",
"MTOKEN": "string",
"METHOD": "string",
"CARD_ID": "string",
"IS_CHARGEBACK": "string"
},
...
]
}
}
Item | Description | Example |
|---|---|---|
| COMPLETE | 1 = All matching transactions are in the response / 0 = There is at least one transaction not including in the response | |
| COUNT | Number of transactions in the response | |
HPAY | Money-in/out | |
ID | Transaction Id | 255 |
TYPE | 0 = Money-in / 1 = Money-out | 10/09/2011 18:09:27 |
DATE | Transaction Date | 10/09/2011 18:09:27 |
SEN | The wallet which did the money-out (null if TYPE is 0) | |
REC | The wallet which did the money-in (null if TYPE is 1) | pizza |
DEB | Amount of the money-out (null if TYPE is 0) | 0.00 |
CRED | Amount of the money-in (null if TYPE is 1) | 15.00 |
COM |
| 2.00 |
MSG | Comment | Order number 245776 |
| INT_STATUS | 0: success | 0 |
INT_MSG | Error codes from our partners or messages from Lemonway | 05-00-05 ERR_PSP_REFUSED |
MLABEL | IBAN when money-in by iDEAL or SDD | |
SCHEDULED_DATE | If it's a money-in by SDD, and if you gave a collection date | 2015/12/31 |
ORIGIN_TRANSACTION | Origin transaction Id of the Refund or Chargeback transactions (null for normal transactions) | 78956 |
MTOKEN | Merchant Token or WkToken (the token that you gave to the MoneyInWebInit function) | |
METHOD | Payment Method:
| 0 |
CARD_ID | The Card token for Rebill transactions (null for normal transactions) | 15 |
IS_CHARGEBACK | 1 for chargeback transactions / 0 otherwise | 0 |
Knowing 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.
Postman Example
XML
JSON
