Statement-Download-v2: Difference between revisions
Jump to navigation
Jump to search
m (added note about the statement file language) |
m (changed transaction type link to localized file writeup) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 72: | Line 72: | ||
| Transaction time || The locale-specific-formatted date and time of the transaction.|| This column is also part of the monthly statement. | | Transaction time || The locale-specific-formatted date and time of the transaction.|| This column is also part of the monthly statement. | ||
|- | |- | ||
| Transaction type || [[ | | Transaction type || [[Localized_transaction_types|The type of the transaction]]. || This column is also part of the monthly statement. | ||
|- | |- | ||
| Customer/beneficiary || The identifier of the payee, payer, or payment method, as appropriate to the transaction: | | Customer/beneficiary || The identifier of the payee, payer, or payment method, as appropriate to the transaction: | ||
| Line 88: | Line 88: | ||
|Currency||The currency of the statement, as specified in the call to the endpoint. || This column is also part of the monthly statement. | |Currency||The currency of the statement, as specified in the call to the endpoint. || This column is also part of the monthly statement. | ||
|- | |- | ||
|Payment ID generated by shop||The identifier | |Payment ID generated by shop||The identifier for the payment generated by the webshop that requested it, if the entry is a payment and a webshop is involved. | ||
|- | |- | ||
|Transaction ID generated by shop||The identifier of the transaction generated by the webshop associated with it, if applicable. | |Transaction ID generated by shop||The identifier of the transaction generated by the webshop associated with it, if applicable. | ||
| Line 107: | Line 107: | ||
|Comment associated with transaction||Comments associated with the transaction. || Comments show up in the monthly statement in the "Other information" column. | |Comment associated with transaction||Comments associated with the transaction. || Comments show up in the monthly statement in the "Other information" column. | ||
|} | |} | ||
If the caller fails to authenticate, the API will produce an empty output with an <code>HTTP 401 Unauthorized</code> status code. | If the caller fails to authenticate, the API will produce an empty output with an <code>HTTP 401 Unauthorized</code> status code. | ||
Latest revision as of 14:40, 22 April 2024
Barion API: Download statement file
| GET | /v2/Statement/Download |
|---|
The /statement/download API endpoint is used to download monthly or daily statement files generated by the Barion system.
Prerequisites before use:
v2 This API endpoint is available in API v2 only.
Authentication
Input properties
| Property name | Property type | Limitations and constraints | Description |
|---|---|---|---|
| Year | int |
|
The statement year. |
| Month | int |
|
The statement month. |
| Day | int |
|
The statement day. If specified, the system will serve a daily statement file.
Otherwise, a monthly statement is returned. IMPORTANT
Daily statements are only available if you explicitly request them from Barion customer service – reach out using the Customer service tab online or the Other>Help screen in the Barion app.
|
| Currency | string |
Accepted values:
|
The currency of the statement's account. Accounts with separate currencies have separate statement files.
If the user doesn't have an account in the specified currency, the API returns an error message with an HTTP 400 Bad request status code. |
Output
Depending on whether a day parameter was passed, the endpoint responds with one of the following outputs:
- if a day parameter was passed, an .xlsx-format daily statement with an XML digital signature (signed by "Barion Payments Zrt", certified by an external issuer) to guarantee data integrity;
- if no day parameter was passed, a PDF-format monthly statement.
Note
Statement files are generated by the Barion back-end for each shop automatically, not in response to an API call. Further calls to the endpoint, even with a different currency parameter, won't generate a new statement.
Note
The statement file is generated in the Barion Wallet's currently active language.
| Column name | Description | Note |
|---|---|---|
| Transaction time | The locale-specific-formatted date and time of the transaction. | This column is also part of the monthly statement. |
| Transaction type | The type of the transaction. | This column is also part of the monthly statement. |
| Customer/beneficiary | The identifier of the payee, payer, or payment method, as appropriate to the transaction:
|
This column is also part of the monthly statement, as "Sender/Recipient". |
| Transaction amount | The locale-specific-formatted amount of the transaction. Deposits are positive, and withdrawals are negative. | This column is also part of the monthly statement. |
| Balance after transaction | The locale-specific-formatted balance of the Barion Wallet after the transaction. Note that reserved payments are immediately reflected in the payee's balance, even though the reserved funds aren't yet available until the payee completes the payment. For the currently actually available funds in a Barion Wallet, excluding pending reserved payments, see the Account/Available value returned by the Accounts endpoint. | This column is also part of the monthly statement. |
| Currency | The currency of the statement, as specified in the call to the endpoint. | This column is also part of the monthly statement. |
| Payment ID generated by shop | The identifier for the payment generated by the webshop that requested it, if the entry is a payment and a webshop is involved. | |
| Transaction ID generated by shop | The identifier of the transaction generated by the webshop associated with it, if applicable. | |
| Unique payment ID generated by Barion | Barion's GUID for the payment. | |
| Unique transaction ID generated by Barion | Barion's GUID for the transaction. | |
| Order ID generated by shop | The identifier generated by the webshop associated with the transaction, if applicable, to identify the order that the transaction was part of, if applicable. | |
| Card number | Last four digits of the debited or credited bank card.
Only applies to transactions credited to or debited from a bank card. |
Card numbers are included in the monthly statement in the "Other information" column. |
| Authorization code | The combination of letters and numbers that the card-issuing bank generates to indicate that the transfer of funds from the account associated with the card was successful.
Only applies to transactions credited to or debited from a bank card. | |
| Comment associated with transaction | Comments associated with the transaction. | Comments show up in the monthly statement in the "Other information" column. |
If the caller fails to authenticate, the API will produce an empty output with an HTTP 401 Unauthorized status code.
If the requested statement file is not available, the API returns an error message with an HTTP 404 Not found status code. This can happen if the requested statement file has not been generated yet.
If generation of the given statement type is disabled for the user, the API returns an error message with an HTTP 403 Forbidden status code.
Things to know
- To get daily statement files please contact Barion from the Customer Center in your Barion wallet.
- Daily statement files will not show up on the secure.barion.com site for download. They can only be downloaded via this API endpoint.
- Once the statement files have been generated, they are available to download for an indefinite time.
Examples
Downloading the daily statement of an EUR account for October 6th 2019:
https://api.barion.com/v2/statement/download?year=2019&month=10&day=6¤cy=EUR
Downloading the monthly statement of an HUF account for April 2019:
https://api.barion.com/v2/statement/download?year=2019&month=4¤cy=HUF