Impact records (single transaction)

What it does

The Impact Records by Transaction endpoint returns all impact and reversal entries linked to a single transaction. Use it when you want a complete picture of what happened for one customer payment or order.

ℹ️

See the API reference for example payloads.

Key fields explained

• transactionReferenceId → the ID of the transaction you want to look up
• impactAmount → amount directed to impact projects
• serviceFee → amount retained as service fee
• fundsFlow → whether the client owes ekko or ekko owes the client
• originalTransactionReferenceId → set on reversals to link them back to the original transaction

Best practices

• Use this endpoint when investigating disputes, refunds, or reconciliation issues on a single transaction
• Store and pass your own transactionReferenceId consistently across systems so you can trace records end-to-end
• Expect both contributions and reversals to be returned if the transaction has been refunded
• Use this alongside the main impact_records endpoint for broader reporting and exports