<?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=Alex</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=Alex"/>
	<link rel="alternate" type="text/html" href="https://docs.barion.com/Special:Contributions/Alex"/>
	<updated>2026-11-21T09:53:24Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://docs.barion.com/index.php?title=UserHistory-GetHistory-v3&amp;diff=4090</id>
		<title>UserHistory-GetHistory-v3</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=UserHistory-GetHistory-v3&amp;diff=4090"/>
		<updated>2023-07-31T14:00:38Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Output properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: transaction history}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=GET&lt;br /&gt;
|uri=/v3/UserHistory/GetHistory&lt;br /&gt;
}}&lt;br /&gt;
The &amp;lt;code&amp;gt;/v3/UserHistory/GetHistory&amp;lt;/code&amp;gt; API endpoint is used to query the transaction history from the Barion system for the authenticated wallet. The [[TransactionHistory-GetDetail-v3|/v3/TransactionHistory/GetDetail]] endpoint can be used to query the details of the history item.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=This API should not be used for reconciliation, use the [[Statement-Download-v2 | statement API]] instead.|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=The item type of history elements does not correlate with the type of transactions exported through GUI or downloaded with[[Statement-Download-v2 | statement API]].|color=#FF7A3D}}&lt;br /&gt;
== Authentication ==&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
== Input properties ==&lt;br /&gt;
The input properties should be defined in the query string.&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| LastVisibleItemId || Guid ||&lt;br /&gt;
* Optional&lt;br /&gt;
 || &lt;br /&gt;
The identifier of the oldest transaction. Only transactions before the defined transaction will be included in the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| LastRequestTime || DateTime || &lt;br /&gt;
* Optional&lt;br /&gt;
*Universal Time Coordinated (UTC)&lt;br /&gt;
|| &lt;br /&gt;
The exact time of the last request. Only transactions after the defined request time will be included in the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Limit || int || &lt;br /&gt;
* Optional&lt;br /&gt;
* If not defined the default value is 20&lt;br /&gt;
* If the defined value is greater than 20 the default value will be used&lt;br /&gt;
|| &lt;br /&gt;
The expected number of transactions in the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Currency || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Required length: 3 characters&lt;br /&gt;
* Must be supplied in ISO 4217 format&lt;br /&gt;
Accepted values: &lt;br /&gt;
{{CurrencyList}}&lt;br /&gt;
|| The currency of the transaction. If the currency is defined, then only transactions in the same currency will be included in the response.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
== Output properties ==&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Id || Guid || The identifier of the history item.&lt;br /&gt;
|-&lt;br /&gt;
| Type || [[HistoryItemType]] || The type of the history item.&lt;br /&gt;
|-&lt;br /&gt;
| HappenedAtUtc || DateTime || The exact time when the item happened.&lt;br /&gt;
|-&lt;br /&gt;
| ConcurrencyOrder || int || The order of the transaction when more than one transaction happened at the same time. When only one transaction happened at a given timestamp, this value can be ignored.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccount || [[UserHistoryParticipant]] || The user who initiated the transaction or from whom the money originated.&lt;br /&gt;
|-&lt;br /&gt;
| TargetAccount || [[UserHistoryParticipant]] || The user who will receive the amount of the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| Amount || decimal || The amount of the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| Currency || string || The 3-character ISO 4217 currency code of the payment.&lt;br /&gt;
|-&lt;br /&gt;
| Description || string || Description of the transaction. Max: 640 characters.&lt;br /&gt;
|-&lt;br /&gt;
| IsInProgress || bool || This flag indicates that the transaction is not in the final state.&lt;br /&gt;
|-&lt;br /&gt;
| BalanceChangeType || [[BalanceChangeType]] || Indicates the direction of change regarding the account&#039;s available balance.&amp;lt;br&amp;gt;&lt;br /&gt;
* &#039;&#039;&#039;NoChange&#039;&#039;&#039;: the account&#039;s balance did not change after the transaction&lt;br /&gt;
* &#039;&#039;&#039;Credit&#039;&#039;&#039;: the account&#039;s balance has increased after the transaction&lt;br /&gt;
* &#039;&#039;&#039;Debit&#039;&#039;&#039;: the account&#039;s balance has decreased after the transaction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=UserHistory-GetHistory-v3&amp;diff=4089</id>
		<title>UserHistory-GetHistory-v3</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=UserHistory-GetHistory-v3&amp;diff=4089"/>
		<updated>2023-07-31T13:57:00Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Output properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: transaction history}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=GET&lt;br /&gt;
|uri=/v3/UserHistory/GetHistory&lt;br /&gt;
}}&lt;br /&gt;
The &amp;lt;code&amp;gt;/v3/UserHistory/GetHistory&amp;lt;/code&amp;gt; API endpoint is used to query the transaction history from the Barion system for the authenticated wallet. The [[TransactionHistory-GetDetail-v3|/v3/TransactionHistory/GetDetail]] endpoint can be used to query the details of the history item.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=This API should not be used for reconciliation, use the [[Statement-Download-v2 | statement API]] instead.|color=#FF7A3D}}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=The item type of history elements does not correlate with the type of transactions exported through GUI or downloaded with[[Statement-Download-v2 | statement API]].|color=#FF7A3D}}&lt;br /&gt;
== Authentication ==&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
== Input properties ==&lt;br /&gt;
The input properties should be defined in the query string.&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| LastVisibleItemId || Guid ||&lt;br /&gt;
* Optional&lt;br /&gt;
 || &lt;br /&gt;
The identifier of the oldest transaction. Only transactions before the defined transaction will be included in the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| LastRequestTime || DateTime || &lt;br /&gt;
* Optional&lt;br /&gt;
*Universal Time Coordinated (UTC)&lt;br /&gt;
|| &lt;br /&gt;
The exact time of the last request. Only transactions after the defined request time will be included in the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Limit || int || &lt;br /&gt;
* Optional&lt;br /&gt;
* If not defined the default value is 20&lt;br /&gt;
* If the defined value is greater than 20 the default value will be used&lt;br /&gt;
|| &lt;br /&gt;
The expected number of transactions in the response.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Currency || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Required length: 3 characters&lt;br /&gt;
* Must be supplied in ISO 4217 format&lt;br /&gt;
Accepted values: &lt;br /&gt;
{{CurrencyList}}&lt;br /&gt;
|| The currency of the transaction. If the currency is defined, then only transactions in the same currency will be included in the response.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
== Output properties ==&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Id || Guid || The identifier of the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| Type || [[HistoryItemType]] || The type of the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| HappenedAtUtc || DateTime || The exact time when the transaction happened.&lt;br /&gt;
|-&lt;br /&gt;
| ConcurrencyOrder || int || The order of the transaction when more than one transaction happened at the same time. When only one transaction happened at a given timestamp, this value can be ignored.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccount || [[UserHistoryParticipant]] || The user who initiated the transaction or from whom the money originated.&lt;br /&gt;
|-&lt;br /&gt;
| TargetAccount || [[UserHistoryParticipant]] || The user who will receive the amount of the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| Amount || decimal || The amount of the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| Currency || string || The 3-character ISO 4217 currency code of the payment.&lt;br /&gt;
|-&lt;br /&gt;
| Description || string || Description of the transaction. Max: 640 characters.&lt;br /&gt;
|-&lt;br /&gt;
| IsInProgress || bool || This flag indicates that the transaction is not in the final state.&lt;br /&gt;
|-&lt;br /&gt;
| BalanceChangeType || [[BalanceChangeType]] || Indicates the direction of change regarding the account&#039;s available balance.&amp;lt;br&amp;gt;&lt;br /&gt;
* &#039;&#039;&#039;NoChange&#039;&#039;&#039;: the account&#039;s balance did not change after the transaction&lt;br /&gt;
* &#039;&#039;&#039;Credit&#039;&#039;&#039;: the account&#039;s balance has increased after the transaction&lt;br /&gt;
* &#039;&#039;&#039;Debit&#039;&#039;&#039;: the account&#039;s balance has decreased after the transaction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=4061</id>
		<title>Registration with pre-filled values</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=4061"/>
		<updated>2023-06-06T17:38:20Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Other query string parameters */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=Opening the Barion wallet registration page with pre-filled values=&lt;br /&gt;
There are certain situations and business models where the user is required to obtain a Barion wallet before they are able to pay for goods or services in the shop. Automatically registering a Barion wallet for a user by third parties is strictly prohibited by law. However, Barion aids the third party in a way so they can supply specific values to pre-fill the registration form, so the process can be completed faster by the user.&lt;br /&gt;
By using the following query string parameters, the third party can redirect the user to the Barion registration form so some fields are already filled for them.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; this is just a convinience feature! By modifying the URL the user can remove these values whenever they want.&lt;br /&gt;
&lt;br /&gt;
==Registration Type Query String Parameter==&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;mode&amp;quot; query string parameter is used to determine the type of registration being requested in the API. We distinguish two registration types: personal and business.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| mode&lt;br /&gt;
| string&lt;br /&gt;
| Indicates the registration type: &amp;lt;code&amp;gt;naturalperson&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;business&amp;lt;/code&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; To accommodate legacy integrations, we support two additional values for the &amp;quot;mode&amp;quot; query string parameter: &amp;quot;NaturalPerson&amp;quot; for personal registration and &amp;quot;Organization&amp;quot; for business registration.&lt;br /&gt;
&lt;br /&gt;
==Personal Wallet Registration Query String Parameters==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| m&lt;br /&gt;
| string&lt;br /&gt;
| The E-mail address of the user.&lt;br /&gt;
|-&lt;br /&gt;
| isEmailLocked&lt;br /&gt;
| boolean&lt;br /&gt;
| Indicates wether the E-mail address field is locked or editable - &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; means locked, &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; means editable.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=&amp;quot;powershell&amp;quot;&amp;gt;&lt;br /&gt;
https://secure.barion.com/Registration?mode=Personal&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Business Wallet Registration Query String Parameters==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| m&lt;br /&gt;
| string&lt;br /&gt;
| The E-mail address of the user.&lt;br /&gt;
|-&lt;br /&gt;
| isEmailLocked&lt;br /&gt;
| boolean&lt;br /&gt;
| Indicates wether the E-mail address field is locked or editable - &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; means locked, &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; means editable.&lt;br /&gt;
|-&lt;br /&gt;
| on&lt;br /&gt;
| string&lt;br /&gt;
| The name of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| onm&lt;br /&gt;
| bool&lt;br /&gt;
| Indicates if the name and short name of the organization match.&lt;br /&gt;
|-&lt;br /&gt;
| osn&lt;br /&gt;
| string&lt;br /&gt;
| Short name of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| oc&lt;br /&gt;
| string&lt;br /&gt;
| The 3-letter iso code of the headquarters address country  (eg. HUN for Hungary, CZE for Czechia).&lt;br /&gt;
|-&lt;br /&gt;
| ot&lt;br /&gt;
| string&lt;br /&gt;
| The city for the headquarters address.&lt;br /&gt;
|-&lt;br /&gt;
| opa&lt;br /&gt;
| string&lt;br /&gt;
| The postal/zip code for the headquarters address.&lt;br /&gt;
|-&lt;br /&gt;
| os&lt;br /&gt;
| string&lt;br /&gt;
| The street name for the headquarters address.&lt;br /&gt;
|-&lt;br /&gt;
| ohn&lt;br /&gt;
| string&lt;br /&gt;
| The house number for the headquarters address.&lt;br /&gt;
|-&lt;br /&gt;
| oam&lt;br /&gt;
| bool&lt;br /&gt;
| Indicates, whether the headquarters and the postal address match.&lt;br /&gt;
|-&lt;br /&gt;
| ocat&lt;br /&gt;
| string&lt;br /&gt;
| The category number of the organization (so called TEÁOR in hungarian). Only the numerical value (eg: &amp;lt;code&amp;gt;0520&amp;lt;/code&amp;gt;) is required.&lt;br /&gt;
|-&lt;br /&gt;
| orn&lt;br /&gt;
| string&lt;br /&gt;
| The registration number of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| otn&lt;br /&gt;
| string&lt;br /&gt;
| The tax number of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| pc&lt;br /&gt;
| string&lt;br /&gt;
| The postal country of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| ppa&lt;br /&gt;
| string&lt;br /&gt;
| The postal zip code of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| pt&lt;br /&gt;
| string&lt;br /&gt;
| The postal city of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| phn&lt;br /&gt;
| string&lt;br /&gt;
| The postal house number of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| rfn&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative&#039;s first name.&lt;br /&gt;
|-&lt;br /&gt;
| rln&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative&#039;s last name.&lt;br /&gt;
|-&lt;br /&gt;
| rmfn&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative mother&#039;s first name.&lt;br /&gt;
|-&lt;br /&gt;
| rmln&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative mother&#039;s last name.&lt;br /&gt;
|-&lt;br /&gt;
| rn&lt;br /&gt;
| string&lt;br /&gt;
| The 3-letter country code of the organization representative&#039;s nationality (eg. HUN for Hungary, CZE for Czechia).&lt;br /&gt;
|-&lt;br /&gt;
| rbp&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative&#039;s birth place.&lt;br /&gt;
|-&lt;br /&gt;
| rbd&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative&#039;s birth date (eg: 1990-01-01).&lt;br /&gt;
|-&lt;br /&gt;
| rbp&lt;br /&gt;
| string&lt;br /&gt;
| The organization representative&#039;s position (eg. CEO).&lt;br /&gt;
|-&lt;br /&gt;
| rc&lt;br /&gt;
| string&lt;br /&gt;
| The 3-letter iso country code of the organization representative&#039;s address (eg. HUN for Hungary, CZE for Czechia).&lt;br /&gt;
|-&lt;br /&gt;
| rpa&lt;br /&gt;
| string&lt;br /&gt;
| The zip code of the organization representative&#039;s address.&lt;br /&gt;
|-&lt;br /&gt;
| rt&lt;br /&gt;
| string&lt;br /&gt;
| The city of the organization representative&#039;s address.&lt;br /&gt;
|-&lt;br /&gt;
| rs&lt;br /&gt;
| string&lt;br /&gt;
| The street of the organization representative&#039;s address.&lt;br /&gt;
|-&lt;br /&gt;
| rhn&lt;br /&gt;
| string&lt;br /&gt;
| The house number of the organization representative&#039;s address.&lt;br /&gt;
|-&lt;br /&gt;
| rpcc&lt;br /&gt;
| string&lt;br /&gt;
| The prefix country code of the organization representative&#039;s phone number (eg. 36 for Hungary, 420 for Czechia).&lt;br /&gt;
|-&lt;br /&gt;
| rpn&lt;br /&gt;
| string&lt;br /&gt;
| The phone number of the organization representative without the country code (eg. 205555555 for a valid hungarian phone number).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=&amp;quot;powershell&amp;quot;&amp;gt;&lt;br /&gt;
https://secure.barion.com/Registration?mode=Business&amp;amp;m=user@example.com&amp;amp;on=Testdata+Company+Ltd&amp;amp;opa=98332&amp;amp;ot=San+José&amp;amp;os=Rockwood+Creek&amp;amp;ohn=32&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Other query string parameters==&lt;br /&gt;
These extra parameters can be used on both the individual and the organization registration page.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| r&lt;br /&gt;
| string&lt;br /&gt;
| The topup code of the referring user, if applicable.&lt;br /&gt;
|-&lt;br /&gt;
| url&lt;br /&gt;
| string&lt;br /&gt;
| The URL where the user should be redirected upon successful registration. The e-mail address entered at the registration is appended to the URL as a query string parameter.&lt;br /&gt;
&#039;&#039;&#039;Warning:&#039;&#039;&#039; this feature is under development and is subject to change without notice!&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Individual registration with referrer and redirect URL:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;powershell&amp;quot;&amp;gt;&lt;br /&gt;
https://secure.barion.com/Registration?mode=Personal&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&amp;amp;r=123456789&amp;amp;url=https://www.example.com/successfulregistration&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=4021</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=4021"/>
		<updated>2023-05-11T12:28:07Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
