<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.barion.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Birot</id>
	<title>Barion Documentation - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.barion.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Birot"/>
	<link rel="alternate" type="text/html" href="https://docs.barion.com/Special:Contributions/Birot"/>
	<updated>2026-11-21T04:21:50Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://docs.barion.com/index.php?title=Payment-Start-v2-old&amp;diff=1473</id>
		<title>Payment-Start-v2-old</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Payment-Start-v2-old&amp;diff=1473"/>
		<updated>2018-11-02T16:44:12Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Input properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: Initialize a new payment}}&lt;br /&gt;
&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;/payment/start&amp;lt;/code&amp;gt; API endpoint is used to create a new payment in the Barion system.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Creating_a_shop|Creating a shop in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; This API endpoint is available in &#039;&#039;&#039;API v2&#039;&#039;&#039; only.&lt;br /&gt;
&lt;br /&gt;
== Use cases ==&lt;br /&gt;
&lt;br /&gt;
This API endpoint is designed to be used in the following scenarios:&lt;br /&gt;
* [[Responsive_web_payment|Responsive Web Payment]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| POSKey || Guid || &lt;br /&gt;
* Required&lt;br /&gt;
|| The secret API key of the shop, generated by Barion. This lets the shop to authenticate through the Barion API, but does not provide access to the account owning the shop itself.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentType || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;Immediate&amp;quot;&lt;br /&gt;
** &amp;quot;Reservation&amp;quot;&lt;br /&gt;
|| The type of the payment, which can be either immediate or a money reservation. Reservation means that the shop has a time window to finish the payment (even though the money transaction still takes place immediately). Reservation amounts can be modified during this time window unless the new amount is lower than the original. &lt;br /&gt;
Click here to learn more about reservation payments: [[Reservation_payment|Reservation payments]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReservationPeriod || TimeSpan (d:hh:mm:ss) || &lt;br /&gt;
* Required only if PaymentType is &amp;quot;Reservation&amp;quot;&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: one year&lt;br /&gt;
* Default value: 30 minutes&lt;br /&gt;
|| Only makes sense at reservation payments. This is the time window that allows the shop to finish (finalize) the payment. If this does not happen within the time window, the system refunds the payment amount to the payer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentWindow || TimeSpan (d:hh:mm:ss) || &lt;br /&gt;
* Optional&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: one week&lt;br /&gt;
* Default value: 30 minutes&lt;br /&gt;
|| Time window for the payment to be completed. The payer must execute the payment before this elapses, or else the payment will expire and can no longer be completed.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| GuestCheckOut || bool || &lt;br /&gt;
* Required&lt;br /&gt;
* Value must be &amp;quot;true&amp;quot; or &amp;quot;false&amp;quot;, integer evaulation is not supported&lt;br /&gt;
|| Flag indicating wether the payment can be completed without a registered Barion wallet. Guest checkout can only be done with bank cards, and the payer must supply a valid e-mail address - this is necessary for fraud control.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| InitiateRecurrence || bool || &lt;br /&gt;
* Optional&lt;br /&gt;
|| This flag indicates that the shop would like to initialize a token payment. This means that the shop is authorized to charge the funding source of the payer in the future without redirecting her/him to the Barion Smart Gateway. It can be used for one-click and susbscription payment scenarios. &lt;br /&gt;
Click here to learn more about token payments: [[Token_payment]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceId || string || &lt;br /&gt;
* Required when executing authorized payments&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
* Must be unique per shop and per user&lt;br /&gt;
|| A string used to identify a given authorized payment. Its purpose is determined by the value of the &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; property.&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; is &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, this property must contain a &amp;lt;u&amp;gt;new&amp;lt;/u&amp;gt; desired identifier for a new authorized payment. This should be generated and stored by the shop before calling the API. Also the shop must ensure that this is unique per user in its own system.&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; is &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;, this property must contain an &amp;lt;u&amp;gt;existing&amp;lt;/u&amp;gt; identifier for an authorized payment. This should be used to charge a payer&#039;s funding source (either bank card or Barion wallet) that was already used successfully for a payment in the shop.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| FundingSources || string[] || &lt;br /&gt;
* Required&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;All&amp;quot;&lt;br /&gt;
** &amp;quot;Balance&amp;quot;&lt;br /&gt;
|| An array of strings containing the allowed funding sources that can be used to complete the payment. &amp;quot;Balance&amp;quot; means that the payer can only use their Barion wallet balance, while &amp;quot;All&amp;quot; means the payment can be completed with either a Barion wallet or a bank card.&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; There is no option to disallow payment by balance, since that would deny Barion Wallet users with a balance the ability to pay. There is an option to exclude cards, but not balance.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this must be supplied as an array, because more funding source types are planned in the future.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentRequestId || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The unique identifier for the payment generated by the shop. This is so the shop can track its own payment identifiers. It is also useful for bookkeeping purposes since this shows up in the monthly account statement and the transaction history export, making identification of payments easier for the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PayerHint || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 256 characters&lt;br /&gt;
|| The shop can optionally supply an e-mail address as a hint on who should complete the payment. This can be used if the shop is certain about that the payer has an active Barion wallet. If provided, the Barion Smart Gateway automatically fills out the e-mail address field in the Barion wallet login form, speeding up the payment process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the payer should be redirected after the payment is completed or cancelled. The payment identifier is added to the query string part of this URL in the &amp;lt;code&amp;gt;PaymentId&amp;lt;/code&amp;gt; parameter. If not provided, the system will use the redirect URL assigned to the shop that started the payment.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallbackUrl || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the Barion system sends a request whenever there is a change in the state of the payment. The payment identifier is added to the query string part of this URL in the &amp;lt;code&amp;gt;PaymentId&amp;lt;/code&amp;gt; parameter. If not provided, the system will use the callback URL assigned to the shop that started the payment. Click here to learn more about the callback mechanism: [[Callback_mechanism|Payment callback mechanism (IPN)]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Transactions || [[PaymentTransaction]][] || &lt;br /&gt;
* Required&lt;br /&gt;
|| An array of payment transactions contained in the payment. A payment must contain at least one such transaction. See the [[PaymentTransaction]] page for the appropriate structure and syntax.&lt;br /&gt;
Defining multiple transactions allow the payment initiator to distribute the payment amount between multiple shops. See the following page to learn more: [[Facilitated payments]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| OrderNumber || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The order number generated by the shop. This is to aid the shop in identifying a given payment in their own system. This also shows up in generated monthly account statements and transaction history exports, so it also helps with bookkeeping.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShippingAddress || [[ShippingAddress]] || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The shipping address associated with the payment, if applicable. Providing this is recommended, because it helps the automatic anti-fraud analysis get more accurate results. See the [[ShippingAddress]] page for the appropriate structure and syntax.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Locale || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 10 characters&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;cs-CZ&amp;quot; (Czech)&lt;br /&gt;
** &amp;quot;de-DE&amp;quot; (German)&lt;br /&gt;
** &amp;quot;en-US&amp;quot; (English)&lt;br /&gt;
** &amp;quot;es-ES&amp;quot; (Spanish)&lt;br /&gt;
** &amp;quot;fr-FR&amp;quot; (French)&lt;br /&gt;
** &amp;quot;hu-HU&amp;quot; (Hungarian)&lt;br /&gt;
** &amp;quot;sk-SK&amp;quot; (Slovakian)&lt;br /&gt;
** &amp;quot;sl-SI&amp;quot; (Slovenian)&lt;br /&gt;
|| This indicates in which language the Barion Smart Gateway should display for the payer upon redirect. &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Currency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Required length: 3 characters&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;CZK&amp;quot; (Czech crown)&lt;br /&gt;
** &amp;quot;EUR&amp;quot; (Euro)&lt;br /&gt;
** &amp;quot;HUF&amp;quot; (Hungarian forint)&lt;br /&gt;
** &amp;quot;USD&amp;quot; (U.S. dollar)&lt;br /&gt;
|| The currency of the payment. Must be supplied in ISO 4217 format. This affects all transactions included in the payment; it is not possible to define multiple transactions in different currencies.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Output properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId || Guid || The identifier of the newly initialized payment, generated by the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentRequestId || string || The payment identifier supplied by the API caller in the request.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || [[PaymentStatus]]|| The status of the payment in the Barion system. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| QRUrl || string || URL for a QR code representing the payment. This is useful in physical real life situations where the payer uses a mobile device.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceResult || RecurrenceResult || Indicates the result of an authorized payment scenario. The result depends on the values of the &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; and &#039;&#039;&#039;RecurrenceId&#039;&#039;&#039; properties supplied in the request.&lt;br /&gt;
&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; was &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, and a new authorized payment was successfully created, this will be &amp;lt;code&amp;gt;None&amp;lt;/code&amp;gt; (because no actual token charge took place yet)&lt;br /&gt;
&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; was &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;, but a previously authorized payment identifier was supplied in &#039;&#039;&#039;RecurrenceId&#039;&#039;&#039;, the system will try to charge the funding source associated with the authorized payment. If this charge is successful, the result is &amp;lt;code&amp;gt;Successful&amp;lt;/code&amp;gt;. If the system could not charge the funding srouce, the result is &amp;lt;code&amp;gt;Failed&amp;lt;/code&amp;gt;. If the given identifier is invalid or does not exist, the result is &amp;lt;code&amp;gt;NotFound&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Transactions || [[ProcessedTransaction]][] || An array containing all transactions associated with the payment. If the Barion system deducts fees from the shop after payments, this also contains these additional fee transactions beside the payment transactions that were sent in the request.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| GatewayUrl || string || The URL of the Barion Smart Gateway (including the payment identifier), where the API caller should redirect the payer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallbackUrl || string || The URL (including the payment identifier) where the Barion system will send a request to whenever there is a change in the state of the payment. If an explicit URL was not supplied, this will be the callback URL associated with the shop that started the payment.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string|| The URL (including the payment identifier) where the payer gets redirected to after the payment is completed or cancelled. If an explicit URL was not supplied, this will be the redirect URL associated with the shop that started the payment.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Payment-Start-v2-old&amp;diff=1472</id>
		<title>Payment-Start-v2-old</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Payment-Start-v2-old&amp;diff=1472"/>
		<updated>2018-11-02T16:43:14Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Input properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: Initialize a new payment}}&lt;br /&gt;
&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;/payment/start&amp;lt;/code&amp;gt; API endpoint is used to create a new payment in the Barion system.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Creating_a_shop|Creating a shop in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; This API endpoint is available in &#039;&#039;&#039;API v2&#039;&#039;&#039; only.&lt;br /&gt;
&lt;br /&gt;
== Use cases ==&lt;br /&gt;
&lt;br /&gt;
This API endpoint is designed to be used in the following scenarios:&lt;br /&gt;
* [[Responsive_web_payment|Responsive Web Payment]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| POSKey || Guid || &lt;br /&gt;
* Required&lt;br /&gt;
|| The secret API key of the shop, generated by Barion. This lets the shop to authenticate through the Barion API, but does not provide access to the account owning the shop itself.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentType || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;Immediate&amp;quot;&lt;br /&gt;
** &amp;quot;Reservation&amp;quot;&lt;br /&gt;
|| The type of the payment, which can be either immediate or a money reservation. Reservation means that the shop has a time window to finish the payment (even though the money transaction still takes place immediately). Reservation amounts can be modified during this time window unless the new amount is lower than the original. &lt;br /&gt;
Click here to learn more about reservation payments: [[Reservation_payment|Reservation payments]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReservationPeriod || TimeSpan (d:hh:mm:ss) || &lt;br /&gt;
* Required only if PaymentType is &amp;quot;Reservation&amp;quot;&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: one year&lt;br /&gt;
* Default value: 30 minutes&lt;br /&gt;
|| Only makes sense at reservation payments. This is the time window that allows the shop to finish (finalize) the payment. If this does not happen within the time window, the system refunds the payment amount to the payer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentWindow || TimeSpan (d:hh:mm:ss) || &lt;br /&gt;
* Optional&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: one week&lt;br /&gt;
* Default value: 30 minutes&lt;br /&gt;
|| Time window for the payment to be completed. The payer must execute the payment before this elapses, or else the payment will expire and can no longer be completed.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| GuestCheckOut || bool || &lt;br /&gt;
* Required&lt;br /&gt;
* Value must be &amp;quot;true&amp;quot; or &amp;quot;false&amp;quot;, integer evaulation is not supported&lt;br /&gt;
|| Flag indicating wether the payment can be completed without a registered Barion wallet. Guest checkout can only be done with bank cards, and the payer must supply a valid e-mail address - this is necessary for fraud control.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| InitiateRecurrence || bool || &lt;br /&gt;
* Optional&lt;br /&gt;
|| This flag indicates that the shop would like to initialize a token payment. This means that the shop is authorized to charge the funding source of the payer in the future without redirecting her/him to the Barion Smart Gateway. It can be used for one-click and susbscription payment scenarios. &lt;br /&gt;
Click here to learn more about token payments: [[Token_payment]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceId || string || &lt;br /&gt;
* Required when executing authorized payments&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
* Must be unique per shop and per user&lt;br /&gt;
|| A string used to identify a given authorized payment. Its purpose is determined by the value of the &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; property.&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; is &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, this property must contain a &amp;lt;u&amp;gt;new&amp;lt;/u&amp;gt; desired identifier for a new authorized payment. This should be generated and stored by the shop before calling the API. Also the shop must ensure that this is unique per user in its own system.&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; is &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;, this property must contain an &amp;lt;u&amp;gt;existing&amp;lt;/u&amp;gt; identifier for an authorized payment. This should be used to charge a payer&#039;s funding source (either bank card or Barion wallet) that was already used successfully for a payment in the shop.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| FundingSources || string[] || &lt;br /&gt;
* Required&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;All&amp;quot;&lt;br /&gt;
** &amp;quot;Balance&amp;quot;&lt;br /&gt;
|| An array of strings containing the allowed funding sources that can be used to complete the payment. &amp;quot;Balance&amp;quot; means that the payer can only use their Barion wallet balance, while &amp;quot;All&amp;quot; means the payment can be completed with either a Barion wallet or a bank card.&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; There is no option to disallow payment by balance, since that would deny Barion Wallet users with a balance the ability to pay. There is an option to exclude cards, but not balance.&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this must be supplied as an array, because more funding source types are planned in the future.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentRequestId || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The unique identifier for the payment generated by the shop. This is so the shop can track its own payment identifiers. It is also useful for bookkeeping purposes since this shows up in the monthly account statement and the transaction history export, making identification of payments easier for the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PayerHint || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 256 characters&lt;br /&gt;
|| The shop can optionally supply an e-mail address as a hint on who should complete the payment. This can be used if the shop is certain about that the payer has an active Barion wallet. If provided, the Barion Smart Gateway automatically fills out the e-mail address field in the Barion wallet login form, speeding up the payment process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the payer should be redirected after the payment is completed or cancelled. The payment identifier is added to the query string part of this URL in the &amp;lt;code&amp;gt;PaymentId&amp;lt;/code&amp;gt; parameter. If not provided, the system will use the redirect URL assigned to the shop that started the payment.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallbackUrl || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the Barion system sends a request whenever there is a change in the state of the payment. The payment identifier is added to the query string part of this URL in the &amp;lt;code&amp;gt;PaymentId&amp;lt;/code&amp;gt; parameter. If not provided, the system will use the callback URL assigned to the shop that started the payment. Click here to learn more about the callback mechanism: [[Callback_mechanism|Payment callback mechanism (IPN)]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Transactions || [[PaymentTransaction]][] || &lt;br /&gt;
* Required&lt;br /&gt;
|| An array of payment transactions contained in the payment. A payment must contain at least one such transaction. See the [[PaymentTransaction]] page for the appropriate structure and syntax.&lt;br /&gt;
Defining multiple transactions allow the payment initiator to distribute the payment amount between multiple shops. See the following page to learn more: [[Facilitated payments]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| OrderNumber || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The order number generated by the shop. This is to aid the shop in identifying a given payment in their own system. This also shows up in generated monthly account statements and transaction history exports, so it also helps with bookkeeping.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShippingAddress || [[ShippingAddress]] || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The shipping address associated with the payment, if applicable. Providing this is recommended, because it helps the automatic anti-fraud analysis get more accurate results. See the [[ShippingAddress]] page for the appropriate structure and syntax.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Locale || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 10 characters&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;cs-CZ&amp;quot; (Czech)&lt;br /&gt;
** &amp;quot;de-DE&amp;quot; (German)&lt;br /&gt;
** &amp;quot;en-US&amp;quot; (English)&lt;br /&gt;
** &amp;quot;es-ES&amp;quot; (Spanish)&lt;br /&gt;
** &amp;quot;fr-FR&amp;quot; (French)&lt;br /&gt;
** &amp;quot;hu-HU&amp;quot; (Hungarian)&lt;br /&gt;
** &amp;quot;sk-SK&amp;quot; (Slovakian)&lt;br /&gt;
** &amp;quot;sl-SI&amp;quot; (Slovenian)&lt;br /&gt;
|| This indicates in which language the Barion Smart Gateway should display for the payer upon redirect. &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Currency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Required length: 3 characters&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;CZK&amp;quot; (Czech crown)&lt;br /&gt;
** &amp;quot;EUR&amp;quot; (Euro)&lt;br /&gt;
** &amp;quot;HUF&amp;quot; (Hungarian forint)&lt;br /&gt;
** &amp;quot;USD&amp;quot; (U.S. dollar)&lt;br /&gt;
|| The currency of the payment. Must be supplied in ISO 4217 format. This affects all transactions included in the payment; it is not possible to define multiple transactions in different currencies.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Output properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId || Guid || The identifier of the newly initialized payment, generated by the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentRequestId || string || The payment identifier supplied by the API caller in the request.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || [[PaymentStatus]]|| The status of the payment in the Barion system. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| QRUrl || string || URL for a QR code representing the payment. This is useful in physical real life situations where the payer uses a mobile device.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceResult || RecurrenceResult || Indicates the result of an authorized payment scenario. The result depends on the values of the &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; and &#039;&#039;&#039;RecurrenceId&#039;&#039;&#039; properties supplied in the request.&lt;br /&gt;
&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; was &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, and a new authorized payment was successfully created, this will be &amp;lt;code&amp;gt;None&amp;lt;/code&amp;gt; (because no actual token charge took place yet)&lt;br /&gt;
&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; was &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;, but a previously authorized payment identifier was supplied in &#039;&#039;&#039;RecurrenceId&#039;&#039;&#039;, the system will try to charge the funding source associated with the authorized payment. If this charge is successful, the result is &amp;lt;code&amp;gt;Successful&amp;lt;/code&amp;gt;. If the system could not charge the funding srouce, the result is &amp;lt;code&amp;gt;Failed&amp;lt;/code&amp;gt;. If the given identifier is invalid or does not exist, the result is &amp;lt;code&amp;gt;NotFound&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Transactions || [[ProcessedTransaction]][] || An array containing all transactions associated with the payment. If the Barion system deducts fees from the shop after payments, this also contains these additional fee transactions beside the payment transactions that were sent in the request.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| GatewayUrl || string || The URL of the Barion Smart Gateway (including the payment identifier), where the API caller should redirect the payer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallbackUrl || string || The URL (including the payment identifier) where the Barion system will send a request to whenever there is a change in the state of the payment. If an explicit URL was not supplied, this will be the callback URL associated with the shop that started the payment.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string|| The URL (including the payment identifier) where the payer gets redirected to after the payment is completed or cancelled. If an explicit URL was not supplied, this will be the redirect URL associated with the shop that started the payment.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=1465</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=1465"/>
		<updated>2018-08-25T12:01:38Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Downloadable plugins, libraries and source code}} &lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot; | __TOC__ |}&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
!Partner&lt;br /&gt;
!URL&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| Open source PHP library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-android-java-app2app&lt;br /&gt;
| Open source Android Java library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-ios-objc-app2app&lt;br /&gt;
| Open source iOS Objective C library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| Open source .NET library&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Open source Wordpress WooCommerce plugin. Training video in Hungarian: https://www.youtube.com/watch?v=Rdrt8eHkmWU&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Free Magento plugin (current version works with HUF only)&lt;br /&gt;
|-&lt;br /&gt;
| VIP partner: Transgate&lt;br /&gt;
| http://bankkartyas-fizetes.hu/index.php?page=barion&lt;br /&gt;
| Commercial plugins for diffrent e-commerce platforms. Charities, subscriptions, event registration solutions. Free trial versions for all plugins. Installation and tech support available at decent pricing. Supported systems: WooCommerce, OpenCart, Virtuemart, HikaShop, Magento Commerce, PrestaShop, Drupal Commerce, CS-Cart. Training video in Hungarian: https://www.youtube.com/watch?v=VAedWvognHw&lt;br /&gt;
|-&lt;br /&gt;
| Franco-Soft&lt;br /&gt;
| https://franco-soft.com/point&lt;br /&gt;
| Plugin based general payment solution and custom integration.&lt;br /&gt;
|-&lt;br /&gt;
| Portum lines&lt;br /&gt;
| http://portumlines.hu/termek/portum-barion-payment-plugin-woocommerce/&lt;br /&gt;
| WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| Galocaffe&lt;br /&gt;
| http://www.galocaffe.com/&lt;br /&gt;
| Custom integration of Barion&lt;br /&gt;
|-&lt;br /&gt;
| Vizmeg Viktor&lt;br /&gt;
| https://addons.prestashop.com/en/payment-card-wallet/23723-barion-online-credit-card-payment.html&lt;br /&gt;
| Official PrestaShop Addons marketplace certified and recommended Barion plugin for Presta Shop &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=1464</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=1464"/>
		<updated>2018-08-25T11:54:50Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Downloadable plugins, libraries and source code}} &lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot; | __TOC__ |}&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
!Partner&lt;br /&gt;
!URL&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| Open source PHP library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-android-java-app2app&lt;br /&gt;
| Open source Android Java library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-ios-objc-app2app&lt;br /&gt;
| Open source iOS Objective C library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| Open source .NET library&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Open source Wordpress WooCommerce plugin. Training video in Hungarian: https://www.youtube.com/watch?v=Rdrt8eHkmWU&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Free Magento plugin (current version works with HUF only)&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| PHP Library Barion integrációhoz&lt;br /&gt;
|-&lt;br /&gt;
| Kiemelt Partnerünk: Transgate&lt;br /&gt;
| http://bankkartyas-fizetes.hu/index.php?page=barion&lt;br /&gt;
| Díjmentesen tesztelhető modulok tucatnyi nyílt forrású webshop szoftverhez, egyedi fejlesztések, fizetés nem csak webáruháznak, pl adakozás, előfizetések, rendezvény regisztráció, stb. Kiemelt támogatású rendszerek: WooCommerce, OpenCart, Virtuemart, HikaShop, Magento Commerce, PrestaShop, Drupal Commerce, CS-Cart. Oktató videó: https://www.youtube.com/watch?v=VAedWvognHw&lt;br /&gt;
|-&lt;br /&gt;
| Franco-Soft&lt;br /&gt;
| https://franco-soft.com/point&lt;br /&gt;
| Saját weboldalba illeszthető, paraméterezhető általános fizetési megoldások és egyedi integrációk megvalósítása&lt;br /&gt;
|-&lt;br /&gt;
| Portum lines&lt;br /&gt;
| http://portumlines.hu/termek/portum-barion-payment-plugin-woocommerce/&lt;br /&gt;
| Portum – Barion fizetés WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| Galocaffe&lt;br /&gt;
| http://www.galocaffe.com/&lt;br /&gt;
| Egyedi integrációs igények kielégítése&lt;br /&gt;
|-&lt;br /&gt;
| Vizmeg Viktor&lt;br /&gt;
| https://addons.prestashop.com/en/payment-card-wallet/23723-barion-online-credit-card-payment.html&lt;br /&gt;
| A hivatalos PrestaShop Addons moduláruház által ellenőrzött és ajánlott Barion kiterjesztés PrestaShop rendszerhez.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=1463</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=1463"/>
		<updated>2018-08-25T11:53:51Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Downloadable resources – libraries and source code}} &lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot; | __TOC__ |}&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
