Payment Services for Adobe Commerce and Magento Open Source offers you comprehensive reporting so that you can get a clear view of your store’s transactions, orders, and payments.
The Transactions report provides visibility into transaction authorization rates and negative transaction trends so that you can effectively monitor the health of your store and preemptively identify and address any transaction issues.
See individual transactions for orders placed on the storefront and their payment methods, result, payment response codes, and more.
The information provided in the Transactions report is intended only for merchant use. Do not share this info with customers or other potential fraudsters. Transactions information could be used to bypass security checks or place orders that result in chargebacks.
You can download the Transactions report in a .csv file format for use in existing accounting or order management software.
You cannot view financial reports if you have not onboarded and activated Live mode for Payment Services.
The Transactions report view is available in the Transactions view of Payment Services. It includes all available information about transactions for your store(s).
On the Admin sidebar, go to Sales > Payment Services > Transactions > View Report to see the detailed tabular Transactions report view.
You can configure this view, per the sections in this topic, to best present the data you desire to see.
See linked Commerce order and provider transaction IDs, transaction amounts, payment method per transaction, and more, all within this report.
Not all payment methods provide the same granularity of information. For instance, credit card transactions provide response, AVS, and CCV codes in the Transactions report; PayPal Smart buttons do not.
You can download transactions in a .csv file format for use in existing accounting or order management software.
In the Transactions report view, you can select the data source—Live or Sandbox—for which you want to see report results.
If Live is the selected data source, you can see report information for your stores that use Payment Services in production mode. If Sandbox is the selected data source, you can see report information for your sandbox mode.
Data source selections work as follows:
To select the data source for your Transactions report:
On the Admin sidebar, go to Sales > Payment Services > Transactions > View Report.
Click Data source and select Live or Sandbox.
The report results regenerate based on the data source selected.
From the Transactions report view, you can customize the timeframe of the transactions you want to view by selecting specific dates. By default, 30 days of transactions are shown in the grid.
From the Transactions report view, you can filter the statuses results you want to view by selecting filter criteria.
The Transactions report shows all available columns of information by default. You can, however, customize which columns you see in your report.
On the Admin sidebar, go to Sales > Payment Services > Transactions > View Report.
Click the Column settings icon .
To customize which columns that you see in the report, check or uncheck columns in the list.
The Transactions report immediately shows any changes you made in the Column settings menu. The column preferences are saved and remain in effect if you navigate away from the report view.
The Transactions report view shows a Last updated timestamp that shows the last time that the report information was updated. By default, Transactions report data is auto-refreshed every three hours.
You can also manually force a refresh of the report data to see the most up-to-date report information.
On the Admin sidebar, go to Sales > Payment Services > Transactions > View Report.
Click the Refresh icon ().
The Transactions report data is refreshed, an Update complete confirmation appears, and the latest information is present in the grid.
You can download a .csv file with all transactions visible in the transactions view grid, whether you are viewing the default 30 days of transactions or a customized timeframe.
Your transactions are downloaded in a .csv format.
Transactions reports include the following information.
Column | Description |
---|---|
Order ID | Commerce order ID (contains only values for successful transactions and is empty for rejected transactions) To see related order info, click the ID. |
Provider Transaction ID | Transaction ID provided by the payment provider; contains only values for successful transactions and contains a dash for rejected transactions. |
Transaction Date | Transaction date timestamp |
Payment Method | Payment method of transaction; available for Payment Services versions 1.6.0 and newer |
Result | The result of the transaction—OK (successful transaction), Rejected by Payment Provider (rejected by PayPal), Rejected by Bank (rejected by bank that issued card) |
Response Code | Error code that provides rejection reason from payment provider or bank; see list of possible response codes and descriptions for Rejected by Bank status and Rejected by Payment Provider status. |
AVS Code | Address Verification Service code; the processor response information for payment requests. See list of possible codes and descriptions for more information. |
CVV Code | Card verification value code for credit and debit cards; see list of possible codes and descriptions for more information. |
Amount | Order amount of transaction |
Currency | Currency used for order in transaction |
Type | Payment action for transaction—Authorize or Authorize and Capture |
The Response Code column shows a specific error or success code related to the transaction. Some common error codes you might see displayed include:
PAYMENT_DENIED
—Transaction was declined by PayPal because it was suspected to be fraud.INTERNAL_SERVER_ERROR
—Transaction was declined by PayPal and incurred a PayPal server error. The transaction can be retried.INSTRUMENT_DECLINED
—Customer was declined by PayPal per selected payment method. Transaction can be retried with a different payment method.9500
—Transaction was declined by the associated bank because it was suspected to be fraud.5120
—Transaction was declined by the associated bank because the customer had insufficient funds for the payment.5650
—Transaction was declined by the associated bank because the bank requires strong customer authentication (3DS).Detailed error response codes for failed transactions are available for transactions newer than June 1, 2023. Partial report data will appear for transactions that occurred before June 1, 2023.