For authentication in these endpoints, see [[Barion Shop Authentication]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
For authentication in these endpoints, see [[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[UserHistory-GetHistory-v3|/GetHistory]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Always prefix endpoints with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about the results of Barion Smart Gateway payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=4020</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=4020"/>
		<updated>2023-05-11T12:27:38Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
For authentication in these endpoints, see [[Barion Shop Authentication]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
For authentication in these endpoints, see [[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[UserHistory-GetHistory-v3/GetHistory]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Always prefix endpoints with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about the results of Barion Smart Gateway payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=3987</id>
		<title>Pos-Get-v1</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=3987"/>
		<updated>2023-05-02T19:15:44Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Request the current state of a POS}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=GET&lt;br /&gt;
|uri=/v1/Pos?PublicKey&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;Pos?PublicKey&amp;lt;/code&amp;gt; API endpoint to query the details and current state of a point of sale (POS).&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Pos-Create-v1|Creating a POS 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;v1&amp;lt;/span&amp;gt; This API endpoint is available in &#039;&#039;&#039;API v1&#039;&#039;&#039; only.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Query string parameters for getting a shop&#039;s state ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| PublicKey &lt;br /&gt;
| string&lt;br /&gt;
| The public key of the POS.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Output properties ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| Name&lt;br /&gt;
| string&lt;br /&gt;
| The unique name of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| PublicKey &lt;br /&gt;
| Guid &lt;br /&gt;
| The public key of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| SecretKey &lt;br /&gt;
| Guid&lt;br /&gt;
| The secret POS key of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| Status &lt;br /&gt;
| [[ShopStatus]] &lt;br /&gt;
| The status of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| IsOpen &lt;br /&gt;
| bool &lt;br /&gt;
| Information on whether the shop is open.&lt;br /&gt;
|-&lt;br /&gt;
| Description&lt;br /&gt;
| string &lt;br /&gt;
| The short description of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| Logo &lt;br /&gt;
| string&lt;br /&gt;
| The logo of the shop, is sent as a URL.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact &lt;br /&gt;
| [[BusinessContact]]&lt;br /&gt;
| The business contact details of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| TechnicalContact &lt;br /&gt;
| [[TechnicalContact]]&lt;br /&gt;
| The technical contact details of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact &lt;br /&gt;
| [[CustomerServiceContact]]&lt;br /&gt;
| The contact details of your customer service desk, where your customers can contact you.&lt;br /&gt;
|-&lt;br /&gt;
| CallBackUrl  &lt;br /&gt;
| string &lt;br /&gt;
| The URL where the Barion system sends a request whenever there is a change in the state of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| ReferenceId &lt;br /&gt;
| string &lt;br /&gt;
| The top-up code of the wallet. Used to distinguish shops arriving through different channels.&lt;br /&gt;
|-&lt;br /&gt;
| CustomTemplate &lt;br /&gt;
| string &lt;br /&gt;
| The custom template you used to modify the displayed data.&lt;br /&gt;
|-&lt;br /&gt;
| CustomCSS &lt;br /&gt;
| string &lt;br /&gt;
| The custom CSS you used to modify the gateway design.&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=FundingInformation&amp;diff=3887</id>
		<title>FundingInformation</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=FundingInformation&amp;diff=3887"/>
		<updated>2023-04-20T11:25:39Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Funding information structure}}&lt;br /&gt;
&lt;br /&gt;
This structure represents the details about the funding source of the last payment attempt. At the moment this is only used when the funding source is a bank card.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This structure is used by the following API endpoints:&lt;br /&gt;
* [[Payment-GetPaymentState-v2]]&lt;br /&gt;
&lt;br /&gt;
= Property list =&lt;br /&gt;
&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| BankCard || [[BankCard]] || The bank card used to complete the payment.&lt;br /&gt;
|-&lt;br /&gt;
| AuthorizationCode || string || The authorization code received by the card processing system when executing the payment.&lt;br /&gt;
|-&lt;br /&gt;
| ProcessResult || string || The result of the last card payment attempt. Possible values:&lt;br /&gt;
* &amp;lt;b&amp;gt;Successful&amp;lt;/b&amp;gt;: the card transaction was successful&lt;br /&gt;
* &amp;lt;b&amp;gt;ProblemWithCard&amp;lt;/b&amp;gt;: the card transaction was unsuccessful: card number, CVC or/and expiry is wrong. The card may have been stolen, deleted, disabled or disabled for online transactions.&lt;br /&gt;
* &amp;lt;b&amp;gt;LowFunds&amp;lt;/b&amp;gt;: the card transaction was unsuccessful due to insufficient funds or limits were reached&lt;br /&gt;
* &amp;lt;b&amp;gt;LostOrStolenCard&amp;lt;/b&amp;gt;: the credit card has been reported lost or stolen&lt;br /&gt;
* &amp;lt;b&amp;gt;Declined&amp;lt;/b&amp;gt;:  the payment card was declined by the acquirer&lt;br /&gt;
* &amp;lt;b&amp;gt;FraudulentTransaction&amp;lt;/b&amp;gt;: potentially fraudulent transaction, the monitoring system declined the transaction&lt;br /&gt;
* &amp;lt;b&amp;gt;CardSystemError&amp;lt;/b&amp;gt;: the card transaction failed due to the card system&lt;br /&gt;
* &amp;lt;b&amp;gt;SoftDeclined&amp;lt;/b&amp;gt;: the payment card did not support SCA at the time of the transaction&lt;br /&gt;
* &amp;lt;b&amp;gt;FailedDuringAuthentication&amp;lt;/b&amp;gt;: there was an  error during the SCA process thus authentication failed. This may not be returned if ChallengePreference was set to &amp;quot;NoChallengeNeeded&amp;quot;&lt;br /&gt;
* &amp;lt;b&amp;gt;CardNotSupported&amp;lt;/b&amp;gt;: the payment card is not supported at the time of the transaction - NOT AVAILABLE&lt;br /&gt;
* &amp;lt;b&amp;gt;SystemError&amp;lt;/b&amp;gt;: system error, in this case we try to refund the transaction amount if we have enough information to initiate it - NOT AVAILABLE&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Download&amp;diff=3886</id>
		<title>Download</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Download&amp;diff=3886"/>
		<updated>2023-04-17T20:05:06Z</updated>

		<summary type="html">&lt;p&gt;Alex: &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;
| https://github.com/tlsoft-ltd/Magento1Barion; https://github.com/laccas/Magento2Barion/&lt;br /&gt;
| Free Magento plugin&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.&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://store.pws-server.net/downloads/prestashop-modules/barion-online-credit-card-payment/&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>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=3885</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=3885"/>
		<updated>2023-04-17T20:01:47Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 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:Barion-smart-gateway-en.png|right|600px]]&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;
*[[3DSecure|Strong customer authentication with 3DSecure]]&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;
==3DSecure/PSD2 SCA==&lt;br /&gt;
*[[3DSecure|3DSecure General Information]]&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&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 websites]]&lt;br /&gt;
*[[App2App_payment|Barion Smart Gateway integraton for mobile applications]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
*[[Delayed_Capture|Delayed Capture: reservation on payment card]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment_3D_Secure|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|Barion Bridge - Payments for platforms]]&lt;br /&gt;
*[[Apple_Pay|Apple Pay]]&lt;br /&gt;
*[[Google_Pay|Google Pay]]&lt;br /&gt;
*[[Bank_Transfer_Payment|Payment with bank transfer]]&lt;br /&gt;
&lt;br /&gt;
==API docs==&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
&lt;br /&gt;
==Barion Pixel==&lt;br /&gt;
{|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot; width=&amp;quot;50%&amp;quot;|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
|[[Getting started with the Barion Pixel]] &lt;br /&gt;
|[[Áttekintés a Barion Pixel működéséről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Base Barion Pixel]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Full Barion Pixel]]&lt;br /&gt;
|[[A Teljes (Full) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Barion Pixel Consent Management requirements]]&lt;br /&gt;
| [[Barion Pixel hozzájáruláskezelési követelmények]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Barion Pixel API reference]]&lt;br /&gt;
|[[Barion Pixel API referencia]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Frequently Asked Questions about the Barion Pixel]]&lt;br /&gt;
|[[Gyakran Ismételt Kérdések a Barion Pixelről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Barion Pixel base code through the Google Tag Manager]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja a Google Tag Managerben]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Smar_Documentation|Implementing the Barion Full Pixel code in Shopify webshop]]&lt;br /&gt;
|[[Smar_Dokumentacio|A Teljes (Full) Barion Pixel implementációja Shopify webáruházban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-woocommerce-webshops|Implementing Base and Full Barion Pixel in woocommerce webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Woocommerce e-kereskedelmi platformon]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-unas-webshops|Implementing Base and Full Barion Pixel in UNAS webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja UNAS webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-shoprenter-webshops|Implementing Base and Full Barion Pixel in shoprenter webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Shoprenter webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|[[alap-es-full-barion-pixel-implementacio-shopstart-webaruhazakban|Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Shopstart webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Viltor webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Barion_releases|Barion releases]]&lt;br /&gt;
*[[Barion_for_Shopify|Barion for Shopify]]&lt;br /&gt;
*[[Troubleshooting|Troubleshooting - list of common pitfalls]]&lt;br /&gt;
*[[Localisation|Localization and list of available languages]]&lt;br /&gt;
*[https://www.barion.com/en/integrations-and-plugins/ Integrations and Plugins]&lt;br /&gt;
*[[Legal_accounting|Legal and accounting information]]&lt;br /&gt;
&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
*[[Dataprocessors|Barion data processor partners]]&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>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3884</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=3884"/>
		<updated>2023-04-17T19:57:33Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* The Barion API */&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;
&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. For security and compatibility reason the GUID is used without hyphens for most of our API.&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;
&lt;br /&gt;
For every request sent to the Barion API you have to authenticate yourself. Depending on the type of endpoint you should use a different type of authentication.&lt;br /&gt;
&lt;br /&gt;
==== Shop-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
Shop-level endpoints can be authenticated using the shop&#039;s unique &amp;lt;tt&amp;gt;POSKey&amp;lt;/tt&amp;gt;. For more details on using and obtaining the POS key, see the [[Barion Shop Authentication]] page.&lt;br /&gt;
&lt;br /&gt;
==== Wallet-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
You can authenticate yourself to endpoints requiring wallet-level authentication via an API key called a &amp;lt;tt&amp;gt;Wallet key&amp;lt;/tt&amp;gt;. For more information on using this API key, see [[Barion Wallet Authentication]].&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;
| PaymentId ||  If the error is related to a business process that involves a given payment, the public identifier of the payment is supplied here. This property is not present on all errors.&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;
&lt;br /&gt;
The following example shows an error case where the shop does not have an account with the currency it specified when trying to create a payment.&lt;br /&gt;
This is a validation error, so the payment identifier is not applicable.&lt;br /&gt;
&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;NotExistingCurrency&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;Payment is not supported&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;Payment is not supported. The POS doesn’t have an account that supports EUR!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&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;
The following example shows a case where after several successful token charges, the customer deleted their payment card from the Barion system, so the subsequent attempt failed.&lt;br /&gt;
&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;OriginalPaymentCardDoesNotExist&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The original payment card does not exist!&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The payment card that was used for the original payment with recurrence ID &#039;TEST-01&#039; no longer exists in the system!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&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>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=3883</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=3883"/>
		<updated>2023-04-17T19:53:34Z</updated>

		<summary type="html">&lt;p&gt;Alex: &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/general-terms/ Terms &amp;amp; Conditions] in online registration. No 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 an account 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/general-terms/ 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, contact us through chat on [https://www.barion.com/ Barion.com] 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://secure.barion.com/Remark 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 making 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 changed 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 chosen 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;
An example for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Please find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
for Hungary and other countries at:  https://download.barion.com/barion/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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=3882</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=3882"/>
		<updated>2023-04-17T19:47:53Z</updated>

		<summary type="html">&lt;p&gt;Alex: &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 online registration. No 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 an account 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 making 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 changed 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 chosen 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;
An example for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Please find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
for Hungary and other countries at:  https://download.barion.com/barion/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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=3881</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=3881"/>
		<updated>2023-04-17T19:46:43Z</updated>

		<summary type="html">&lt;p&gt;Alex: &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 online registration. No 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 making 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 changed 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 chosen 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;
An example for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Please find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
for Hungary and other countries at:  https://download.barion.com/barion/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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=3880</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=3880"/>
		<updated>2023-04-17T19:43:18Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Logo placement */&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 online registration. No 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 making 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 changed 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 chosen 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;
An example for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Please find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
for Hungary and other countries at:  https://download.barion.com/barion/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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=3879</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=3879"/>
		<updated>2023-04-17T19:42:56Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Logo placement */&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 online registration. No 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 making 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 changed 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 chosen 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;
An examaple for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Please find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
for Hungary and other countries at:  https://download.barion.com/barion/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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=File:Barion-card-strip-intl_large.png&amp;diff=3878</id>
		<title>File:Barion-card-strip-intl large.png</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=File:Barion-card-strip-intl_large.png&amp;diff=3878"/>
		<updated>2023-04-17T19:37:51Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=BalanceChangeType&amp;diff=3874</id>
		<title>BalanceChangeType</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=BalanceChangeType&amp;diff=3874"/>
		<updated>2023-03-28T12:13:58Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Balance change type type enumeration}}&lt;br /&gt;
&lt;br /&gt;
This enum indicates the direction of change regarding the account&#039;s available balance. It is used in context of a certain transaction.&lt;br /&gt;
&lt;br /&gt;
= Included in =&lt;br /&gt;
&lt;br /&gt;
Balance change types are used in the following structures:&lt;br /&gt;
* [[UserHistory-GetHistory-v3]]&lt;br /&gt;
&lt;br /&gt;
= Enum list =&lt;br /&gt;
&lt;br /&gt;
{{api_enum_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| NoChange || 1 || The account&#039;s balance did not change (e.g. the user paid with a saved card)&lt;br /&gt;
|-&lt;br /&gt;
| Credit || 2 || The account&#039;s balance has been increased (e.g. money arrived to the account by wire transfer)&lt;br /&gt;
|-&lt;br /&gt;
| Debit || 3 || The account&#039;s balance has been decreased (e.g. money was transfered from the account by wire transfer)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Google_Pay&amp;diff=3778</id>
		<title>Google Pay</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Google_Pay&amp;diff=3778"/>
		<updated>2023-01-20T09:28:01Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Google Pay integration}}&lt;br /&gt;
__NOTOC__&lt;br /&gt;
Google Pay™ is a payment option for the customer. Google securely stores the customer&#039;s card information and hands it over to the merchant for processing. The process ensures that the card information stays secure and encrypted, the merchant does not know the details of the card.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=We currently only support Google Pay for the web, Android support is coming soon.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
= Payment Process =&lt;br /&gt;
This picture describes the payment process:&lt;br /&gt;
&lt;br /&gt;
[[File:Googlepay.png]]&lt;br /&gt;
&lt;br /&gt;
# The customer clicks the Google Pay button. A window will pop up where the customer can choose a previously saved card to charge or even provide a new one. &lt;br /&gt;
# The JS code receives the encrypted card information.&lt;br /&gt;
# The JS code send the encrypted information to the merchant&#039;s server side&lt;br /&gt;
# The merchant&#039;s server side gathers all the information to start a payment and calls the Barion API&lt;br /&gt;
# The Barion API handles the request, decrypts the packages and charges the card. The result of the payment is sent back to the caller.&lt;br /&gt;
# The merchant&#039;s server communicates the result to the client side and the webshop renders the result of the payment.&lt;br /&gt;
&lt;br /&gt;
= Integration =&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=To integrate this feature you have to develop the integration yourself! You need to understand Javascript code and it is also required to modify your webshop&#039;s server code!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
These are the steps that you have to complete to use Google Pay on your website:&lt;br /&gt;
&lt;br /&gt;
# [[#Creating_a_shop_in_Barion | Register a wallet in Barion and create a shop]]&lt;br /&gt;
# [[#Implementing_the_Google_Pay_button|Implement the Google Pay button on your webshop&#039;s client side]]&lt;br /&gt;
# [[#Implementing_the_Barion_API_call|Implement the Barion API call on your webshop&#039;s server side]]&lt;br /&gt;
&lt;br /&gt;
== Creating a shop in Barion ==&lt;br /&gt;
&lt;br /&gt;
To be able to use Barion as a Google Pay token processor you have to register a wallet and open a shop for your webshop.&lt;br /&gt;
* You must [[Creating_an_account|register a Barion wallet]] at the Barion website or in the Sandbox environment. Learn more about the Sandbox environment [[Sandbox|here]].&lt;br /&gt;
* For this wallet you have to [[Creating_a_shop|create a shop]] which should be approved by Barion.&lt;br /&gt;
* For every currency you plan to conduct payments in you have to make sure there is an account created in your Barion wallet. This means that if you plan to have USD payments then there should be an USD account created in your wallet.&lt;br /&gt;
* To make sure every corner case scenario works for your webshop it is best to topup that account with a small amount (approx. 5-10EUR or your choice of currency around the same value).&lt;br /&gt;
&lt;br /&gt;
== Implementing the Google Pay button ==&lt;br /&gt;
&lt;br /&gt;
First read through the: &lt;br /&gt;
# [https://developers.google.com/pay/api/web/overview Introduction] &lt;br /&gt;
# [https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist Integration checklist] &lt;br /&gt;
# [https://developers.google.com/pay/api/web/guides/brand-guidelines Brand guidelines] &lt;br /&gt;
&lt;br /&gt;
in Google&#039;s documentation to see what you need to do to accept payments via Google Pay. If your system is ready, follow [https://developers.google.com/pay/api/web/guides/tutorial this Google tutorial] to create the JS code that renders the Google Pay button.&lt;br /&gt;
&lt;br /&gt;
To identify the request towards Google you have to provide two IDs:&lt;br /&gt;
* &#039;&#039;&#039;gateway id&#039;&#039;&#039;, the ID that identifies the gateway you are using to process the charges. This is &amp;lt;code&amp;gt;barion&amp;lt;/code&amp;gt; &lt;br /&gt;
* &#039;&#039;&#039;the gateway merchant id&#039;&#039;&#039;, the ID that identifies your webshop. This can be copied from the detail page of your shop (in Barion) &amp;lt;br/&amp;gt; [[File:Merchantid.png]]&lt;br /&gt;
&lt;br /&gt;
These IDs must be set in your JS code, like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot; line=&#039;line&#039;&amp;gt;&lt;br /&gt;
const tokenizationSpecification = {&lt;br /&gt;
  type: &#039;PAYMENT_GATEWAY&#039;,&lt;br /&gt;
  parameters: {&lt;br /&gt;
    &#039;gateway&#039;: &#039;barion&#039;,&lt;br /&gt;
    &#039;gatewayMerchantId&#039;: &#039;PUT HERE YOUR SHOPS MERCHANT ID FROM BARION&#039;&lt;br /&gt;
  }&lt;br /&gt;
};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
We support four card types: American Express, Discover, MasterCard and Visa. You have to specify this in your JS code:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot; line=&#039;line&#039;&amp;gt;&lt;br /&gt;
const allowedCardNetworks = [&amp;quot;AMEX&amp;quot;, &amp;quot;DISCOVER&amp;quot;, &amp;quot;MASTERCARD&amp;quot;, &amp;quot;VISA&amp;quot;];&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Currently, we only support cards that already been authenticated with 3DS or via ID&amp;amp;V as network tokens, so you have to specify this as well.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot; line=&#039;line&#039;&amp;gt;&lt;br /&gt;
const allowedCardAuthMethods = [&amp;quot;CRYPTOGRAM_3DS&amp;quot;, &amp;quot;PAN_ONLY&amp;quot;];&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The system needs the billing address, for this the following parameterization must be used:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot; line=&#039;line&#039;&amp;gt;&lt;br /&gt;
parameters: {&lt;br /&gt;
     billingAddressRequired: true,&lt;br /&gt;
     billingAddressParameters: {&lt;br /&gt;
         format: &amp;quot;FULL&amp;quot;&lt;br /&gt;
     }&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
Please use the FULL value to specify the format. See [https://developers.google.com/pay/api/web/reference/request-objects#BillingAddressParameters BillingAddressParameters] for more information. &lt;br /&gt;
&lt;br /&gt;
To be able to get the e-mail address of the customer, please specify the &amp;lt;code&amp;gt;&amp;quot;emailRequired&amp;quot;: true&amp;lt;/code&amp;gt; in the [https://developers.google.com/pay/api/web/reference/request-objects#PaymentDataRequest PaymentDataRequest]. This will the Google API to send back the e-mail address of the Google wallet in the [https://developers.google.com/pay/api/web/reference/response-objects#PaymentData PaymentData] object.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Make sure to comply with the [https://developers.google.com/pay/api/web/guides/brand-guidelines Google Brand Guidelines] when you place the pay button on your webshop.&lt;br /&gt;
&lt;br /&gt;
=== Performing 3DS authentication ===&lt;br /&gt;
&lt;br /&gt;
Barion is performing 3DS authentication on all transaction. In case of Google Pay, merchants need to implement our &lt;br /&gt;
[https://docs.barion.com/Token_payment_3D_Secure#Off-site_3DS_v2_authentication Off-site 3DS authentication] process by using the described css and javascript files in the code of their site.&lt;br /&gt;
&lt;br /&gt;
== Implementing the Barion API call ==&lt;br /&gt;
&lt;br /&gt;
To be able to pass on the encrypted token to Barion you have to implement a Barion API call. For the technical communication guide please read the this: [[Calling_the_API|Calling the API]].&lt;br /&gt;
&lt;br /&gt;
The endpoint you have to implement is the [[Payment-StartPaymentWithGoogleToken-v3|/v3/Payment/StartPaymentWithGoogleToken]]. The data that you have to provide here has three key elements:&lt;br /&gt;
* all the information about the goods you want to sell&lt;br /&gt;
* the e-mail address of the customer (provided by Google)&lt;br /&gt;
* the Google Pay token (provided by Google)&lt;br /&gt;
&lt;br /&gt;
=== Possible error responses ===&lt;br /&gt;
&lt;br /&gt;
The endpoint can result in any error described [https://docs.barion.com/Responsive_web_payment#Processing_the_error_response at the web payment scenario]. Besides those these are the specific error messages for this scenario&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidGoogleToken || The token provided was invalid. Either &lt;br /&gt;
* malformed &lt;br /&gt;
* or contained invalid structure&lt;br /&gt;
|-&lt;br /&gt;
| InvalidGoogleMessage || The content of the token was invalid. Either &lt;br /&gt;
* contained data that was not recognized&lt;br /&gt;
* or the message was expired&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_Wallet_Authentication&amp;diff=3757</id>
		<title>Barion Wallet Authentication</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_Wallet_Authentication&amp;diff=3757"/>
		<updated>2022-11-22T13:43:23Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* What is wallet authentication? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= What is wallet authentication? =&lt;br /&gt;
&lt;br /&gt;
Some API endpoints can only be reached using wallet-level authentication (for a full list see [[List_of_API_endpoints|List of Barion API endpoints]]). This is achieved through the usage of API keys tied to each wallet.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=This feature is only available to business accounts.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
= Using API keys =&lt;br /&gt;
&lt;br /&gt;
To use an endpoint which requires wallet-level authentication, simply send your API key in the &amp;lt;code&amp;gt;x-api-key&amp;lt;/code&amp;gt; header of your request.&lt;br /&gt;
&lt;br /&gt;
You can directly use values copied from the secure site&#039;s access page.&lt;br /&gt;
&lt;br /&gt;
= Managing API keys =&lt;br /&gt;
&lt;br /&gt;
The management interface of wallet-level API keys can be found on the [https://secure.barion.com Barion secure site] under the &amp;lt;tt&amp;gt;Wallet -&amp;gt; Access&amp;lt;/tt&amp;gt; menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Wallet_key_management_page.png|The wallet key management page with only one active API key]]&lt;br /&gt;
&lt;br /&gt;
You can view your currently active API key or place it onto the clipboard via clicking the icons on the right side of the screen.&lt;br /&gt;
&lt;br /&gt;
== Rotating keys ==&lt;br /&gt;
&lt;br /&gt;
In case a key&#039;s secrecy is compromised it is important to change it to avoid unauthorized parties from using Barion in your name.&lt;br /&gt;
&lt;br /&gt;
You can add a new API key to your wallet by clicking the &amp;quot;rotate&amp;quot; icon to the right of the key. &amp;lt;strong&amp;gt;This does not deactivate the old API key&amp;lt;/strong&amp;gt;, it just adds a new one. After changing all usages of the old key to the new one, the old one can be safely deleted.&lt;br /&gt;
&lt;br /&gt;
[[File:Wallet_key_management_page_-_under_rotation.png|The wallet key management page with two active API keys]]&lt;br /&gt;
&lt;br /&gt;
As there can only be at most two active API keys tied to a wallet at all times, it is not possible to rotate one of two active keys. You&#039;ll have to delete one of them to start rotating the other one.&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_Wallet_Authentication&amp;diff=3756</id>
		<title>Barion Wallet Authentication</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_Wallet_Authentication&amp;diff=3756"/>
		<updated>2022-11-22T13:37:03Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Using API keys */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= What is wallet authentication? =&lt;br /&gt;
&lt;br /&gt;
Some API endpoints can only be reached using wallet-level authentication (for a full list see [[List_of_API_endpoints|List of Barion API endpoints]]). This is achieved through the usage of API keys tied to each wallet.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=This feature is only available to organizations registered to Barion. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
= Using API keys =&lt;br /&gt;
&lt;br /&gt;
To use an endpoint which requires wallet-level authentication, simply send your API key in the &amp;lt;code&amp;gt;x-api-key&amp;lt;/code&amp;gt; header of your request.&lt;br /&gt;
&lt;br /&gt;
You can directly use values copied from the secure site&#039;s access page.&lt;br /&gt;
&lt;br /&gt;
= Managing API keys =&lt;br /&gt;
&lt;br /&gt;
The management interface of wallet-level API keys can be found on the [https://secure.barion.com Barion secure site] under the &amp;lt;tt&amp;gt;Wallet -&amp;gt; Access&amp;lt;/tt&amp;gt; menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Wallet_key_management_page.png|The wallet key management page with only one active API key]]&lt;br /&gt;
&lt;br /&gt;
You can view your currently active API key or place it onto the clipboard via clicking the icons on the right side of the screen.&lt;br /&gt;
&lt;br /&gt;
== Rotating keys ==&lt;br /&gt;
&lt;br /&gt;
In case a key&#039;s secrecy is compromised it is important to change it to avoid unauthorized parties from using Barion in your name.&lt;br /&gt;
&lt;br /&gt;
You can add a new API key to your wallet by clicking the &amp;quot;rotate&amp;quot; icon to the right of the key. &amp;lt;strong&amp;gt;This does not deactivate the old API key&amp;lt;/strong&amp;gt;, it just adds a new one. After changing all usages of the old key to the new one, the old one can be safely deleted.&lt;br /&gt;
&lt;br /&gt;
[[File:Wallet_key_management_page_-_under_rotation.png|The wallet key management page with two active API keys]]&lt;br /&gt;
&lt;br /&gt;
As there can only be at most two active API keys tied to a wallet at all times, it is not possible to rotate one of two active keys. You&#039;ll have to delete one of them to start rotating the other one.&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=TopUpInfo&amp;diff=3754</id>
		<title>TopUpInfo</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=TopUpInfo&amp;diff=3754"/>
		<updated>2022-11-21T16:23:48Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=TopUpInfo structure}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;TopUpInfo&#039;&#039;&#039; structure contains information about ow to topup an account.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This structure is used by the following API endpoints:&lt;br /&gt;
* [[Accounts-Get-v2|/Accounts]]&lt;br /&gt;
&lt;br /&gt;
= Properties =&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| DomesticCountry || string || Two letter country code || The code of the country which counts as domestic for the currency of the account&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| FromDomesticCountry || [[BankAccountInfo]] || || Information about the bank account to use for the topup from the domestic country&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| FromNonDomesticCountry || [[BankAccountInfo]] || || Information about the bank account to use for the topup from any othe than the domestic country&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Balance&amp;diff=3641</id>
		<title>Balance</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Balance&amp;diff=3641"/>
		<updated>2022-11-04T11:20:14Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Balance structure}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Balance&#039;&#039;&#039; structure indicates the balance of a selected account in a Barion wallet.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This structure is used by the following API endpoints:&lt;br /&gt;
* [[Accounts-Get-v2|/Accounts]]&lt;br /&gt;
&lt;br /&gt;
= Properties =&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Available || decimal || &lt;br /&gt;
* greater than or equal to zero&lt;br /&gt;
|| The currently available amount in the account, in the account&#039;s currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Blocked || decimal || &lt;br /&gt;
* greater than or equal to zero&lt;br /&gt;
|| The currently blocked amount in the account, in the account&#039;s currency.&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Account&amp;diff=3640</id>
		<title>Account</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Account&amp;diff=3640"/>
		<updated>2022-11-04T11:19:45Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Account structure}}&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Account&#039;&#039;&#039; structure represents an account in a Barion wallet.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This structure is used by the following API endpoints:&lt;br /&gt;
* [[Accounts-Get-v2|/Accounts]]&lt;br /&gt;
&lt;br /&gt;
= Properties =&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| AccountId || Guid || &lt;br /&gt;
|| The unique identifier of the account&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Balance || [[Balance]] || &lt;br /&gt;
|| The current balance of the account&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Currency || string || &lt;br /&gt;
|| The currency of the account in 3-letter ISO country code format&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Accounts-Get-v2&amp;diff=3639</id>
		<title>Accounts-Get-v2</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Accounts-Get-v2&amp;diff=3639"/>
		<updated>2022-11-04T11:16:38Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: Get existing accounts of the user}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=GET&lt;br /&gt;
|uri=/v2/Accounts&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;/accounts&amp;lt;/code&amp;gt; API endpoint is used to query the existing accounts of the calling user.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
* API: [[Transfer-Email-v2 | /Transfer/Email]]&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;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| UserName || string || &lt;br /&gt;
* Required&lt;br /&gt;
|| Your e-mail address in the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Password || string || &lt;br /&gt;
* Required&lt;br /&gt;
|| Your password in the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&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;
| Accounts || [[Account]][] || The list of accounts in the user&#039;s Barion wallet&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3638</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3638"/>
		<updated>2022-11-04T11:15:38Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Endpoints must be prefixed with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about the results of Barion Smart Gateway payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Withdraw-BankTransfer-v3&amp;diff=3629</id>
		<title>Withdraw-BankTransfer-v3</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Withdraw-BankTransfer-v3&amp;diff=3629"/>
		<updated>2022-10-28T11:10:42Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: Initiate a bank transfer}}&lt;br /&gt;
