What are the different transaction identifiers?

When working with Ivy payments, you’ll encounter multiple identifiers across the dashboard, exports, and API. Here’s how they differ and where each is used:

Order ID

• What it is:
  A unique internal identifier generated by Ivy when the user selects a bank and an order is officially created.

• Where to find it:
  Visible in the dashboard, webhooks, and API responses.

• Used for:

  • Tracking the entire payment lifecycle (from creation to settlement or failure)

  • Linking payments with customer actions

  • Support queries

Reference ID

• What it is:
  A UUID created to track and link the transaction across systems. It’s consistent throughout the lifecycle of a specific transaction and created by the merchant once the checkout session is created.

• Where to find it:

  • In your dashboard (next to each transaction)

  • In your API and webhook payloads

• Used for:

  • System-to-system tracking

  • Reconciliation and correlation with your internal order systems

  • Debugging and referencing specific transactions across integrations

Bank Statement Reference

• What it is:
  The reference text (e.g., irfbe81c4b7c85df1) sent to the user’s bank to identify the payment in the transaction description.

• Where to find it:

  • On the payment details page in your dashboard

  • In the user’s bank statement

  • In your webhook payloads under bankStatementReference

• Used for:

  • Ensuring correct payment matching (especially for manual bank transfers)

  • Merchant reconciliation

  • Detecting unmatched deposits