PayeeTransaction: Difference between revisions
Jump to navigation
Jump to search
(removed mention of enabling Barion Bridge until the feature is released) |
(Undo revision 4339 by [email protected] (talk)) Tag: Undo |
||
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. | || 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}} | ||
|- | |- | ||
| Total || decimal || | | Total || decimal || |
Latest revision as of 06:46, 24 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 |
|
The unique identifier of the transaction at the shop that started the payment. |
Payee | string |
|
The recipient's e-mail address. Note
Payees other than the shop owner's Barion Wallet can only be listed if the shop has Barion Bridge enabled.
|
Total | decimal |
|
The total amount of the transaction. |
Comment | string |
|
Comment of the transaction. This is shown to the recipient. |