&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v3/Withdraw/BankTransfer&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;/withdraw/banktransfer&amp;lt;/code&amp;gt; API endpoint is used to send money out of the Barion Wallet via bank (wire) transfer.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account 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;v3&amp;lt;/span&amp;gt; This API endpoint is available in &#039;&#039;&#039;API v3&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
Barion users are authenticated either with username/password provided in the querystring or with basic authentication. You can find more information about basic authentication [[Basic_authentication|here]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UserName || string || &lt;br /&gt;
* Required&lt;br /&gt;
|| Your e-mail address in the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Password || string || &lt;br /&gt;
* Required&lt;br /&gt;
|| Your password in the Barion system.&lt;br /&gt;
&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 bank transfer. &lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Barion does not do currency rate conversion. The caller must have an active account with the selected currency, and must ensure that the target bank accepts the selected currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Amount || decimal || &lt;br /&gt;
* Required&lt;br /&gt;
* Must be greater than zero&lt;br /&gt;
|| The total amount to withdraw, excluding fees.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Comment|| string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 90 characters&lt;br /&gt;
|| The comment of the bank transfer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BankAccount|| [[BankAccountDetails]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Information about the recipient&#039;s bank account.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Bank|| [[BankDetails]] || &lt;br /&gt;
* Required for foreign withdrawals&lt;br /&gt;
|| Information about the recipient&#039;s bank.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Recipient|| [[RecipientDetails]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Information about the recipient.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
== Example requests ==&lt;br /&gt;
[[Withdraw-BankTransfer-v3-examples]]&lt;br /&gt;
&lt;br /&gt;
== Output properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TransactionId || Guid || The unique identifier of the bank transfer, generated by the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Currency || string || The currency of the bank transfer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Amount || decimal || The total amount transferred.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Comment || string || The comment of the bank transfer&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BankAccount|| [[BankAccountDetails]] || Information about the recipient&#039;s bank account.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Bank|| [[BankDetails]] || Information about the recipient&#039;s bank.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Recipient|| [[RecipientDetails]] || Information about the recipient.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Possible error responses  ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| ModelValidationError || This happens when some of the input properties fail the basic validation. For example a string property exceeds its allowed length.&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The provided UserName or Password are not correct.&lt;br /&gt;
|-&lt;br /&gt;
| MinimumWithdrawAmountNotReached || The amount specified does not reach the minimum bank transfer amount. &#039;&#039;&#039;This is not in production yet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCharacter || One of the characters is invalid for the bank transfer process&lt;br /&gt;
|-&lt;br /&gt;
| InvalidAccount || There is no account belonging to the user with the specified currency.&lt;br /&gt;
|-&lt;br /&gt;
| InappropriateVerificationLevel || The user does not have the verification level to be able to transfer.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCurrency || The system does not support the specified currency&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCountry || The Country specified in the BankAccount field is invalid.&lt;br /&gt;
|-&lt;br /&gt;
| LowBalance || There are not enough funds to cover the withdraw amount and the fee.&lt;br /&gt;
|-&lt;br /&gt;
| BankAccountNumberBlackListed || The target bankaccount number is on blacklist, the withdraw process is terminated and the customer gets suspended. &lt;br /&gt;
|-&lt;br /&gt;
| UserIsOverWithdrawLimit|| The withdraw amount exceeded the allowed limit for non-verified customers, the withdraw process is terminated and the customer gets suspended. &lt;br /&gt;
|-&lt;br /&gt;
| UserIsDeleted || The user is deleted from the system, the withdraw is not possible. &lt;br /&gt;
|-&lt;br /&gt;
| UserIsSuspended || The user is suspended until the suspension is lifted no withdraws are allowed.&lt;br /&gt;
|-&lt;br /&gt;
| WithdrawFromCustomerAccountToSystemAccount || Withdraw to the specified target account is not allowed.&lt;br /&gt;
|-&lt;br /&gt;
| BankAccountNumberNotAllowed|| Target Bank account number not in the list of allowed bank account numbers for this account.&lt;br /&gt;
|-&lt;br /&gt;
| InternalServerError || Something unexpected happened&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Bank transfer amount limitations  ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Currency || Target country || Amount limitation&lt;br /&gt;
|-&lt;br /&gt;
| HUF || Anywhere || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| EUR || Anywhere || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| USD || Anywhere || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| CZK || Czechia || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| CZK || Not Czechia || Minimum 100 CZK&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Bank transfer character limitations  ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Currency || Target country || Character limitation&lt;br /&gt;
|-&lt;br /&gt;
| HUF || Anywhere || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| EUR || Anywhere || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| USD || Anywhere || No limitation&lt;br /&gt;
|-&lt;br /&gt;
| CZK || Czechia || Allowed characters: &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z, á, ä, č, ď, é, ě, í, ľ, ň, ó, ô, ö, ř, ŕ, š, ť, ú, ů, ü, ý, ž, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, Á, Ä, Č, Ď, É, Ě, Í, Ľ, Ň, Ó, Ô, Ö, Ř, Ŕ, Š, Ť, Ú, Ů, Ü, Ý, Ž, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, /, -, ?, :, (, ), ., ,, &#039;, +, !, &amp;quot;, #, $, %, &amp;amp;, *, ;, &amp;lt;, =, &amp;gt;, @, [, ], ^, `, {, |, }, ~, §, SPACE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| CZK || Not Czechia || Allowed characters: &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, /, -, ?, :, (, ), ., ,, &#039;, +, SPACE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Transfer-Email-v2&amp;diff=3628</id>
		<title>Transfer-Email-v2</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Transfer-Email-v2&amp;diff=3628"/>
		<updated>2022-10-28T10:08:41Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: send money to an e-mail address}}&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/Transfer/Email&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;/transfer/email&amp;lt;/code&amp;gt; API endpoint is used to send money to another Barion Wallet.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account 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;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UserName || string || &lt;br /&gt;
* Required&lt;br /&gt;
|| Your e-mail address in the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Password || string || &lt;br /&gt;
* Required&lt;br /&gt;
|| Your password in the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| SourceAccountId || GUID || &lt;br /&gt;
* Required&lt;br /&gt;
* Must be an account of the authenticating user, in the same currency as the transfer itself&lt;br /&gt;
|| The identifier of the Barion wallet. This can be determined using the [[Accounts-Get-v2]] API endpoint.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Amount || [[Money]] || &lt;br /&gt;
* Required&lt;br /&gt;
* Must be greater than zero&lt;br /&gt;
|| The total amount to transfer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TargetEmail|| string || &lt;br /&gt;
* Required&lt;br /&gt;
|| The e-mail address of the recipient of the transfer. If they are an active Barion user, they receive the money instantly. If the e-mail address is not registered in Barion, they must register in 7 days in order to claim the money. If the money is not claimed, it gets transferred back to the sender.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Comment || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 1000 characters&lt;br /&gt;
|| The comment of the money transfer.&lt;br /&gt;
&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;
&lt;br /&gt;
| IsTransferSuccessful || bool || Indicates wether the e-money transfer was successfuly finished.&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3627</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3627"/>
		<updated>2022-10-28T10:07:41Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts/Get]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Endpoints must be prefixed with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about the results of Barion Smart Gateway payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3626</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3626"/>
		<updated>2022-10-28T10:07:02Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{| &lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts/Get]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Endpoints must be prefixed with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about the results of Barion Smart Gateway payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3625</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3625"/>
		<updated>2022-10-28T09:59:12Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Other interfaces */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Endpoints must be prefixed with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
{| &lt;br /&gt;
&lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts/Get]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about the results of Barion Smart Gateway payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3624</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3624"/>
		<updated>2022-10-28T09:57:53Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Endpoints must be prefixed with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
{| &lt;br /&gt;
&lt;br /&gt;
|&#039;&#039;&#039;Barion Smart Gateway&#039;&#039;&#039;&lt;br /&gt;
|&#039;&#039;&#039;Barion Wallet&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;padding-right: 100px;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
| style=&amp;quot;vertical-align: top&amp;quot; |&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts/Get]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about successful payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3623</id>
		<title>List of API endpoints</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=List_of_API_endpoints&amp;diff=3623"/>
		<updated>2022-10-27T18:23:23Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Endpoint list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=List of Barion API endpoints}}&lt;br /&gt;
&lt;br /&gt;
On this page you can find the currently available API endpoints in the Barion system. If you are new here, first please read the [[Getting_started|Getting started]] page.&lt;br /&gt;
&lt;br /&gt;
==API base URL==&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;
{{NotificationBox|title=IMPORTANT|text=Always double check that you are connecting to the proper environment to avoid unnecessary troubleshooting!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Endpoint list==&lt;br /&gt;
&lt;br /&gt;
Currently the following endpoints are available in the Barion API.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Start-v2|/Payment/Start]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Complete-v2|/Payment/Complete]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-FinishReservation-v2|/Payment/FinishReservation]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Capture-v2|/Payment/Capture]] &lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-CancelAuthorization-v2|/Payment/CancelAuthorization]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Payment-Refund-v2|/Payment/Refund]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v2|/Withdraw/BankTransfer]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v3&amp;lt;/span&amp;gt; [[Withdraw-BankTransfer-v3|/Withdraw/BankTransfer]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Accounts-Get-v2|/Accounts/Get]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Statement-Download-v2|/Statement/Download]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; [[Transfer-Email-v2|/Transfer/Email]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; [[Transfer-Send-v1|/Transfer/Send]] (deprecated)&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Endpoints must be prefixed with the corresponding API version.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Other interfaces==&lt;br /&gt;
[[Callback_mechanism|Barion callback mechanism - how to properly get notified about successful payments]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Security_Measures&amp;diff=3618</id>
		<title>Security Measures</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Security_Measures&amp;diff=3618"/>
		<updated>2022-09-28T11:49:45Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Legacy IP addresses until 2022.09.26 */&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;
&lt;br /&gt;
== Legacy IP addresses until 2022.09.26 ==&lt;br /&gt;
Plese keep them in your firewall settings till end of October 2022.&lt;br /&gt;
* 40.69.88.149&lt;br /&gt;
* 52.169.80.55&lt;br /&gt;
* 40.69.88.240&lt;br /&gt;
* 13.79.241.141&lt;br /&gt;
* 52.164.220.205&lt;br /&gt;
* 52.138.142.128&lt;br /&gt;
* 52.138.141.52&lt;br /&gt;
* 51.104.153.241&lt;br /&gt;
* 20.54.0.121&lt;br /&gt;
* 20.54.2.121&lt;br /&gt;
* 20.54.3.63&lt;br /&gt;
* 20.54.3.71&lt;br /&gt;
* 20.54.3.182&lt;br /&gt;
* 20.54.3.253&lt;br /&gt;
* 20.54.4.138&lt;br /&gt;
* 20.54.4.161&lt;br /&gt;
* 20.54.5.2&lt;br /&gt;
* 20.54.5.86&lt;br /&gt;
* 20.54.5.146&lt;br /&gt;
&lt;br /&gt;
== IP address(es) - sandbox environment == &lt;br /&gt;
* 20.223.214.216 &amp;lt;span style=&amp;quot;background-color:#1993c7; color: white; padding-left:5px; padding-right:5px;&amp;quot;&amp;gt;from 2022.09.05.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== IP address(es) - production environment == &lt;br /&gt;
* 40.113.73.229 &amp;lt;span style=&amp;quot;background-color:#1993c7; color: white; padding-left:5px; padding-right:5px;&amp;quot;&amp;gt;from 2022.09.26.&amp;lt;/span&amp;gt;&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.2 and above - former encryption standards (SSLv3, TLS1.0 etc.) are not supported. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system only supports TLS v1.2 and above|color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=C2C_Payments&amp;diff=3450</id>
		<title>C2C Payments</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=C2C_Payments&amp;diff=3450"/>
		<updated>2022-06-24T08:01:57Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion Bridge - payments for platforms}}&lt;br /&gt;