!Partner&lt;br /&gt;
!URL&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| Open source PHP library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-android-java-app2app&lt;br /&gt;
| Open source Android Java library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-ios-objc-app2app&lt;br /&gt;
| Open source iOS Objective C library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| Open source .NET library&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Open source Wordpress WooCommerce plugin. Training video in Hungarian: https://www.youtube.com/watch?v=Rdrt8eHkmWU&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Free Magento plugin (current version works with HUF only)&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| PHP Library Barion integrációhoz&lt;br /&gt;
|-&lt;br /&gt;
| Kiemelt Partnerünk: Transgate&lt;br /&gt;
| http://bankkartyas-fizetes.hu/index.php?page=barion&lt;br /&gt;
| Díjmentesen tesztelhető modulok tucatnyi nyílt forrású webshop szoftverhez, egyedi fejlesztések, fizetés nem csak webáruháznak, pl adakozás, előfizetések, rendezvény regisztráció, stb. Kiemelt támogatású rendszerek: WooCommerce, OpenCart, Virtuemart, HikaShop, Magento Commerce, PrestaShop, Drupal Commerce, CS-Cart. Oktató videó: https://www.youtube.com/watch?v=VAedWvognHw&lt;br /&gt;
|-&lt;br /&gt;
| Franco-Soft&lt;br /&gt;
| https://franco-soft.com/point&lt;br /&gt;
| Saját weboldalba illeszthető, paraméterezhető általános fizetési megoldások és egyedi integrációk megvalósítása&lt;br /&gt;
|-&lt;br /&gt;
| Portum lines&lt;br /&gt;
| http://portumlines.hu/termek/portum-barion-payment-plugin-woocommerce/&lt;br /&gt;
| Portum – Barion fizetés WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| Galocaffe&lt;br /&gt;
| http://www.galocaffe.com/&lt;br /&gt;
| Egyedi integrációs igények kielégítése&lt;br /&gt;
|-&lt;br /&gt;
| Vizmeg Viktor&lt;br /&gt;
| https://addons.prestashop.com/en/payment-card-wallet/23723-barion-online-credit-card-payment.html&lt;br /&gt;
| A hivatalos PrestaShop Addons moduláruház által ellenőrzött és ajánlott Barion kiterjesztés PrestaShop rendszerhez.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=1462</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=1462"/>
		<updated>2018-08-25T11:51:33Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Downloadable resources – libraries and source code}} &lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot; | __TOC__ |}&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
