Display related transactions for an order
Check the related transactions for an order
To display the transactions for an order, do these steps.
-
From an Orders list, click on the ID of the order or the CUSTOMER name.
-
The Order Summary displays the order details. At the bottom of the screen, Related Transactions displays the authorisations and payments that have been processed for the card.
Display the transactions related to an order
-
To display processing details for a payment, click on the Transaction Unique ID. The Transaction Details pop-up will open. It includes the Result and the Card Details.
Transactions list
The Transactions list contains the following fields.
| Field | Description |
|---|---|
| Status indicator | A green dot represents an approved transaction, and a red dot represents a declined transaction |
| Date/Time UTC | The date and time that the transaction was processed in UTC time |
| SPID | The system's unique identifier of a scheduled payment for an active instalment, subscription, or metered order. |
| Type | See Transaction types |
| Transaction unique ID | The Gateway ID for the transaction. Click to display the transaction details. |
| Reference ID | The Gateway ID of a previous related transaction. For example, if you refund a DB (debit) transaction, then the Reference ID of the refund is the Gateway ID of the DB transaction |
| Amount | The amount of the transaction. The amount will be debited from or credited to the merchant account, depending on the transaction type. |
| Currency | The currency of the transaction. |
| Refund | If it is possible to refund a DB or CP transaction, BillPro displays the circular arrow Refund button next to it. Click this button to make a refund. When the transaction has been fully refunded, BillPro will hide the Refund button. |
Approved transactions
If the transaction is approved, the gateway's Result Code will have a value of 000.000.000. In a test environment, it may have other values. The Scheme Response Code will have a value of 0. If it is a recurring payment, the Merchant Advice Code or Visa Category Code will also have a value of 0. If there are non-zero values, the transaction was declined.
Details of a transaction approved with CardCorp
Transaction approval flow
The transaction approval process goes through the entities in this order.
- Gateway
- Acquirer
- Card Scheme
In the transaction response, the gateway returns one or more codes to the merchant, depending on which stage in the approval process a transaction reaches.
Transaction response workflow
Declined transactions
If a transaction is declined, the gateway's Result Code will be non-zero. For all gateway result codes, see Gateway documentation of result codes.
As an example, a gateway Result Code of 800.100.152 with the Description of transaction declined by authorization system means the issuer declined the transaction.
There will also be a non-zero Scheme Response Code or Acquirer Response Code and an Extended Description, which can provide more details of why the transaction was declined.
For recurring payments, declined transactions may also have a Visa Category Code or Merchant Advice Code. These codes define whether the transaction was hard-declined due to a permanent issue with the card or soft-declined due to a temporary issue with the card.
- If the transaction is hard-declined, you cannot retry it.
- If the transaction is soft-declined, you can retry it up to 15 times within 30 days of the soft decline.
If there is no Merchant Advice Code, Visa Category Code, or Scheme Response Code, it is possible that the transaction was soft-declined or failed at the payment gateway.
Visa table of Visa Category Codes (VCCs)
| Description | Visa Category Code (VCC) | In BillPro |
|---|---|---|
| Approved | 0 | Approved |
| Issuer will never approve | 1 | Hard-declined |
| Issuer cannot approve at this time | 2 | Soft-declined |
| Data quality issues / revalidate data | 3 | Soft-declined |
| Generic response codes | 4 | Soft-declined |
MasterCard table of Merchant Advice Codes (MACs)
| MAC Code | Description | In BillPro |
|---|---|---|
| 00 | Approved | Approved |
| 01 | Updated/additional information needed | Soft-declined |
| 02 | Try again later | Soft-declined |
| 03 | Do not try again | Hard-declined |
| 04 | Token requirements are not fulfilled for this token type | Soft-declined |
| 21 | Payment cancellation | Hard-declined |
Examples of transaction details
The following examples show declined transactions. For a description of the Transaction details fields, see Transaction details.
Expired card
For example, for an expired Visa card, the gateway sends a result code of 100.100.303.
A transaction that was hard declined due to an expired card
Soft declined transaction
The following transaction was soft-declined. For MasterCard, a code value of 02 is soft-declined, and for Visa a code value of 2 is soft-declined. When a transaction is soft-declined, you can retry it (automatically or manually) up to 15 times in the following month. You can also configure BillPro to retry transactions automatically. See Auto-retry billing events.
Hard declined transaction
The following transaction was hard-declined. For MasterCard, a code value of 03 is hard-declined, and for Visa, a code value of 1 is hard-declined. When a transaction is hard-declined, you cannot retry it. You must contact the customer and update the card details. See Update cards.
Updated 3 months ago