==Barion Bridge overview==&lt;br /&gt;
Barion Bridge makes it possible for companies to facilitate payments between people or other parties. There are roles, as indicated on the diagram. &lt;br /&gt;
*The Customer is the user who uses the services of or buys goods from the Seller (or multiple Sellers in case of marketplaces) and pays the Seller directly. &lt;br /&gt;
*The Facilitator, the company that facilitates the service is organizing the payment with the Barion API. The Facilitator is able to transfer a fee from each payment to herself and to one or more Contributors. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=Please note|text=The Customer does not need a Barion account, but the Seller and Contributors do.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
Barion transaction fees are always covered by the Facilitator, no other parties pay transaction fees to Barion.&lt;br /&gt;
&lt;br /&gt;
[[CodeSamples|Code Samples]] are available.&lt;br /&gt;
&lt;br /&gt;
Examples of use for such payments:&lt;br /&gt;
*Sharing Economy business model (such as Uber)&lt;br /&gt;
*Marketplaces, where shopper may buy from multiple Sellers in one transaction&lt;br /&gt;
*Where law mandates direct payment to Seller, e.g. in certain insurance scenarios&lt;br /&gt;
*To optimize taxation&lt;br /&gt;
&lt;br /&gt;
[[file:Sharing-economy.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
==Barion Bridge with escrow==&lt;br /&gt;
The Facilitator has the option to control the payment of the Customer to Seller, by placing the sum in an escrow and decide about fulfillment at a later time, such as when the delivery is confirmed. The funds can be partially or completely refunded to the Customer in case Seller does not deliver properly.&lt;br /&gt;
&lt;br /&gt;
For further details about escrow please check out [[Reservation_payment|Payments with reservation / escrow]].&lt;br /&gt;
&lt;br /&gt;
For further details about facilitator or contributor fees check out [[Payee_transactions|Payee transactions]].&lt;br /&gt;
&lt;br /&gt;
For further details about Barion Bridge payments please  check out [[Facilitated_payments|Marketplace, sharing economy, and facilitated payments]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[file:sharing-economy-escrow.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;Uber&amp;quot; style simple sharing economy example==&lt;br /&gt;
If &amp;quot;Uber&amp;quot; was using Barion, the passenger would be the Customer, and the Driver would be the Seller. &amp;quot;Uber&amp;quot; would ask for a fee from the driver, as the blue lines indicate. Barion transaction fees would be payed by &amp;quot;Uber&amp;quot;. Drivers would need a Barion account set up before the first ride. Automatic charging would &lt;br /&gt;
be solved by [[Token_payment|Token payments]].&lt;br /&gt;
&lt;br /&gt;
For further details about facilitator or contributor fees check out [[Payee_transactions|Payee transactions]].&lt;br /&gt;
&lt;br /&gt;
For further details about Barion Bridge payments please check out [[Facilitated_payments|Marketplace, sharing economy, and facilitated payments]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[file:sharing-economy-uber.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
==&amp;quot;Marketplace with agents&amp;quot; sharing economy example==&lt;br /&gt;
This example shows a marketplace, where multiple Sellers sell goods or services to the Customer, and both the Facilitator and third party agents receive a fee.&lt;br /&gt;
&lt;br /&gt;
For further details about Barion Bridge payments please check out [[Facilitated_payments|Marketplace, sharing economy, and facilitated payments]].&lt;br /&gt;
&lt;br /&gt;
For further details about facilitator or contributor fees check out [[Payee_transactions|Payee transactions]].&lt;br /&gt;
&lt;br /&gt;
Please check out the [[Marketplace_Example|detailed example of a marketplace payment]] page for more informations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[file:sharing-economy-marketplace.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
==Barion Bridge transactions mapped to API structure==&lt;br /&gt;
The following diagram helps developers match the Barion Bridge payment structure the the API Json structure.&lt;br /&gt;
[[file:sharing-economy-api-mapping.png|1000px]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=3449</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=3449"/>
		<updated>2022-06-24T07:57:56Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 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:Barion-smart-gateway-en.png|right|600px]]&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;
*[[3DSecure|Strong customer authentication with 3DSecure]]&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;
==3DSecure/PSD2 SCA==&lt;br /&gt;
*[[3DSecure|3DSecure General Information]]&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&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 websites]]&lt;br /&gt;
*[[App2App_payment|Barion Smart Gateway integraton for mobile applications]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
*[[Delayed_Capture|Delayed Capture: reservation on payment card]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment_3D_Secure|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|Barion Bridge - Payments for platforms]]&lt;br /&gt;
*[[Apple_Pay|Apple Pay]]&lt;br /&gt;
*[[Google_Pay|Google Pay]]&lt;br /&gt;
*[[Bank_Transfer_Payment|Payment with bank transfer]]&lt;br /&gt;
&lt;br /&gt;
==API docs==&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
&lt;br /&gt;
==Barion Pixel==&lt;br /&gt;
{|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot; width=&amp;quot;50%&amp;quot;|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
|[[Getting started with the Barion Pixel]] &lt;br /&gt;
|[[Áttekintés a Barion Pixel működéséről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Base Barion Pixel]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Full Barion Pixel]]&lt;br /&gt;
|[[A Teljes (Full) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Barion Pixel Consent Management requirements]]&lt;br /&gt;
| [[Barion Pixel hozzájáruláskezelési követelmények]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Barion Pixel API reference]]&lt;br /&gt;
|[[Barion Pixel API referencia]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Frequently Asked Questions about the Barion Pixel]]&lt;br /&gt;
|[[Gyakran Ismételt Kérdések a Barion Pixelről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Barion Pixel base code through the Google Tag Manager]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja a Google Tag Managerben]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Smar_Documentation|Implementing the Barion Full Pixel code in Shopify webshop]]&lt;br /&gt;
|[[Smar_Dokumentacio|A Teljes (Full) Barion Pixel implementációja Shopify webáruházban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-woocommerce-webshops|Implementing Base and Full Barion Pixel in woocommerce webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Woocommerce e-kereskedelmi platformon]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-unas-webshops|Implementing Base and Full Barion Pixel in UNAS webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja UNAS webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-shoprenter-webshops|Implementing Base and Full Barion Pixel in shoprenter webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Shoprenter webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Viltor webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Barion_for_Shopify|Barion for Shopify]]&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;
&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
*[[Dataprocessors|Barion data processor partners]]&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>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Bank_Transfer_Payment&amp;diff=3442</id>
		<title>Bank Transfer Payment</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Bank_Transfer_Payment&amp;diff=3442"/>
		<updated>2022-06-10T08:04:17Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* For EUR */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Bank Transfer Payment}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the case of payment by bank transfer, the customer fulfills its payment obligation by bank transfer. This means that a customer can choose to pay for the goods via a prepared bank transfer. This is an additional option for the customer to choose from (besides e-money payment from a wallet and card payment).&lt;br /&gt;