!Partner&lt;br /&gt;
!URL&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| Open source PHP library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-android-java-app2app&lt;br /&gt;
| Open source Android Java library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-ios-objc-app2app&lt;br /&gt;
| Open source iOS Objective C library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| Open source .NET library&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Open source Wordpress WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Free Magento plugin (current version works with HUF only)&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| PHP Library Barion integrációhoz&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| .NET Library Barion integrációhoz &lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Woocommerce nyílt forráskódú, ingyenes modul. Oktató videó: https://www.youtube.com/watch?v=Rdrt8eHkmWU&lt;br /&gt;
|-&lt;br /&gt;
| Kiemelt Partnerünk: Transgate&lt;br /&gt;
| http://bankkartyas-fizetes.hu/index.php?page=barion&lt;br /&gt;
| Díjmentesen tesztelhető modulok tucatnyi nyílt forrású webshop szoftverhez, egyedi fejlesztések, fizetés nem csak webáruháznak, pl adakozás, előfizetések, rendezvény regisztráció, stb. Kiemelt támogatású rendszerek: WooCommerce, OpenCart, Virtuemart, HikaShop, Magento Commerce, PrestaShop, Drupal Commerce, CS-Cart. Oktató videó: https://www.youtube.com/watch?v=VAedWvognHw&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Ingyenes modul Magento rendszerhez&lt;br /&gt;
|-&lt;br /&gt;
| Franco-Soft&lt;br /&gt;
| https://franco-soft.com/point&lt;br /&gt;
| Saját weboldalba illeszthető, paraméterezhető általános fizetési megoldások és egyedi integrációk megvalósítása&lt;br /&gt;
|-&lt;br /&gt;
| Portum lines&lt;br /&gt;
| http://portumlines.hu/termek/portum-barion-payment-plugin-woocommerce/&lt;br /&gt;
| Portum – Barion fizetés WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| Galocaffe&lt;br /&gt;
| http://www.galocaffe.com/&lt;br /&gt;
| Egyedi integrációs igények kielégítése&lt;br /&gt;
|-&lt;br /&gt;
| Vizmeg Viktor&lt;br /&gt;
| https://addons.prestashop.com/en/payment-card-wallet/23723-barion-online-credit-card-payment.html&lt;br /&gt;
| A hivatalos PrestaShop Addons moduláruház által ellenőrzött és ajánlott Barion kiterjesztés PrestaShop rendszerhez.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=1461</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=1461"/>
		<updated>2018-08-25T11:51:15Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Downloadable resources – libraries and source code}} &lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot; | __TOC__ |}&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!Partner&lt;br /&gt;
