Developers1 min read
Every protected transaction carries an ArosaPay transaction identifier and, where you set one, your own merchant reference. Using them for the right job keeps reconciliation and support clean.
The transaction identifier
- Issued by ArosaPay and unique across the platform.
- Stable for the life of the transaction, including through the exception path.
- The identifier to quote in support and to match settlements on.
Your merchant reference
- Set by your system when the transaction is created.
- Should be unique in your own order system — duplicates make reconciliation ambiguous.
- Keep it free of customer personal data; it appears on operational records.
In practice
Store both against your order at creation time. Match settlements on the transaction identifier and use your reference to route the match back into your ledger — see Payment reconciliation.
Go deeper
Related guides
DevelopersPayment reconciliationHow to tie released settlements back to orders in a finance system, and where exceptions come from.DevelopersAPI overviewWhat the ArosaPay API covers, how it is authenticated, and where the full reference lives.SellersSettlement and reconciliationHow released settlements arrive, what appears on the record, and how to match them to your orders.
Last updated