Transactions Reconciliations

This page details how Evonet's best-in-class reconciliation reports utilize merchant-provided data fields to streamline the reconciliation process across all integration methods (LinkPay, Drop-in, and Direct API).

Key Reconciliation Fields

By consistently mapping your internal identifiers to the following fields, you can achieve automated, one-to-one matching between your business records and Evonet transaction reports:

• merchantOrderReference: This is the primary field for your internal order number or unique reference code. It appears prominently in all Evonet reconciliation exports to facilitate easy search and mapping.
• merchantOrderID: A secondary identifier often used to group multiple transactions under a single business order.
• merchantTransID: A unique transaction-level identifier from your system. Providing this ensures that even in complex scenarios like partial refunds or re-authorizations, every movement of funds is uniquely traceable.
• Metadata: A flexible "value" object that allows you to pass custom business data (e.g., Channel: "mobile_app", or customer_loyalty_id "12345"). This data is preserved throughout the transaction lifecycle and included in your reconciliation reports for advanced segmenting and reporting.

Consideration based on API Integration

During reconciliation, data can be sourced from Request, Response, and Webhook.

📘

Note

• merchantTransID is used for uniqueness verification to identify a single transaction.
• merchantOrderReference refers to a single order in the merchant's system. The same order may have multiple payments (different merchantTransID values).
• For LinkPay and Drop-in orders, merchantTransID and merchantOrderReference are key reconciliation fields.