!URL&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| Open source PHP library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-android-java-app2app&lt;br /&gt;
| Open source Android Java library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-ios-objc-app2app&lt;br /&gt;
| Open source iOS Objective C library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| Open source .NET library&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Open source Wordpress WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Free Magento plugin (current version works with HUF only)&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| PHP Library Barion integrációhoz&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| .NET Library Barion integrációhoz &lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Woocommerce nyílt forráskódú, ingyenes modul. Oktató videó: https://www.youtube.com/watch?v=Rdrt8eHkmWU&lt;br /&gt;
|-&lt;br /&gt;
| Kiemelt Partnerünk: Transgate&lt;br /&gt;
| http://bankkartyas-fizetes.hu/index.php?page=barion&lt;br /&gt;
| Díjmentesen tesztelhető modulok tucatnyi nyílt forrású webshop szoftverhez, egyedi fejlesztések, fizetés nem csak webáruháznak, pl adakozás, előfizetések, rendezvény regisztráció, stb. Kiemelt támogatású rendszerek: WooCommerce, OpenCart, Virtuemart, HikaShop, Magento Commerce, PrestaShop, Drupal Commerce, CS-Cart. Oktató videó: https://www.youtube.com/watch?v=VAedWvognHw&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Ingyenes modul Magento rendszerhez&lt;br /&gt;
|-&lt;br /&gt;
| Franco-Soft&lt;br /&gt;
| https://franco-soft.com/point&lt;br /&gt;
| Saját weboldalba illeszthető, paraméterezhető általános fizetési megoldások és egyedi integrációk megvalósítása&lt;br /&gt;
|-&lt;br /&gt;
| Portum lines&lt;br /&gt;
| http://portumlines.hu/termek/portum-barion-payment-plugin-woocommerce/&lt;br /&gt;
| Portum – Barion fizetés WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| Galocaffe&lt;br /&gt;
| http://www.galocaffe.com/&lt;br /&gt;
| Egyedi integrációs igények kielégítése&lt;br /&gt;
|-&lt;br /&gt;
| Vizmeg Viktor&lt;br /&gt;
| https://addons.prestashop.com/en/payment-card-wallet/23723-barion-online-credit-card-payment.html&lt;br /&gt;
| A hivatalos PrestaShop Addons moduláruház által ellenőrzött és ajánlott Barion kiterjesztés PrestaShop rendszerhez.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=1460</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=1460"/>
		<updated>2018-08-25T11:50:53Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Downloadable resources – libraries and source code}} &lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot; | __TOC__ |}&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!Partner&lt;br /&gt;
!URL&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| Open source PHP library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-android-java-app2app&lt;br /&gt;
| Open source Android Java library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-ios-objc-app2app&lt;br /&gt;
| Open source iOS Objective C library and sample code&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| Open source .NET library&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Open source Wordpress WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Free Magento plugin (current version works with HUF only)&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot;|rules=rows class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!Szolgáltató&lt;br /&gt;
!Weboldal&lt;br /&gt;
!Leírás&lt;br /&gt;
|-&lt;br /&gt;
| Barion&lt;br /&gt;
| https://github.com/barion/barion-web-php&lt;br /&gt;
| PHP Library Barion integrációhoz&lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://github.com/szelpe/barion-dotnet&lt;br /&gt;
| .NET Library Barion integrációhoz &lt;br /&gt;
|-&lt;br /&gt;
| Szél Péter&lt;br /&gt;
| https://wordpress.org/plugins/pay-via-barion-for-woocommerce/&lt;br /&gt;
| Woocommerce nyílt forráskódú, ingyenes modul. Oktató videó: https://www.youtube.com/watch?v=Rdrt8eHkmWU&lt;br /&gt;
|-&lt;br /&gt;
| Kiemelt Partnerünk: Transgate&lt;br /&gt;
| http://bankkartyas-fizetes.hu/index.php?page=barion&lt;br /&gt;
| Díjmentesen tesztelhető modulok tucatnyi nyílt forrású webshop szoftverhez, egyedi fejlesztések, fizetés nem csak webáruháznak, pl adakozás, előfizetések, rendezvény regisztráció, stb. Kiemelt támogatású rendszerek: WooCommerce, OpenCart, Virtuemart, HikaShop, Magento Commerce, PrestaShop, Drupal Commerce, CS-Cart. Oktató videó: https://www.youtube.com/watch?v=VAedWvognHw&lt;br /&gt;
|-&lt;br /&gt;
| TLSoft&lt;br /&gt;
| http://www.magentocommerce.com/magento-connect/barion-payment-gateway.html&lt;br /&gt;
| Ingyenes modul Magento rendszerhez&lt;br /&gt;
|-&lt;br /&gt;
| Franco-Soft&lt;br /&gt;
| https://franco-soft.com/point&lt;br /&gt;
| Saját weboldalba illeszthető, paraméterezhető általános fizetési megoldások és egyedi integrációk megvalósítása&lt;br /&gt;
|-&lt;br /&gt;
| Portum lines&lt;br /&gt;
| http://portumlines.hu/termek/portum-barion-payment-plugin-woocommerce/&lt;br /&gt;
| Portum – Barion fizetés WooCommerce plugin&lt;br /&gt;
|-&lt;br /&gt;
| Galocaffe&lt;br /&gt;
| http://www.galocaffe.com/&lt;br /&gt;
| Egyedi integrációs igények kielégítése&lt;br /&gt;
|-&lt;br /&gt;
| Vizmeg Viktor&lt;br /&gt;
| https://addons.prestashop.com/en/payment-card-wallet/23723-barion-online-credit-card-payment.html&lt;br /&gt;
| A hivatalos PrestaShop Addons moduláruház által ellenőrzött és ajánlott Barion kiterjesztés PrestaShop rendszerhez.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1438</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1438"/>
		<updated>2018-08-07T15:39:51Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 was switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Template:Api_input_table_header&amp;diff=1437</id>
		<title>Template:Api input table header</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Template:Api_input_table_header&amp;diff=1437"/>
		<updated>2018-07-23T10:38:32Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Limitations and constraints&lt;br /&gt;
!Description&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Template:Api_input_table_header&amp;diff=1436</id>
		<title>Template:Api input table header</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Template:Api_input_table_header&amp;diff=1436"/>
		<updated>2018-07-23T10:38:02Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable sortable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Limitations and constraints&lt;br /&gt;
!Description&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=1435</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=1435"/>
		<updated>2018-07-18T12:53:33Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Security */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Going live}}&lt;br /&gt;
&lt;br /&gt;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] in an online registration. Na paperwork or hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register on the live Barion server at https://secure.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
See alse:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, it is easy to mix up live and sandbox accounts! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. Only shops that are legal and comply with our [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] are allowed. Barion does not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, consult our [https://www.barion.com/en/merchants/ experts] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you will be asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you will be asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payment must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://www.barion.com/en/merchants/ experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
To go live, the following changes must be made in the payment solution. We advise to make these parameters, so you can easily switch between the sandbox and live servers.&lt;br /&gt;
*API endpoint URL must be changed to live (https://api.test.barion.com -&amp;gt; https://api.barion.com)&lt;br /&gt;
*Payment GUI redirect URL must be changes to live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay)&lt;br /&gt;
*POSKey must be changed to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here)&lt;br /&gt;
*Return URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*Callback URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*E-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;-s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if different in sandbox&lt;br /&gt;
*Certificates, if checking server certificates&lt;br /&gt;
*If using token payment, sandbox Tokens will not work in the live system&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your choosen price package. Please refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps placement. Please follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-card-payment-banner-2016-432x50px.png]]&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-smart-payment-banners.zip]]&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff will check it and will only approve shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Please refer to [[Support|Getting support]] for more information.&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Current limitations of the live Barion system:&lt;br /&gt;
*Reservation and 3rd party payment only works with HUF currency&lt;br /&gt;
*Barion Mobile App only shows HUF transactions&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=These limitations are planned to be lifted in Q4 2017.|color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Security_Measures&amp;diff=1434</id>
		<title>Security Measures</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Security_Measures&amp;diff=1434"/>
		<updated>2018-07-18T12:52:36Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Encryption */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Security Measures}}&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
This page lists different measures we take to maintain security and service levels. Please read carefully and follow the instructions, especially where changes may happen any time. If you do not update your settings when a change occurs, you might risk your Barion implementation&#039;s ability to work properly or at all.&lt;br /&gt;
&lt;br /&gt;
=Callback=&lt;br /&gt;
It makes sense to limit the range of IP addresses where the merchant&#039;s server accepts callback requests from, although you must be aware that the IP addresses can change.&lt;br /&gt;
&lt;br /&gt;
The callback request currently originate from the following IP addresses: &lt;br /&gt;
* 13.79.241.141&lt;br /&gt;
* 40.69.88.149&lt;br /&gt;
* 40.69.88.240&lt;br /&gt;
* 52.164.220.205&lt;br /&gt;
* 52.169.80.55&lt;br /&gt;
* 195.56.171.161&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=The IP address of the callback request may change any time for security reasons.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
If the IP address changes, we publish the list of new IP addresses here and notify our developers and merchants in the Facebook group (See: [[Support|Getting support]]) and in a newsletter, sent to the merchant&#039;s e-mail used at registration.&lt;br /&gt;
&lt;br /&gt;
=Barion API Calls=&lt;br /&gt;
We recommend that you use Domain Name Service (DNS) results to determine the IP addresses of our API servers. We may change records we do not provide notification of changes.&lt;br /&gt;
&lt;br /&gt;
=Encryption=&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not supported. You can test your solution in the [[Sandbox]] server, where TLS 1.0 has already been disabled.&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system only supports TLS v1.1 / v1.2|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1433</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1433"/>
		<updated>2018-07-18T12:51:45Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer|in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only GET or only POST requests - there are no universal endpoints available.&lt;br /&gt;
On each API endpoint reference page, you can find the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system only supports TLS v1.1 / v1.2|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support http method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Some things you must ensure when creating an API request:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; should also be specified explicitly in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32 character string representation, like this: &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used e.g. to identify payments.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; avoid integer or byte evaluation when constructing the request JSON!&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Always double check that you are connecting to the proper environment to avoid unnecessary hassle and troubleshooting!&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, whenever there is a major update to an API endpoint, it is moved to a higher level of API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. See the reference page of a given API endpoint to see which versions are available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), it is recommended to always specify the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
For every request sent to the Barion API you have to authenticate yourself. For this every API request should cointain a &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; property containing the secret API key for the shop. This key is in the confirmation e-mail that was sent to you when you opened the shop or can be copied from the details page of the shop (secure.barion.com -&amp;gt; Manage my shops -&amp;gt; Details). This is unique for every shop in the system. Be aware that the test and live environment are completely separate environments, you need to create different shops. Make sure that you use the secret key and not th public key:&lt;br /&gt;
&lt;br /&gt;
[[File:Poskey.jpg]]&lt;br /&gt;
&lt;br /&gt;
If the key is invalid you will receive an &amp;lt;code&amp;gt;AuthenticationFailed&amp;lt;/code&amp;gt; error.&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however on property can found in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, this can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, this is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingPaymentId&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The given payment id is invalid&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The given payment id(510bbd38-08c9-40b9-9e21-c6f6cb9eb4f1) is invalid!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/GetPaymentState?POSKey=5b65f8f7a5f4405bb19495383dcf170a&amp;amp;PaymentId=510bbd3808c940b99e21c6f6cb9eb4f1&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before staring to code.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1432</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1432"/>
		<updated>2018-07-18T12:51:33Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* HTTPS and Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=HTTPS and Certificates=&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed. You can test your solution on the Sandbox server, where TLS 1.0 has already been disabled.&lt;br /&gt;