&lt;br /&gt;
If all the technical requirements are met (see below) on the gateway there will visible a third funding source option for the customer.&lt;br /&gt;
&lt;br /&gt;
[[File:Banktransfer.png]]&lt;br /&gt;
&lt;br /&gt;
The process is the following&lt;br /&gt;
# The customer arrives at the Barion Smart Gateway&lt;br /&gt;
# Customer decides to pay with bank transfer, selects one of the banks, and clicks the &#039;&#039;Pay&#039;&#039; button.&lt;br /&gt;
# Customer is redirected to the selected bank&#039;s GUI&lt;br /&gt;
# Customer inputs all the necessary information required to make the transfer&lt;br /&gt;
# Customer is redirected to the Barion Smart Gateway and is presented with the result&lt;br /&gt;
# Customer is redirected to the merchant&#039;s shop&lt;br /&gt;
&lt;br /&gt;
In case the transfer was unsuccessful the customer is allowed to try the payment again with another bank or even with another funding source. If the transfer was successful a callback is sent to the merchant&#039;s server.&lt;br /&gt;
&lt;br /&gt;
However, there are certain bank transfers that take longer so by the time the customer finishes the payment process the result of the process is not known yet. In these scenarios the customer is presented with an appropriate message that contains information about the situation. Later when the result of the transfer is decided an e-mail message is sent to the customer about the result.&lt;br /&gt;
&lt;br /&gt;
== Availability ==&lt;br /&gt;
At the moment we only support &#039;&#039;&#039;immediate payment&#039;&#039;&#039; scenarios, later the [[Reservation_payment|reservation/escrow]] scenario will be supported as well. Until then in reservation scenarios, the gateway will not offer the bank transfer payment option for the customer.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This feature is only available for payments conducted in CZK or EUR. For all other currencies this option will be hidden.&#039;&#039;&#039; &amp;lt;br/&amp;gt;&lt;br /&gt;
You can view the full list of supported banks by creating a payment in our [https://demomerchant.shop/ demo shop]. In order to see the banks available for different countries, make sure to adjust the Country - Currency (CZK/EUR) in the top right corner.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;WARNING&amp;lt;/b&amp;gt; - the payments in the demo shop are processed in a production/live environment with real money transfers. &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Different banks are available for EUR and CZK|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=== For CZK === &lt;br /&gt;
[[File:AIRBANK_CZ.png|100px|link=]] &lt;br /&gt;
[[File:CSAS_CZ.png|100px|link=]]&lt;br /&gt;
[[File:CSOB_CZ.png|100px|link=]]&lt;br /&gt;
[[File:FIO_CZ.png|100px|link=]]&lt;br /&gt;
[[File:KB_CZ.png|100px|link=]] &lt;br /&gt;
[[File:MBANK_CZ.png|100px|link=]] &lt;br /&gt;
[[File:MONETA_CZ.png|100px|link=]] &lt;br /&gt;
[[File:RAIFFEISEN_CZ.png|100px|link=]] &lt;br /&gt;
[[File:REVOLUT_CZ.png|100px|link=]] &lt;br /&gt;
[[File:UNICREDIT_CZ.png|100px|link=]] &lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== For EUR ===&lt;br /&gt;
&#039;&#039;&#039;In Slovakia&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:CSOB_SK.png|100px|link=]] &lt;br /&gt;
[[File:INTESA_SANPAOLO_SK.png|100px|link=]] &lt;br /&gt;
[[File:PRIMABANKA_SK.png|100px|link=]] &lt;br /&gt;
[[File:RAIFFEISEN_SK.png|100px|link=]] &lt;br /&gt;
[[File:REVOLUT_SK.png|100px|link=]] &lt;br /&gt;
[[File:SLSP_SK.png|100px|link=]] &lt;br /&gt;
[[File:UNICREDIT_SK.png|100px|link=]] &lt;br /&gt;
[[File:TATRA_SK.png|100px|link=]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;In other countries&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Many banks in the following countries:&lt;br /&gt;
* Austria&lt;br /&gt;
* Belgium&lt;br /&gt;
* Germany &lt;br /&gt;
* Estonia&lt;br /&gt;
* Finland&lt;br /&gt;
* France&lt;br /&gt;
* Greece&lt;br /&gt;
* Ireland&lt;br /&gt;
* Italy&lt;br /&gt;
* Latvia&lt;br /&gt;
* Lithuania&lt;br /&gt;
* Luxemburg&lt;br /&gt;
* The Netherlands&lt;br /&gt;
* Portugal&lt;br /&gt;
* Slovenia&lt;br /&gt;
* Spain&lt;br /&gt;
&lt;br /&gt;
= Callback process for bank transfer payment scenarios =&lt;br /&gt;
&lt;br /&gt;
There are two types of transfer scenarios regarding bank transfer payments. Only after the customer completes the transfer will the system know which scenario is used. So, every system that handles payments that can be paid with bank transfer must handle the asynchronous scenario as well.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Synchronous scenario&#039;&#039;&#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
In this case, the result of the bank transfer is known immediately after the transfer. This scenario works the same way as the card payment scenario. After the final [[PaymentStatus|status]] of the payment is known a [[Callback_mechanism|callback mechanism]] is started to notify the merchant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Asynchronous scenario &#039;&#039;&#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
There is a scenario where the result of the bank transfer is not available at the end of the payment. It can take up to five days to receive the final result of the transfer. In this case the Barion system starts two callback process.&lt;br /&gt;
# One process will be started when the Barion system receives information that the asynchronous scenario is applied for the transfer,&lt;br /&gt;
# and one process when the final result of the transfer is available.&lt;br /&gt;
As with any callback the merchant should use the [[Payment-GetPaymentState-v2|GetPaymentState]] request to decide what happened.&lt;br /&gt;
&lt;br /&gt;
In the first callback mechanism a new [[PaymentStatus|payment status]] is introduced, called &amp;lt;tt&amp;gt;Waiting&amp;lt;/tt&amp;gt;. This represents the status where the Barion system is waiting for the final result of the bank transfer. &#039;&#039;&#039;At this point the payment is not completed and still can be &amp;lt;tt&amp;gt;Failed&amp;lt;/tt&amp;gt; as well.&lt;br /&gt;
&lt;br /&gt;
When the Barion system receives the final result of the transfer, a new callback mechanism is started to notify the merchant again.&lt;br /&gt;
&lt;br /&gt;
= &amp;lt;tt&amp;gt;GetPaymentState&amp;lt;/tt&amp;gt; implications =&lt;br /&gt;
&lt;br /&gt;
If a customer paid with bank transfer there are a number of [[TransactionType|transaction types]] that can appear in the response of a [[Payment-GetPaymentState-v2|GetPaymentState]] call.&lt;br /&gt;
* &amp;lt;code&amp;gt;BankTransferPayment&amp;lt;/code&amp;gt;: the actual payment transaction itself&lt;br /&gt;
* &amp;lt;code&amp;gt;RefundToBankAccount&amp;lt;/code&amp;gt;: if there was a refund, this represents it&lt;br /&gt;
* &amp;lt;code&amp;gt;StornoUnSuccessfulRefundToBankAccount&amp;lt;/code&amp;gt;: if the refund was not successful, this is the storno for it&lt;br /&gt;
* &amp;lt;code&amp;gt;BankTransferPaymentFee&amp;lt;/code&amp;gt;: The fee deducted for using this feature&lt;br /&gt;
&lt;br /&gt;
These are unique for this type of payment, but apart from these, any other transaction type can be present like in any other payment scenario.&lt;br /&gt;
&lt;br /&gt;
= Payment status changes =&lt;br /&gt;
This is a diagram for the payment status changes if the payment was funded with a bank transfer.&lt;br /&gt;
&lt;br /&gt;
[[File:Payment_states_pb.png]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Bank_Transfer_Payment&amp;diff=3441</id>
		<title>Bank Transfer Payment</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Bank_Transfer_Payment&amp;diff=3441"/>
		<updated>2022-06-10T08:04:00Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* For EUR */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Bank Transfer Payment}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the case of payment by bank transfer, the customer fulfills its payment obligation by bank transfer. This means that a customer can choose to pay for the goods via a prepared bank transfer. This is an additional option for the customer to choose from (besides e-money payment from a wallet and card payment).&lt;br /&gt;
&lt;br /&gt;
If all the technical requirements are met (see below) on the gateway there will visible a third funding source option for the customer.&lt;br /&gt;
&lt;br /&gt;
[[File:Banktransfer.png]]&lt;br /&gt;
&lt;br /&gt;
The process is the following&lt;br /&gt;
# The customer arrives at the Barion Smart Gateway&lt;br /&gt;
# Customer decides to pay with bank transfer, selects one of the banks, and clicks the &#039;&#039;Pay&#039;&#039; button.&lt;br /&gt;
# Customer is redirected to the selected bank&#039;s GUI&lt;br /&gt;
# Customer inputs all the necessary information required to make the transfer&lt;br /&gt;
# Customer is redirected to the Barion Smart Gateway and is presented with the result&lt;br /&gt;
# Customer is redirected to the merchant&#039;s shop&lt;br /&gt;
&lt;br /&gt;
In case the transfer was unsuccessful the customer is allowed to try the payment again with another bank or even with another funding source. If the transfer was successful a callback is sent to the merchant&#039;s server.&lt;br /&gt;
&lt;br /&gt;
However, there are certain bank transfers that take longer so by the time the customer finishes the payment process the result of the process is not known yet. In these scenarios the customer is presented with an appropriate message that contains information about the situation. Later when the result of the transfer is decided an e-mail message is sent to the customer about the result.&lt;br /&gt;
&lt;br /&gt;
== Availability ==&lt;br /&gt;
At the moment we only support &#039;&#039;&#039;immediate payment&#039;&#039;&#039; scenarios, later the [[Reservation_payment|reservation/escrow]] scenario will be supported as well. Until then in reservation scenarios, the gateway will not offer the bank transfer payment option for the customer.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This feature is only available for payments conducted in CZK or EUR. For all other currencies this option will be hidden.&#039;&#039;&#039; &amp;lt;br/&amp;gt;&lt;br /&gt;
You can view the full list of supported banks by creating a payment in our [https://demomerchant.shop/ demo shop]. In order to see the banks available for different countries, make sure to adjust the Country - Currency (CZK/EUR) in the top right corner.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;WARNING&amp;lt;/b&amp;gt; - the payments in the demo shop are processed in a production/live environment with real money transfers. &amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Different banks are available for EUR and CZK|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
=== For CZK === &lt;br /&gt;
[[File:AIRBANK_CZ.png|100px|link=]] &lt;br /&gt;
[[File:CSAS_CZ.png|100px|link=]]&lt;br /&gt;
[[File:CSOB_CZ.png|100px|link=]]&lt;br /&gt;
[[File:FIO_CZ.png|100px|link=]]&lt;br /&gt;
[[File:KB_CZ.png|100px|link=]] &lt;br /&gt;
[[File:MBANK_CZ.png|100px|link=]] &lt;br /&gt;
[[File:MONETA_CZ.png|100px|link=]] &lt;br /&gt;
[[File:RAIFFEISEN_CZ.png|100px|link=]] &lt;br /&gt;
[[File:REVOLUT_CZ.png|100px|link=]] &lt;br /&gt;
[[File:UNICREDIT_CZ.png|100px|link=]] &lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== For EUR ===&lt;br /&gt;
&#039;&#039;&#039;In Slovakia&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:CSOB_SK.png|100px|link=]] &lt;br /&gt;
[[File:INTESA_SANPAOLO_SK.png|100px|link=]] &lt;br /&gt;
[[File:PRIMABANKA_SK.png|100px|link=]] &lt;br /&gt;
[[File:RAIFFEISEN_SK.png|100px|link=]] &lt;br /&gt;
[[File:REVOLUT_SK.png|100px|link=]] &lt;br /&gt;
[[File:SLSP_SK.png|100px|link=]] &lt;br /&gt;
[[File:UNICREDIT_SK.png|100px|link=]] &lt;br /&gt;
[[File:TATRA_SK.png|100px|link=]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;In other countries&#039;&#039;&#039;&lt;br /&gt;
Many banks in the following countries:&lt;br /&gt;
* Austria&lt;br /&gt;
* Belgium&lt;br /&gt;
* Germany &lt;br /&gt;
* Estonia&lt;br /&gt;
* Finland&lt;br /&gt;
* France&lt;br /&gt;
* Greece&lt;br /&gt;
* Ireland&lt;br /&gt;
* Italy&lt;br /&gt;
* Latvia&lt;br /&gt;
* Lithuania&lt;br /&gt;
* Luxemburg&lt;br /&gt;
* The Netherlands&lt;br /&gt;
* Portugal&lt;br /&gt;
* Slovenia&lt;br /&gt;
* Spain&lt;br /&gt;
&lt;br /&gt;
= Callback process for bank transfer payment scenarios =&lt;br /&gt;
&lt;br /&gt;
There are two types of transfer scenarios regarding bank transfer payments. Only after the customer completes the transfer will the system know which scenario is used. So, every system that handles payments that can be paid with bank transfer must handle the asynchronous scenario as well.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Synchronous scenario&#039;&#039;&#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
In this case, the result of the bank transfer is known immediately after the transfer. This scenario works the same way as the card payment scenario. After the final [[PaymentStatus|status]] of the payment is known a [[Callback_mechanism|callback mechanism]] is started to notify the merchant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Asynchronous scenario &#039;&#039;&#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
There is a scenario where the result of the bank transfer is not available at the end of the payment. It can take up to five days to receive the final result of the transfer. In this case the Barion system starts two callback process.&lt;br /&gt;
# One process will be started when the Barion system receives information that the asynchronous scenario is applied for the transfer,&lt;br /&gt;
# and one process when the final result of the transfer is available.&lt;br /&gt;
As with any callback the merchant should use the [[Payment-GetPaymentState-v2|GetPaymentState]] request to decide what happened.&lt;br /&gt;
&lt;br /&gt;
In the first callback mechanism a new [[PaymentStatus|payment status]] is introduced, called &amp;lt;tt&amp;gt;Waiting&amp;lt;/tt&amp;gt;. This represents the status where the Barion system is waiting for the final result of the bank transfer. &#039;&#039;&#039;At this point the payment is not completed and still can be &amp;lt;tt&amp;gt;Failed&amp;lt;/tt&amp;gt; as well.&lt;br /&gt;
&lt;br /&gt;
When the Barion system receives the final result of the transfer, a new callback mechanism is started to notify the merchant again.&lt;br /&gt;
&lt;br /&gt;
= &amp;lt;tt&amp;gt;GetPaymentState&amp;lt;/tt&amp;gt; implications =&lt;br /&gt;
&lt;br /&gt;
If a customer paid with bank transfer there are a number of [[TransactionType|transaction types]] that can appear in the response of a [[Payment-GetPaymentState-v2|GetPaymentState]] call.&lt;br /&gt;
* &amp;lt;code&amp;gt;BankTransferPayment&amp;lt;/code&amp;gt;: the actual payment transaction itself&lt;br /&gt;
* &amp;lt;code&amp;gt;RefundToBankAccount&amp;lt;/code&amp;gt;: if there was a refund, this represents it&lt;br /&gt;
* &amp;lt;code&amp;gt;StornoUnSuccessfulRefundToBankAccount&amp;lt;/code&amp;gt;: if the refund was not successful, this is the storno for it&lt;br /&gt;
* &amp;lt;code&amp;gt;BankTransferPaymentFee&amp;lt;/code&amp;gt;: The fee deducted for using this feature&lt;br /&gt;
&lt;br /&gt;
These are unique for this type of payment, but apart from these, any other transaction type can be present like in any other payment scenario.&lt;br /&gt;
&lt;br /&gt;
= Payment status changes =&lt;br /&gt;
This is a diagram for the payment status changes if the payment was funded with a bank transfer.&lt;br /&gt;
&lt;br /&gt;
[[File:Payment_states_pb.png]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3382</id>
		<title>Apple Pay</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3382"/>
		<updated>2022-05-23T12:13:18Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Prerequisites */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Apple Pay integration}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
Apple Pay™ is a payment option for the customer. Apple securely stores the customer&#039;s card information and hands it over to the merchant for processing.&lt;br /&gt;
{{NotificationBox|title=NOTE|text=We currently only support Apple Pay for the web, native iPhone app support is coming soon.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
== Implementation modes ==&lt;br /&gt;
Apple Pay can be emebedded two ways into your payment flow. In the first case, it will be displayed on Barion Smart Gateway (&amp;quot;Hosted Gateway&amp;quot;), which needs no further configuration and/or development on your side. The second option is to display the Apple Pay button on your site (&amp;quot;integrated mode&amp;quot;), however this needs configuration and development on your side. This page will discuss the latter.&lt;br /&gt;
* Apple Pay Hosted Gateway demo: https://test.demomerchant.shop/en/DemoClub/Pay (click the Pay button)&lt;br /&gt;
* Apple Pay integrated mode demo: https://test.demomerchant.shop/en/DemoGame/Pay&lt;br /&gt;
&lt;br /&gt;
== Prerequisites ==&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=To integrate this feature you have to develop the integration yourself! You need to understand Javascript code and it is also required to modify your webshop&#039;s server code!|color=#FF7A3D}}&lt;br /&gt;
* you (the merchant) must have a Barion wallet&lt;br /&gt;
* the beforementioned Barion wallet must have and approved shop&lt;br /&gt;
* for every currency you plan to conduct payments in you have to make sure there is an account created in your Barion wallet. This means that if you plan to have USD payments then there should be an USD account created in your wallet.&lt;br /&gt;
* all the example codes assume the availability of jQuery&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
=== Technical ===&lt;br /&gt;
Using Apple Pay as a token payment is currently not possible.&lt;br /&gt;
&lt;br /&gt;
=== Shopper ===&lt;br /&gt;
Apple Pay will only be visible to shoppers fulfilling the following criteria:&lt;br /&gt;
* Use an [https://support.apple.com/en-us/HT208531 Apple Pay-compatible device]&lt;br /&gt;
* Use [https://support.apple.com/en-us/HT208531#notes Safari]&lt;br /&gt;
* Located in a country or region where [https://support.apple.com/en-us/HT207957 Apple Pay is available]&lt;br /&gt;
* Have an [https://support.apple.com/guide/iphone/set-up-apple-pay-iph9b7f53382/ios existing card added to their Apple Pay wallet]&lt;br /&gt;
&lt;br /&gt;
=== Shop ===&lt;br /&gt;
* Your shop must not sell [https://developer.apple.com/apple-pay/acceptable-use-guidelines-for-websites/ prohibited items by Apple]&lt;br /&gt;
* Your site must use https!&lt;br /&gt;
&lt;br /&gt;
==Payment Process==&lt;br /&gt;
# The customer clicks the Apple Pay button.&lt;br /&gt;
# Apple Pay session has to be created using the library provided by Apple as discussed [[#Create an Apple Pay session|here]].&lt;br /&gt;
# The JS code receives a session data&lt;br /&gt;
# The JS code sends this information to the server side of the merchant&lt;br /&gt;
# The server side gathers the information necessary to call the [[ApplePay-ValidateSession|/v2/ApplePay/ValidateSession]] endpoint.&lt;br /&gt;
# Apple Pay screen is displayed, where the customer can select the card, shipping address and contact details.&lt;br /&gt;
# The JS code receives the encrypted card information.&lt;br /&gt;
# The JS code sends the encrypted information to the sever side of the merchant&lt;br /&gt;
# The server side gathers the information needed to call the [[ApplePay-StartPaymentWithAppleToken|/v2/ApplePay/StartPaymentWithAppleToken]] endpoint.&lt;br /&gt;
# The Barion API handles the request, decrypts the packages and charges the card. The result of the payment is sent back to the caller.&lt;br /&gt;
# The merchant&#039;s server communicates the result to the client side and the webshop renders the result of the payment.&lt;br /&gt;
&lt;br /&gt;
==  Configuration ==&lt;br /&gt;
=== Domain verification file===&lt;br /&gt;
First head over to secure.barion.com, and under [https://secure.barion.com/Shop Manage My Shops] page select the appropriate one, and from the dropdown, click on settings. At the bottom click the Manage Apple Pay settings blue button under the Apple Pay Settings section. On the next page  Click on the Download domain verification file button, which will download a domain association file. You should place this file at the content root of all of your sites, you&#039;re about to use apple pay in integrated mode.&lt;br /&gt;
The file must:&lt;br /&gt;
* mimemap for extension &amp;quot;.&amp;quot; should be set to &amp;quot;application/json&amp;quot;, for eg.:&lt;br /&gt;
*: &amp;lt;syntaxhighlight lang=&amp;quot;xml&amp;quot;&amp;gt;&amp;lt;mimeMap fileExtension=&amp;quot;.&amp;quot; mimeType=&amp;quot;application/json&amp;quot; /&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
* be externally accessible.&lt;br /&gt;
* not be password protected.&lt;br /&gt;
* the file cannot be behind a proxy or redirect.&lt;br /&gt;
* your site must use https.&lt;br /&gt;
&lt;br /&gt;
===Configure Domains===&lt;br /&gt;
On the exact same page you&#039;ve downloaded the domain association file, enter all the domains (one in each line, without https:// or https://) you&#039;re intending to use Apple Pay.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
=== Include the Apple Pay SDK===&lt;br /&gt;
Include the following code snippet in the header of your checkout page:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;script src=&amp;quot;https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
===Display the Apple Pay button===&lt;br /&gt;
Add the Apple Pay button to your checkout page as discussed [https://developer.apple.com/documentation/apple_pay_on_the_web/displaying_apple_pay_buttons_using_javascript here]&lt;br /&gt;
===Create an Apple Pay session===&lt;br /&gt;
When the user taps the Apple Pay button, provide a payment request and create the [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession session] as discussed [https://developer.apple.com/documentation/apple_pay_on_the_web/apple_pay_js_api/creating_an_apple_pay_session here]. Create a variable which will store, if the Apple Pay UI is dismissed (isSessionCanceled).&lt;br /&gt;
&lt;br /&gt;
===Subscribe to the &amp;lt;code&amp;gt;[https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778021-onvalidatemerchant onvalidatemerchant]&amp;lt;/code&amp;gt; event===&lt;br /&gt;
Call your backend, which will in turn call the Barion Api [[ApplePay-ValidateSession|ValidateSession]] endpoint in the event handler with the provided url as the payload, if the payment ui is not dismissed meanwhile:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
	 appleSession.onvalidatemerchant = function (event) {&lt;br /&gt;
		// TODO: disable Apple Pay button&lt;br /&gt;
		const data = {&lt;br /&gt;
			SessionValidationUrl: event.validationURL&lt;br /&gt;
		};&lt;br /&gt;
&lt;br /&gt;
		$.ajax({&lt;br /&gt;
			method: &amp;quot;POST&amp;quot;,&lt;br /&gt;
			url: &amp;quot;https://yourserver.com/ValidateApplePaySession&amp;quot;,&lt;br /&gt;
			data: data,&lt;br /&gt;
			success: function (response, status, xhr) {&lt;br /&gt;
				const merchantSession = JSON.parse(response.ApplePaySessionResponse);&lt;br /&gt;
				if(!isSessionCanceled) {&lt;br /&gt;
					appleSession.completeMerchantValidation(merchantSession);&lt;br /&gt;
				}&lt;br /&gt;
			},&lt;br /&gt;
			error: function (xhr, status, error) {&lt;br /&gt;
				// failure callback&lt;br /&gt;
				// TODO: enable Apple Pay button&lt;br /&gt;
			}&lt;br /&gt;
		});&lt;br /&gt;
	};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Subscribe to the &amp;lt;code&amp;gt;[https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778020-onpaymentauthorized onpaymentauthorized ]&amp;lt;/code&amp;gt; event===&lt;br /&gt;
Call your backend, which will in turn call the Barion Api [[ApplePay-StartPaymentWithAppleToken|StartPaymentWithAppleToken]] endpoint in the event handler with the provided payment payload:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
	appleSession.onpaymentauthorized = function (event) {&lt;br /&gt;
		let cart = {&lt;br /&gt;
			Payload = event.payment&lt;br /&gt;
			PaymentType = &amp;quot;Immediate&amp;quot;,&lt;br /&gt;
			Mode = &amp;quot;&amp;quot;,&lt;br /&gt;
		};&lt;br /&gt;
&lt;br /&gt;
		$.ajax({&lt;br /&gt;
			method: &amp;quot;POST&amp;quot;,&lt;br /&gt;
			url: &amp;quot;https://yourserver.com/StartApplePayment&amp;quot;,&lt;br /&gt;
			data: cart,&lt;br /&gt;
			success: function (response, status, xhr) {&lt;br /&gt;
				if (response.IsSuccessful &amp;amp;&amp;amp; response.PaymentStatus === 40) {&lt;br /&gt;
					appleSession.completePayment(appleSession.STATUS_SUCCESS);&lt;br /&gt;
				} else {&lt;br /&gt;
					appleSession.completePayment(appleSession.STATUS_FAILURE);&lt;br /&gt;
				}&lt;br /&gt;
			},&lt;br /&gt;
			error: function (xhr, status, error) {&lt;br /&gt;
				appleSession.completePayment(appleSession.STATUS_FAILURE);&lt;br /&gt;
			}&lt;br /&gt;
		});&lt;br /&gt;
	};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Subscribe to the &amp;lt;code&amp;gt;[https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778029-oncancel oncancel]&amp;lt;/code&amp;gt; event===&lt;br /&gt;
This method gets called every time the Apple Pay UI is dismissed. You should implement your needs accordingly (for eg. re-enable pay button). Furthermore indicate that the session was canceled, so the completePayment won&#039;t be executed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
	appleSession.onpaymentauthorized = function (event) {&lt;br /&gt;
          	// TODO: enable Apple Pay button&lt;br /&gt;
            &lt;br /&gt;
            isSessionCanceled = true;&lt;br /&gt;
	};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Call &amp;lt;code&amp;gt;ApplePaySession.begin&amp;lt;/code&amp;gt; method===&lt;br /&gt;
Call the [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778001-begin begin] method, and the merchant validation process begins. So your final client side code will look like this:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
var request = {&lt;br /&gt;
  countryCode: &#039;HU&#039;,&lt;br /&gt;
  currencyCode: &#039;HUF&#039;,&lt;br /&gt;
  supportedNetworks: [&#039;visa&#039;, &#039;masterCard&#039;, &#039;amex&#039;, &#039;discover&#039;],&lt;br /&gt;
  merchantCapabilities: [&#039;supports3DS&#039;],&lt;br /&gt;
  total: { label: &#039;Your Merchant Name&#039;, amount: &#039;1000.00&#039; },&lt;br /&gt;
};&lt;br /&gt;
var isSessionCanceled = false;&lt;br /&gt;
&lt;br /&gt;
var appleSession = new ApplePaySession(3, request);&lt;br /&gt;
appleSession.onvalidatemerchant = function (event) {...}&lt;br /&gt;
appleSession.onpaymentauthorized = function (event) {...}&lt;br /&gt;
appleSession.begin();&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== API reference ==&lt;br /&gt;
* Barion&lt;br /&gt;
** [[ApplePay-ValidateSession|/v2/ApplePay/ValidateSession]]&lt;br /&gt;
** [[ApplePay-StartPaymentWithAppleToken|/v2/ApplePay/StartPaymentWithAppleToken]]&lt;br /&gt;
* Apple&lt;br /&gt;
** [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession ApplePaySession interface]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=FundingSources&amp;diff=3364</id>
		<title>FundingSources</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=FundingSources&amp;diff=3364"/>
		<updated>2022-03-18T10:06:22Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=FundingSources array}}&lt;br /&gt;
&lt;br /&gt;
This array inidcates the payment methods, that will be available to the payer on the gateway.&lt;br /&gt;
&lt;br /&gt;
This array is used by the following API endpoints:&lt;br /&gt;
* [[Payment-Start-v2-3DS]]&lt;br /&gt;
&lt;br /&gt;
= Possible values =&lt;br /&gt;
&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;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| All || Payment can be completed with all funding sources. Equivalent to [&amp;quot;Balance&amp;quot;, &amp;quot;Card&amp;quot;, &amp;quot;GooglePay&amp;quot;, &amp;quot;ApplePay&amp;quot;]&lt;br /&gt;
|-&lt;br /&gt;
| Balance || Payer can use their Barion wallet balance&lt;br /&gt;
|-&lt;br /&gt;
| BankCard|| Charge can be executed by bank card, either as a guest or as a logged-in Barion user.&lt;br /&gt;
|-&lt;br /&gt;
| GooglePay || Payment can be completed using GooglePay &amp;lt;br/&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Only available as guest on capable devices&lt;br /&gt;
|-&lt;br /&gt;
| ApplePay || Payment can be completed using ApplePay&amp;lt;br/&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Only available as guest on capable devices&lt;br /&gt;
|-&lt;br /&gt;
| BankTransfer || Payment can be completed via bank transfer&amp;lt;br/&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Supported banks vary by country and currency&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Available payment methods may be limited by Barion operators for your shop, so for eg. if your contract does not allow Google Pay, it won&#039;t be displayed on Barion Smart Gateway, no matter what you send in this property.&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=FundingInformation&amp;diff=3362</id>
		<title>FundingInformation</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=FundingInformation&amp;diff=3362"/>
		<updated>2022-03-08T13:47:04Z</updated>

		<summary type="html">&lt;p&gt;Alex: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Funding information structure}}&lt;br /&gt;
&lt;br /&gt;
This structure represents the details about the funding source of the last payment attempt. At the moment this is only used when the funding source is a bank card.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This structure is used by the following API endpoints:&lt;br /&gt;
* [[Payment-GetPaymentState-v2]]&lt;br /&gt;
&lt;br /&gt;
= Property list =&lt;br /&gt;
&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| BankCard || [[BankCard]] || The bank card used to complete the payment.&lt;br /&gt;
|-&lt;br /&gt;
| AuthorizationCode || string || The authorization code received by the card processing system when executing the payment.&lt;br /&gt;
|-&lt;br /&gt;
| ProcessResult || string || The result of the last card payment attempt. Possible values:&lt;br /&gt;
* &amp;lt;b&amp;gt;Successful&amp;lt;/b&amp;gt;: the card transaction was successful&lt;br /&gt;
* &amp;lt;b&amp;gt;ProblemWithCard&amp;lt;/b&amp;gt;: the card transaction was unsuccessful: card number, CVC or/and expiry is wrong. &lt;br /&gt;
* &amp;lt;b&amp;gt;LowFunds&amp;lt;/b&amp;gt;: the card transaction was unsuccessful due to insufficient funds&lt;br /&gt;
* &amp;lt;b&amp;gt;LostOrStolenCard&amp;lt;/b&amp;gt;: the credit card has been reported lost or stolen&lt;br /&gt;
* &amp;lt;b&amp;gt;Declined&amp;lt;/b&amp;gt;:  the payment card was declined by the acquirer&lt;br /&gt;
* &amp;lt;b&amp;gt;FraudulentTransaction&amp;lt;/b&amp;gt;: potentially fraudulent transaction, the monitoring system declined the transaction&lt;br /&gt;
* &amp;lt;b&amp;gt;CardSystemError&amp;lt;/b&amp;gt;: the card transaction failed due to the card system&lt;br /&gt;
* &amp;lt;b&amp;gt;SoftDeclined&amp;lt;/b&amp;gt;: the payment card did not support SCA at the time of the transaction&lt;br /&gt;
* &amp;lt;b&amp;gt;FailedDuringAuthentication&amp;lt;/b&amp;gt;: there was an  error during the SCA process thus authentication failed. This may not be returned if ChallengePreference was set to &amp;quot;NoChallengeNeeded&amp;quot;&lt;br /&gt;
* &amp;lt;b&amp;gt;CardNotSupported&amp;lt;/b&amp;gt;: the payment card is not supported at the time of the transaction - NOT AVAILABLE&lt;br /&gt;
* &amp;lt;b&amp;gt;SystemError&amp;lt;/b&amp;gt;: system error, in this case we try to refund the transaction amount if we have enough information to initiate it - NOT AVAILABLE&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3289</id>
		<title>Apple Pay</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3289"/>
		<updated>2021-12-14T10:45:37Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Prerequisits */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Apple Pay integration}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
Apple Pay™ is a payment option for the customer. Apple securely stores the customer&#039;s card information and hands it over to the merchant for processing.&lt;br /&gt;
{{NotificationBox|title=NOTE|text=We currently only support Apple Pay for the web, native iPhone app support is coming soon.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
== Implementation modes ==&lt;br /&gt;
Apple Pay can be emebedded two ways into your payment flow. In the first case, it will be displayed on Barion Smart Gateway (&amp;quot;Hosted Gateway&amp;quot;), which needs no further configuration and/or development on your side. The second option is to display the Apple Pay button on your site (&amp;quot;integrated mode&amp;quot;), however this needs configuration and development on your side. This page will discuss the latter.&lt;br /&gt;
* Apple Pay Hosted Gateway demo: https://test.demomerchant.shop/en/DemoClub/Pay (click the Pay button)&lt;br /&gt;
* Apple Pay integrated mode demo: https://test.demomerchant.shop/en/DemoGame/Pay&lt;br /&gt;
&lt;br /&gt;
== Prerequisites ==&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=To integrate this feature you have to develop the integration yourself! You need to understand Javascript code and it is also required to modify your webshop&#039;s server code!|color=#FF7A3D}}&lt;br /&gt;
* you must have a Barion wallet&lt;br /&gt;
* the beforementioned Barion wallet must have and approved shop&lt;br /&gt;
* for every currency you plan to conduct payments in you have to make sure there is an account created in your Barion wallet. This means that if you plan to have USD payments then there should be an USD account created in your wallet.&lt;br /&gt;
* all the example codes assume the availability of jQuery&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
=== Technical ===&lt;br /&gt;
Using Apple Pay as a token payment is currently not possible.&lt;br /&gt;
&lt;br /&gt;
=== Shopper ===&lt;br /&gt;
Apple Pay will only be visible to shoppers fulfilling the following criteria:&lt;br /&gt;
* Use an [https://support.apple.com/en-us/HT208531 Apple Pay-compatible device]&lt;br /&gt;
* Use [https://support.apple.com/en-us/HT208531#notes Safari]&lt;br /&gt;
* Located in a country or region where [https://support.apple.com/en-us/HT207957 Apple Pay is available]&lt;br /&gt;
* Have an [https://support.apple.com/guide/iphone/set-up-apple-pay-iph9b7f53382/ios existing card added to their Apple Pay wallet]&lt;br /&gt;
&lt;br /&gt;
=== Shop ===&lt;br /&gt;
* Your shop must not sell [https://developer.apple.com/apple-pay/acceptable-use-guidelines-for-websites/ prohibited items by Apple]&lt;br /&gt;
* Your site must use https!&lt;br /&gt;
&lt;br /&gt;
==Payment Process==&lt;br /&gt;
# The customer clicks the Apple Pay button.&lt;br /&gt;
# Apple Pay session has to be created using the library provided by Apple as discussed [[#Create an Apple Pay session|here]].&lt;br /&gt;
# The JS code receives a session data&lt;br /&gt;
# The JS code sends this information to the server side of the merchant&lt;br /&gt;
# The server side gathers the information necessary to call the [[ApplePay-ValidateSession|/v2/ApplePay/ValidateSession]] endpoint.&lt;br /&gt;
# Apple Pay screen is displayed, where the customer can select the card, shipping address and contact details.&lt;br /&gt;
# The JS code receives the encrypted card information.&lt;br /&gt;
# The JS code sends the encrypted information to the sever side of the merchant&lt;br /&gt;
# The server side gathers the information needed to call the [[ApplePay-StartPaymentWithAppleToken|/v2/ApplePay/StartPaymentWithAppleToken]] endpoint.&lt;br /&gt;
# The Barion API handles the request, decrypts the packages and charges the card. The result of the payment is sent back to the caller.&lt;br /&gt;
# The merchant&#039;s server communicates the result to the client side and the webshop renders the result of the payment.&lt;br /&gt;
&lt;br /&gt;
==  Configuration ==&lt;br /&gt;
=== Domain verification file===&lt;br /&gt;
First head over to secure.barion.com, and under [https://secure.barion.com/Shop Manage My Shops] page select the appropriate one, and from the dropdown, click on settings. At the bottom click the Manage Apple Pay settings blue button under the Apple Pay Settings section. On the next page  Click on the Download domain verification file button, which will download a domain association file. You should place this file at the content root of all of your sites, you&#039;re about to use apple pay in integrated mode.&lt;br /&gt;
The file must:&lt;br /&gt;
* mimemap for extension &amp;quot;.&amp;quot; should be set to &amp;quot;application/json&amp;quot;, for eg.:&lt;br /&gt;
*: &amp;lt;syntaxhighlight lang=&amp;quot;xml&amp;quot;&amp;gt;&amp;lt;mimeMap fileExtension=&amp;quot;.&amp;quot; mimeType=&amp;quot;application/json&amp;quot; /&amp;gt;&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
* be externally accessible.&lt;br /&gt;
* not be password protected.&lt;br /&gt;
* the file cannot be behind a proxy or redirect.&lt;br /&gt;
* your site must use https.&lt;br /&gt;
&lt;br /&gt;
===Configure Domains===&lt;br /&gt;
On the exact same page you&#039;ve downloaded the domain association file, enter all the domains (one in each line, without https:// or https://) you&#039;re intending to use Apple Pay.&lt;br /&gt;
&lt;br /&gt;
== Development ==&lt;br /&gt;
=== Include the Apple Pay SDK===&lt;br /&gt;
Include the following code snippet in the header of your checkout page:&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;script src=&amp;quot;https://applepay.cdn-apple.com/jsapi/v1/apple-pay-sdk.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
===Display the Apple Pay button===&lt;br /&gt;
Add the Apple Pay button to your checkout page as discussed [https://developer.apple.com/documentation/apple_pay_on_the_web/displaying_apple_pay_buttons_using_javascript here]&lt;br /&gt;
===Create an Apple Pay session===&lt;br /&gt;
When the user taps the Apple Pay button, provide a payment request and create the [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession session] as discussed [https://developer.apple.com/documentation/apple_pay_on_the_web/apple_pay_js_api/creating_an_apple_pay_session here]. Create a variable which will store, if the Apple Pay UI is dismissed (isSessionCanceled).&lt;br /&gt;
&lt;br /&gt;
===Subscribe to the &amp;lt;code&amp;gt;[https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778021-onvalidatemerchant onvalidatemerchant]&amp;lt;/code&amp;gt; event===&lt;br /&gt;
Call your backend, which will in turn call the Barion Api [[ApplePay-ValidateSession|ValidateSession]] endpoint in the event handler with the provided url as the payload, if the payment ui is not dismissed meanwhile:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
	 appleSession.onvalidatemerchant = function (event) {&lt;br /&gt;
		// TODO: disable Apple Pay button&lt;br /&gt;
		const data = {&lt;br /&gt;
			SessionValidationUrl: event.validationURL&lt;br /&gt;
		};&lt;br /&gt;
&lt;br /&gt;
		$.ajax({&lt;br /&gt;
			method: &amp;quot;POST&amp;quot;,&lt;br /&gt;
			url: &amp;quot;https://yourserver.com/ValidateApplePaySession&amp;quot;,&lt;br /&gt;
			data: data,&lt;br /&gt;
			success: function (response, status, xhr) {&lt;br /&gt;
				const merchantSession = JSON.parse(response.ApplePaySessionResponse);&lt;br /&gt;
				if(!isSessionCanceled) {&lt;br /&gt;
					appleSession.completeMerchantValidation(merchantSession);&lt;br /&gt;
				}&lt;br /&gt;
			},&lt;br /&gt;
			error: function (xhr, status, error) {&lt;br /&gt;
				// failure callback&lt;br /&gt;
				// TODO: enable Apple Pay button&lt;br /&gt;
			}&lt;br /&gt;
		});&lt;br /&gt;
	};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Subscribe to the &amp;lt;code&amp;gt;[https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778020-onpaymentauthorized onpaymentauthorized ]&amp;lt;/code&amp;gt; event===&lt;br /&gt;
Call your backend, which will in turn call the Barion Api [[ApplePay-StartPaymentWithAppleToken|StartPaymentWithAppleToken]] endpoint in the event handler with the provided payment payload:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
	appleSession.onpaymentauthorized = function (event) {&lt;br /&gt;
		let cart = {&lt;br /&gt;
			Payload = event.payment&lt;br /&gt;
			PaymentType = &amp;quot;Immediate&amp;quot;,&lt;br /&gt;
			Mode = &amp;quot;&amp;quot;,&lt;br /&gt;
		};&lt;br /&gt;
&lt;br /&gt;
		$.ajax({&lt;br /&gt;
			method: &amp;quot;POST&amp;quot;,&lt;br /&gt;
			url: &amp;quot;https://yourserver.com/StartApplePayment&amp;quot;,&lt;br /&gt;
			data: cart,&lt;br /&gt;
			success: function (response, status, xhr) {&lt;br /&gt;
				if (response.IsSuccessful &amp;amp;&amp;amp; response.PaymentStatus === 40) {&lt;br /&gt;
					appleSession.completePayment(appleSession.STATUS_SUCCESS);&lt;br /&gt;
				} else {&lt;br /&gt;
					appleSession.completePayment(appleSession.STATUS_FAILURE);&lt;br /&gt;
				}&lt;br /&gt;
			},&lt;br /&gt;
			error: function (xhr, status, error) {&lt;br /&gt;
				appleSession.completePayment(appleSession.STATUS_FAILURE);&lt;br /&gt;
			}&lt;br /&gt;
		});&lt;br /&gt;
	};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Subscribe to the &amp;lt;code&amp;gt;[https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778029-oncancel oncancel]&amp;lt;/code&amp;gt; event===&lt;br /&gt;
This method gets called every time the Apple Pay UI is dismissed. You should implement your needs accordingly (for eg. re-enable pay button). Furthermore indicate that the session was canceled, so the completePayment won&#039;t be executed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
	appleSession.onpaymentauthorized = function (event) {&lt;br /&gt;
          	// TODO: enable Apple Pay button&lt;br /&gt;
            &lt;br /&gt;
            isSessionCanceled = true;&lt;br /&gt;
	};&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Call &amp;lt;code&amp;gt;ApplePaySession.begin&amp;lt;/code&amp;gt; method===&lt;br /&gt;
Call the [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778001-begin begin] method, and the merchant validation process begins. So your final client side code will look like this:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;javascript&amp;quot;&amp;gt;&lt;br /&gt;
var request = {&lt;br /&gt;
  countryCode: &#039;HU&#039;,&lt;br /&gt;
  currencyCode: &#039;HUF&#039;,&lt;br /&gt;
  supportedNetworks: [&#039;visa&#039;, &#039;masterCard&#039;, &#039;amex&#039;, &#039;discover&#039;],&lt;br /&gt;
  merchantCapabilities: [&#039;supports3DS&#039;],&lt;br /&gt;
  total: { label: &#039;Your Merchant Name&#039;, amount: &#039;1000.00&#039; },&lt;br /&gt;
};&lt;br /&gt;
var isSessionCanceled = false;&lt;br /&gt;
&lt;br /&gt;
var appleSession = new ApplePaySession(3, request);&lt;br /&gt;
appleSession.onvalidatemerchant = function (event) {...}&lt;br /&gt;
appleSession.onpaymentauthorized = function (event) {...}&lt;br /&gt;
appleSession.begin();&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== API reference ==&lt;br /&gt;
* Barion&lt;br /&gt;
** [[ApplePay-ValidateSession|/v2/ApplePay/ValidateSession]]&lt;br /&gt;
** [[ApplePay-StartPaymentWithAppleToken|/v2/ApplePay/StartPaymentWithAppleToken]]&lt;br /&gt;
* Apple&lt;br /&gt;
** [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession ApplePaySession interface]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=3288</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=3288"/>
		<updated>2021-12-14T10:41:19Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 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:Barion-smart-gateway-en.png|right|600px]]&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;
*[[3DSecure|Strong customer authentication with 3DSecure]]&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;
==3DSecure/PSD2 SCA==&lt;br /&gt;
*[[3DSecure|3DSecure General Information]]&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&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 websites]]&lt;br /&gt;
*[[App2App_payment|Barion Smart Gateway integraton for mobile applications]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
*[[Delayed_Capture|Delayed Capture: reservation on payment card]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment_3D_Secure|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]]&lt;br /&gt;
*[[Apple_Pay|Apple Pay]]&lt;br /&gt;
*[[Google_Pay|Google Pay]]&lt;br /&gt;
*[[Payment_Buttons|Payment with bank transfer (Payment Buttons)]]&lt;br /&gt;
&lt;br /&gt;
==API docs==&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
&lt;br /&gt;
==Barion Pixel==&lt;br /&gt;
{|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot; width=&amp;quot;50%&amp;quot;|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
|[[Getting started with the Barion Pixel]] &lt;br /&gt;
|[[Áttekintés a Barion Pixel működéséről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Base Barion Pixel]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Full Barion Pixel]]&lt;br /&gt;
|[[A Teljes (Full) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Barion Pixel Consent Management requirements]]&lt;br /&gt;
| [[Barion Pixel hozzájáruláskezelési követelmények]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Barion Pixel API reference]]&lt;br /&gt;
|[[Barion Pixel API referencia]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Frequently Asked Questions about the Barion Pixel]]&lt;br /&gt;
|[[Gyakran Ismételt Kérdések a Barion Pixelről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Barion Pixel base code through the Google Tag Manager]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja a Google Tag Managerben]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Smar_Documentation|Implementing the Barion Full Pixel code in Shopify webshop]]&lt;br /&gt;
|[[Smar_Dokumentacio|A Teljes (Full) Barion Pixel implementációja Shopify webáruházban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-woocommerce-webshops|Implementing Base and Full Barion Pixel in woocommerce webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Woocommerce e-kereskedelmi platformon]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-unas-webshops|Implementing Base and Full Barion Pixel in UNAS webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja UNAS webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-shoprenter-webshops|Implementing Base and Full Barion Pixel in shoprenter webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Shoprenter webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Viltor webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Barion_for_Shopify|Barion for Shopify]]&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;
&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
*[[Dataprocessors|Barion data processor partners]]&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>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Main_Page&amp;diff=3287</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Main_Page&amp;diff=3287"/>
		<updated>2021-12-14T10:37:45Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 3DSecure/PSD2 SCA */&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:Barion-smart-gateway-en.png|right|600px]]&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;
*[[3DSecure|Strong customer authentication with 3DSecure]]&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;
==3DSecure/PSD2 SCA==&lt;br /&gt;
*[[3DSecure|3DSecure General Information]]&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&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 websites]]&lt;br /&gt;
*[[App2App_payment|Barion Smart Gateway integraton for mobile applications]]&lt;br /&gt;
*[[Reservation_payment|Payments with reservation / escrow]]&lt;br /&gt;
*[[Delayed_Capture|Delayed Capture: reservation on payment card]]&lt;br /&gt;
&amp;lt;!--*[[Mobile-app-payment|Mobile App Payment - payment for native mobile apps]]--&amp;gt;&lt;br /&gt;
*[[Token_payment_3D_Secure|Token payments - for one click or recurring payments]]&lt;br /&gt;
*[[C2C_Payments|C2C payments - sharing economy and marketplaces]]&lt;br /&gt;
*[[Payment_Buttons|Payment with bank transfer (Payment Buttons)]]&lt;br /&gt;
&lt;br /&gt;
==API docs==&lt;br /&gt;
*[[List_of_API_endpoints|List of Barion API endpoints]]&lt;br /&gt;
&lt;br /&gt;
==Barion Pixel==&lt;br /&gt;
{|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot; width=&amp;quot;50%&amp;quot;|&lt;br /&gt;
! style=&amp;quot;text-align:left;&amp;quot;|&lt;br /&gt;
|-&lt;br /&gt;
|[[Getting started with the Barion Pixel]] &lt;br /&gt;
|[[Áttekintés a Barion Pixel működéséről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Base Barion Pixel]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Full Barion Pixel]]&lt;br /&gt;
|[[A Teljes (Full) Barion Pixel implementációja]]&lt;br /&gt;
|-&lt;br /&gt;
| [[Barion Pixel Consent Management requirements]]&lt;br /&gt;
| [[Barion Pixel hozzájáruláskezelési követelmények]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Barion Pixel API reference]]&lt;br /&gt;
|[[Barion Pixel API referencia]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Frequently Asked Questions about the Barion Pixel]]&lt;br /&gt;
|[[Gyakran Ismételt Kérdések a Barion Pixelről]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing the Barion Pixel base code through the Google Tag Manager]]&lt;br /&gt;
|[[Az Alap (Base) Barion Pixel implementációja a Google Tag Managerben]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Smar_Documentation|Implementing the Barion Full Pixel code in Shopify webshop]]&lt;br /&gt;
|[[Smar_Dokumentacio|A Teljes (Full) Barion Pixel implementációja Shopify webáruházban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-woocommerce-webshops|Implementing Base and Full Barion Pixel in woocommerce webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Woocommerce e-kereskedelmi platformon]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-unas-webshops|Implementing Base and Full Barion Pixel in UNAS webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja UNAS webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|[[Implementing-the-barion-base-and-full-pixel-in-shoprenter-webshops|Implementing Base and Full Barion Pixel in shoprenter webshops]]&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Shoprenter webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|[[Az Alap (Base) és a Teljes (Full) Barion Pixel implementációja Viltor webshopokban]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Other useful info==&lt;br /&gt;
*[[Barion_for_Shopify|Barion for Shopify]]&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;
&lt;br /&gt;
*[[CodeSamples|Code Samples]]&lt;br /&gt;
*[[Security Measures]]&lt;br /&gt;
*[https://www.barion.com/en Barion Website]&lt;br /&gt;
*[[Editing_guide|Contributor guidelines and best practices]]&lt;br /&gt;
*[[Dataprocessors|Barion data processor partners]]&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>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Responsive_web_payment&amp;diff=3267</id>
		<title>Responsive web payment</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Responsive_web_payment&amp;diff=3267"/>
		<updated>2021-12-09T13:27:01Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Preparing the payment */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Responsive Web Payment}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This scenario is the most common integration for webshops that don&#039;t need any extra steps in the payment process. Users can pay through a web browser (PC, tablets, mobiles, etc.) or through the Barion mobile app (if it is installed). The Barion mobile app catches the redirection to the Barion Smart Gateway and it handles the payment within the app. You can also integrate [[App2App_payment|Barion Smart Gateway to you mobile app]].&lt;br /&gt;
&lt;br /&gt;
== Prerequisites ==&lt;br /&gt;
To be able to integrate your webshop with the Barion Payment Gateway: &lt;br /&gt;
* You must [[Creating_an_account|register a Barion wallet]] at the Barion website or in the Sandbox environment. Learn more about the Sandbox environment [[Sandbox|here]].&lt;br /&gt;
* For this wallet you have to [[Creating_a_shop|create a shop]] which should be approved by Barion.&lt;br /&gt;
* For every currency you plan to conduct payments in you have to make sure there is an account created in your Barion wallet. This means that if you plan to have USD payments then there should be an USD account created in your wallet.&lt;br /&gt;
* To make sure every corner case scenario works for your webshop it is best to topup that account with a small amount (approx. 5-10EUR or your choice of currency around the same value).&lt;br /&gt;
* For the technical communication guide please read the this: [[Calling_the_API|Calling the API]]&lt;br /&gt;
&lt;br /&gt;
== The payment process ==&lt;br /&gt;
# In all scenarios the payment starts with the &#039;&#039;&#039;preparation&#039;&#039;&#039; of the payment. This means that the webshop creates a JSON representation of the payment data. This data contains all the necessary information about the items to be purchased, the customer and the desired payment scenario.  This JSON should be sent as the body of a POST request to the &amp;lt;code&amp;gt;/v2/Payment/Start&amp;lt;/code&amp;gt; API endpoint. After the system recives the data it will be validated. If all the properties are correct a payment will be prepared in the database and a HTTP response is returned to the webshop.&lt;br /&gt;
# The &#039;&#039;&#039;response&#039;&#039;&#039; should be processed by the webshop system and the Id of the payment (&amp;lt;tt&amp;gt;PaymentId&amp;lt;/tt&amp;gt;) should be extracted from the response. This Id should be stored in the webshop database with the initial information about the payment. This is necessary because every following request is based on this Id.&lt;br /&gt;
# The next step is to &#039;&#039;&#039;redirect&#039;&#039;&#039; the customer to the Barion website to a specific URL with the &amp;lt;tt&amp;gt;PaymentId&amp;lt;/tt&amp;gt; as a query parameter.&lt;br /&gt;
# After the customer paid the requested amount and the payment is completed a server to server request is initiated by Barion towards the webshop. This is called the &#039;&#039;&#039;callback mechanism&#039;&#039;&#039;.&lt;br /&gt;
# At this point the customer is advised on the screen to return to the webshop to complete the process. If the customer clicks through the customer is &#039;&#039;&#039;redirected&#039;&#039;&#039; back to the webshop.&lt;br /&gt;
# At any point of the process the webshop can request information about the payment through the &amp;lt;code&amp;gt;v2/Payment/GetPaymentState&amp;lt;/code&amp;gt; API endpoint.&lt;br /&gt;
&lt;br /&gt;
The following two diagrams show the payment process in &amp;lt;tt&amp;gt;HTTPS&amp;lt;/tt&amp;gt; request level detail.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guest user pays with bank card&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Detailed-process-guest.png|1000px|Guest payment]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Barion user pays with their wallet&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Detailed-process-wallet.png|1000px|Wallet payment]]&lt;br /&gt;
&lt;br /&gt;
== Preparing the payment ==&lt;br /&gt;
To prepare a new payment an HTTP POST request should be made to the [[Payment-Start-v2|&amp;lt;tt&amp;gt;/v2/Payment/Start&amp;lt;/tt&amp;gt;]] API endpoint. The body of this request should contain a well-formed JSON representation of the desired payment process. To see the full specification of this endpoint head over to the [[Payment-Start-v2|API reference]]. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Structure &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The structure of a Barion Gateway payment is hierarchical. The payment is the meta information that describes the process. This payment contains at least one transaction. The transaction represents a financial transfer from a customer to a seller. The payment can contain multiple transactions, this is up to the webshop to decide how the structure of the whole process should be represented. The purchased products should be represented in the &amp;lt;tt&amp;gt;Items &amp;lt;/tt&amp;gt; array of the transactions. The total payment amount will be calculated from the attached transactions. The amount specified for the items is not validated against the transaction Total it is up to the integrator to make sure it is calculated appropriately. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Identification &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
To make sure that the payment can be properly identified always generate an Id for the payment, that is is unique in the webshop. This should be sent in the &amp;lt;code&amp;gt;PaymentRequestId&amp;lt;/code&amp;gt; property. This is true for all the transactions attached to the payment. For this user the &amp;lt;code&amp;gt;POSTransactionId&amp;lt;/code&amp;gt; of the [[PaymentTransaction]] entity. If the webshop only handles one transaction per payment it is possible to use the same Id for both the &amp;lt;code&amp;gt;PaymentRequestId&amp;lt;/code&amp;gt; and the &amp;lt;code&amp;gt;POSTransactionId&amp;lt;/code&amp;gt; although it is not recommended. In addition to this you can also provide an &amp;lt;code&amp;gt;OrderNumber&amp;lt;/code&amp;gt; for the payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Payment scenario&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In this scenario the &amp;lt;code&amp;gt;PaymentType&amp;lt;/code&amp;gt; should be set to &amp;lt;code&amp;gt;Immediate&amp;lt;/code&amp;gt; indicating that the financial transaction should take place immediately after the successful customer charge. This means that the amount charged will be placed immediately in the account of the webshop. &lt;br /&gt;
&lt;br /&gt;
Every attached transaction has a &amp;lt;code&amp;gt;Payee&amp;lt;/code&amp;gt; property. That property indicates the user wallet that will receive the amount of the transaction. It is very important to make sure that this wallet &#039;&#039;is the same wallet&#039;&#039; that opened the webshop. In technical terms the &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; provided should belong to one of the Payee&#039;s shop. This is valid for all the transactions attached to the particular payment. If one of the payees is different the scenario autmatically will be upgraded to sharing economy scenario.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Currency&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can define the currency of the payment by specifying the &amp;lt;tt&amp;gt;Currency&amp;lt;/tt&amp;gt; payment property. It is important to mention that multi-currency transactions are not supported. This means that the currency you define for the payment will be automatically the currency of all the attached transactions. The currency also defines the available precision of the transaction &amp;lt;tt&amp;gt;Total&amp;lt;/tt&amp;gt;. For example for HUF payments no decimal digits allowed while for EUR payments two decimal digits can be used. To be able to receive payments in the selected currency the shop has to have an account created in that currency in the wallet. This means that if the shop only has HUF and USD accounts in its wallet, EUR payments will not be allowed to prepare.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Example preparation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This is an example POST Start with minimum provided information.&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Always double check your POSKey and Payee properties. The POSKey is different in the sandbox and live Barion systems.|color=#FF7A3D}}&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;630ee026-3e19-469f-8325-afc9bd1ae6a6&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentType&amp;quot;: &amp;quot;Immediate&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;RedirectUrl&amp;quot;: &amp;quot;https://merchanturl/Redirect?paymentId=xyz&amp;quot;,&lt;br /&gt;
    &amp;quot;CallbackUrl&amp;quot;: &amp;quot;https://merchanturl/Callback?paymentId=xyz&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;webshop@example.com&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 37.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;A brief description of the transaction&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;iPhone 7 smart case&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Durable elegant phone case / matte black&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;piece&amp;quot;,&lt;br /&gt;
                    &amp;quot;UnitPrice&amp;quot;: 25.2,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 25.2,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-01&amp;quot;&lt;br /&gt;
                },&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Fast delivery&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Next day delivery&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;piece&amp;quot;,&lt;br /&gt;
                    &amp;quot;UnitPrice&amp;quot;: 12,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 12,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-01&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Processing the successful response ===&lt;br /&gt;
&lt;br /&gt;
After a successfully preparing the payment a JSON response is sent back as response. This JSON should be processed and some properties should be saved in the database of the webshop. The single most important property of this JSON is the &amp;lt;tt&amp;gt;PaymentId&amp;lt;/tt&amp;gt;. This should be saved into the database of the webshop along the the ids of the transactions (&amp;lt;code&amp;gt;TransactionId&amp;lt;/code&amp;gt;) attached.&lt;br /&gt;
&lt;br /&gt;
The successful response will also contain the appropriate URL where the customer should be redirected so the integration doesn&#039;t have to hard-code any URL. This information is displayed in the &amp;lt;code&amp;gt;GatewayUrl&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
At this point the &#039;&#039;Status&#039;&#039; of the payment should be &amp;lt;code&amp;gt;Prepared&amp;lt;/code&amp;gt;. This means that all the necessary information is prepared for the payment but no financial transfer happened yet.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;code&amp;gt;Transactions&amp;lt;/code&amp;gt; array are all the transaction that were processed. This array also contains the various fee transactions as well. So if there are transaction here that are not familiar it&#039;s because they were not sent by the webshop.&lt;br /&gt;
&lt;br /&gt;
==== Example success response ====&lt;br /&gt;
In this response there are no errors because the &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array is empty. There is no fee charged for the payment because there is only one transaction in the &amp;lt;code&amp;gt;Transactions&amp;lt;/code&amp;gt; array and it&#039;s the one the webshop sent in.&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;PaymentId&amp;quot;: &amp;quot;31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001&amp;quot;,&lt;br /&gt;
  &amp;quot;Status&amp;quot;: &amp;quot;Prepared&amp;quot;,&lt;br /&gt;
  &amp;quot;QRUrl&amp;quot;: &amp;quot;https://api.barion.com/qr/generate?paymentId=31dfdaff-269e-4aa0-b7a1-2e1c0cc2f933&amp;amp;size=Large&amp;quot;,&lt;br /&gt;
  &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
      &amp;quot;TransactionId&amp;quot;: &amp;quot;a4ead1d965bd48b3934847504c67ec8c&amp;quot;,&lt;br /&gt;
      &amp;quot;Status&amp;quot;: &amp;quot;Prepared&amp;quot;,&lt;br /&gt;
      &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
      &amp;quot;TransactionTime&amp;quot;: &amp;quot;2017-02-03T13:07:10.215&amp;quot;,&lt;br /&gt;
      &amp;quot;RelatedId&amp;quot;: null&lt;br /&gt;
    }&lt;br /&gt;
  ],&lt;br /&gt;
  &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;None&amp;quot;,&lt;br /&gt;
  &amp;quot;GatewayUrl&amp;quot;: &amp;quot;https://secure.barion.com/Pay?Id=31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;RedirectUrl&amp;quot;: &amp;quot;https://webshop.example.com/Redirect?paymentId=31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;CallbackUrl&amp;quot;: &amp;quot;https://webshop.example.com/blank.html?paymentId=31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: []&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Processing the error response ===&lt;br /&gt;
If there is something wrong during the preparation an error response will be provided. If this happens the &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array will be filled out with information about the problem.&lt;br /&gt;
&lt;br /&gt;
==== Possible error responses ====&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| ModelValidationError || This happens when some of the input properties fail the basic validation. For example a string property exceeds its allowed length.&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The provided &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; is invalid. Check that the key used is appropriate for the environment. The test and production environment are separate so the keys are only valid for one environment. Another problem could be that the provided key is the public key and not the private key. For API requests the secret API key should be used.&lt;br /&gt;
|-&lt;br /&gt;
| ShopIsClosed || The shop is closed in the Barion system, no payments are allowed.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser|| There is a problem with one of the participants taking part in the payment. All of them should be registered Barion users.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantReceiveEMoney|| There is a problem with the recipient of the payment. Every &amp;lt;code&amp;gt;Payee&amp;lt;/code&amp;gt; specified in the attached transactions should be a fully registered user of Barion. &lt;br /&gt;
|-&lt;br /&gt;
| NotExistingCurrency || The currency specified for the payment is not supported by the Barion system.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidFundingSource || The specified funding source is not valid. Check the &amp;lt;code&amp;gt;FundingSources&amp;lt;/code&amp;gt; input parameter.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCulture || The specified culture is not supported by the Barion system. &lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;s&amp;gt;DoNotHaveEnoughMoneyToPreparePayment&amp;lt;/s&amp;gt; || In certain corner cases when the webshops Barion balance and the incoming money is not enough to cover the Barion fee this error message is sent.&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this error code is not sent anymore&lt;br /&gt;
|-&lt;br /&gt;
| FacilitatorDoesntHaveEnoughMoney || The maximum possible income from the payment will not cover the total amount of fees the shop must pay after this transactio (topup the account of the shop, thereafter payments could be prepared).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Example error response ====&lt;br /&gt;
For example this is the error response when the authentication data (the &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt;) is not correct.&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;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;AuthenticationFailed&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;User authentication failed.&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The login information provided is incorrect. There is no such user in the system or the password is incorrect.&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/payment/start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: null,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-03T13:18:07.8878292Z&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;
== Redirecting the customer ==&lt;br /&gt;
After a successful payment preparation the next step is to redirect the customer to the secure Barion site. The URL is provided in the response of the &amp;lt;code&amp;gt;Payment/Start&amp;lt;/code&amp;gt; request. &#039;&#039;&#039;Make sure that the user is redirected properly no iframe hacks are allowed.&#039;&#039;&#039; At this point the webshop gives the flow control to the Barion system. There is no need for constant &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; requests, at least for a reasonable time period. The callback mechanism will take care of the notification. However mistakes could happen so after a reasonable time the webshop can make a &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; request just to rule out any callback errors. Again, this should not be frequent, let the user fill out its credit card information. If you want to shorten the period the user is allowed to pay you can specify this time period in the &amp;lt;code&amp;gt;PaymentWindow&amp;lt;/code&amp;gt; property.&lt;br /&gt;
&lt;br /&gt;
Once the customer arrives to the secure Barion server the payment GUI is displayed. At this point the customer either pays with e-money or with its credit card. If the payment fails for any reason (invalid card for example) the customer can try the payment again &#039;&#039;&#039;without leaving the Barion payment GUI&#039;&#039;&#039;. This means that the customer won&#039;t return automatically to webshop when the payment fails. This is worth mentioning because this could lengthen the time the customer takes at the Barion server.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Do not try to pay with the account that owns the shop! It is not permitted to purchase in your own shop!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Processing the callback ==&lt;br /&gt;
Once the payment completed a callback request is sent to webshop&#039;s server to the specified URL. In fact any change happens in the state of the payment a callback is sent out to notify the webshop. This can be interpreted as a signal to start a &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; request towards the Barion system. &#039;&#039;&#039;The callback signal is only a signal does not indicate the success of the payment!&#039;&#039;&#039; Therefore a &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; request is mandatory to make sure that the appropriate payment state is registered in the webshop as well. Read more about the whole [[Callback_mechanism|callback mechanism]].&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=WARNING|text=Flooding the Barion servers with unnecessary API calls, instead of relying on the callback mechanism, may lead to suspension of the shop.|color=#ff0000}}&lt;br /&gt;
&lt;br /&gt;
== Requesting information about the payment ==&lt;br /&gt;
Once the webshop server received the callback the webshop needs to request information about the outcome of the payment process. For this a [[Payment-GetPaymentState-v2|&amp;lt;tt&amp;gt;Payment/GetPaymentState&amp;lt;/tt&amp;gt;]] request should be sent to the Barion API.&lt;br /&gt;
&lt;br /&gt;
== Processing the returning customer ==&lt;br /&gt;
At the end of the payment process the customer decides whether to return to the webshop or just close the browser. Therefore &#039;&#039;&#039;no financial decision should be made based on the returning customer&#039;&#039;&#039;. The only valid way to decide what to do with the order to request information about the payment through the GetPaymentState API endpoint.&lt;br /&gt;
&lt;br /&gt;
== Reference ==&lt;br /&gt;
* [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
* [[Payment-Start-v2|/Payment/Start]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Responsive_web_payment&amp;diff=3266</id>
		<title>Responsive web payment</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Responsive_web_payment&amp;diff=3266"/>
		<updated>2021-12-09T13:26:09Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Preparing the payment */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Responsive Web Payment}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
This scenario is the most common integration for webshops that don&#039;t need any extra steps in the payment process. Users can pay through a web browser (PC, tablets, mobiles, etc.) or through the Barion mobile app (if it is installed). The Barion mobile app catches the redirection to the Barion Smart Gateway and it handles the payment within the app. You can also integrate [[App2App_payment|Barion Smart Gateway to you mobile app]].&lt;br /&gt;
&lt;br /&gt;
== Prerequisites ==&lt;br /&gt;
To be able to integrate your webshop with the Barion Payment Gateway: &lt;br /&gt;
* You must [[Creating_an_account|register a Barion wallet]] at the Barion website or in the Sandbox environment. Learn more about the Sandbox environment [[Sandbox|here]].&lt;br /&gt;
* For this wallet you have to [[Creating_a_shop|create a shop]] which should be approved by Barion.&lt;br /&gt;
* For every currency you plan to conduct payments in you have to make sure there is an account created in your Barion wallet. This means that if you plan to have USD payments then there should be an USD account created in your wallet.&lt;br /&gt;
* To make sure every corner case scenario works for your webshop it is best to topup that account with a small amount (approx. 5-10EUR or your choice of currency around the same value).&lt;br /&gt;
* For the technical communication guide please read the this: [[Calling_the_API|Calling the API]]&lt;br /&gt;
&lt;br /&gt;
== The payment process ==&lt;br /&gt;
# In all scenarios the payment starts with the &#039;&#039;&#039;preparation&#039;&#039;&#039; of the payment. This means that the webshop creates a JSON representation of the payment data. This data contains all the necessary information about the items to be purchased, the customer and the desired payment scenario.  This JSON should be sent as the body of a POST request to the &amp;lt;code&amp;gt;/v2/Payment/Start&amp;lt;/code&amp;gt; API endpoint. After the system recives the data it will be validated. If all the properties are correct a payment will be prepared in the database and a HTTP response is returned to the webshop.&lt;br /&gt;
# The &#039;&#039;&#039;response&#039;&#039;&#039; should be processed by the webshop system and the Id of the payment (&amp;lt;tt&amp;gt;PaymentId&amp;lt;/tt&amp;gt;) should be extracted from the response. This Id should be stored in the webshop database with the initial information about the payment. This is necessary because every following request is based on this Id.&lt;br /&gt;
# The next step is to &#039;&#039;&#039;redirect&#039;&#039;&#039; the customer to the Barion website to a specific URL with the &amp;lt;tt&amp;gt;PaymentId&amp;lt;/tt&amp;gt; as a query parameter.&lt;br /&gt;
# After the customer paid the requested amount and the payment is completed a server to server request is initiated by Barion towards the webshop. This is called the &#039;&#039;&#039;callback mechanism&#039;&#039;&#039;.&lt;br /&gt;
# At this point the customer is advised on the screen to return to the webshop to complete the process. If the customer clicks through the customer is &#039;&#039;&#039;redirected&#039;&#039;&#039; back to the webshop.&lt;br /&gt;
# At any point of the process the webshop can request information about the payment through the &amp;lt;code&amp;gt;v2/Payment/GetPaymentState&amp;lt;/code&amp;gt; API endpoint.&lt;br /&gt;
&lt;br /&gt;
The following two diagrams show the payment process in &amp;lt;tt&amp;gt;HTTPS&amp;lt;/tt&amp;gt; request level detail.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guest user pays with bank card&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Detailed-process-guest.png|1000px|Guest payment]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Barion user pays with their wallet&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[file:Detailed-process-wallet.png|1000px|Wallet payment]]&lt;br /&gt;
&lt;br /&gt;
== Preparing the payment ==&lt;br /&gt;
To prepare a new payment an HTTP POST request should be made to the [[Payment-Start-v2|&amp;lt;tt&amp;gt;/v2/Payment/Start&amp;lt;/tt&amp;gt;]] API endpoint. The body of this request should contain a well-formed JSON representation of the desired payment process. To see the full specification of this endpoint head over to the [[Payment-Start-v2|API reference]]. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Structure &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The structure of a Barion Gateway payment is hierarchical. The payment is the meta information that describes the process. This payment contains at least one transaction. The transaction represents a financial transfer from a customer to a seller. The payment can contain multiple transactions, this is up to the webshop to decide how the structure of the whole process should be represented. The purchased products should be represented in the &amp;lt;tt&amp;gt;Items &amp;lt;/tt&amp;gt; array of the transactions. The total payment amount will be calculated from the attached transactions. The amount specified for the items is not validated against the transaction Total it is up to the integrator to make sure it is calculated appropriately. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Identification &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
To make sure that the payment can be properly identified always generate an Id for the payment, that is is unique in the webshop. This should be sent in the &amp;lt;code&amp;gt;PaymentRequestId&amp;lt;/code&amp;gt; property. This is true for all the transactions attached to the payment. For this user the &amp;lt;code&amp;gt;POSTransactionId&amp;lt;/code&amp;gt; of the [[PaymentTransaction]] entity. If the webshop only handles one transaction per payment it is possible to use the same Id for both the &amp;lt;code&amp;gt;PaymentRequestId&amp;lt;/code&amp;gt; and the &amp;lt;code&amp;gt;POSTransactionId&amp;lt;/code&amp;gt; although it is not recommended. In addition to this you can also provide an &amp;lt;code&amp;gt;OrderNumber&amp;lt;/code&amp;gt; for the payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Payment scenario&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In this scenario the &amp;lt;code&amp;gt;PaymentType&amp;lt;/code&amp;gt; should be set to &amp;lt;code&amp;gt;Immediate&amp;lt;/code&amp;gt; indicating that the financial transaction should take place immediately after the successful customer charge. This means that the amount charged will be placed immediately in the account of the webshop. &lt;br /&gt;
&lt;br /&gt;
Every attached transaction has a &amp;lt;code&amp;gt;Payee&amp;lt;/code&amp;gt; property. That property indicates the user wallet that will receive the amount of the transaction. It is very important to make sure that this wallet &#039;&#039;is the same wallet&#039;&#039; that opened the webshop. In technical terms the &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; provided should belong to one of the Payee&#039;s shop. This is valid for all the transactions attached to the particular payment. If one of the payees is different the scenario autmatically will be upgraded to sharing economy scenario.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Currency&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You can define the currency of the payment by specifying the &amp;lt;tt&amp;gt;Currency&amp;lt;/tt&amp;gt; payment property. It is important to mention that multi-currency transactions are not supported. This means that the currency you define for the payment will be automatically the currency of all the attached transactions. The currency also defines the available precision of the transaction &amp;lt;tt&amp;gt;Total&amp;lt;/tt&amp;gt;. For example for HUF payments no decimal digits allowed while for EUR payments two decimal digits can be used. To be able to receive payments in the selected currency the shop has to have an account created in that currency in the wallet. This means that if the shop only has HUF and USD accounts in its wallet, EUR payments will not be allowed to prepare.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Example preparation&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
This is an example POST Start with minimum provided information.&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Always double check your POSKey and Payee properties. The POSKey is different in the sandbox and live Barion systems.|color=#FF7A3D}}&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;630ee026-3e19-469f-8325-afc9bd1ae6a6&amp;quot;,&lt;br /&gt;
    &amp;quot;RedirectUrl&amp;quot;: &amp;quot;https://merchanturl/Redirect?paymentId=xyz&amp;quot;,&lt;br /&gt;
    &amp;quot;CallbackUrl&amp;quot;: &amp;quot;https://merchanturl/Callback?paymentId=xyz&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentType&amp;quot;: &amp;quot;Immediate&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;webshop@example.com&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 37.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;A brief description of the transaction&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;iPhone 7 smart case&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Durable elegant phone case / matte black&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;piece&amp;quot;,&lt;br /&gt;
                    &amp;quot;UnitPrice&amp;quot;: 25.2,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 25.2,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-01&amp;quot;&lt;br /&gt;
                },&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Fast delivery&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Next day delivery&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;piece&amp;quot;,&lt;br /&gt;
                    &amp;quot;UnitPrice&amp;quot;: 12,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 12,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-01&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Processing the successful response ===&lt;br /&gt;
&lt;br /&gt;
After a successfully preparing the payment a JSON response is sent back as response. This JSON should be processed and some properties should be saved in the database of the webshop. The single most important property of this JSON is the &amp;lt;tt&amp;gt;PaymentId&amp;lt;/tt&amp;gt;. This should be saved into the database of the webshop along the the ids of the transactions (&amp;lt;code&amp;gt;TransactionId&amp;lt;/code&amp;gt;) attached.&lt;br /&gt;
&lt;br /&gt;
The successful response will also contain the appropriate URL where the customer should be redirected so the integration doesn&#039;t have to hard-code any URL. This information is displayed in the &amp;lt;code&amp;gt;GatewayUrl&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
At this point the &#039;&#039;Status&#039;&#039; of the payment should be &amp;lt;code&amp;gt;Prepared&amp;lt;/code&amp;gt;. This means that all the necessary information is prepared for the payment but no financial transfer happened yet.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;code&amp;gt;Transactions&amp;lt;/code&amp;gt; array are all the transaction that were processed. This array also contains the various fee transactions as well. So if there are transaction here that are not familiar it&#039;s because they were not sent by the webshop.&lt;br /&gt;
&lt;br /&gt;
==== Example success response ====&lt;br /&gt;
In this response there are no errors because the &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array is empty. There is no fee charged for the payment because there is only one transaction in the &amp;lt;code&amp;gt;Transactions&amp;lt;/code&amp;gt; array and it&#039;s the one the webshop sent in.&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;PaymentId&amp;quot;: &amp;quot;31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001&amp;quot;,&lt;br /&gt;
  &amp;quot;Status&amp;quot;: &amp;quot;Prepared&amp;quot;,&lt;br /&gt;
  &amp;quot;QRUrl&amp;quot;: &amp;quot;https://api.barion.com/qr/generate?paymentId=31dfdaff-269e-4aa0-b7a1-2e1c0cc2f933&amp;amp;size=Large&amp;quot;,&lt;br /&gt;
  &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
      &amp;quot;TransactionId&amp;quot;: &amp;quot;a4ead1d965bd48b3934847504c67ec8c&amp;quot;,&lt;br /&gt;
      &amp;quot;Status&amp;quot;: &amp;quot;Prepared&amp;quot;,&lt;br /&gt;
      &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
      &amp;quot;TransactionTime&amp;quot;: &amp;quot;2017-02-03T13:07:10.215&amp;quot;,&lt;br /&gt;
      &amp;quot;RelatedId&amp;quot;: null&lt;br /&gt;
    }&lt;br /&gt;
  ],&lt;br /&gt;
  &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;None&amp;quot;,&lt;br /&gt;
  &amp;quot;GatewayUrl&amp;quot;: &amp;quot;https://secure.barion.com/Pay?Id=31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;RedirectUrl&amp;quot;: &amp;quot;https://webshop.example.com/Redirect?paymentId=31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;CallbackUrl&amp;quot;: &amp;quot;https://webshop.example.com/blank.html?paymentId=31dfdaff269e4aa0b7a12e1c0cc2f933&amp;quot;,&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: []&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Processing the error response ===&lt;br /&gt;
