One of the required fields of any transaction request is the
externalId. This value allows you to track a transaction using a unique value and keep a record to assist a merchant with reconciliation. Clover also records this value so any transaction can be examined for issues in the future. There are two types of transaction identifiers used by integrated apps:
externalId—Required. Universally unique identifiers (UUID) for tracking transactions in Clover systems.
externalReferenceId—Optional. Universally unique identifiers (UUID) used for invoice or purchase order tracking that flows through to external reporting systems.
Uniqueness of the of the identifier (Id) is essential. Each example app shows a simple method for creating an Id in the recommended format, which is a string of at least 13 alphanumeric characters.
- Remote Pay Android—
- Remote Pay Cloud—
- Remote Pay iOS—
- Remote Pay Windows—
To ensure the value is always available, it is recommended that point of sale (POS) apps save the external Id as soon as possible and not wait for the transaction response from Clover. If Clover does not return a response for some reason, the POS will still have a record that the transaction was attempted.
Merchants may use non-Clover reporting tools to view their settlement information. To provide traceability of a given transaction, you must set the
externalReferenceId to a unique Id that is 12 or fewer characters. This length is a limitation of other systems the merchant may use).
To ensure the value is always available, you must ensure that POS apps save the reference Id as soon as possible and not wait for the transaction response from Clover. If Clover doesn't return a response for some reason, your POS app will still have a record that the transaction was attempted.
Updated about 1 month ago