PayeeTransaction: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
No edit summary
(removed mention of enabling Barion Bridge until the feature is released)
Line 23: Line 23:
* Must be the e-mail address of a valid Barion Wallet
* Must be the e-mail address of a valid Barion Wallet
* Maximum length: 256 characters
* Maximum length: 256 characters
|| The recipient's e-mail address. {{NotificationBox|title=Note|text=Payees other than the shop owner's Barion Wallet can only be listed if the shop has [[C2C_Payments|Barion Bridge]] enabled.|color=#1993c7}}
|| The recipient's e-mail address.
|-
|-
| Total || decimal ||  
| Total || decimal ||  

Revision as of 14:15, 15 April 2024

Payee transaction structure

This structure represents payee transaction included in a payment transaction. These are e-money sub-transactions that are executed after the payment was fully completed.

Payee transactions can be used to transfer royalties, agent fees or such to a third party, or to distribute the amount paid by the payer to multiple Barion wallets.

Included in

Payee transactions are used in the following structures:

Property list

Property name Property type Limitations and constraints Description
POSTransactionId string
  • Required
  • Maximum length: 100 characters
The unique identifier of the transaction at the shop that started the payment.
Payee string
  • Required
  • Must be the e-mail address of a valid Barion Wallet
  • Maximum length: 256 characters
The recipient's e-mail address.
Total decimal
  • Required
  • Must be greater than zero
  • Maximum value: the Total amount of the PaymentTransaction containing this PayeeTransaction
The total amount of the transaction.
Comment string
  • Optional
  • Maximum length: 640 characters
Comment of the transaction. This is shown to the recipient.