Difference between revisions of "TransactionToFinish"

From Barion Documentation
Jump to navigation Jump to search
(Add Payment capture to API usage)
(Add Payment capture to API usage)
 
(No difference)

Latest revision as of 08:08, 14 October 2019

Payment transaction structure when finishing reservations

This structure represents a payment transaction related to a payment, when used for finishing pending reservations.

API usage

This structure is used by the following API endpoints:

Property list

Property name Property type Limitations and constraints Description
TransactionId guid
  • Required
The unique identifier of the transaction in the Barion system.
Total decimal
  • Required
  • Must be greater than zero
  • Decimal precision depends on payment curreny
The total amount of the transaction. This is the amount that is charged towards the payer when completing the payment. The final amount of the transactiom. This will overwrite the original amount.

The allowed number of decimal digits depends on the currency of the payment containing this transaction:

  • CZK: two digits
  • EUR: two digits
  • HUF: zero digits
  • USD: two digits
Comment string
  • Optional
A comment associated with the transaction. This is NOT shown to the payer. Description of the transaction, this will overwrite the original description
PayeeTransactions PayeeTransactionToFinish[]
  • Optional
An array containing the sub-transactions. You have to add all payee transaction which was in the original payment start request . See the PayeeTransactionToFinish page for structure and syntax.

These are NOT shown to the payer.

Items Item[]
  • Optional
An array containing the items (products or services) included in the transaction. See the Item page for structure and syntax. Items of the transaction. These will overwrite the original items

These are shown to the payer on the Barion Smart Gateway.