HistoryItemType

History item type enumeration

This enum indicates the type of history items.

Included in

History item types are used in the following structures:

• UserHistory-GetHistory-v2

Enum list

Enum value	Byte / int value	Description
InternalTransfer	1	Internal e-money transfer between Barion users.
InternalTransferToExternalUser	2	E-money transfer to a non-existent user. In this case, the recipient has a defined timeframe to get the amount of the transaction.
ElectronicPayment	3	The initialized payment transaction was paid with Barion Wallet. History items with this type can be reserved1 or successfully completed transactions.
CardPayment	4	The initialized payment transaction was paid with a bank card. History items with this type can be reserved1 or successfully completed transactions.
RefundToCard	5	Refund to a bank card after a completed payment transaction. In this case, the funding source of the payment is a bank card. Payment transactions of this type can be failed or successfully completed. Failed transactions are normalized, and the system initializes the refund process. In other cases, the refund was initiated through GUI or the API.
PayeeTransaction	6	If the integrated system works with complex payment scenarios, then one or more payee transactions can be defined for each payment transaction. More details of the Payee transactions can be found here.
GatewayFee	7	Barion fee. It belongs to a payment transaction.
CardProcessingFee	8	Barion fee. It belongs to a payment transaction.
CardTopUp	9	Top up a Barion account via bank card.
UnsuccessfulTransfer	10	When the recipient does not complete the transfer transaction, so the money did not receive by the recipient during the defined timeframe, the system handles it as an unsuccessful transaction.
WireTopUp	11	Top up a Barion account via wire transfer.
CashTopUp	12	Top up a Barion account via cash.
Withdraw	13	Wire transfer from a Barion account to a bank account.
UnsuccessfulWithdraw	14	Withdrawals can be unsuccessful for many reasons. If a withdrawal transaction cannot be completed successfully then the Barion system handles it and tops up the transaction amount to the account.
RefundToWallet	15	Payment transactions completed with Barion Wallet with e-money can be refunded to the wallet.
UnsuccessfulRefundToCard	16	Refund to bank card transactions can be unsuccessful for many reasons. Unsuccessful refund transactions are handled by the Barion system and their amount tops up to the source account.
IssueFromCustody	17	In some cases, the transaction amount may be moved to custody. If the participants can verify the transaction the Barion Team can issue the amount to the appropriate account.
WithdrawFee	18
RejectedWithdraw	19
RejectedWithdrawFee	20
BankTransferPayment	21
RefundToBankAccount	22
UnSuccessfulRefundToBankAccount	23
BankTransferPaymentFee	24
Commission	40
Donation	41
UnderReview	42
Release	43
Parking	100
AutomaticParking	101

¹ Reserved transactions are in progress, they are not finalized, and can be changed in the future. These transactions' amounts can be changed at the time of the completion.