Zettle transaction id tracing

[TriStarGod]

Expected Behavior

Please describe the behavior you are expecting. When we create a reference created by TransactionReference.Builder("12345").put("PAYMENT_EXTRA_INFO", "Test 12345").build(), we expect that id "12345" is the originatingTransactionUuid returned from calling Get account transactions API. We are using Get account transactions API to audit and confirm our transaction history matches independently from the sdk-android because refunds can be made via the zettle website.

Current Behavior

What is the current behavior? A new reference uuid is generated and we can't trace it back to the original payment.

Is it because

1. Our uuid isn't unique or long enough. Currently using a 5 character string.
2. Using the wrong API or calling the API incorrectly?

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. Create a reference as mentioned before
2. Send an intent to charge $X amount
3. Pay with card
4. Couple hours later, call Get account transactions API with date range set current day, transactionType=LIQUID and includeTransactionType=PAYMENT

Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

• Operating Version: Android 12
• SDK version: 1.36.1

Failure Logs

Please include any relevant log snippets or files here. N/A