&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 has been disabled on the Sandbox, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=1431</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=1431"/>
		<updated>2018-07-18T12:51:21Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 20th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Going live}}&lt;br /&gt;
&lt;br /&gt;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] in an online registration. Na paperwork or hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register on the live Barion server at https://secure.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
See alse:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, it is easy to mix up live and sandbox accounts! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. Only shops that are legal and comply with our [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] are allowed. Barion does not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, consult our [https://www.barion.com/en/merchants/ experts] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you will be asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you will be asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payment must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://www.barion.com/en/merchants/ experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
To go live, the following changes must be made in the payment solution. We advise to make these parameters, so you can easily switch between the sandbox and live servers.&lt;br /&gt;
*API endpoint URL must be changed to live (https://api.test.barion.com -&amp;gt; https://api.barion.com)&lt;br /&gt;
*Payment GUI redirect URL must be changes to live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay)&lt;br /&gt;
*POSKey must be changed to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here)&lt;br /&gt;
*Return URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*Callback URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*E-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;-s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if different in sandbox&lt;br /&gt;
*Certificates, if checking server certificates&lt;br /&gt;
*If using token payment, sandbox Tokens will not work in the live system&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your choosen price package. Please refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps placement. Please follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-card-payment-banner-2016-432x50px.png]]&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-smart-payment-banners.zip]]&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff will check it and will only approve shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Please refer to [[Support|Getting support]] for more information.&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Current limitations of the live Barion system:&lt;br /&gt;
*Reservation and 3rd party payment only works with HUF currency&lt;br /&gt;
*Barion Mobile App only shows HUF transactions&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=These limitations are planned to be lifted in Q4 2017.|color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Security_Measures&amp;diff=1429</id>
		<title>Security Measures</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Security_Measures&amp;diff=1429"/>
		<updated>2018-07-18T12:01:54Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Encryption */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Security Measures}}&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
This page lists different measures we take to maintain security and service levels. Please read carefully and follow the instructions, especially where changes may happen any time. If you do not update your settings when a change occurs, you might risk your Barion implementation&#039;s ability to work properly or at all.&lt;br /&gt;
&lt;br /&gt;
=Callback=&lt;br /&gt;
It makes sense to limit the range of IP addresses where the merchant&#039;s server accepts callback requests from, although you must be aware that the IP addresses can change.&lt;br /&gt;
&lt;br /&gt;
The callback request currently originate from the following IP addresses: &lt;br /&gt;
* 13.79.241.141&lt;br /&gt;
* 40.69.88.149&lt;br /&gt;
* 40.69.88.240&lt;br /&gt;
* 52.164.220.205&lt;br /&gt;
* 52.169.80.55&lt;br /&gt;
* 195.56.171.161&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=The IP address of the callback request may change any time for security reasons.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
If the IP address changes, we publish the list of new IP addresses here and notify our developers and merchants in the Facebook group (See: [[Support|Getting support]]) and in a newsletter, sent to the merchant&#039;s e-mail used at registration.&lt;br /&gt;
&lt;br /&gt;
=Barion API Calls=&lt;br /&gt;
We recommend that you use Domain Name Service (DNS) results to determine the IP addresses of our API servers. We may change records we do not provide notification of changes.&lt;br /&gt;
&lt;br /&gt;
=Encryption=&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system only supports TLS v1.1 / v1.2|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1428</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1428"/>
		<updated>2018-07-18T12:00:15Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Protocols and communication */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer|in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only GET or only POST requests - there are no universal endpoints available.&lt;br /&gt;
On each API endpoint reference page, you can find the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system only supports TLS v1.1 / v1.2|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support http method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Some things you must ensure when creating an API request:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; should also be specified explicitly in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32 character string representation, like this: &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used e.g. to identify payments.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; avoid integer or byte evaluation when constructing the request JSON!&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Always double check that you are connecting to the proper environment to avoid unnecessary hassle and troubleshooting!&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, whenever there is a major update to an API endpoint, it is moved to a higher level of API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. See the reference page of a given API endpoint to see which versions are available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), it is recommended to always specify the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
For every request sent to the Barion API you have to authenticate yourself. For this every API request should cointain a &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; property containing the secret API key for the shop. This key is in the confirmation e-mail that was sent to you when you opened the shop or can be copied from the details page of the shop (secure.barion.com -&amp;gt; Manage my shops -&amp;gt; Details). This is unique for every shop in the system. Be aware that the test and live environment are completely separate environments, you need to create different shops. Make sure that you use the secret key and not th public key:&lt;br /&gt;
&lt;br /&gt;
[[File:Poskey.jpg]]&lt;br /&gt;
&lt;br /&gt;
If the key is invalid you will receive an &amp;lt;code&amp;gt;AuthenticationFailed&amp;lt;/code&amp;gt; error.&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however on property can found in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, this can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, this is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingPaymentId&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The given payment id is invalid&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The given payment id(510bbd38-08c9-40b9-9e21-c6f6cb9eb4f1) is invalid!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/GetPaymentState?POSKey=5b65f8f7a5f4405bb19495383dcf170a&amp;amp;PaymentId=510bbd3808c940b99e21c6f6cb9eb4f1&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before staring to code.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=1427</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=1427"/>
		<updated>2018-07-18T11:59:44Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Security */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Going live}}&lt;br /&gt;
&lt;br /&gt;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] in an online registration. Na paperwork or hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register on the live Barion server at https://secure.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
See alse:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, it is easy to mix up live and sandbox accounts! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. Only shops that are legal and comply with our [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] are allowed. Barion does not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, consult our [https://www.barion.com/en/merchants/ experts] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you will be asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you will be asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payment must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://www.barion.com/en/merchants/ experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
To go live, the following changes must be made in the payment solution. We advise to make these parameters, so you can easily switch between the sandbox and live servers.&lt;br /&gt;
*API endpoint URL must be changed to live (https://api.test.barion.com -&amp;gt; https://api.barion.com)&lt;br /&gt;
*Payment GUI redirect URL must be changes to live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay)&lt;br /&gt;
*POSKey must be changed to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here)&lt;br /&gt;
*Return URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*Callback URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*E-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;-s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if different in sandbox&lt;br /&gt;
*Certificates, if checking server certificates&lt;br /&gt;
*If using token payment, sandbox Tokens will not work in the live system&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your choosen price package. Please refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps placement. Please follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-card-payment-banner-2016-432x50px.png]]&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-smart-payment-banners.zip]]&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff will check it and will only approve shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Please refer to [[Support|Getting support]] for more information.&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Current limitations of the live Barion system:&lt;br /&gt;
*Reservation and 3rd party payment only works with HUF currency&lt;br /&gt;
*Barion Mobile App only shows HUF transactions&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=These limitations are planned to be lifted in Q4 2017.|color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=1426</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=1426"/>
		<updated>2018-07-18T11:59:32Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Going live}}&lt;br /&gt;
&lt;br /&gt;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] in an online registration. Na paperwork or hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register on the live Barion server at https://secure.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
See alse:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, it is easy to mix up live and sandbox accounts! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. Only shops that are legal and comply with our [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] are allowed. Barion does not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, consult our [https://www.barion.com/en/merchants/ experts] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you will be asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you will be asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payment must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://www.barion.com/en/merchants/ experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
To go live, the following changes must be made in the payment solution. We advise to make these parameters, so you can easily switch between the sandbox and live servers.&lt;br /&gt;
*API endpoint URL must be changed to live (https://api.test.barion.com -&amp;gt; https://api.barion.com)&lt;br /&gt;
*Payment GUI redirect URL must be changes to live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay)&lt;br /&gt;
*POSKey must be changed to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here)&lt;br /&gt;
*Return URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*Callback URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*E-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;-s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if different in sandbox&lt;br /&gt;
*Certificates, if checking server certificates&lt;br /&gt;
*If using token payment, sandbox Tokens will not work in the live system&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your choosen price package. Please refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps placement. Please follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-card-payment-banner-2016-432x50px.png]]&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-smart-payment-banners.zip]]&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff will check it and will only approve shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Please refer to [[Support|Getting support]] for more information.&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Current limitations of the live Barion system:&lt;br /&gt;
*Reservation and 3rd party payment only works with HUF currency&lt;br /&gt;
*Barion Mobile App only shows HUF transactions&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=These limitations are planned to be lifted in Q4 2017.|color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1425</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1425"/>
		<updated>2018-07-18T11:58:37Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1424</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1424"/>
		<updated>2018-07-18T11:58:22Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* HTTPS and Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=HTTPS and Certificates=&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed. You can test your solution on the Sandbox server, where TLS 1.0 has already been disabled.&lt;br /&gt;
&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 has been disabled on the Sandbox, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 25th of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1423</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1423"/>
		<updated>2018-07-18T11:53:30Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* HTTPS and Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=HTTPS and Certificates=&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed. You can test your solution on the Sandbox server, where TLS 1.0 has already been disabled.&lt;br /&gt;
&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 has been disabled on the Sandbox, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 31st of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1422</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1422"/>
		<updated>2018-07-18T11:52:34Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=WARNING|text=TLS 1.0 will be switched off on the 31st of July 2018 on the live servers, switch to TLS 1.1 / 1.2 now!|color=#FF0000}}&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1421</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1421"/>
		<updated>2018-07-18T11:51:01Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* HTTPS and Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=HTTPS and Certificates=&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed. You can test your solution on the Sandbox server, where TLS 1.0 has already been disabled.&lt;br /&gt;