If there is something wrong during the preparation an error response will be provided. If this happens the &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array will be filled out with information about the problem.&lt;br /&gt;
&lt;br /&gt;
==== Possible error responses ====&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| ModelValidationError || This happens when some of the input properties fail the basic validation. For example a string property exceeds its allowed length.&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The provided &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt; is invalid. Check that the key used is appropriate for the environment. The test and production environment are separate so the keys are only valid for one environment. Another problem could be that the provided key is the public key and not the private key. For API requests the secret API key should be used.&lt;br /&gt;
|-&lt;br /&gt;
| ShopIsClosed || The shop is closed in the Barion system, no payments are allowed.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser|| There is a problem with one of the participants taking part in the payment. All of them should be registered Barion users.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantReceiveEMoney|| There is a problem with the recipient of the payment. Every &amp;lt;code&amp;gt;Payee&amp;lt;/code&amp;gt; specified in the attached transactions should be a fully registered user of Barion. &lt;br /&gt;
|-&lt;br /&gt;
| NotExistingCurrency || The currency specified for the payment is not supported by the Barion system.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidFundingSource || The specified funding source is not valid. Check the &amp;lt;code&amp;gt;FundingSources&amp;lt;/code&amp;gt; input parameter.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCulture || The specified culture is not supported by the Barion system. &lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;s&amp;gt;DoNotHaveEnoughMoneyToPreparePayment&amp;lt;/s&amp;gt; || In certain corner cases when the webshops Barion balance and the incoming money is not enough to cover the Barion fee this error message is sent.&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this error code is not sent anymore&lt;br /&gt;
|-&lt;br /&gt;
| FacilitatorDoesntHaveEnoughMoney || The maximum possible income from the payment will not cover the total amount of fees the shop must pay after this transactio (topup the account of the shop, thereafter payments could be prepared).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Example error response ====&lt;br /&gt;
For example this is the error response when the authentication data (the &amp;lt;code&amp;gt;POSKey&amp;lt;/code&amp;gt;) is not correct.&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;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;AuthenticationFailed&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;User authentication failed.&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The login information provided is incorrect. There is no such user in the system or the password is incorrect.&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/payment/start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: null,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-03T13:18:07.8878292Z&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;
== Redirecting the customer ==&lt;br /&gt;
After a successful payment preparation the next step is to redirect the customer to the secure Barion site. The URL is provided in the response of the &amp;lt;code&amp;gt;Payment/Start&amp;lt;/code&amp;gt; request. &#039;&#039;&#039;Make sure that the user is redirected properly no iframe hacks are allowed.&#039;&#039;&#039; At this point the webshop gives the flow control to the Barion system. There is no need for constant &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; requests, at least for a reasonable time period. The callback mechanism will take care of the notification. However mistakes could happen so after a reasonable time the webshop can make a &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; request just to rule out any callback errors. Again, this should not be frequent, let the user fill out its credit card information. If you want to shorten the period the user is allowed to pay you can specify this time period in the &amp;lt;code&amp;gt;PaymentWindow&amp;lt;/code&amp;gt; property.&lt;br /&gt;
&lt;br /&gt;
Once the customer arrives to the secure Barion server the payment GUI is displayed. At this point the customer either pays with e-money or with its credit card. If the payment fails for any reason (invalid card for example) the customer can try the payment again &#039;&#039;&#039;without leaving the Barion payment GUI&#039;&#039;&#039;. This means that the customer won&#039;t return automatically to webshop when the payment fails. This is worth mentioning because this could lengthen the time the customer takes at the Barion server.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Do not try to pay with the account that owns the shop! It is not permitted to purchase in your own shop!|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Processing the callback ==&lt;br /&gt;
Once the payment completed a callback request is sent to webshop&#039;s server to the specified URL. In fact any change happens in the state of the payment a callback is sent out to notify the webshop. This can be interpreted as a signal to start a &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; request towards the Barion system. &#039;&#039;&#039;The callback signal is only a signal does not indicate the success of the payment!&#039;&#039;&#039; Therefore a &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; request is mandatory to make sure that the appropriate payment state is registered in the webshop as well. Read more about the whole [[Callback_mechanism|callback mechanism]].&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=WARNING|text=Flooding the Barion servers with unnecessary API calls, instead of relying on the callback mechanism, may lead to suspension of the shop.|color=#ff0000}}&lt;br /&gt;
&lt;br /&gt;
== Requesting information about the payment ==&lt;br /&gt;
Once the webshop server received the callback the webshop needs to request information about the outcome of the payment process. For this a [[Payment-GetPaymentState-v2|&amp;lt;tt&amp;gt;Payment/GetPaymentState&amp;lt;/tt&amp;gt;]] request should be sent to the Barion API.&lt;br /&gt;
&lt;br /&gt;
== Processing the returning customer ==&lt;br /&gt;
At the end of the payment process the customer decides whether to return to the webshop or just close the browser. Therefore &#039;&#039;&#039;no financial decision should be made based on the returning customer&#039;&#039;&#039;. The only valid way to decide what to do with the order to request information about the payment through the GetPaymentState API endpoint.&lt;br /&gt;
&lt;br /&gt;
== Reference ==&lt;br /&gt;
* [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]]&lt;br /&gt;
* [[Payment-Start-v2|/Payment/Start]]&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=3142</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=3142"/>
		<updated>2021-10-04T15:01:10Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 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 during working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The live and the sandbox 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;
