GetP2PTransactions: retreive a list of P2P transactions

How it works

Use this function to get essential information of the P2P transactions which match the "filtering rules".

  • The supported filtering rules are:
    • a list of wallets ← the function will return transactions which 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 which was created after this start date
    • a end date ← the function will return transactions which was 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 of the returning result.
    • we will return at most 25000 matching transactions (this number might be different on 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 including 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 support@lemonway.com

Request

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

 

{
  "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"
}

Item

Description

Mandatory

Format

Example

wallets

A list of wallets external Ids: take transactions which 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

A integer: Take transactions which have a greater transaction Id (>=)

No

int

100

transactionIdEnd

A integer: Take transactions which have a lower transaction Id (<=)

No

int

1000

startDateA date: Take transactions which was 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"

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

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

Item

Description

Example

COMPLETE1 = All matching transactions are in the response / 0 = There is at least one transaction not including in the response 
COUNTNumber of transactions in the response 

HPAY

MONEY IN / OUT

ID

P2P Transaction Id

255

DATE

Transaction Date

10/09/2011 18:09:27

SEN

Wallet Sender

capital01

REC

Wallet Receiver

project01

DEB

Amount of the P2P

15.00

CRED

Amount of the P2P (same as DEB)

15.00

MSG

Comment

Order number 245776

STATUS

3: success
5: pending
others: error

3

SCHEDULED_DATE

execution date for delayed P2P

2015/12/31

IS_FEE
the P2P is a fee or a commission78956
FEE_REF
Origin Money In / Out transaction 4567

Knowing issue: In the response, you might see more fields than in this documentation, the value of these additional fields are 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