Retrieve a List of Money-In/Out Transactions

GetMoneyTransactions

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
    • an 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 returned 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 [email protected]

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>
<?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

{
  "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"
}
{   
    "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"
            },
            ...
        ]
    }
}

Request Input Description

ItemDescriptionMandatoryFormatExample
walletsA list of wallets external IDs: take transactions that belong to these walletsNo[char(100)]["marketplace", "abc"]
transactionsIdsA list of transaction IDs: take transactions whose ID appeared in this listNo[number, number..][89, 90, 91]
merchantTokensA list of merchant tokens (wkToken given in MoneyInWebInit)No[char(50)]["312232", "command10"]
transactionIdStartAn integer: Take transactions that have a greater transaction Id (>=)Noint100
transactionIdEndAn integer: Take transactions that have a lower transaction ID (<=)Noint1000
startDateA 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"
endDateA date: Take transactions which were created before this date (<=)No(same as start date)

Response Output Description

ItemDescriptionExample
COMPLETE1 = All matching transactions are in the response / 0 = There is at least one transaction not included in the response
COUNTNumber of transactions in the response
HPAYMoney-In/Out
IDTransaction ID255
TYPE0 = Money-In
1 = Money-Out
10/9/2011 18:09
DATETransaction Date10/9/2011 18:09
SENThe wallet which did the Money-Out (null if TYPE is 0)
RECThe wallet which did the Money-In (null if TYPE is 1)pizza
DEBAmount of the Money-Out (null if TYPE is 0)0
CREDAmount of the Money-In (null if TYPE is 1)15
COMYour fee in case autoCom = 0 or Lemonway fee if the autoCom = 12
MSGCommentOrder number 245776
INT_STATUS0: success0
4: pending
6: error
7: cancelled (by client or time out)
16: wait for validation/finalization
INT_MSGError codes from our partners or messages from Lemonway05-00-05 ERR_PSP_REFUSED
MLABELIBAN when Money-In by iDEAL or SDD
SCHEDULED_DATEIf it's a Money-In by SDD, and if you have a collection date12/31/2015
ORIGIN_TRANSACTIONOrigin transaction ID of the Refund or Chargeback transactions (null for normal transactions)78956
MTOKENMerchant Token or WkToken (the token that you gave to the MoneyInWebInit function)
METHODPayment Method:0
0: Card
1: MoneyIn By Wire
15: Check
...
CARD_IDThe Card token for Rebill transactions (null for normal transactions)15
IS_CHARGEBACK1 for chargeback transactions
0 otherwise
0

🚧

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

XML

JSON

JSON