*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. &lt;br /&gt;
&#039;&#039;&#039;Note that you still have to &amp;lt;u&amp;gt;send the shop for approval&amp;lt;/u&amp;gt; on the shop editing page!&#039;&#039;&#039;&lt;br /&gt;
Also 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.&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;
=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;
&amp;lt;br&amp;gt;Each test cards are represented with different value in the response of &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; (see &amp;lt;code&amp;gt;FundingInformation&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;ProcessResult&amp;lt;/code&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - SUCCEED - the card transaction was successful&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;
GetPaymentState result: &amp;lt;code&amp;gt;Successful&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - FAIL - the card transaction was unsuccessful: card number, CVC or/and expiry is wrong.&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;
GetPaymentState result: &amp;lt;code&amp;gt;ProblemwithCard&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 3&#039;&#039;&#039; - FAIL - the card transaction was unsuccessful due to insufficient funds&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 9999&#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;
GetPaymentState result: &amp;lt;code&amp;gt;LowFunds&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 4&#039;&#039;&#039; - FAIL - the credit card has been reported lost or stolen&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 1111&#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;
GetPaymentState result: &amp;lt;code&amp;gt;LostOrStolenCard&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 5&#039;&#039;&#039; - FAIL - the payment card was declined by the acquirer&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 3331&#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;
GetPaymentState result: &amp;lt;code&amp;gt;Declined&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 6&#039;&#039;&#039; - FAIL - Due to potentially fraudulent transaction, the monitoring system declined the transaction&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 6664&#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;
GetPaymentState result: &amp;lt;code&amp;gt;FraudulentTransaction&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 7&#039;&#039;&#039; - FAIL - the card transaction failed due to the card system&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 7779&#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;
GetPaymentState result: &amp;lt;code&amp;gt;CardSystemError&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 8&#039;&#039;&#039; - FAIL - the payment card did not support SCA at the time of the transaction&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 0006&#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;
GetPaymentState result: &amp;lt;code&amp;gt;ScaSoftDeclined&amp;lt;/code&amp;gt;&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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=RecurrenceType&amp;diff=3085</id>
		<title>RecurrenceType</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=RecurrenceType&amp;diff=3085"/>
		<updated>2021-09-08T14:19:40Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Enum list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=RecurrenceType enumeration}}&lt;br /&gt;
