View Transaction (Split-In/Pull-In) 
Type: Form
Description: Provides additional information about the split-in/pull-in transaction.
Items:
View Transaction (Split-In) |
|
Includes information on the split-in transaction.
|
| ¦_ |
Receipt
|
Opens the receipt of the transaction in .pdf document. |
| ¦_ |
Close
|
Closes the form without saving any changes. |
General |
|
Includes general information about the transaction.
|
| ¦_ |
ID
|
Identifier of the object used for references; auto-incremented integer value. References: Transaction.Id |
| ¦_ |
Request Date
|
Date when transaction was sent to Provider for processing. References: Charge Transaction.Request Date |
| ¦_ |
Account ID/Code/Name
|
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 |
| ¦_ |
Terminal ID
|
Identifier of the object used for references; auto-incremented integer value. References: Terminal Data.Id |
| ¦_ |
Terminal Code
|
Identifier of the terminal assigned within a submitter's system. References: Charge Transaction.Terminal Code |
Amounts |
|
Includes information on the amounts of the selected transaction.
|
Transaction Amounts |
|
Includes information about main transaction amounts.
|
| ¦_ |
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 |
| ¦_ |
Currency Code
|
Represents code of the currency used in the authorization transaction. References: Charge Transaction.Authorization Currency Code CL |
| ¦_ |
Settlement
|
Total amount of the transactions including discount and tax. The amount element defines the amount of the transaction. Supply the value in cents without a decimal point. References: Charge Transaction.Amount |
| ¦_ |
Currency Code
|
Represents code of the currency used for capture transactions. References: Charge Transaction.Capture Currency Code CL |
| ¦_ |
Net
|
Net settled amount of the transaction. References: Charge Transaction.Net Amount |
| ¦_ |
Currency Code
|
Represents code of the currency used in the authorization transaction. References: Charge Transaction.Authorization Currency Code CL |
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 |
| ¦_ |
Country
|
Country code of the billing address. References: Charge Transaction.Country Code |
| ¦_ |
State
|
State of the billing address. References: Charge Transaction.State |
| ¦_ |
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 |
| ¦_ |
ZIP Code
|
ZIP/Postal code of the billing address. References: Charge Transaction.ZIP Code |
Account Info |
|
Includes general account information.
|
| ¦_ |
Account Type
|
Represents the type of the account (e.g. credit card or bank account) associated with the transaction. References: Charge Transaction.Account CL |
| ¦_ |
Token
|
Token that replaces account number for security purposes.
When Tokenization is enabled, each account number is replaced with a token value for persistence. Token code is automatically replaced with a real account number right before the data is sent to a Provider. The token is stored in its internal representation (value returned by an encryption appliance). When token is returned to a client/submitter, account type and last four digits are added to it. References: Charge Transaction.Token Code |
| ¦_ |
Bank Account #/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 |
| ¦_ |
Routing #/Exp Date
|
Masked version of the accessory (expiration date or routing number) associated with the transaction.
For expiration date, the mask is produced using last 2 digits (**12), for routing numbers the mask is produced using last 4 digits (****3452). References: Charge Transaction.Account Accessory Masked |
| ¦_ |
Holder Name
|
Name of the credit card holder. |
| ¦_ |
Holder Birthdate
|
Date of birth of the cardholder. References: Charge Transaction.Holder Birthdate |
Detail |
|
Includes detailed information about the transaction.
|
Details |
|
Includes transaction details.
|
| ¦_ |
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. |
| ¦_ |
Source
|
Represents the type of payment, which is used for the transaction. References: Charge Transaction.Account Source CL |
| ¦_ |
Status
|
Current status of the transaction. References: Transaction.Transaction Status Cl |
Card Entry Info |
|
Includes card entry information of the transaction.
|
| ¦_ |
Entry Mode
|
Represents current entry mode type. References: Charge Transaction.Entry Mode CL |
| ¦_ |
Entry Medium
|
Represents current entry medium type. References: Charge Transaction.Entry Medium CL |
| ¦_ |
Holder Verification Mode
|
Represents current type of holder verification mode. References: Charge Transaction.Holder Verification Mode Type CL |
Reference Info |
|
Includes reference information of the transaction.
|
| ¦_ |
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 |
| ¦_ |
Origin Code
|
The code of the original sub-batch transaction. References: Charge Transaction.Original Sub Batch 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 |
| ¦_ |
Ticket Number
|
Unique identifier of the ticket assigned by the gateway. References: Charge Transaction.Ticket Number |
| ¦_ |
User Code
|
This field is used to specify information about the user who created / canceled transaction. References: Charge Transaction.User Code |
Gateway Response |
|
Includes information on the response from the gateway.
|
| ¦_ |
Date
|
References: Charge Transaction.
|
| ¦_ |
Approval Code
|
Authorization code returned by a Provider that approved this transaction.
In some instances might also be used to store response code returned by Provider when transaction declines. References: Charge Transaction.Approval Code |
| ¦_ |
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
|
CVV2/CSC verification response code. References: Charge Transaction.CSC 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.
|
| ¦_ |
Processor
|
Processor of the transaction. |
| ¦_ |
Code
|
Response code returns by the underlying processor/bank. References: Charge Transaction.Provider Response Code |
| ¦_ |
Message
|
Message returned by Provider in response to this transaction. References: Charge Transaction.Provider Response Message |
| ¦_ |
CSC Code
|
Original provider's CSC Response Code. References: Charge Transaction.Provider CSC Response Code |
| ¦_ |
AVS Code
|
Original provider's AVS Response Code. References: Charge Transaction.Provider AVS Response Code |
Batch |
|
Includes values, associated with underlying batch file.
|
| ¦_ |
Batch Code
|
Code of the initial batch file. Reference to the entity that represents a group of batch transactions which must be settled together. References: Batch Transaction.Batch FK |
| ¦_ |
Sub Batch Code
|
Code of the sub-batch associated with the initial batch file. Reference to the entity that represents information about the associated sub-batch transaction. References: Batch Transaction.Sub Batch FK |
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 |
Memo |
|
Includes any additional information provided by the merchant.
|
Descriptor |
|
Includes values, associated with underlying merchant ID (or can be specified for each transaction processing).
|
| ¦_ |
Item
|
The number of items purchased. |
| ¦_ |
Merchant
|
The name of the merchant. |
3D Secure |
|
Includes information about 3D Secure authentication.
|
| ¦_ |
Authentication Status
|
Indicates the status of 3D Secure check. |
| ¦_ |
Authentication Code
|
The special 3D Secure authentication code received from a cardholder. |
| ¦_ |
Profile Code
|
Reference to the entity that represents 3D Secure profile. References: Authentication Three D Secure.Three D Secure Profile FK |
| ¦_ |
Acceptance Policy
|
Indicates whether transaction is going to be processed without 3D Secure verification or not, and on what conditions.
Possible values:
If one or more condition checkboxes are checked off, then transaction is going to be processed despite the specified condition. References: Authentication Three D Secure.Acceptance Policy |
| ¦_ |
View Logs
|
Allows to view list of 3D Secure logs for the selected transaction. |
3D Secure Logs List |
|
Includes information about 3D Secure logs associated with the selected transaction.
|
| ¦_ |
Close
|
Closes the form without saving any changes. |
| ¦_ |
Date
|
Date when the record was created. References: Three D Secure Log.Create Date |
| ¦_ |
Type
|
Type of the record. |
| ¦_ |
View Response Details
|
Allows to view response details of the selected 3D Secure log. |
Response Details |
|
Includes detailed information about 3D Secure logs.
|
| ¦_ |
Close
|
Closes the form without saving any changes. |
| ¦_ |
Host
|
URL address of the processed request. References: Three D Secure Log.Host |
| ¦_ |
Content
|
Parameters of the processed request. References: Three D Secure Log.Content |
|
View complete information
|
Allows to view complete BIN information of the selected transaction. |
|
BIN |
|
Includes general BIN information.
|
| ¦_ |
Range
|
Range of the issuer's bank identification number. |
| ¦_ |
PAN Length Min
|
Minimum length of the account number (PAN). References: Bank Identification Number.PAN Length Min |
| ¦_ |
PAN Length Max
|
Maximum length of the account number (PAN). References: Bank Identification Number.PAN Length Max |
| ¦_ |
Update Date
|
Update date of the bank identification number. References: Bank Identification Number.BIN Update Date |
| ¦_ |
BIN Code
|
Internal identifier associated with a BIN range that this bank belongs to. References: Bank Identification Number.Code |
Issuer Bank Info |
|
Includes information about issuer's bank.
|