Transaction History is the list of card results. Use it to see whether a payment was approved, declined, voided, or refunded.
Who can use this. You need the dashboard permission, or super admin. The menu name is Report, then Transaction History. The address is /dashboard/new_transaction_history.
Before you start. Stay in the correct business. The older address /dashboard/transaction_history still exists and is linked from some wallet rows. The menu opens the newer list.
Steps
- Open Report, then Transaction History.
- Set Status to Any, Approved (AA), or Declined (ND).
- Set Type to Any, Sale, Refund, Pre-Auth, or Force.
- Set the channel to Both, Online, or Terminal. For a Castle terminal business, Terminal in the left menu opens this same list already filtered to terminal.
- Set the card brand or the source. Sources are API, Payment Link, Payment Page, Subscription, Checkout API, Virtual Terminal, Terminal, and Refund By Reference.
- Search, then read Date & Time, Transaction ID, Batch, Type, Status, Amount, Card, Terminal, User, and Channel.
- Open a row for the detail. From there you can refund, void, or force only when that action is offered for the row.
| What you see | Meaning | What happens next |
|---|---|---|
| Approved (AA) | The list filter for response code AA. | An approved sale can still be waiting for settlement. |
| Declined (ND) | The decline filter. | No funds were captured for that row. |
| APPROVAL | Status text when an online row is approved and is not a refund. | The payment succeeded at the card step. |
| voided | The sale was voided while its batch was still open. | The approval was cancelled before settlement. |
| refunded | The type is a return. | This is a refund row, not the original sale. |
| PARTIAL APPROVAL | A terminal row where the approved amount is less than the amount requested. | Compare the amount with what you expected before you fulfill the order. |
| ND, RD, or CD on a terminal row | Shown as a failed terminal result. | Use the response text on the row. Do not treat it as approved. |
| Pre-Auth | Type Credit Card.Auth Only. | Not captured until a Force is accepted. |
| Force | Completes an eligible pre-auth. | Creates the capture result. It is not a refund. |
After you save or submit. Export downloads a file. The dashboard warns that a CSV can contain untrusted data. Opening the export does not change the payment.
Example. Example only: a fictional sale for 42.00 from a payment link shows Channel Payment Link, Status APPROVAL, and response filtering as Approved (AA). A second fictional attempt for 42.00 with Status ND is a decline. Only the APPROVAL row took the card payment.
Troubleshooting
- The payment is approved but the bank deposit is not there. Approval is not settlement. Open the wallet and batch articles.
- You cannot find the attempt. Widen Status to Any and check the date and business. Then open Payment Attempts on the link, page, or checkout session. A failure before the card was sent may have no transaction row.
- The detail offers no Refund. Refund is available only when the code is AA, the batch is no longer voidable, a card is stored, the payment is not a pre-auth, and the business wallet can cover it.
Related
Found this helpful?
( 1 out of 1 found helpful )
