Query transactions

You can retrieve a transaction by its transactionIdentifier:

get /v2/transactions/{transactionIdentifier} Try it out! Response
	"status": "ok",
	"data": {
		"identifier": "af6c42cd-2b9f-4751-90cd-61059225ea43",
		"customIdentifier": "123-xyz",
		"status": "APPROVED",
		"subject": "Sundays Shopping",
		"groupIdentifier": "4697008c-8d1e-426a-9a72-8d31d7843e2a",
		"processingDetails": {…},
		"receiptDetails": {…},
		"type": "CHARGE",
		"paymentDetails": {…},
		"locationDetails": {…},
		"currency": "EUR",
		"mode": "TEST",
		"amount": 17.07,
		"created": "2013-09-05 15:18:54",
		"statusDetails": {…},
		"reader": {…},
		"cardDetails": {
			"fingerprint": "a5e2188a-f676-11e5-b944-593944fafab9",
			"scheme": "MASTERCARD",
			"maskedCardNumber": "541333******0086",
			"expiryMonth": 2,
			"expiryYear": 2017,
			"cardholderName": null

Important Parameters:

The fingerprint is a unique identifier can be stored by your backend as a reference to the shopper. It can be used to build features such as a purchase history for loyalty programs or to associate a shopper with an email address for automated receipts and promotions.