Page tree
Skip to end of metadata
Go to start of metadata

 Request

Response


The transaction search function is used to obtain the list of transactions corresponding to the search criteria entered by the user.

Request


The request has the following structure :

Element

Description

Required

Format

API REST Value

Example

version

Version of Payline web services. Check the history to set up a value. To be valued at least with the value "3"

Yes

N2


18

transactionID

The identifier of the transaction communicated by Payline

No

AN50



orderRef

The identifier of the order at the merchant

NoAN50

startDate

Start of the period for which transactions are done

NoAN10
22/01/2010
endDate

End of the period for which transactions are done

NoAN10

22/01/2010

contractNumber

Contract number associated with the transaction

NoAN50

authorizationNumber

Authorization number of the transaction

NoAN6

returnCode

Return code sent to the user

NoAN5

paymentMean

The payment method used

NoAN3

transactionType

Transaction Type, see all values here.

NoAN3
1
name

The name of the buyer

NoAN100

firstNameThe first name of the buyerNoAN100

email

The email address of the buyer

NoAN150

cardNumber

The card number used to complete the transaction

NoAN20

currency

The currency code used to complete the transaction

NoAN3

minAmount

Minimum amount of the transaction

NoAN12

maxAmount

Maximum amount of the transaction

NoAN12

walletId

The identifier of the wallet used for the transaction

NoAN50

sequenceNumber

Sequence number used during the transaction

NoAN50

token

Alias ​​of the card number

NoAN19
1111gPNzHtyu4444
pointOfSellIdPoint of sale identifier.NoAN
From version 23
cardNetworkCard network code. See values : cardNetworkNoAN
From version 23
threeDSecuredType of transaction's 3DS authentication. See values : threeDSecuredNoAN
From version 23
customerMediaId Customer media code. See values : customerMediaIdNoAN
From version 23