View Transaction 
Type: Form
Description: Allows to see additional information about the selected blacklisted transaction.
Items:
View Transaction |
|
Includes information on the selected transaction.
|
| ¦_ |
Receipt
|
Opens the receipt of the transaction in .pdf document. |
| ¦_ |
Close
|
Closes the form without saving any changes. |
Detail |
|
Includes detailed information on the transaction selected.
|
| ¦_ |
Id
|
Identifier of the object used for references; auto-incremented integer value. References: Transaction.Id |
| ¦_ |
Account
|
Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code. The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database. References: Transaction.Merchant Account Code |
| ¦_ |
Source
|
Represents the type of payment, which is used for the transaction. References: Charge Transaction.Account Source CL |
| ¦_ |
Type
|
Type of transaction. For more information see
{|class="newtable newtablenorowspan pull-left"
!style="font-weight:bold"| Transaction type/ Transaction state
!style="font-weight:bold"|approval
!style="font-weight:bold"|decline
!style="font-weight:bold"|delayed decline*
!style="font-weight:bold"|void
!style="font-weight:bold"|blacklist
!style="font-weight:bold"|error
|-
|sale
|sale
|decline
|decline (d)
|void
|blacklist
|rowspan="2"|error
|-
|sale
|sale
|decline (c)
|decline (cd)
|void (c)
|blacklist (c)
|}
*applicable only for certain processors
Splits and Pulls
For sale transactions:
— Split-in - transaction generated in the context of the split payments functionality based on a sale transaction, which creates a record that an affiliate has received the commissions as a part of the original sale transaction processed by a merchant. On the user interface, a split-in transaction is always displayed with “+” symbol.
— Split-out - transaction generated in the context of the split payments functionality based on a sale transaction, which creates a record that a merchant, that processed the original transaction, has transferred the commissions to an affiliate. On the user interface, a split-out transaction is always displayed with “-” symbol.
For credit/refund/chargeback/return transactions:
— Pull-in - transaction generated in the context of the split payments functionality based on the credit/refund/chargeback/return of the original transaction and creates a record that the merchant has received the commissions, previously charged via split-in, from the affiliate.
— Pull-out - transaction generated in the context of the split payments functionality based on the credit/refund/chargeback/return of the original transaction and creates a record that the affiliate has transferred the commissions, previously charged via split-out, to the merchant.
Splits and pulls on the gateway user interface depending on the transaction state:
{|class="newtable newtablenorowspan pull-left"
!style="font-weight:bold"| Transaction type/ Transaction state
!style="font-weight:bold"|approval
!style="font-weight:bold"|void
|-
|Split-in
|split-in
|rowspan="2"|void (i)
|-
|Pull
|pull-in
|-
|Split-out
|split-out
|rowspan="2"|void (o)
|-
|Pull-out
|pull-out
|}
Non-financial transactions
— Notice (notice of change) - direct debit transaction that is returned by a bank and notify that some details of the transaction were corrected.
— Inquiry (balance inquiry) - operation used to verify balance on debit, prepaid or gift cards.
— Verification (account verification) - operation used to verify that an account is active and to perform AVS verification without actual authorization.
— Fee (convenience fee) - operation used to calculate a surcharge to a cardholder to cover the cost of credit card processing.
For gift cards:
— Transfer - operation used to transfer a balance from one gift card to another.
— Activation - operation used to activate a gift card.
— Deactivation - operation used to deactivate an active gift card.
— Reactivation - operation used to reactivate a previously deactivated gift card.
— Create-alias - operation used to create an alias (token) for a gift card.
— Delete-alias - operation used to remove a previously created alias (token) for a gift card.
" >Transaction type. |
| ¦_ |
Account Type
|
Represents the type of the account (e.g. credit card or bank account) associated with the transaction. References: Charge Transaction.Account CL |
| ¦_ |
Status
|
Current status of the transaction. References: Transaction.Transaction Status Cl |
| ¦_ |
Request Date
|
Date when transaction was sent to Provider for processing. References: Charge Transaction.Request Date |
| ¦_ |
Customer Name
|
Name of the account holder, assosiated with this transaction.
It is also used as first name of the billing address. References: Charge Transaction.First Name |
| ¦_ |
Credit Card #
|
Masked version of the account number (credit card or bank account) associated with this transaction. The mask is formed by using the first and last digits of the account.
For example, 4********5655. References: Charge Transaction.Account Number Masked |
| ¦_ |
Exp Date
|
When transaction is associated with a credit card, the field contains card's expiration date.
When transaction is associated with a bank account, the field contains account's routing number. References: Charge Transaction.Account Accessory |
| ¦_ |
Transaction Code
|
Value from the transaction submitter's system.
It is used to assign submitter's specific transaction id to the transaction, to cross reference this transaction between two systems. Usually, the value will contain a reference to an entity representing this transaction in submitter's front-end system. References: Charge Transaction.Transaction Code |
| ¦_ |
Customer Code
|
Value from the transaction submitter's system.
It is used to assign submitter's specific customer (owner) code to the transaction, to identify in the future the ownership of the transaction and to be able to cross reference the value between two systems. Usually, the value will contain a reference to an record representing an owner of the transaction in the submitter's front-end system. References: Charge Transaction.Customer Account Code |
| ¦_ |
Item Code
|
Value from the transaction submitter's system.
It is used to assign submitter's specific merchandise code (SKEW#, Bar Code, etc) to the transaction, to identify in the future the reason why this transaction was processed. Usually, the value will contain a reference to a catalog item for which the payment is collected and is, therefore, only applicable in cases when a payment is collected for a single item. References: Charge Transaction.Item Code |
| ¦_ |
Memo
|
Description of the transaction, might be coming from the submitter's system or assigned internally. References: Charge Transaction.Transaction Memo |
Amounts |
|
Includes information on the amounts of the selected transaction.
|
| ¦_ |
Original (Auth)
|
For credit cards only. Original amount of the transaction. In most cases, Original Amount and Amount fields will match.
In case of partial authorizations, however, original amount will contain the originally requested amount of the transaction, while Amount field will contain the amount of money available on the card (usually occurs when debit cards or gift cards are involved). References: Charge Transaction.Original Amount |
| ¦_ |
Settlement
|
Total amount of the transaction.
When partial authorizations are done, amount represents required amount, which may or may not be available. References: Transaction.Amount |
| ¦_ |
Cashback
|
Amount of money, returned to a customer upon "Sale with Cashback" transaction. References: Charge Transaction.Cash Back Amount |
| ¦_ |
Net
|
Net settled amount of the transaction. References: Charge Transaction.Net Amount |
| ¦_ |
Discount
|
Amount of the total discount applied on this order/transaction.
References: Charge Transaction.Discount Amount |
| ¦_ |
Tip
|
For restaurant industry only. Amount of the tip. References: Charge Transaction.Tip Amount |
| ¦_ |
Convenience Fee
|
Amount of a fee assessed to cover the cost of credit card processing. |
| ¦_ |
Retry Fee
|
Amount of retry fee applied to this transaction if any. See Transaction Reprocessing for additional information. References: Charge Transaction.Retry Fee Amount |
| ¦_ |
Tax
|
Amount of tax charged as part of this transaction. The value is included in the total transaction Amount. References: Charge Transaction.Tax Amount |
| ¦_ |
National Tax
|
Amount of national/federal tax charged on the order/transaction.
References: Charge Transaction.National Tax Amount |
| ¦_ |
Local Tax
|
Amount of local (city, count, etc) tax charged on the order/transaction.
The value in database is stored in cents. For example: $1 = 100 References: Charge Transaction.Local Tax Amount |
Address |
|
Includes information on the address associated with the selected transaction.
|
| ¦_ |
Street
|
Street of the billing address.
Both Street 1 line and Street 2 line are combined in this field. References: Charge Transaction.Street |
| ¦_ |
City
|
City of the billing address. References: Charge Transaction.City |
| ¦_ |
State
|
Country and state of the billing address. |
| ¦_ |
Zip Code
|
ZIP/Postal code of the billing address. References: Charge Transaction.ZIP Code |
| ¦_ |
Phone
|
Billing phone or contact phone of the account holder. References: Charge Transaction.Phone |
| ¦_ |
Email
|
Contact email of the account holder. References: Charge Transaction.Email |
Processing |
|
Includes information on the processing options for the selected transaction.
|
| ¦_ |
Rebill Enabled
|
Indicates whether decline reprocessing mechanism is enabled or not. References: Charge Transaction.Is Rebill Enabled |
Gateway Response |
|
Includes information on the response from the gateway.
|
| ¦_ |
Date
|
Date when ACH return/CC chargeback was received. References: Chargeback Transaction.Response Date |
| ¦_ |
Code
|
Response code for the transaction.
All possible response codes are defined in Reprocessing Profile. The value is produced from the Provider specific response code, which is returned after a transaction is processed with the Provider. References: Transaction.Response Code |
| ¦_ |
Message
|
Response message that corresponds to the response code for this transaction.
Response message includes Provider's response message as well as standard system message associated with this specific response code. References: Transaction.Response Message |
| ¦_ |
CSC Code
|
Response code supplied by the Provider that processed the transaction based on CVV2 value supplied during transaction authorization. References: Retail Transaction.Cvv2 Response Code |
| ¦_ |
AVS Code
|
Address verification response code returned by Provider for this transaction based on the billing address supplied for transaction processing. References: Charge Transaction.AVS Result Code |
Processor Response |
|
Includes information on the response from the processor.
|
| ¦_ |
Code
|
Response code for the transaction.
All possible response codes are defined in Reprocessing Profile. The value is produced from the Provider specific response code, which is returned after a transaction is processed with the Provider. References: Transaction.Response Code |
| ¦_ |
Message
|
Response message that corresponds to the response code for this transaction.
Response message includes Provider's response message as well as standard system message associated with this specific response code. References: Transaction.Response Message |
| ¦_ |
CSC Code
|
Response code supplied by the Provider that processed the transaction based on CVV2 value supplied during transaction authorization. References: Retail Transaction.Cvv2 Response Code |
| ¦_ |
AVS Code
|
Address verification response code returned by Provider for this transaction based on the billing address supplied for transaction processing. References: Charge Transaction.AVS Result Code |
Descriptor |
|
Includes values, associated with underlying merchant ID (or can be specified for each transaction processing).
|