&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 has been disabled on the Sandbox, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1420</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1420"/>
		<updated>2018-07-18T11:49:58Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=HTTPS and Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 has been disabled on the Sandbox, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1419</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1419"/>
		<updated>2018-07-18T11:49:30Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 has been disabled on the Sandbox, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1418</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1418"/>
		<updated>2018-07-18T11:48:50Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Certificates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1417</id>
		<title>Troubleshooting</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1417"/>
		<updated>2018-07-18T11:47:11Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Using deprecated or obosolete encryption methods */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=TLS 1.0 will be no longer supported, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
{{PageTitle|title= Troubleshooting - list of common pitfalls}}&lt;br /&gt;
&lt;br /&gt;
Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list.&lt;br /&gt;
&lt;br /&gt;
==Polling the server instead of using the callback ==&lt;br /&gt;
Many developers fail to implement the [[Callback_mechanism|callback mechanism]]. Instead, they either rely on faulty strategies:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Calling GetPaymentState only when the customer is redirected to the shop &lt;br /&gt;
|This approach only works if the customer actually returns to the shop. If the user closes the browser after payment, but before returning to the shop, the merchant will not get notified about the successful payment. As a result, some developers choose to poll the server periodically. We strongly recommend using the callback.&lt;br /&gt;
|-&lt;br /&gt;
|Polling the server with GetPaymentState calls&lt;br /&gt;
|This approach floods the Barion servers with unnecessary API calls, slowing it down. It is also more complex to code and to test. We strongly recommend using the callback.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Always rely on the callback. The Barion server retries the callback 5 times, so the chances of losing a payment is very little.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Flooding the Barion servers with unnecessary API calls may lead to suspension of the shop|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Mixing up sandbox and live accounts ==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. Since the two systems are totally separated, you can have an account with the same e-mail address in both systems. Double check, if you can not log on.&lt;br /&gt;
&lt;br /&gt;
==Forgot to update POSKey to live==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. A very common mistake is to not update the POSKey to the Live server when going live. Same goes to URL-s.&lt;br /&gt;
&lt;br /&gt;
==Shop not approved==&lt;br /&gt;
Log on to Barion Web App and check if your shop is approved and open. The Sandbox server does it automatically, but the Live requires human approval.&lt;br /&gt;
&lt;br /&gt;
==Paying in your own shop==&lt;br /&gt;
If you try to pay as the owner of the shop that started the payment (meaning the payer and payee e-mail addresses are the same), you will get an error message. You cannot pay in your own shop.&lt;br /&gt;
&lt;br /&gt;
==Bank card payment with extreme low amounts==&lt;br /&gt;
Bank card payments do not work with very small amounts such as 1 HUF or 0.02 EUR. Please use the following amounts for card transactions, even when testing!&lt;br /&gt;
* HUF: 10 HUF or more&lt;br /&gt;
* EUR: 0.10 EUR or more&lt;br /&gt;
* USD: 0.10 USD or more&lt;br /&gt;
&lt;br /&gt;
==Authentication error upon request==&lt;br /&gt;
If you have managed to avoid all problems mentioned above, yet you still receive an API response showing &#039;&#039;&#039;&#039;Authentication error&#039;&#039;&#039;&#039;, check your request JSON for errors. Broken multibyte strings or unescaped special characters can render the JSON unparseable, which prevents the Barion API from identifying your POSKey, resulting in an authentication error.&lt;br /&gt;
&lt;br /&gt;
==Firewall rejects GUID==&lt;br /&gt;
Some firewalls produce a false positive when long GUID-s travel in https requests.&lt;br /&gt;
&lt;br /&gt;
==Wrong or missing API version==&lt;br /&gt;
If you omit the version from the URL, the system assumes V1. In case of a V2 API, this will lead to an error. The correct way to call V2 API-s is &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.test.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; on the sandbox.&lt;br /&gt;
&lt;br /&gt;
== Using deprecated or obosolete encryption methods ==&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed! You can test your solution in the [[Sandbox]] server, where TLS 1.0 has already been disabled.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1416</id>
		<title>Troubleshooting</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1416"/>
		<updated>2018-07-18T11:46:56Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Using deprecated or obosolete encryption methods */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=TLS 1.0 will be no longer supported, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
{{PageTitle|title= Troubleshooting - list of common pitfalls}}&lt;br /&gt;
&lt;br /&gt;
Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list.&lt;br /&gt;
&lt;br /&gt;
==Polling the server instead of using the callback ==&lt;br /&gt;
Many developers fail to implement the [[Callback_mechanism|callback mechanism]]. Instead, they either rely on faulty strategies:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Calling GetPaymentState only when the customer is redirected to the shop &lt;br /&gt;
|This approach only works if the customer actually returns to the shop. If the user closes the browser after payment, but before returning to the shop, the merchant will not get notified about the successful payment. As a result, some developers choose to poll the server periodically. We strongly recommend using the callback.&lt;br /&gt;
|-&lt;br /&gt;
|Polling the server with GetPaymentState calls&lt;br /&gt;
|This approach floods the Barion servers with unnecessary API calls, slowing it down. It is also more complex to code and to test. We strongly recommend using the callback.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Always rely on the callback. The Barion server retries the callback 5 times, so the chances of losing a payment is very little.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Flooding the Barion servers with unnecessary API calls may lead to suspension of the shop|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Mixing up sandbox and live accounts ==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. Since the two systems are totally separated, you can have an account with the same e-mail address in both systems. Double check, if you can not log on.&lt;br /&gt;
&lt;br /&gt;
==Forgot to update POSKey to live==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. A very common mistake is to not update the POSKey to the Live server when going live. Same goes to URL-s.&lt;br /&gt;
&lt;br /&gt;
==Shop not approved==&lt;br /&gt;
Log on to Barion Web App and check if your shop is approved and open. The Sandbox server does it automatically, but the Live requires human approval.&lt;br /&gt;
&lt;br /&gt;
==Paying in your own shop==&lt;br /&gt;
If you try to pay as the owner of the shop that started the payment (meaning the payer and payee e-mail addresses are the same), you will get an error message. You cannot pay in your own shop.&lt;br /&gt;
&lt;br /&gt;
==Bank card payment with extreme low amounts==&lt;br /&gt;
Bank card payments do not work with very small amounts such as 1 HUF or 0.02 EUR. Please use the following amounts for card transactions, even when testing!&lt;br /&gt;
* HUF: 10 HUF or more&lt;br /&gt;
* EUR: 0.10 EUR or more&lt;br /&gt;
* USD: 0.10 USD or more&lt;br /&gt;
&lt;br /&gt;
==Authentication error upon request==&lt;br /&gt;
If you have managed to avoid all problems mentioned above, yet you still receive an API response showing &#039;&#039;&#039;&#039;Authentication error&#039;&#039;&#039;&#039;, check your request JSON for errors. Broken multibyte strings or unescaped special characters can render the JSON unparseable, which prevents the Barion API from identifying your POSKey, resulting in an authentication error.&lt;br /&gt;
&lt;br /&gt;
==Firewall rejects GUID==&lt;br /&gt;
Some firewalls produce a false positive when long GUID-s travel in https requests.&lt;br /&gt;
&lt;br /&gt;
==Wrong or missing API version==&lt;br /&gt;
If you omit the version from the URL, the system assumes V1. In case of a V2 API, this will lead to an error. The correct way to call V2 API-s is &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.test.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; on the sandbox.&lt;br /&gt;
&lt;br /&gt;
== Using deprecated or obosolete encryption methods ==&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed! You can test your solution in the [Sandbox] server, where TLS 1.0 has already been disabled.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1415</id>
		<title>Troubleshooting</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1415"/>
		<updated>2018-07-18T11:46:39Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Using deprecated or obosolete encryption methods */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=TLS 1.0 will be no longer supported, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
{{PageTitle|title= Troubleshooting - list of common pitfalls}}&lt;br /&gt;
&lt;br /&gt;
Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list.&lt;br /&gt;
&lt;br /&gt;
==Polling the server instead of using the callback ==&lt;br /&gt;
Many developers fail to implement the [[Callback_mechanism|callback mechanism]]. Instead, they either rely on faulty strategies:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Calling GetPaymentState only when the customer is redirected to the shop &lt;br /&gt;
|This approach only works if the customer actually returns to the shop. If the user closes the browser after payment, but before returning to the shop, the merchant will not get notified about the successful payment. As a result, some developers choose to poll the server periodically. We strongly recommend using the callback.&lt;br /&gt;
|-&lt;br /&gt;
|Polling the server with GetPaymentState calls&lt;br /&gt;
|This approach floods the Barion servers with unnecessary API calls, slowing it down. It is also more complex to code and to test. We strongly recommend using the callback.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Always rely on the callback. The Barion server retries the callback 5 times, so the chances of losing a payment is very little.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Flooding the Barion servers with unnecessary API calls may lead to suspension of the shop|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Mixing up sandbox and live accounts ==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. Since the two systems are totally separated, you can have an account with the same e-mail address in both systems. Double check, if you can not log on.&lt;br /&gt;
&lt;br /&gt;
==Forgot to update POSKey to live==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. A very common mistake is to not update the POSKey to the Live server when going live. Same goes to URL-s.&lt;br /&gt;
&lt;br /&gt;
==Shop not approved==&lt;br /&gt;
Log on to Barion Web App and check if your shop is approved and open. The Sandbox server does it automatically, but the Live requires human approval.&lt;br /&gt;
&lt;br /&gt;
==Paying in your own shop==&lt;br /&gt;
If you try to pay as the owner of the shop that started the payment (meaning the payer and payee e-mail addresses are the same), you will get an error message. You cannot pay in your own shop.&lt;br /&gt;
&lt;br /&gt;
==Bank card payment with extreme low amounts==&lt;br /&gt;
Bank card payments do not work with very small amounts such as 1 HUF or 0.02 EUR. Please use the following amounts for card transactions, even when testing!&lt;br /&gt;
* HUF: 10 HUF or more&lt;br /&gt;
* EUR: 0.10 EUR or more&lt;br /&gt;
* USD: 0.10 USD or more&lt;br /&gt;
&lt;br /&gt;
==Authentication error upon request==&lt;br /&gt;
If you have managed to avoid all problems mentioned above, yet you still receive an API response showing &#039;&#039;&#039;&#039;Authentication error&#039;&#039;&#039;&#039;, check your request JSON for errors. Broken multibyte strings or unescaped special characters can render the JSON unparseable, which prevents the Barion API from identifying your POSKey, resulting in an authentication error.&lt;br /&gt;
&lt;br /&gt;
==Firewall rejects GUID==&lt;br /&gt;
Some firewalls produce a false positive when long GUID-s travel in https requests.&lt;br /&gt;
&lt;br /&gt;
==Wrong or missing API version==&lt;br /&gt;
If you omit the version from the URL, the system assumes V1. In case of a V2 API, this will lead to an error. The correct way to call V2 API-s is &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.test.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; on the sandbox.&lt;br /&gt;
&lt;br /&gt;
== Using deprecated or obosolete encryption methods ==&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed! You can test your solution in the Sandbox server, where TLS 1.0 has already been disabled.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1414</id>
		<title>Troubleshooting</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Troubleshooting&amp;diff=1414"/>
		<updated>2018-07-18T11:45:53Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=TLS 1.0 will be no longer supported, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
{{PageTitle|title= Troubleshooting - list of common pitfalls}}&lt;br /&gt;
&lt;br /&gt;
Before contacting support, please run through the list of common pitfalls. This will save both you and us a lot of time. Here we go with the list.&lt;br /&gt;
&lt;br /&gt;
==Polling the server instead of using the callback ==&lt;br /&gt;
Many developers fail to implement the [[Callback_mechanism|callback mechanism]]. Instead, they either rely on faulty strategies:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|Calling GetPaymentState only when the customer is redirected to the shop &lt;br /&gt;
|This approach only works if the customer actually returns to the shop. If the user closes the browser after payment, but before returning to the shop, the merchant will not get notified about the successful payment. As a result, some developers choose to poll the server periodically. We strongly recommend using the callback.&lt;br /&gt;
|-&lt;br /&gt;
|Polling the server with GetPaymentState calls&lt;br /&gt;
|This approach floods the Barion servers with unnecessary API calls, slowing it down. It is also more complex to code and to test. We strongly recommend using the callback.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Always rely on the callback. The Barion server retries the callback 5 times, so the chances of losing a payment is very little.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Flooding the Barion servers with unnecessary API calls may lead to suspension of the shop|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Mixing up sandbox and live accounts ==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. Since the two systems are totally separated, you can have an account with the same e-mail address in both systems. Double check, if you can not log on.&lt;br /&gt;
&lt;br /&gt;
==Forgot to update POSKey to live==&lt;br /&gt;
It is very easy to mix up [[sandbox|Live and Sandbox]] environments. A very common mistake is to not update the POSKey to the Live server when going live. Same goes to URL-s.&lt;br /&gt;
&lt;br /&gt;
==Shop not approved==&lt;br /&gt;
Log on to Barion Web App and check if your shop is approved and open. The Sandbox server does it automatically, but the Live requires human approval.&lt;br /&gt;
&lt;br /&gt;
==Paying in your own shop==&lt;br /&gt;
If you try to pay as the owner of the shop that started the payment (meaning the payer and payee e-mail addresses are the same), you will get an error message. You cannot pay in your own shop.&lt;br /&gt;
&lt;br /&gt;
==Bank card payment with extreme low amounts==&lt;br /&gt;
Bank card payments do not work with very small amounts such as 1 HUF or 0.02 EUR. Please use the following amounts for card transactions, even when testing!&lt;br /&gt;
* HUF: 10 HUF or more&lt;br /&gt;
* EUR: 0.10 EUR or more&lt;br /&gt;
* USD: 0.10 USD or more&lt;br /&gt;
&lt;br /&gt;
==Authentication error upon request==&lt;br /&gt;
If you have managed to avoid all problems mentioned above, yet you still receive an API response showing &#039;&#039;&#039;&#039;Authentication error&#039;&#039;&#039;&#039;, check your request JSON for errors. Broken multibyte strings or unescaped special characters can render the JSON unparseable, which prevents the Barion API from identifying your POSKey, resulting in an authentication error.&lt;br /&gt;
&lt;br /&gt;
==Firewall rejects GUID==&lt;br /&gt;
Some firewalls produce a false positive when long GUID-s travel in https requests.&lt;br /&gt;
&lt;br /&gt;
==Wrong or missing API version==&lt;br /&gt;
If you omit the version from the URL, the system assumes V1. In case of a V2 API, this will lead to an error. The correct way to call V2 API-s is &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.test.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; on the sandbox.&lt;br /&gt;
&lt;br /&gt;
== Using deprecated or obosolete encryption methods ==&lt;br /&gt;
All communication with the Barion system must be done using TLS v1.1 / 1.2 - former encryption standards (SSLv3, TLS1.0 etc.) are not allowed!&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1413</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1413"/>
		<updated>2018-07-18T11:43:13Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 will be no longer supported, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1412</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1412"/>
		<updated>2018-07-18T11:43:01Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 will be no longer supported on the Barion servers, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1411</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1411"/>
		<updated>2018-07-18T11:42:44Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=TLS 1.0 will be no longer supported on the Barion servers, switch to TLS 1.1 / 1.2 now, otherwise your Barion implementation will not work!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1400</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1400"/>
		<updated>2018-07-14T10:42:40Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1399</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1399"/>
		<updated>2018-07-14T10:41:52Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=File:Live-sandbox.png&amp;diff=1380</id>
		<title>File:Live-sandbox.png</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=File:Live-sandbox.png&amp;diff=1380"/>
		<updated>2018-02-12T14:55:34Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1378</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1378"/>
		<updated>2018-02-12T14:45:19Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Payment GUI */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard SSL is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment as well, so DO NOT use any real e-mail address that does not belong to you. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1377</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1377"/>
		<updated>2018-02-12T14:44:35Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Payment GUI */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard SSL is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Comodo Site Authority is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Confirmation e-mails are actually sent out in the Sandbox environment, so DO NOT use any real e-mail address that does not belong to you, when you enter e-mail addresses for guest payments. Please use your own personal or development e-mail address, or if you do not care about the e-mail itself, use the @example.com e-mail domain.&lt;br /&gt;
