The search function of a transaction permits to obtain the details of a payment transaction whatever its state.
The getTransactionDetailsRequest message is used to search the details of a payment transaction.
The query has the following structure:.
We recommend to use transactionID to identify a unique transaction. For specific case, you can use orderRef to identify the transaction, but you have to be sure, there is only one operation to do not get any error. ![(avertissement)](/s/-sus15c/8804/os61ar/_/images/icons/emoticons/warning.svg)
Request
Extrait |
---|
Element | Description | Required | Format | version | Payline web services version. To be valued with the latest version: see the table of versions. | Yes | N2 | transactionIDtransactionid | The identifier of the transaction communicated by Payline. | YesNo | AN50 | orderRef | The identifier of the order at the merchant. | No | AN50 | startDate | Start of the period for which transactions are sought. Format DD/MM/YYYY. | No | Date | endDate | End of the period for which transactions are sought. Format DD/MM/YYYY. | No | Date | transactionHistory | This flag retrieves the list of associated payments (associatedTransactions) as well as the status history (statusHistoryList) for a given transaction. This feature is optional. The possible values are: - "Y": display of the status history and associated payments; - "N": absence of status history and associated payments; - Null or unspecified: absence of status history. | No | A1 | archiveSearch | True: The search in the archive database will be activated. False: The search in the archive database will not be activated. | No | Boolean |
|