&lt;br /&gt;
This enum indicates the type of recurrence that the payment represents.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This enum is used by the following API endpoints:&lt;br /&gt;
* [[Payment-Start-v2-3DS]]&lt;br /&gt;
&lt;br /&gt;
= Enum list =&lt;br /&gt;
&lt;br /&gt;
{{api_enum_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| OneClickPayment || 10 || &lt;br /&gt;
&#039;&#039;&#039;Consumer-initiated transactions (CITs):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The purchase is initiated by the customer on the merchant&#039;s website , but instead of redirecting the customer to the Barion Smart Gateway the recurrence Id is used for a more convenient payment flow.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:red&amp;quot;&amp;gt;In this case &amp;lt;u&amp;gt;3DS authentication is required&amp;lt;/u&amp;gt; on the merchant&#039;s site.&amp;lt;/span&amp;gt; More info: [[Token_payment_3D_Secure#Off-site 3DS v2 authentication|off-site 3DS v2 authentication]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MerchantInitiatedPayment || 0 || &lt;br /&gt;
&#039;&#039;&#039;Merchant-initiated transactions (MITs) with non-fixed value:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
The customer authorizes the merchant to charge her in the future. Subsequent payments are initiated by the merchant and the customer is not present for these purchases. &lt;br /&gt;
&lt;br /&gt;
For subsequent payments &#039;&#039;&#039;no 3DS&#039;&#039;&#039; authentication (challenge) is required. This type of transaction is out of scope of the &amp;lt;abbr title=&amp;quot;Strong Customer Authentication&amp;quot;&amp;gt;SCA&amp;lt;/abbr&amp;gt; framework.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The liability in case of fraud is on the merchant.&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| RecurringPayment || 20 || &lt;br /&gt;
&#039;&#039;&#039;Merchant-initiated transactions (MITs) with fixed value: &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The customer authorizes the merchant to charge for the services/products periodically, typically in case of subscriptions. Subsequent payments are initiated by the merchant and &#039;&#039;&#039;the customer is not present&#039;&#039;&#039; during these payment. Subsequent charges can only be the &#039;&#039;&#039;same or lower as the initial amount&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For subsequent payments &#039;&#039;&#039;no 3DS&#039;&#039;&#039; authentication (challenge) is required. This type of transaction can be exempted from the &amp;lt;abbr title=&amp;quot;Strong Customer Authentication&amp;quot;&amp;gt;SCA&amp;lt;/abbr&amp;gt; framework.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The liability in case of fraud is on the card issuer.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Im case of this type the RecurringExpiry and RecurringFrequency subfields are mandatory in the PurchaseInformation field.  More info: [[PurchaseInformation]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=RecurrenceType&amp;diff=3084</id>
		<title>RecurrenceType</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=RecurrenceType&amp;diff=3084"/>
		<updated>2021-09-08T14:14:26Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* Enum list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=RecurrenceType enumeration}}&lt;br /&gt;
&lt;br /&gt;
This enum indicates the type of recurrence that the payment represents.&lt;br /&gt;
&lt;br /&gt;
= API usage =&lt;br /&gt;
&lt;br /&gt;
This enum is used by the following API endpoints:&lt;br /&gt;
* [[Payment-Start-v2-3DS]]&lt;br /&gt;
&lt;br /&gt;
= Enum list =&lt;br /&gt;
&lt;br /&gt;
{{api_enum_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| OneClickPayment || 10 || &lt;br /&gt;
&#039;&#039;&#039;Consumer-initiated transactions (CITs):&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The purchase is initiated by the customer on the merchant&#039;s website , but instead of redirecting the customer to the Barion Smart Gateway the recurrence Id is used for a more convenient payment flow.&lt;br /&gt;
&amp;lt;span style=&amp;quot;color:red&amp;quot;&amp;gt;In this case &amp;lt;u&amp;gt;3DS authentication is required&amp;lt;/u&amp;gt; on the merchant&#039;s site.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| MerchantInitiatedPayment || 0 || &lt;br /&gt;
&#039;&#039;&#039;Merchant-initiated transactions (MITs) with non-fixed value:&#039;&#039;&#039;&lt;br /&gt;
 &lt;br /&gt;
The customer authorizes the merchant to charge her in the future. Subsequent payments are initiated by the merchant and the customer is not present for these purchases. &lt;br /&gt;
&lt;br /&gt;
For subsequent payments &#039;&#039;&#039;no 3DS&#039;&#039;&#039; authentication (challenge) is required. This type of transaction is out of scope of the &amp;lt;abbr title=&amp;quot;Strong Customer Authentication&amp;quot;&amp;gt;SCA&amp;lt;/abbr&amp;gt; framework.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The liability in case of fraud is on the merchant.&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| RecurringPayment || 20 || &lt;br /&gt;
&#039;&#039;&#039;Merchant-initiated transactions (MITs) with fixed value: &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The customer authorizes the merchant to charge for the services/products periodically, typically in case of subscriptions. Subsequent payments are initiated by the merchant and &#039;&#039;&#039;the customer is not present&#039;&#039;&#039; during these payment. Subsequent charges can only be the &#039;&#039;&#039;same or lower as the initial amount&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For subsequent payments &#039;&#039;&#039;no 3DS&#039;&#039;&#039; authentication (challenge) is required. This type of transaction can be exempted from the &amp;lt;abbr title=&amp;quot;Strong Customer Authentication&amp;quot;&amp;gt;SCA&amp;lt;/abbr&amp;gt; framework.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The liability in case of fraud is on the card issuer.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Im case of this type the RecurringExpiry and RecurringFrequency subfields are mandatory in the PurchaseInformation field.  More info: [[PurchaseInformation]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=3041</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=3041"/>
		<updated>2021-08-24T20:20:09Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 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 during working hours)&lt;br /&gt;
*Sandbox is totally self-service, no contract or NDA needed to use it&lt;br /&gt;
*No transaction fees are spent during development and testing&lt;br /&gt;
*The live and the sandbox 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;
*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. &lt;br /&gt;
&#039;&#039;&#039;Note that you still have to &amp;lt;u&amp;gt;send the shop for approval&amp;lt;/u&amp;gt; on the shop editing page!&#039;&#039;&#039;&lt;br /&gt;
Also 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.&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;
=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;
&amp;lt;br&amp;gt;Each test cards are represented with different value in the response of &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; (see &amp;lt;code&amp;gt;FundingInformation&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;ProcessResult&amp;lt;/code&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
[[file:Test-card2.png]]&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 1&#039;&#039;&#039; - SUCCEED - the card transaction was successful&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;
GetPaymentState result: &amp;lt;code&amp;gt;Successful&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 2&#039;&#039;&#039; - FAIL - the card transaction was unsuccessful: card number, CVC or/and expiry is wrong.&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;
GetPaymentState result: &amp;lt;code&amp;gt;ProblemwithCard&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 3&#039;&#039;&#039; - FAIL - the card transaction was unsuccessful due to insufficient funds&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 9999&#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;
GetPaymentState result: &amp;lt;code&amp;gt;LowFunds&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 4&#039;&#039;&#039; - FAIL - the credit card has been reported lost or stolen&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 1111&#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;
GetPaymentState result: &amp;lt;code&amp;gt;LostOrStolenCard&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 5&#039;&#039;&#039; - FAIL - the payment card was declined by the acquirer&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 3331&#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;
GetPaymentState result: &amp;lt;code&amp;gt;Declined&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 6&#039;&#039;&#039; - FAIL - Due to potentially fraudulent transaction, the monitoring system declined the transaction&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 6664&#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;
GetPaymentState result: &amp;lt;code&amp;gt;FraudulentTransaction&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 7&#039;&#039;&#039; - FAIL - the card transaction failed due to the card system&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 7779&#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;
GetPaymentState result: &amp;lt;code&amp;gt;CardSystemError&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;CARD 8&#039;&#039;&#039; - FAIL - the payment card did not support SCA at the time of the transaction&lt;br /&gt;
*BIN: &#039;&#039;&#039;4444 8888 8888 0006&#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;
GetPaymentState result: &amp;lt;code&amp;gt;ScaSoftDeclined&amp;lt;/code&amp;gt;&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;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Payment-Start-v2&amp;diff=3038</id>
		<title>Payment-Start-v2</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Payment-Start-v2&amp;diff=3038"/>
		<updated>2021-08-18T07:24:02Z</updated>

		<summary type="html">&lt;p&gt;Alex: /* 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;
{|&lt;br /&gt;
|-&lt;br /&gt;
|{{3dsfield}} || Properties marked with this must be provided to comply with 3D Secure authentication. The more attributes you provide the more chance you have to avoid the challenge flow.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; if the merchant does not provide 3DS-related properties, it doesn&#039;t mean that the payment will fail. It means that the payer will have a higher chance of getting a challenge during payment.&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;
** &amp;quot;DelayedCapture&amp;quot; &lt;br /&gt;
|| The type of 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]], and delayed capture: [[Delayed_Capture|Delayed capture]].&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;
| DelayedCapturePeriod || TimeSpan (d.hh:mm:ss) || &lt;br /&gt;
* Required only if PaymentType is &amp;quot;DelayedCapture&amp;quot;&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: 7 days (21 days in case of a Hungarian shop)&lt;br /&gt;
* Default value: seven days&lt;br /&gt;
|| This is the time window that allows the shop to complete (finalize) the payment. If this does not happen within the time window, the system releases the payment amount.&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 evaluation is not supported&lt;br /&gt;
|| Flag indicating whether 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 subscription 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 token payments&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
* Must be unique per shop and per user&lt;br /&gt;
* [https://docs.barion.com/Token_payment#Creating_the_token Generated by the shop]&lt;br /&gt;
|| A string used to identify a given token 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 token 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 a token 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;
&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;
** &amp;quot;Card&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;
&lt;br /&gt;
&lt;br /&gt;
| PayerHint || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Optional, but recommended&lt;br /&gt;
* Maximum length: 256 characters&lt;br /&gt;
|| The shop can 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 or the shop would like to help the guest payer with filling in the email field for her/him. If provided, the Barion Smart Gateway automatically fills out the e-mail address field in the Barion wallet login form and the guest payer form, speeding up the payment process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CardHolderNameHint || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Optional, but recommended&lt;br /&gt;
* Between 2 and 45 characters&lt;br /&gt;
|| The shop can provide a hint for the customer&#039;s name on the card to speed up the payment flow. If a value is provided, the cardholder name input will be pre-filled with it and the customer can use the pre-filled value instead of typing it out on its own, which speeds up the payment process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceType || [[RecurrenceType]] || &lt;br /&gt;
* Required for {{3dsfield}}, when executing token payments&lt;br /&gt;
|| Describes the nature of the token payment.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TraceId || string || &lt;br /&gt;
* Required for {{3dsfield}}, when executing token payments&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| Identifies the nature of the token payment. &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string || &lt;br /&gt;
* Required &lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the payer should be redirected after the payment is completed or canceled. 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;
* Required &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. 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 its 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;
* Required for {{3dsfield}}&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; (Slovak)&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;
{{CurrencyList}}&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;
| PayerPhoneNumber || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
* Required for using payment buttons&lt;br /&gt;
|| The &#039;&#039;&#039;mobile&#039;&#039;&#039; phone number of the payer. Must be set to enable [[Payment_Buttons|payment buttons]]. The number must be sent in the expected format, without + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| PayerWorkPhoneNumber || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|| The work phone of the payer. The number must be sent in the expected format, without + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| PayerHomeNumber || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|| The home phone number of the payer. The number must be sent in the expected format, without + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| BillingAddress || [[BillingAddress]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| The billing address associated with the payment, if applicable.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PayerAccount || [[PayerAccountInformation]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| Information about the account of the payer in the merchant&#039;s system.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PurchaseInformation|| [[PurchaseInformation]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| Information about current purchase.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ChallengePreference || [[ChallengePreference]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| The merchant&#039;s preference of the 3DS challenge. Here you can specify what 3DS authentication should be utilized.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&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 source, 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;. In case the payment can not be processed due to lack of 3DS v2 information &amp;lt;code&amp;gt;ThreeDSAuthenticationRequired&amp;lt;/code&amp;gt; is returned. In this case, either offsite 3DS v2 authentication should be performed or the TraceId of the initial payment should be sent as well.&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;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ThreeDsClientAuthData || string || Encrypted client authentication data required for 3D Secure processing. This value can be used when the webshop first tried to complete the payment without user interaction, but the charge failed due to a 3D Secure challenge being mandatory.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TraceId || string || A unique value generated by the card issuer to track a chain of [[Token_payment_3D_Secure|recurring or token payments that require 3D Secure authentication]]. This shall be used in such scenarios, otherwise it can be ignored.&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Alex</name></author>
	</entry>
</feed>