We would like to submit an identifier with a transactions such that in reports (chargeback, returns, etc.) direct from a processor (Chase, for example) we can correlate entries with our own records. Is "tp-request-id" the way to do this? The documentation states that this should be a UUID or GUID, but it's not clear if this is asking to use a standard format or not.
If this field is not the way to achieve our goal, is there another way?
You can submit a referenceNumber in the triPOS Cloud request, but where it shows up with the gateway processor reports depends on the gateway processor itself. There is no single field that can be sent in and reported on across all back-end processors behind Express.
For Vantiv, the referenceNumber submitted (first 35 chars) flows to the Customer Discretionary Data Field 1 in the settlement reports.
For Chase Paymentech, the referenceNumber submitted (first 30 chars) flow to the Customer Defined Data Token in the settlement reports.
For First Data, the referenceNumber submitted (first 12 chars) may get passed to FDC settlement systems only in certain cases, in which case it would flow into the Special Use Fields S Record.
Note that tp-request-id is not used for back-end settlement reporting purposes.
You can submit a referenceNumber in the triPOS Cloud request, but where it shows up with the gateway processor reports depends on the gateway processor itself. There is no single field that can be sent in and reported on across all back-end processors behind Express.
For Vantiv, the referenceNumber submitted (first 35 chars) flows to the Customer Discretionary Data Field 1 in the settlement reports.
For Chase Paymentech, the referenceNumber submitted (first 30 chars) flow to the Customer Defined Data Token in the settlement reports.
For First Data, the referenceNumber submitted (first 12 chars) may get passed to FDC settlement systems only in certain cases, in which case it would flow into the Special Use Fields S Record.
Note that tp-request-id is not used for back-end settlement reporting purposes.