|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1362</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1362"/>
		<updated>2018-01-04T15:27:16Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Payment scenarios */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]] &lt;br /&gt;
*[[Facilitated_payments|Marketplace, sharing economy, and facilitated payments description]]&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1171</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1171"/>
		<updated>2017-11-28T19:34:30Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Test cards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard SSL is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous ones do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Norton logo is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1170</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1170"/>
		<updated>2017-11-28T19:34:14Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Test cards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard SSL is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available and previous one do not work.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Norton logo is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1169</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1169"/>
		<updated>2017-11-28T19:31:06Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Test cards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard SSL is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available |color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Norton logo is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=File:Test-card2.png&amp;diff=1168</id>
		<title>File:Test-card2.png</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=File:Test-card2.png&amp;diff=1168"/>
		<updated>2017-11-28T19:30:13Z</updated>

		<summary type="html">&lt;p&gt;Birot: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=1164</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=1164"/>
		<updated>2017-11-28T19:26:56Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Test cards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Setting up the Sandbox environment and testing payments}}&lt;br /&gt;
&lt;br /&gt;
=Sandbox server=&lt;br /&gt;
Although Barion payments are super easy to integrate, we strongly advise all developers to use the sandbox server for development and testing, before going live. &lt;br /&gt;
&lt;br /&gt;
There are many advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is available 7/24/365, you can even start working at night or during weekends (many developers do just that, but please note that except for the Facebook group, [[Support|support]] is only available durig working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No approvals required&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The two systems are completely separated, so the same e-mail address can be used in both systems (warning: easy to mix them up!)&lt;br /&gt;
&lt;br /&gt;
=Limitations in functionality=&lt;br /&gt;
The sandbox server is a copy of the live Barion servers, with some minor differences:&lt;br /&gt;
&lt;br /&gt;
*From the developers perspective, the only difference is the URL&lt;br /&gt;
*No real money in the sandbox, all transactions are using &amp;quot;test&amp;quot; money that has no real value&lt;br /&gt;
*Since the sandbox is not using real money, withdrawal to bank accounts is not possible &lt;br /&gt;
*Real bank cards do not work, we provide a test card&lt;br /&gt;
*Top-up is only possible with test card&lt;br /&gt;
*Shops are automatically approved&lt;br /&gt;
*The servers are of smaller capacity&lt;br /&gt;
*Simple SSL certificates are used&lt;br /&gt;
*Sandbox servers are updated regularly without notice (we are doing our best not to lose any data)&lt;br /&gt;
&lt;br /&gt;
[[file:live-sandbox.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
=Registering accounts=&lt;br /&gt;
Just as in the live server, a simple online form is needed to register a Barion account. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. Note: It is easy to mix up the live and sandbox accounts, so please always double check before calling support. &lt;br /&gt;
&lt;br /&gt;
https://secure.test.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/Registration, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
=Opening a shop=&lt;br /&gt;
Opening a shop in the sandbox is the same as opening one in the live server. The only difference is that the sandbox is wired to automatically approve all changes, while the live server requires a human compliance officer to approve the shop. Prepare for questions and some minor paperwork when switching from sandbox to live.&lt;br /&gt;
&lt;br /&gt;
=API URL=&lt;br /&gt;
The base URL for the Barion API is the same as the live, with the word &amp;quot;test&amp;quot; added.&lt;br /&gt;
&lt;br /&gt;
https://api.test.barion.com&lt;br /&gt;
&lt;br /&gt;
=Certificates=&lt;br /&gt;
Our sandbox server is using more economical certificates, than the live server. Standard SSL is used, instead of Extended Validation (EV), and a less well known brand has been chosen. This does not effect security and development, and applies only to the sandbox.&lt;br /&gt;
&lt;br /&gt;
=Test cards=&lt;br /&gt;
&lt;br /&gt;
The sandbox server is connected to a card acquirer, so all transactions using the test card reach out to that server. This can cause a variation in card processing time. Please note, that if you make many payments to a merchant, the account can reach a balance where another level of KYC is required, and the account will be temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Try to avoid this, or in case you don&#039;t, drop a mail to support. Although theoretically the test card has unlimited funds, occasionally it can run out of money, so do not make transactions of large volumes, just because it is not real money. We know it can be fun, but it can ruin the day of all developers using the card. Please stick to a few EUR per transaction. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=UPDATE|text=From 28th November 2017, the following test cards are available |color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - payments with this card will always SUCCEED&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 5559&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - payments with this card will always FAIL&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 4446&#039;&#039;&#039;&lt;br /&gt;
*Expiration date: &#039;&#039;&#039;any future date&#039;&#039;&#039;&lt;br /&gt;
*CVC: &#039;&#039;&#039;any 3-digit number&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Payment GUI=&lt;br /&gt;
The payment GUI in the sandbox server is the same as in the live, with some exceptions:&lt;br /&gt;
*A black bar is present at the top, with a message saying &amp;quot;sandbox server&amp;quot;&lt;br /&gt;
*The Norton logo is missing, since the sandbox server uses a different SSL certificate&lt;br /&gt;
*The URL has the word &amp;quot;test&amp;quot; in it&lt;br /&gt;
*It only accpets the test card, no real cards can be used&lt;br /&gt;
*All payments are with &amp;quot;test&amp;quot; money, not real money&lt;br /&gt;
&lt;br /&gt;
[[file:Sandbox-payment-gui.PNG|600px]]&lt;br /&gt;
&lt;br /&gt;
=Using the Barion Web App in Sandbox mode=&lt;br /&gt;
You can log into the Barion Web App on the same URL, with the word &amp;quot;test&amp;quot; added. A black bar is shown on top of each screen to help differentiate from the live server.&lt;br /&gt;
https://secure.test.barion.com/&lt;br /&gt;
&lt;br /&gt;
This URL is identical to https://test.barion.com/, the word &amp;quot;secure&amp;quot; can be omitted.&lt;br /&gt;
&lt;br /&gt;
= Using the Barion Mobile App in Sandbox mode =&lt;br /&gt;
You can also use the Barion Mobile App with the sandbox server by entering &amp;lt;tt&amp;gt;test#&amp;lt;/tt&amp;gt; before the e-mail address when logging into the app. The title bar of the app turns green to help differentiate from live accounts. You can download the app from Google Play or from the App Store.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;html4strict&amp;quot;&amp;gt;&lt;br /&gt;
test#youremail@example.com&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Limitations of the Barion Mobile App=&lt;br /&gt;
Current version of the Barion Mobile App supports HUF payments only. If you do not have an HUF currency set up in your wallet, the mobile app login will fail.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=1158</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=1158"/>
		<updated>2017-11-23T11:29:32Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Other useful info */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Barion technical documentation}}&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|right|500px]]&lt;br /&gt;
