HistoryItemType: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 9: Line 9:
History item types are used in the following structures:
History item types are used in the following structures:
* [[UserHistory-GetHistory-v2]]
* [[UserHistory-GetHistory-v2]]
* [[UserHistory-GetHistory-v3]]
* [[TransactionHistory-GetDetail-v3]]


= Enum list =
= Enum list =
Line 61: Line 63:
|-
|-
| BankTransferPaymentFee || 24|| Barion fee. Paid after bank transfer payments.
| BankTransferPaymentFee || 24|| Barion fee. Paid after bank transfer payments.
|-
| BarionBalanceProcessingFee || 25 || Barion fee. This fee type is used when the payer paid with their Barion balance and the shop has been configured to pay this fee.
|-
|-
| Commission || 40|| Barion fee. It is a generic commission transaction. ''(deprecated)''
| Commission || 40|| Barion fee. It is a generic commission transaction. ''(deprecated)''

Latest revision as of 10:48, 11 July 2023

History item type enumeration

This enum indicates the type of history items.

IMPORTANT
The item type of history elements does not correlate with the type of transactions exported from GUI or downloaded from statement API.

Included in

History item types are used in the following structures:

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 source 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 Barion fee. Paid after withdrawal transactions.
RejectedWithdraw 19 Barion system has a complex withdrawal filtering system, which can decide to reject the withdrawal transaction.
RejectedWithdrawFee 20 If the withdrawal transaction was rejected the system does not deduct the withdrawal fee, it will be issued to the source account.
BankTransferPayment 21 A payment transaction can be completed with a wire transfer as well. This payment scenario is described here.
RefundToBankAccount 22 Bank transfer payments can also be refunded. In these cases, the Barion system initiates a wire transfer to the source bank account.
UnSuccessfulRefundToBankAccount 23 If a bank transfer payment refund is unsuccessful then the Barion system issues the amount of the transaction to the source account.
BankTransferPaymentFee 24 Barion fee. Paid after bank transfer payments.
BarionBalanceProcessingFee 25 Barion fee. This fee type is used when the payer paid with their Barion balance and the shop has been configured to pay this fee.
Commission 40 Barion fee. It is a generic commission transaction. (deprecated)
Donation 41 Donate a Barion Wallet with e-money. (deprecated)
UnderReview 42 Technical transaction initiated by Barion. If the transaction is risky or the Barion receives a chargeback inquiry from the acquirers the amount of the payment transaction will be blocked.
Release 43 When a risky payment transaction that is under review is clarified the Barion releases the amount of the transaction. Transactions can be released before deissuing as well.
Parking 100 Barion operates a parking service as well. Every Barion Wallet can use its e-money to pay the parking fee in Hungary.
AutomaticParking 101 Automatic parking service fee. (deprecated)

1 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 completion.