Retreive a List of P2P Transactions

GetP2PTransactions

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 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
    • a 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 returning 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 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 [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

ItemDescriptionMandatoryFormatExample
walletsA list of wallets external Ids: take transactions that belong to these walletsNo[char(100)]["marketplace", "abc"]
transactionsIdsA list of transactions Ids: take transactions whose id appeared in this listNo[number, number..][89, 90, 91]
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 was 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 including in the response
COUNTNumber of transactions in the response
HPAYMoney-in/out
IDP2P Transaction Id255
DATETransaction Date10/9/2011 18:09
SENWallet Sendercapital01
RECWallet Receiverproject01
DEBAmount of the P2P15
CREDAmount of the P2P (same as DEB)15
MSGCommentOrder number 245776
STATUS3: success3
5: pending
others: error
SCHEDULED_DATEExecution date for delayed P2P12/31/2015
IS_FEEThe P2P is a fee or a commission78956
FEE_REFOrigin money-in/out transaction4567

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

XMLXML

JSON

JSONJSON