Need TAG from Payeezy Search and Payment API to Clover

With Payeezy Search and Reporting API no longer supported, we're in the process of migrating our Reporting operations to Clover. Within our internal accounting application, we rely on fetching transaction data and matching it with our database of itemized transactions. To make this happen, we use a unique identifier called the Transaction TAG. In the past, we got this TAG from Payeezy's API response for each successful transaction.

The hiccup we're facing is that we can't seem to find this Transaction TAG in the data we get from Clover's Payment API Reporting.

Is there a way you can help us figure out how to retrieve this crucial Transaction TAG data using Clover's Payment API? Our main goal is to ensure a smooth transition without losing our ability to accurately match and reconcile transaction information.

Any insights or guidance you can provide on this matter would be greatly appreciated.

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

bryanvargas ♦♦ commented · Aug 28, 2023 at 04:16 PM

From what I researched on the Transaction TAG, Clover does have a transactions number that increments by 1 with each card transaction. You can see this by running the GET PAYMENTS endpoint and expand on cardTransactions: .

{ {baseUrl}}/v3/merchants/{ {mId}}/payments?expand=cardTransaction

In the expanded field you will see a transactionNo field.

However, Clover always have payments IDs you can report on that are alphanumeric and unique.

You can also explore our externalReference field, and invoice field

0 ·