Welcome to the technical documentation of the Barion Smart Gateway electronic payment system. In this wiki you can find the resources needed to implement quick and reliable payment services in your web shop or mobile application.&lt;br /&gt;
&lt;br /&gt;
==Before you start coding==&lt;br /&gt;
*[[Getting_started|Getting started - overview of Barion payments]]&lt;br /&gt;
*[[Sandbox|Setting up the Sandbox environment and testing payments]]&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
*[[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&amp;lt;!--*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]--&amp;gt;&lt;br /&gt;
*[[Support|Getting support]]&lt;br /&gt;
*[[Going_live|Going live]]&lt;br /&gt;
&lt;br /&gt;
==Payment scenarios==&lt;br /&gt;
*[[Responsive_web_payment|Responsive Web Payment - simple web shop payment for desktop and mobile]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C Payments - transactions between users with optional commission and escrow, ideal for Sharing Economy and Marketplaces]]&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[[Download|Downloadable resources – libraries and source code]]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
&lt;br /&gt;
==Contributors&#039; guide==&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- ==Other relevant services==&lt;br /&gt;
*[[refunding|Refunding payments to customers - automated with API]]&lt;br /&gt;
*[[withdrawing|Withdrawing money to bank account  - automated with API]]&lt;br /&gt;
*[[sending-money|Sending money to other Barion accounts for free - automated with API]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1157</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1157"/>
		<updated>2017-11-23T11:25:26Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Security */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer|in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only GET or only POST requests - there are no universal endpoints available.&lt;br /&gt;
On each API endpoint reference page, you can find the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; all communication must be done over HTTPS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support http method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Some things you must ensure when creating an API request:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; should also be specified explicitly in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32 character string representation, like this: &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used e.g. to identify payments.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; avoid integer or byte evaluation when constructing the request JSON!&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Always double check that you are connecting to the proper environment to avoid unnecessary hassle and troubleshooting!&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, whenever there is a major update to an API endpoint, it is moved to a higher level of API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. See the reference page of a given API endpoint to see which versions are available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), it is recommended to always specify the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
For every request sent to the Barion API you have to authenticate yourself. For this every API request should cointain a &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; property containing the secret API key for the shop. This key is in the confirmation e-mail that was sent to you when you opened the shop or can be copied from the details page of the shop (secure.barion.com -&amp;gt; Manage my shops -&amp;gt; Details). This is unique for every shop in the system. Be aware that the test and live environment are completely separate environments, you need to create different shops. Make sure that you use the secret key and not th public key:&lt;br /&gt;
&lt;br /&gt;
[[File:Poskey.jpg]]&lt;br /&gt;
&lt;br /&gt;
If the key is invalid you will receive an &amp;lt;code&amp;gt;AuthenticationFailed&amp;lt;/code&amp;gt; error.&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however on property can found in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, this can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, this is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingPaymentId&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The given payment id is invalid&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The given payment id(510bbd38-08c9-40b9-9e21-c6f6cb9eb4f1) is invalid!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/GetPaymentState?POSKey=5b65f8f7a5f4405bb19495383dcf170a&amp;amp;PaymentId=510bbd3808c940b99e21c6f6cb9eb4f1&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before staring to code.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1156</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=1156"/>
		<updated>2017-11-23T11:24:39Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* Handling the response */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer|in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only GET or only POST requests - there are no universal endpoints available.&lt;br /&gt;
On each API endpoint reference page, you can find the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; all communication must be done over HTTPS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support http method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Some things you must ensure when creating an API request:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; should also be specified explicitly in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32 character string representation, like this: &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used e.g. to identify payments.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; avoid integer or byte evaluation when constructing the request JSON!&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Always double check that you are connecting to the proper environment to avoid unnecessary hassle and troubleshooting!&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, whenever there is a major update to an API endpoint, it is moved to a higher level of API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. See the reference page of a given API endpoint to see which versions are available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), it is recommended to always specify the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
For every request sent to the Barion API you have to authenticate yourself. For this every API request should cointain a &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; property containing the secret API key for the shop. This key is in the confirmation e-mail that was sent to you when you opened the shop or can be copied from the details page of the shop (secure.barion.com -&amp;gt; Manage my shops -&amp;gt; Details). This is unique for every shop in the system. Be aware that the test and live environment are completely separate environments, you need to create different shops. Make sure that you use the secret key and not th public key:&lt;br /&gt;
&lt;br /&gt;
[[File:Poskey.jpg]]&lt;br /&gt;
&lt;br /&gt;
If the key is invalid you will receive an &amp;lt;code&amp;gt;AuthenticationFailed&amp;lt;/code&amp;gt; error.&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however on property can found in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, this can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, this is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingPaymentId&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The given payment id is invalid&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The given payment id(510bbd38-08c9-40b9-9e21-c6f6cb9eb4f1) is invalid!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/GetPaymentState?POSKey=5b65f8f7a5f4405bb19495383dcf170a&amp;amp;PaymentId=510bbd3808c940b99e21c6f6cb9eb4f1&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before going live.&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=1155</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=1155"/>
		<updated>2017-11-23T11:23:18Z</updated>

		<summary type="html">&lt;p&gt;Birot: /* T&amp;amp;C requirements */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Going live}}&lt;br /&gt;
&lt;br /&gt;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] in an online registration. Na paperwork or hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited onto this account, immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register on the live Barion server at https://secure.barion.com/Registration&lt;br /&gt;
&lt;br /&gt;
See alse:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, it is easy to mix up live and sandbox accounts! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. Only shops that are legal and comply with our [https://www.barion.com/en/legal/ Terms &amp;amp; Conditions] are allowed. Barion does not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, consult our [https://www.barion.com/en/merchants/ experts] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you will be asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you will be asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payment must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://www.barion.com/en/merchants/ experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
To go live, the following changes must be made in the payment solution. We advise to make these parameters, so you can easily switch between the sandbox and live servers.&lt;br /&gt;
*API endpoint URL must be changed to live (https://api.test.barion.com -&amp;gt; https://api.barion.com)&lt;br /&gt;
*Payment GUI redirect URL must be changes to live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay)&lt;br /&gt;
*POSKey must be changed to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here)&lt;br /&gt;
*Return URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*Callback URL must be changed, if you are using your own sandbox shop&lt;br /&gt;
*E-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;-s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if different in sandbox&lt;br /&gt;
*Certificates, if checking server certificates&lt;br /&gt;
*If using token payment, sandbox Tokens will not work in the live system&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data! |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your choosen price package. Please refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps placement. Please follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-card-payment-banner-2016-432x50px.png]]&lt;br /&gt;
&lt;br /&gt;
[[file:Barion-smart-payment-banners.zip]]&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff will check it and will only approve shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Please refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Please refer to [[Support|Getting support]] for more information.&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Current limitations of the live Barion system:&lt;br /&gt;
*Reservation and 3rd party payment only works with HUF currency&lt;br /&gt;
*Barion Mobile App only shows HUF transactions&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=These limitations are planned to be lifted in Q4 2017.|color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Birot</name></author>
	</entry>
</feed>