<?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=Stankovicsa</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=Stankovicsa"/>
	<link rel="alternate" type="text/html" href="https://docs.barion.com/Special:Contributions/Stankovicsa"/>
	<updated>2026-11-21T13:01:57Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_release_notes_-_2023r2&amp;diff=4072</id>
		<title>Barion release notes - 2023r2</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_release_notes_-_2023r2&amp;diff=4072"/>
		<updated>2023-06-16T12:17:07Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion release notes - 2023.05.23}}&lt;br /&gt;
&lt;br /&gt;
=Short summary=&lt;br /&gt;
Barion is introducing a set of new API endpoints that greatly enhance the creation and querying functionalities of online shops, known as points of sale (POS), for customers who already possess a Barion Wallet. These endpoints offer businesses powerful tools to automate the process of establishing their shops directly from their own interface. The two key features provided by these endpoints are:&lt;br /&gt;
&lt;br /&gt;
* [[Pos-Create-v1|Create a POS]]&lt;br /&gt;
* [[Pos-Get-v1|Query all details of a POS]]&lt;br /&gt;
&lt;br /&gt;
In addition, we rollout out a new update that transforms bank transfers from your Barion Wallet to a Barion virtual account number into a direct money transfer. This update enables you to transfer funds directly for free.&lt;br /&gt;
&lt;br /&gt;
=Creating a new POS=&lt;br /&gt;
With the [[Pos-Create-v1|Create a POS]] endpoint, you can effortlessly generate a new point of sale (POS) by making a simple API call. To utilize this functionality, it is essential to have already created a Barion Wallet and possess a solid understanding of how to interact with the Barion API ([[Calling_the_API|call the Barion API]]). By leveraging this endpoint, you can seamlessly integrate the creation of POS systems into your existing workflow, enhancing the overall experience for both you and your customers.&lt;br /&gt;
&lt;br /&gt;
=Querying POS details=&lt;br /&gt;
The [[Pos-Get-v1|Query all details of a POS]] endpoint offers the capability to retrieve comprehensive information about a point of sale (POS) that is associated with a Barion Wallet. By making use of this endpoint, you can easily obtain all the relevant details and data related to a specific POS.&lt;br /&gt;
&lt;br /&gt;
=Barion Wallet to Barion vIBAN transfers=&lt;br /&gt;
From this release onwards, when you initiate a bank transfer from your Barion Wallet to a Barion vIBAN or GIRO, we automatically recognize it and handle it as a direct transfer instead. This means that the transaction is instantaneous and free of charge.&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_release_notes_-_2023r2&amp;diff=4071</id>
		<title>Barion release notes - 2023r2</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_release_notes_-_2023r2&amp;diff=4071"/>
		<updated>2023-06-16T12:16:24Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Querying POS details */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion release notes - 2023.05.23}}&lt;br /&gt;
&lt;br /&gt;
=Short summary=&lt;br /&gt;
Barion is introducing a set of new API endpoints that greatly enhance the creation and querying functionalities of online shops, known as points of sale (POS), for customers who already possess a Barion Wallet. These endpoints offer businesses powerful tools to automate the process of establishing their shops directly from their own interface. The two key features provided by these endpoints are:&lt;br /&gt;
&lt;br /&gt;
* [[Pos-Create-v1|Create a POS]]&lt;br /&gt;
* [[Pos-GetState-v1|Query all details of a POS]]&lt;br /&gt;
&lt;br /&gt;
In addition, we rollout out a new update that transforms bank transfers from your Barion Wallet to a Barion virtual account number into a direct money transfer. This update enables you to transfer funds directly for free.&lt;br /&gt;
&lt;br /&gt;
=Creating a new POS=&lt;br /&gt;
With the [[Pos-Create-v1|Create a POS]] endpoint, you can effortlessly generate a new point of sale (POS) by making a simple API call. To utilize this functionality, it is essential to have already created a Barion Wallet and possess a solid understanding of how to interact with the Barion API ([[Calling_the_API|call the Barion API]]). By leveraging this endpoint, you can seamlessly integrate the creation of POS systems into your existing workflow, enhancing the overall experience for both you and your customers.&lt;br /&gt;
&lt;br /&gt;
=Querying POS details=&lt;br /&gt;
The [[Pos-Get-v1|Query all details of a POS]] endpoint offers the capability to retrieve comprehensive information about a point of sale (POS) that is associated with a Barion Wallet. By making use of this endpoint, you can easily obtain all the relevant details and data related to a specific POS.&lt;br /&gt;
&lt;br /&gt;
=Barion Wallet to Barion vIBAN transfers=&lt;br /&gt;
From this release onwards, when you initiate a bank transfer from your Barion Wallet to a Barion vIBAN or GIRO, we automatically recognize it and handle it as a direct transfer instead. This means that the transaction is instantaneous and free of charge.&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4070</id>
		<title>Error codes notifications</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4070"/>
		<updated>2023-06-16T12:16:07Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* HTTP status codes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Barion error codes and notifications}}&lt;br /&gt;
&lt;br /&gt;
This page serves as a repository for the Barion error codes and notifications you can encounter when using or integrating.&lt;br /&gt;
&lt;br /&gt;
== 3DS error responses ==&lt;br /&gt;
&lt;br /&gt;
=== Possible error responses for the recurring payment requests ===&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;
| RecurringPaymentNotAllowed || The token payment is not allowed for the shop identified by the &#039;&#039;&#039;POSKey&#039;&#039;&#039;. Contact Barion to request this feature.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Possible error responses for the subsequent payment requests ===&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;
| InvalidRecurrenceId|| The token specified in the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; is invalid. Check if the token registration was successful.&lt;br /&gt;
|-&lt;br /&gt;
| RecurringPaymentDenied|| Something happened to the user since the token registration, either deleted, suspended, or blocked. Payment is not allowed in these cases.&lt;br /&gt;
|-&lt;br /&gt;
| InsufficientFunds|| If the original payment was with an e-money wallet and the customer doesn&#039;t have enough money to fulfill this charge this error happens.&lt;br /&gt;
|-&lt;br /&gt;
| OriginalPaymentWasntSuccessful || This means that the token belongs to an originally unsuccessful payment so this token can not be used anymore. This could only happen if the original payment was financed with a credit card.&lt;br /&gt;
|-&lt;br /&gt;
|InvalidCurrency || If the original payment was paid with e-money and the current token payment is in a currency that the wallet does not have an account in this error happens.&lt;br /&gt;
|-&lt;br /&gt;
|CardExpired || The card that was used to fulfill the initial payment is no longer valid. The &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; has to be re-initialized.&lt;br /&gt;
|-&lt;br /&gt;
|TopUpFailed || The attempt to charge the card that was used to fulfill the initial payment was unsuccessful. Often accompanied by other more specific errors.&lt;br /&gt;
|-&lt;br /&gt;
|ThreeDsNotEnabled || The card issuer rejected the card due to a lack of Strong Customer Authentication. Check whether the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is specified correctly (in case the scenario requires it).&lt;br /&gt;
|-&lt;br /&gt;
|InvalidUser || The payee defined in the transaction is not a valid Barion wallet. Either does not exist or is not fully activated.&lt;br /&gt;
|-&lt;br /&gt;
|UserCantMakeOutgoingTransaction || The payee specified in the transaction is not allowed to make payee transactions since the wallet is suspended or does not exist.&lt;br /&gt;
|-&lt;br /&gt;
|CardError || An error happened in the 3DSecure authentication system or the bank system when trying to process the card that has been used to complete the initial payment. This can mean a few things, from security settings to active limits on the card. The possible reasons should be discussed with the customer.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[ApplePay-ValidateSession|Validate]] an ApplePay session  ==&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;
| AuthenticationFailed|| Authentication failed.&lt;br /&gt;
|-&lt;br /&gt;
| ModelValidationError || This happens when some of the input properties fail the basic validation. For example, the session request URL is malformed.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidShop|| The provided poskey is invalid.&lt;br /&gt;
|-&lt;br /&gt;
| NotRegisteredToApple|| The provided shop URL is not registered to Apple.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidShopUrl|| The provided shop URL is invalid.&lt;br /&gt;
|-&lt;br /&gt;
| UnableToCreateApplePaySession|| A technical error occurred, and Apple Pay Session could not be created.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Payment-Refund-v2|Refunding a payment]]  ==&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;
| NotExistingPaymentId || The specified payment id is invalid.&lt;br /&gt;
|-&lt;br /&gt;
| SuspendedUserTriedToRefund || You are not allowed to refund payment if you are suspended.&lt;br /&gt;
|-&lt;br /&gt;
| TheSourceAndDestinationAccountsAreMatched || Very rare error, this happens in case the payment was paid by the shop owner.&lt;br /&gt;
|-&lt;br /&gt;
| PaymentStatusNotValid || Only payments in &amp;lt;code&amp;gt;Succeeded&amp;lt;/code&amp;gt; [[PaymentStatus|status]] can be refunded.&lt;br /&gt;
|-&lt;br /&gt;
| TransactionDoesNotBelongToPayment || The transaction specified in the request body does not belong to a payment.&lt;br /&gt;
|- &lt;br /&gt;
| InvalidTransactionType || The transaction specified is not a refundable [[TransactionType|transaction type]]. Only &amp;lt;code&amp;gt;CardPayment&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;Shop&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;BankTransferPayment&amp;lt;/code&amp;gt; types are refundable.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidAccount || The account is not eligible for a refund.&lt;br /&gt;
|- &lt;br /&gt;
| TooLowBalanceToMakeRefund || There are not enough funds to fulfill the refund request.&lt;br /&gt;
|-&lt;br /&gt;
| AmountToRefundIsGreaterThanTransactionAmount || The amount specified to refund is greater than the original payment transaction itself.&lt;br /&gt;
|- &lt;br /&gt;
| InternalServerError || Something unexpected happened.&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Identification-Information-v2|Fetching information]] about an organization ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| NoIdentifiedPartnerFound || The given partner key was not valid&lt;br /&gt;
|-&lt;br /&gt;
| PartnerDataCannotBeRetrieved || The trusted partner data could not be retrieved (possibly has no rights for this endpoint)&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || Authentication failed for the target organization (incorrect login name or password)&lt;br /&gt;
|-&lt;br /&gt;
| RemoteRegisterInfoReturnedWithError || The company register service returned an error&lt;br /&gt;
|- &lt;br /&gt;
| RegisterInfoCannotBeRetrievedFromDb || The company register record could not be retrieved from the Barion database. Contact Barion support.&lt;br /&gt;
|- &lt;br /&gt;
| RegisterInfoCannotBeRetrievedFromRemote || The company register record could not be retrieved from the remote service. Possible causes:&lt;br /&gt;
* The given company is not based in Hungary (there is no service to call)&lt;br /&gt;
* The company register remote service is down&lt;br /&gt;
|-&lt;br /&gt;
| CompanyRegisterDoesNotExistsForCountry || No company register service exists for the organization&#039;s country&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Identification-RemoteSelfEmployed-v2|Self-employed KYC]] remote identification ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| UserNotFound || The given user was not found in the system&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || Authentication failed for the given account (incorrect password)&lt;br /&gt;
|-&lt;br /&gt;
| LoginHasWrongAccountType || The given account is not an organization account in Barion&lt;br /&gt;
|-&lt;br /&gt;
| IdentificationPending || The given account already has a pending identification process&lt;br /&gt;
|-&lt;br /&gt;
| RegistrationNumberMissing || The given organization did not provide a registration number in Barion&lt;br /&gt;
|-&lt;br /&gt;
| IdentificationPending || The given account already has a pending identification process&lt;br /&gt;
|-&lt;br /&gt;
| InvalidBusinessType || The given account is an organization that is not eligible to be identified as a self-employed organization (e.g. it has a valid company record)&lt;br /&gt;
|-&lt;br /&gt;
| IncompleteData || The given company data was incomplete (owner or organization data missing)&lt;br /&gt;
|-&lt;br /&gt;
| NameIsOnProhibitionList || The company owner is on the prohibition list. In this case, contact legal authorities!&lt;br /&gt;
|-&lt;br /&gt;
| DocumentsMissing || The caller did not provide the personal documents for the identification&lt;br /&gt;
|-&lt;br /&gt;
| DocumentValidityMissing || One or more documents that have a mandatory validity did not have the validity set&lt;br /&gt;
|-&lt;br /&gt;
| DocumentExpired || One or more supplied document is expired&lt;br /&gt;
|-&lt;br /&gt;
| RemoteIdentificationFailed || A general error occurred - contact the Barion support&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Identification-RemoteCompany-v2|Organization]] remote identification ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| UserNotFound || The given user was not found in the system&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || Authentication failed for the given account (incorrect password)&lt;br /&gt;
|-&lt;br /&gt;
| LoginHasWrongAccountType || The given account is not an organization account in Barion&lt;br /&gt;
|-&lt;br /&gt;
| IdentificationPending || The given account already has a pending identification process&lt;br /&gt;
|-&lt;br /&gt;
| RegistrationNumberMissing || The given organization did not provide a registration number in Barion&lt;br /&gt;
|-&lt;br /&gt;
| IdentificationPending || The given account already has a pending identification process&lt;br /&gt;
|-&lt;br /&gt;
| IncompleteData || The given company data was incomplete (owners or representatives are missing)&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCompanyRegisterId || The supplied company register record was not found in the database. You must place a call to [[Identification-Information-v2]] to obtain this identifier.&lt;br /&gt;
|-&lt;br /&gt;
| SignatoryStatusMismatch || The supplied list of representatives does not comply with the signatory requirements of the company record&lt;br /&gt;
|-&lt;br /&gt;
| InvalidRepresentatives || One or more supplied representatives do not match the ones found in the company record&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCountryCode || The given country code for an owner or representative was in an invalid format&lt;br /&gt;
|-&lt;br /&gt;
| NameIsOnProhibitionList || One of the supplied owners or representatives is on the prohibition list. In this case, contact legal authorities!&lt;br /&gt;
|-&lt;br /&gt;
| DocumentsMissing || The caller did not provide the personal documents for the identification&lt;br /&gt;
|-&lt;br /&gt;
| DocumentValidityMissing || One or more documents that have a mandatory validity did not have the validity set&lt;br /&gt;
|-&lt;br /&gt;
| DocumentExpired || One or more supplied document is expired&lt;br /&gt;
|-&lt;br /&gt;
| RemoteIdentificationFailed || A general error occurred - contact the Barion support&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[ApplePay-StartPaymentWithAppleToken|Apple token]] payment  ==&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;
| AuthenticationFailed|| Authentication failed.&lt;br /&gt;
|-&lt;br /&gt;
| ModelValidationError || This happens when some of the input properties fail the basic validation. For example, the session request URL is malformed.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidApplePayToken|| The provided token is invalid.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidApplePayMessage|| The provided message is invalid.&lt;br /&gt;
|-&lt;br /&gt;
| ApplePayNotAllowed|| Apple Pay is not allowed for token payments.&lt;br /&gt;
|-&lt;br /&gt;
| NotRegisteredToApple|| The provided shop URL is not registered to Apple.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Google_Pay|GooglePay]] ==&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;br /&gt;
&lt;br /&gt;
== [[Token_payment|Token payment]] ==&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;
| RecurringPaymentNotAllowed || The token payment is not allowed for the shop identified by the &#039;&#039;&#039;POSKey&#039;&#039;&#039;. Contact Barion to request this feature.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Withdraw-BankTransfer-v3|Withdrawing]] via bank transfer  ==&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 authentication is 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 withdrawal amount and the fee.&lt;br /&gt;
|-&lt;br /&gt;
| BankAccountNumberBlackListed || The target bank account number is blacklisted, the withdrawal process is terminated and the customer gets suspended. &lt;br /&gt;
|-&lt;br /&gt;
| UserIsOverWithdrawLimit|| The withdrawn amount exceeded the allowed limit for non-verified customers, the withdrawal process is terminated and the customer gets suspended. &lt;br /&gt;
|-&lt;br /&gt;
| UserIsDeleted || The user is deleted from the system, the withdrawal is not possible. &lt;br /&gt;
|-&lt;br /&gt;
| UserIsSuspended || The user is suspended until the suspension is lifted no withdrawals are allowed.&lt;br /&gt;
|-&lt;br /&gt;
| WithdrawFromCustomerAccountToSystemAccount || Withdrawing 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;
== [[Responsive_web_payment|Responsive]] web payment ==&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 webshop&#039;s 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 transaction (topup the account of the shop, thereafter payments could be prepared).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== HTTP status codes ==&lt;br /&gt;
&lt;br /&gt;
These are the HTTP status codes with their Barion-specific use cases. For more generic information, consult [https://www.rfc-editor.org/rfc/rfc9110#section-15| RFC 9110].&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! HTTP code || Barion scenario || Used by?&lt;br /&gt;
|-&lt;br /&gt;
| 200 || Sent by the merchant shop to the IPN callback || [[Callback_mechanism]]&lt;br /&gt;
|-&lt;br /&gt;
| 400 || Sent if you do not have an account in the specified currency|| &lt;br /&gt;
* [[Statement-Download-v2]] &lt;br /&gt;
* [[Pos-Create-v1]]&lt;br /&gt;
|-&lt;br /&gt;
| 401 || Sent if you fail to authenticate yourself properly || &lt;br /&gt;
* [[Statement-Download-v2]] &lt;br /&gt;
* [[Pos-Get-v1]]&lt;br /&gt;
|-&lt;br /&gt;
| 403 || Sent if you are not allowed to generate the given statement type || [[Statement-Download-v2]]&lt;br /&gt;
|-&lt;br /&gt;
| 404 || Sent if the shop does not exist. || [[Pos-Get-v1]]&lt;br /&gt;
|-&lt;br /&gt;
| 429|| Sent if you submit a request less than 5 seconds after a successful request.|| [[Callback_mechanism]]&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopStatus&amp;diff=4069</id>
		<title>ShopStatus</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopStatus&amp;diff=4069"/>
		<updated>2023-06-16T12:15:42Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop status structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the details for the status of your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-Get-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Unspecified&lt;br /&gt;
| string &lt;br /&gt;
| The shop&#039;s status has not been specified. This particular status is a result of a technical error. If you encounter this status, please contact our technical team for assistance.&lt;br /&gt;
|-&lt;br /&gt;
| NewUnderApproval&lt;br /&gt;
| string &lt;br /&gt;
&lt;br /&gt;
| The shop has recently been created and is currently undergoing the approval process.&lt;br /&gt;
|-&lt;br /&gt;
| NewForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop has been rejected by our team, and the shop owner needs to make further modifications and additions before it can be approved.&lt;br /&gt;
|-&lt;br /&gt;
| Open&lt;br /&gt;
| string&lt;br /&gt;
| The shop is open, and all Barion operations are available.&lt;br /&gt;
|-&lt;br /&gt;
| OpenWaitForModificationApproval&lt;br /&gt;
| string&lt;br /&gt;
| The shop is open, and the customer has made some minor modifications requiring approval. Despite these changes, the shop remains open.&lt;br /&gt;
|-&lt;br /&gt;
| OpenModificationForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop owner is required to make additional modifications before approval can be granted. However, even with these pending changes, the shop continues to operate without interruption.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosed&lt;br /&gt;
| string&lt;br /&gt;
| The customer has chosen to temporarily close the shop. During this closure, the shop will not accept any payments. However, the customer still has the ability to make modifications, which will need to be approved if changes are made while the shop is closed. Once the customer re-opens the shop, normal operations will resume.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosedWaitForModificationApproval&lt;br /&gt;
| string&lt;br /&gt;
| The customer has opted to temporarily close the shop and made modifications to the data during the closure. Now, the customer has initiated the process of re-opening the shop, and the changes made during the closure require approval before they can take effect.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosedModificationForbidden&lt;br /&gt;
| string&lt;br /&gt;
| After selecting to re-open the shop, the changes made during the temporarily closed phase have been rejected. The shop owner is required to make additional modifications before approval can be granted.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosed&lt;br /&gt;
| string&lt;br /&gt;
| The customer has made the decision to permanently close the shop.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosedByUser&lt;br /&gt;
| string&lt;br /&gt;
| The customer has chosen to permanently close her Barion Wallet, which has resulted in the automatic closure of the associated shop.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosedByOfficer&lt;br /&gt;
| string&lt;br /&gt;
| A Barion officer&#039;s decision to close the Barion Wallet has led to the automatic closure of the associated shop.&lt;br /&gt;
|-&lt;br /&gt;
| ClosedByOfficer&lt;br /&gt;
| string&lt;br /&gt;
| A Barion officer has temporarily closed the shop, but it can be reopened.&lt;br /&gt;
|-&lt;br /&gt;
| ReOpen_WaitingForApproval&lt;br /&gt;
| string&lt;br /&gt;
| The shop was closed by a Barion officer; however, the customer has requested to re-open the shop, which requires approval.&lt;br /&gt;
|-&lt;br /&gt;
| Draft&lt;br /&gt;
| string&lt;br /&gt;
| The shop is currently in a draft state, indicating that the customer has not provided all the necessary data or has not yet submitted the shop for approval. In the API scenario, the concept of a &amp;quot;draft state&amp;quot; may not be applicable as all the necessary data is provided through the API, and manual submission for approval is not required.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=CustomerServiceContact&amp;diff=4068</id>
		<title>CustomerServiceContact</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=CustomerServiceContact&amp;diff=4068"/>
		<updated>2023-06-16T12:15:26Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Customer service contact structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the details for the customer service contact of your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-Get-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Name&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| The name of the customer service desk. &lt;br /&gt;
|-&lt;br /&gt;
| PhoneNumber&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|The number must be sent in the expected format, without a + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| Email&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| The email address of the customer service desk.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=TechnicalContact&amp;diff=4067</id>
		<title>TechnicalContact</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=TechnicalContact&amp;diff=4067"/>
		<updated>2023-06-16T12:15:15Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Technical contact structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the details for the technical contact of your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-Get-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Name&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| The name of the technical contact person. &lt;br /&gt;
|-&lt;br /&gt;
| PhoneNumber&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|The number must be sent in the expected format, without a + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| Email&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| The email address of the technical contact.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=BusinessContact&amp;diff=4066</id>
		<title>BusinessContact</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=BusinessContact&amp;diff=4066"/>
		<updated>2023-06-16T12:15:00Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Business contact structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the details for the business contact of your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-Get-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Name&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| The name of the business contact person. &lt;br /&gt;
|-&lt;br /&gt;
| PhoneNumber&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|The number must be sent in the expected format, without a + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| Email&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| The email address of the business contact.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4065</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4065"/>
		<updated>2023-06-16T12:14:31Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-Get-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| BeautyHealth (21)&lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| Property (12)&lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| SportLeisureTravel (19)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| Tobacco (26)&lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| Vehicle (13)&lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-GetState-v1&amp;diff=4064</id>
		<title>Pos-GetState-v1</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Pos-GetState-v1&amp;diff=4064"/>
		<updated>2023-06-16T12:13:56Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: Stankovicsa moved page Pos-GetState-v1 to Pos-Get-v1: Consistent naming&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Pos-Get-v1]]&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=4063</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=4063"/>
		<updated>2023-06-16T12:13:56Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: Stankovicsa moved page Pos-GetState-v1 to Pos-Get-v1: Consistent naming&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Request all details 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 all details and the 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;
| OwnerEmail&lt;br /&gt;
| string&lt;br /&gt;
| The email address of the shop owner.&lt;br /&gt;
|-&lt;br /&gt;
| GooglePayMerchantId&lt;br /&gt;
| string &lt;br /&gt;
| The ID that identifies your webshop. This can be copied from the &#039;&#039;&#039;Detail&#039;&#039;&#039; page of your shop (in Barion). For more information, see [[Google_Pay]]. &lt;br /&gt;
|-&lt;br /&gt;
| PixelId&lt;br /&gt;
| string&lt;br /&gt;
| This is referenced when integrating our Barion Pixel.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=4060</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=4060"/>
		<updated>2023-06-01T04:18:19Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Registration Type Query String Parameter */&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 E-mail address OR 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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=4050</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=4050"/>
		<updated>2023-05-17T09:30:08Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Request all details 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 all details and the 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;
| Payee&lt;br /&gt;
| Guid&lt;br /&gt;
| The email address of the shop owner.&lt;br /&gt;
|-&lt;br /&gt;
| GooglePayMerchantId&lt;br /&gt;
| string &lt;br /&gt;
| The ID that identifies your webshop. This can be copied from the &#039;&#039;&#039;Detail&#039;&#039;&#039; page of your shop (in Barion). For more information, see [[Google_Pay]]. &lt;br /&gt;
|-&lt;br /&gt;
| PixelId&lt;br /&gt;
| string&lt;br /&gt;
| This is referenced when integrating our Barion Pixel.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=4049</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=4049"/>
		<updated>2023-05-17T09:29:54Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Request all details 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 all details and the 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;
| Payee&lt;br /&gt;
| Guid&lt;br /&gt;
| The email address of the shop owner.&lt;br /&gt;
|-&lt;br /&gt;
| GooglePayMerchantId&lt;br /&gt;
| string &lt;br /&gt;
| The ID that identifies your webshop. This can be copied from the &#039;&#039;&#039;Detail&#039;&#039;&#039; page of your shop (in Barion). For more information, see [[Google_Pay]]. &lt;br /&gt;
|-&lt;br /&gt;
| PixelId&lt;br /&gt;
| string&lt;br /&gt;
| This is referenced when integrating our Barion Pixel.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4033</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4033"/>
		<updated>2023-05-11T12:45:19Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| BeautyHealth (21)&lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| Property (12)&lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| SportLeisureTravel (19)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| Tobacco (26)&lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| Vehicle (13)&lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4032</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4032"/>
		<updated>2023-05-11T12:44:15Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| BeautyHealth (21)&lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| SportLeisureTravel (19)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| Tobacco (26)&lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| Vehicle (13)&lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4031</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4031"/>
		<updated>2023-05-11T12:43:27Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| BeautyHealth (21)&lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| Tobacco (26)&lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4030</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4030"/>
		<updated>2023-05-11T12:43:04Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| BeautyHealth (21)&lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| Tobacco (26)&lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4029</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4029"/>
		<updated>2023-05-11T12:42:30Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| BeautyHealth (21)&lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4028</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4028"/>
		<updated>2023-05-11T12:42:02Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FoodDrink (8)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4027</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4027"/>
		<updated>2023-05-11T12:41:27Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| FashionClothes (7)&lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| FurnitureAntiquity (6)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| GiftToyFlower (1)&lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| HomeDesignGarden (18)&lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| JobEducation (2)&lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| BuildingMaterialMachine (9)&lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| Baby (4)&lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| FilmMusic (10)&lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| Other (25)&lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| Pet (11)&lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| Service (22)&lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| BettingGambling (20)&lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| WatchJewelry (17)&lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4026</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4026"/>
		<updated>2023-05-11T12:37:26Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
| BonusCoupon (5)&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
| Dating (23)&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| Electronics (16)&lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4025</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4025"/>
		<updated>2023-05-11T12:36:38Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
| Agriculture (15)&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| Ad (3)&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4024</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4024"/>
		<updated>2023-05-11T12:36:04Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| BookNewsPaper (14)&lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Ad (3)&lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4023</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4023"/>
		<updated>2023-05-11T12:34:59Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Property value&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4022</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=4022"/>
		<updated>2023-05-11T12:34:11Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Shop category structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the shop categories available when creating your shop in Barion.&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;
* [[Pos-Create-v1]]&lt;br /&gt;
* [[Pos-GetState-v1]]&lt;br /&gt;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
!Property name&lt;br /&gt;
!Property type&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
| Agriculture&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with agricultural products and tasks. &lt;br /&gt;
|-&lt;br /&gt;
| Book, newspaper&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops that deal in printed press objects.&lt;br /&gt;
|-&lt;br /&gt;
| Classifieds&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Coupons, discount&lt;br /&gt;
| string&lt;br /&gt;
|&lt;br /&gt;
| Set this option if you want to use coupons or discounts in your shop.&lt;br /&gt;
|-&lt;br /&gt;
| Dating&lt;br /&gt;
| string &lt;br /&gt;
|&lt;br /&gt;
| Set this option for shops dealing with dating activities and materiel.&lt;br /&gt;
|-&lt;br /&gt;
| Electronics&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in electronics.&lt;br /&gt;
|-&lt;br /&gt;
| Fashion &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in fashion.&lt;br /&gt;
|-&lt;br /&gt;
| Food, beverages&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with food and beverages.&lt;br /&gt;
|-&lt;br /&gt;
| Furniture, antique&lt;br /&gt;
| string&lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with furniture or antique items.&lt;br /&gt;
|-&lt;br /&gt;
| Gift, toy, flower&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various gifts, toys, and floral items.&lt;br /&gt;
|-&lt;br /&gt;
| Health, beauty&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in health and beauty related products.&lt;br /&gt;
|-&lt;br /&gt;
| Home, design, garden&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various home appliances, design items, or gardening accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Jobs, education&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in educational items and material, or job-specific items.&lt;br /&gt;
|-&lt;br /&gt;
| Material, machine&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing with materials, machines, and related services.&lt;br /&gt;
|-&lt;br /&gt;
| Maternity and baby&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items related to maternity and children.&lt;br /&gt;
|-&lt;br /&gt;
| Movie, music &lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in audiovisual entertainment.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Pets&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in pet-related items and accessories.&lt;br /&gt;
|-&lt;br /&gt;
| Real estate&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and products related to real estate.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Other&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in anything that does not fit into the other categories.&lt;br /&gt;
|-&lt;br /&gt;
| Services&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various services.&lt;br /&gt;
|-&lt;br /&gt;
| Sporting goods, leisure, travel&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in sporting goods, leisure and travel items.&lt;br /&gt;
|-&lt;br /&gt;
| Sports betting, gambling&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in items and services related to sports betting and gambling.&lt;br /&gt;
|-&lt;br /&gt;
| Tobacco shop&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in tobacco-related products.&lt;br /&gt;
|-&lt;br /&gt;
| Vehicle&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in vehicles and related items and services.&lt;br /&gt;
|-&lt;br /&gt;
| Watches, jewelry&lt;br /&gt;
| string &lt;br /&gt;
| &lt;br /&gt;
| Set this option for shops dealing in various watches, jewelry, and related services.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3979</id>
		<title>Pos-Create-v1</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3979"/>
		<updated>2023-05-02T14:36:07Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Input properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Create a POS in Barion }}&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=POST&lt;br /&gt;
|uri=/v1/Pos&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;/pos&amp;lt;/code&amp;gt; API endpoint to create a shop in Barion.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Create an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Call 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; and above.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| Name || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum 200 characters&lt;br /&gt;
|| The unique name of the point of sale (POS) displayed on the Barion Payment Gateway. You have to provide a new name if the intended name is already marked as existing.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Url || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| In the case of a webpage, the URL of it, in the case of a mobile application, the download URL (iOS/Android), in the case of a billing program, the URL of it. Only pages with HTTPS protocol, indicated safe by the browser will be accepted.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Description || string || &lt;br /&gt;
* Required&lt;br /&gt;
* 20-200 characters&lt;br /&gt;
|| Enter a brief description of the product/service your POS provides. This is required for the approval of your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Logo || string || &lt;br /&gt;
* Required&lt;br /&gt;
* The image encoded in a base64 string&lt;br /&gt;
|| The POS logo. This is required for approval. Do not use stock photos downloaded from the internet. Maximum upload size is 10 MB.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Category || [[ShopCategory]] || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| You can select multiple categories.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The technical contact of the shop&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Enter the contact details of your customer service desk, where your customers can contact you.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PrimaryCurrency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Possible values: HUF, CZK, EUR, USD&lt;br /&gt;
|| Specify the primary currency of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ExpectedTurnover || [[ExpectedTurnover]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Expected Barion turnover in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| AverageBasketValue || int || &lt;br /&gt;
* Must be &amp;gt;0&lt;br /&gt;
|| Average basket value in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfB2BCustomers || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of B2B customers in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfNonEuCards || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of non-EU cards in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BarionFullPixel || bool || &lt;br /&gt;
&lt;br /&gt;
|| This specifies if you implement Barion Pixel or Full Pixel.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UsePosForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set it *True* when you use the shop only for an e-invoicing program.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackUrl  || string || &lt;br /&gt;
* Maximum length is 2000 characters&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;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceId || string || &lt;br /&gt;
* referenceId: top-up code&lt;br /&gt;
|| Use the top-up code of the wallet to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
* Number of characters&lt;br /&gt;
|| Provide additional information for identification if your site is not public.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify individual templates when you open the shop to determine the data displayed. You can edit these on the modification page.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify an individual CustomCss if you want to modify the gateway design of the shop.&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;
| Name || string || The unique name of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PublicKey || Guid || The public key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| SecretKey || Guid || The secret POS key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || [[ShopStatus]] || The status of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| IsOpen || string || Information whether the shop is open.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Description || string || The short description of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Logo || string || The logo of the shop, sent as a URL.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || The technical contact of the shop.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || The customer service contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackURL  || string || 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;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceId || string || The top-up code of the wallet. Used to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || The custom template you used to modify the displayed data.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || The custom CSS you used to modify the gateway design.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Callbacks only provide information on the shop state change. If you need more details, implement a separate GetShopState call. |color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3955</id>
		<title>Pos-Create-v1</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3955"/>
		<updated>2023-05-02T12:32:30Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Output properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Create a POS in Barion using API}}&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=POST&lt;br /&gt;
|uri=/v1/Pos&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;/pos&amp;lt;/code&amp;gt; API endpoint to create a shop in Barion.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Create an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Call 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; and above.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| PosName || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum 200 characters&lt;br /&gt;
|| The unique name of the point of sale (POS) displayed on the Barion Payment Gateway. You have to provide a new name if the intended name is already marked as existing.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosUrl || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| In the case of a webpage, the URL of it, in the case of a mobile application, the download URL (iOS/Android), in the case of a billing program, the URL of it. Only pages with HTTP protocol, indicated safe by the browser will be accepted.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosDescription || string || &lt;br /&gt;
* Required&lt;br /&gt;
* 20-200 characters&lt;br /&gt;
|| Enter a brief description of the product/service your POS provides. This is required for the approval of your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShopLogo || string || &lt;br /&gt;
* Required&lt;br /&gt;
* The image encoded in a base64 string&lt;br /&gt;
|| The POS logo. This is required for approval. Do not use stock photos downloaded from the internet. Maximum upload size is 10 MB.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosCategory || [[ShopCategory]] || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| You can select multiple categories.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The technical contact of the shop&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Enter the contact details of your customer service desk, where your customers can contact you.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PrimaryCurrency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Possible values: HUF, CZK, EUR, USD&lt;br /&gt;
|| Specify the primary currency of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ExpectedTurnover || [[ExpectedTurnover]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Expected Barion turnover in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| AverageBasketValue || int || &lt;br /&gt;
* Must be &amp;gt;0&lt;br /&gt;
|| Average basket value in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfB2BCustomers || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of B2B customers in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfNonEuCards || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of non-EU cards in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BarionFullPixel || bool || &lt;br /&gt;
&lt;br /&gt;
|| This specifies if you implement Barion Pixel or Full Pixel.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UsePosForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set it *True* when you use the shop only for an e-invoicing program.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackUrl  || string || &lt;br /&gt;
* Maximum length is 2000 characters&lt;br /&gt;
|| Specify the URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceId || string || &lt;br /&gt;
* referenceId: top-up code&lt;br /&gt;
|| Use the top-up code of the wallet to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
* Number of characters&lt;br /&gt;
|| Provide additional information for identification if your site is not public.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify individual templates when you open the shop to determine the data displayed. You can edit these on the modification page.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify an individual CustomCss if you want to modify the gateway design of the shop.&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;
| Name || string || The unique name of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PublicKey || Guid || The public key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| SecretKey || Guid || The secret POS key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || string || The status of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| IsOpen || string || Information whether the shop is open.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Description || string || The short description of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosLogo || string || The logo of the shop, sent as a URL.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || The technical contact of the shop.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || The customer service contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackURL  || string || The URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceID || string || The top-up code of the wallet. Used to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || The custom template you used to modify the displayed data.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || The custom CSS you used to modify the gateway design.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Callbacks only provide information on the shop state change. If you need more details, implement a separate GetShopState call. |color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3954</id>
		<title>Pos-Create-v1</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3954"/>
		<updated>2023-05-02T12:32:10Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Output properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Create a POS in Barion using API}}&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=POST&lt;br /&gt;
|uri=/v1/Pos&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;/pos&amp;lt;/code&amp;gt; API endpoint to create a shop in Barion.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Create an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Call 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; and above.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| PosName || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum 200 characters&lt;br /&gt;
|| The unique name of the point of sale (POS) displayed on the Barion Payment Gateway. You have to provide a new name if the intended name is already marked as existing.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosUrl || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| In the case of a webpage, the URL of it, in the case of a mobile application, the download URL (iOS/Android), in the case of a billing program, the URL of it. Only pages with HTTP protocol, indicated safe by the browser will be accepted.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosDescription || string || &lt;br /&gt;
* Required&lt;br /&gt;
* 20-200 characters&lt;br /&gt;
|| Enter a brief description of the product/service your POS provides. This is required for the approval of your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShopLogo || string || &lt;br /&gt;
* Required&lt;br /&gt;
* The image encoded in a base64 string&lt;br /&gt;
|| The POS logo. This is required for approval. Do not use stock photos downloaded from the internet. Maximum upload size is 10 MB.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosCategory || [[ShopCategory]] || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| You can select multiple categories.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The technical contact of the shop&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Enter the contact details of your customer service desk, where your customers can contact you.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PrimaryCurrency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Possible values: HUF, CZK, EUR, USD&lt;br /&gt;
|| Specify the primary currency of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ExpectedTurnover || [[ExpectedTurnover]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Expected Barion turnover in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| AverageBasketValue || int || &lt;br /&gt;
* Must be &amp;gt;0&lt;br /&gt;
|| Average basket value in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfB2BCustomers || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of B2B customers in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfNonEuCards || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of non-EU cards in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BarionFullPixel || bool || &lt;br /&gt;
&lt;br /&gt;
|| This specifies if you implement Barion Pixel or Full Pixel.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UsePosForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set it *True* when you use the shop only for an e-invoicing program.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackUrl  || string || &lt;br /&gt;
* Maximum length is 2000 characters&lt;br /&gt;
|| Specify the URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceId || string || &lt;br /&gt;
* referenceId: top-up code&lt;br /&gt;
|| Use the top-up code of the wallet to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
* Number of characters&lt;br /&gt;
|| Provide additional information for identification if your site is not public.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify individual templates when you open the shop to determine the data displayed. You can edit these on the modification page.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify an individual CustomCss if you want to modify the gateway design of the shop.&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;
| PosName || string || The unique name of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosPublicKey || Guid || The public key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosSecretKey || Guid || The secret POS key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || string || The status of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| IsOpen || string || Information whether the shop is open.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShopDescription || string || The short description of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosLogo || string || The logo of the shop, sent as a URL.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || The technical contact of the shop.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || The customer service contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackURL  || string || The URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceID || string || The top-up code of the wallet. Used to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || The custom template you used to modify the displayed data.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || The custom CSS you used to modify the gateway design.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Callbacks only provide information on the shop state change. If you need more details, implement a separate GetShopState call. |color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3953</id>
		<title>Pos-Create-v1</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3953"/>
		<updated>2023-05-02T12:30:09Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Input properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Create a POS in Barion using API}}&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=POST&lt;br /&gt;
|uri=/v1/Pos&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;/pos&amp;lt;/code&amp;gt; API endpoint to create a shop in Barion.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Create an account in Barion]]&lt;br /&gt;
* [[Calling_the_API|Call 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; and above.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| PosName || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum 200 characters&lt;br /&gt;
|| The unique name of the point of sale (POS) displayed on the Barion Payment Gateway. You have to provide a new name if the intended name is already marked as existing.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosUrl || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| In the case of a webpage, the URL of it, in the case of a mobile application, the download URL (iOS/Android), in the case of a billing program, the URL of it. Only pages with HTTP protocol, indicated safe by the browser will be accepted.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosDescription || string || &lt;br /&gt;
* Required&lt;br /&gt;
* 20-200 characters&lt;br /&gt;
|| Enter a brief description of the product/service your POS provides. This is required for the approval of your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShopLogo || string || &lt;br /&gt;
* Required&lt;br /&gt;
* The image encoded in a base64 string&lt;br /&gt;
|| The POS logo. This is required for approval. Do not use stock photos downloaded from the internet. Maximum upload size is 10 MB.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosCategory || [[ShopCategory]] || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| You can select multiple categories.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The technical contact of the shop&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Enter the contact details of your customer service desk, where your customers can contact you.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PrimaryCurrency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Possible values: HUF, CZK, EUR, USD&lt;br /&gt;
|| Specify the primary currency of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ExpectedTurnover || [[ExpectedTurnover]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| Expected Barion turnover in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| AverageBasketValue || int || &lt;br /&gt;
* Must be &amp;gt;0&lt;br /&gt;
|| Average basket value in the primary currency.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfB2BCustomers || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of B2B customers in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PercentageOfNonEuCards || decimal || &lt;br /&gt;
* Between 0-100 or equal&lt;br /&gt;
|| The expected percentage of non-EU cards in your shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BarionFullPixel || bool || &lt;br /&gt;
&lt;br /&gt;
|| This specifies if you implement Barion Pixel or Full Pixel.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UsePosForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set it *True* when you use the shop only for an e-invoicing program.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackUrl  || string || &lt;br /&gt;
* Maximum length is 2000 characters&lt;br /&gt;
|| Specify the URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceId || string || &lt;br /&gt;
* referenceId: top-up code&lt;br /&gt;
|| Use the top-up code of the wallet to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
* Number of characters&lt;br /&gt;
|| Provide additional information for identification if your site is not public.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify individual templates when you open the shop to determine the data displayed. You can edit these on the modification page.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || &lt;br /&gt;
&lt;br /&gt;
|| You can specify an individual CustomCss if you want to modify the gateway design of the shop.&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;
| PosName || string || The unique name of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosPublicKey || Guid || The public key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosSecretKey || Guid || The secret POS key of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || string || The status of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| isOpen || string || Information whether the shop is open.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShopDescription || string || The short description of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PosLogo || string || The logo of the shop, sent as a URL.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact || [[BusinessContact]] || The business contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TechnicalContact || [[TechnicalContact]] || The technical contact of the shop.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || The customer service contact of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallBackURL  || string || The URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReferenceID || string || The top-up code of the wallet. Used to distinguish shops arriving through different channels.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomTemplate || string || The custom template you used to modify the displayed data.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CustomCSS || string || The custom CSS you used to modify the gateway design.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Callbacks only provide information on the shop state change. If you need more details, implement a separate GetShopState call. |color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Token_payment_upgrade_to_3DS&amp;diff=3767</id>
		<title>Token payment upgrade to 3DS</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Token_payment_upgrade_to_3DS&amp;diff=3767"/>
		<updated>2023-01-13T13:31:04Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Upgrading token payment implementation to comply with 3DS}}&lt;br /&gt;
__NOTOC__&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=This tutorial was created to help merchants that already have token payment integration with Barion. First, please read through the detailed description of the new [[Token_payment_3D_Secure|token payment with 3DS]]!|color=#1993c7}}&lt;br /&gt;
= Background =&lt;br /&gt;
[[Token_payment_3D_Secure|Token payment]] is a solution that enables the merchant to charge the payer without the presence of them. It is a powerful tool to conduct subscription-like or payer-not-present scenarios. This scenario requires the merchant to create a token that would act as an identifier for the payer&#039;s funding source. To attach that token to a valid funding source the merchant had to do several things:&lt;br /&gt;
# Create an alphanumeric token&lt;br /&gt;
# Conduct an initial payment in which this token gets registered in the Barion system &lt;br /&gt;
# Refer to this token in a subsequent payment attempt&lt;br /&gt;
&lt;br /&gt;
[[File:Recurring-pre3ds.png|1280px]]&lt;br /&gt;
&lt;br /&gt;
This meant that as far as this token referenced a valid (and still available) funding source the merchant could create payments without any limitations. Basically, this token symbolized the funding source. It was up to the merchant to decide what it is used for, neither Barion nor the card issuer was aware of the nature of the subsequent payments. &lt;br /&gt;
&lt;br /&gt;
This funding source can be either a card or an e-money wallet and this is up to the payer to choose. In case the payer chooses to fund the payment from their e-money wallet there is no further need for extra security. On the other hand, when it comes to card payment the authentication process changed with the new Strong Customer Authentication directive and the 3DS v2 protocol.&lt;br /&gt;
&lt;br /&gt;
= Changes =&lt;br /&gt;
To make sure that the payer has more control over these token scenarios and the card issuer knows more about the payment scenarios several things need to be changed. &lt;br /&gt;
&lt;br /&gt;
== Token payment scenarios ==&lt;br /&gt;
&lt;br /&gt;
First of all the merchant has to decide what kind of token payment scenario is suitable. These scenarios are the following:&lt;br /&gt;
* &#039;&#039;&#039;One-click payment&#039;&#039;&#039;: The payer clicks on the &amp;quot;Purchase&amp;quot; button but the charge happens in the background without the payer leaving the merchant&#039;s site.&lt;br /&gt;
* &#039;&#039;&#039;Recurring payment&#039;&#039;&#039;: The payer authorizes the merchant (at the initial payment) to charge their card periodically without being present with the same amount.&lt;br /&gt;
* &#039;&#039;&#039;Merchant initiated payment&#039;&#039;&#039;: The payer authorizes the merchant to charge their card without restrictions (eg. amounts can vary).&lt;br /&gt;
&lt;br /&gt;
To decide on a suitable scenario, please [[Token_payment_3D_Secure#Token_payment_scenarios|read this detailed description]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=The intended scenario must be specified in the new [[RecurrenceType|RecurrenceType]] property (located in the [[Payment-Start-v2|Payment/Start]] request)|color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
== Usage of TraceId ==&lt;br /&gt;
&lt;br /&gt;
3DS authentication requires another identifier. This new identifier is used to differentiate these token payment scenarios and help the issuer control what is a non-fraudulent transaction.&lt;br /&gt;
&lt;br /&gt;
So from now on, there will be two IDs for every payer-not-present scenario:&lt;br /&gt;
* &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; for the funding source: this identifies the source of the money (could be card or wallet)&lt;br /&gt;
* &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; (new) for the &#039;&#039;nature of the charge:&#039;&#039; this identifies the type of token payment scenario the merchant is conducting.&lt;br /&gt;
&lt;br /&gt;
This new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is generated and stored by the card issuer. The Id is available in the [[Payment-GetPaymentState-v2|GetPaymentState]] response once the charge is successfully completed.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=The TraceId must processed from the [[Payment-GetPaymentState-v2|GetPaymentState]] response and must be attached to the payment in merchant&#039;s system. |color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
Once the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is acquired it must be sent in the [[Payment-Start-v2|Payment/Start]] request to identify the scenario. This is crucial for the card transactions otherwise they could be declined. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=The TraceId must specified in the [[Payment-Start-v2|Payment/Start]] for the subsequent token charges. |color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
== 3DS v2 authentication ==&lt;br /&gt;
&lt;br /&gt;
The new more secure 3DS v2 authentication must be conducted for every online card payment. These token payment scenarios also need to use these new secure way of authentication. &lt;br /&gt;
The initial payment must be authenticated every time although the subsequent payments may be exempted in certain cases. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Technical changes required =&lt;br /&gt;
The technical changes depend on what type of token scenario is needed for the business. It is important to notice that these scenarios can be implemented beside each other, a merchant is not required to choose only one type of token payment. The main goal is to appropriately use each scenario.&lt;br /&gt;
&lt;br /&gt;
== Technical changes for Recurring payments ==&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039; For the token registration&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request the new properties have to be specified:&lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;RecurringPayment&amp;quot;&amp;lt;/code&amp;gt; to indicate the scenario&lt;br /&gt;
#* &amp;lt;code&amp;gt;PurchaseInformation.RecurringExpiry&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PurchaseInformation.RecurringFrequency&amp;lt;/code&amp;gt; for the limitations &amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt; &lt;br /&gt;
#Once the callback is received get the response of [[Payment-GetPaymentState-v2|GetPaymentState]]. In case the charge was successful, there will be a &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; property for the payment. The value of it must be saved and attached to the payment.  &lt;br /&gt;
#&#039;&#039;&#039;For subsequent payments&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request specify the &lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;RecurringPayment&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
#* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; you received for the initial payment.&lt;br /&gt;
&lt;br /&gt;
== Technical changes for Merchant initiated payments ==&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039; For the token registration&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request the new property has to be specified:&lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;MerchantInitiatedPayment&amp;quot;&amp;lt;/code&amp;gt; to indicate the scenario&lt;br /&gt;
#Once the callback is received get the response of [[Payment-GetPaymentState-v2|GetPaymentState]]. In case the charge was successful, there will be a &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; property for the payment. The value of it must be saved and attached to the payment.  &lt;br /&gt;
#&#039;&#039;&#039;For subsequent payments&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request specify the &lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;MerchantInitiatedPayment&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
#* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; you received for the initial payment.&lt;br /&gt;
&lt;br /&gt;
== Technical changes for One-click payments ==&lt;br /&gt;
&lt;br /&gt;
This modification needs the most attention since the merchant has to implement client-side functionality and add a new step at the end of the flow.&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039; For the token registration&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request the new property has to be specified:&lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;OneClickPayment&amp;quot;&amp;lt;/code&amp;gt; to indicate the scenario&lt;br /&gt;
#&#039;&#039;&#039;For subsequent payments&#039;&#039;&#039; the merchant has to integrate the barion.offsitegw.js to be able to authenticate the payer via 3DS v2 on the merchant&#039;s site. To do this read the tutorial on [[Token_payment_3D_Secure#OneClick payment|how to integrate this]].&lt;br /&gt;
# After a successful authentication a new Barion API endpoint ([[Payment-Complete-v2|/Payment/Complete]]) must be called to finalize the process and charge the card&lt;br /&gt;
&lt;br /&gt;
Please notice that in case this scenario is used there is no need to use the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; since the 3DS authentication will be performed every time.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=In case of one-click token scenario the merchant has to authenticate every card payment with 3DS v2|color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What happens if the merchant doesn&#039;t upgrade its implementation ==&lt;br /&gt;
&lt;br /&gt;
There will be a two-phase ramp-up period to make sure that integrations can be upgraded.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Until December 31, 2020&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In this period the integrations that are not up-to-date and are not capable to handle 3DS v2 transactions &#039;&#039;&#039;will work&#039;&#039;&#039;. &lt;br /&gt;
* New tokens can be initiated (without RecurrenceType and TraceId) and the 3DSv2 authentication will be performed by the Barion Smart Gateway.&lt;br /&gt;
* Subsequent payments can use existing tokens (RecurrenceId) without specifying the TraceId.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Between January 1 and January 31, 2021 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In this period the integrations that are not up-to-date and are not capable to handle 3DS v2 transactions &#039;&#039;&#039;will work&#039;&#039;&#039;. However, to comply with the card scheme mandates Barion has to substitute the missing information.&lt;br /&gt;
* New tokens can be initiated (without RecurrenceType and TraceId) and the 3DSv2 authentication will be performed by the Barion Smart Gateway. The payment will be marked as an initial MIT transaction. The MerchantInitiatedPayment RecurrenceType will be used as a fallback.&lt;br /&gt;
* Subsequent payments can use existing tokens (RecurrenceId) without specifying the TraceId. They will be handled as the subsequent MIT payment of the initial transaction. The TraceId will be filled in by Barion.&lt;br /&gt;
* This period allows all merchants to finish upgrading their integrations, receive TraceIds during subsequent payments, and send it back with the next subsequent payment, so Barion doesn&#039;t have to substitute it with a static value anymore.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;From February 1, 2021&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Until this date, all integrations must be upgraded. &lt;br /&gt;
* New tokens can only be initiated with the appropriate 3DSv2 information (RecurrenceType set). Otherwise, the payment/start will result in a validation error.&lt;br /&gt;
* Subsequent payments can use existing tokens (RecurrenceId) without specifying the TraceId. They will be handled as the subsequent MIT payment of the initial transaction. The TraceId will be filled in by Barion. This can be used until the card schemes allow this kind of TraceId substitution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=SUPPORT|text=In case you have difficulties with the upgrade please contact our developers at devsupport@barion.com |color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Token_payment_upgrade_to_3DS&amp;diff=3766</id>
		<title>Token payment upgrade to 3DS</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Token_payment_upgrade_to_3DS&amp;diff=3766"/>
		<updated>2023-01-13T13:30:29Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Upgrading token payment implementation to comply with 3DS}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=This tutorial was created to help merchants that already have token payment integration with Barion. First, please read through the detailed description of the new [[Token_payment_3D_Secure|token payment with 3DS]]!|color=#1993c7}}&lt;br /&gt;
= Background =&lt;br /&gt;
[[Token_payment_3D_Secure|Token payment]] is a solution that enables the merchant to charge the payer without the presence of them. It is a powerful tool to conduct subscription-like or payer-not-present scenarios. This scenario requires the merchant to create a token that would act as an identifier for the payer&#039;s funding source. To attach that token to a valid funding source the merchant had to do several things:&lt;br /&gt;
# Create an alphanumeric token&lt;br /&gt;
# Conduct an initial payment in which this token gets registered in the Barion system &lt;br /&gt;
# Refer to this token in a subsequent payment attempt&lt;br /&gt;
&lt;br /&gt;
[[File:Recurring-pre3ds.png|1280px]]&lt;br /&gt;
&lt;br /&gt;
This meant that as far as this token referenced a valid (and still available) funding source the merchant could create payments without any limitations. Basically, this token symbolized the funding source. It was up to the merchant to decide what it is used for, neither Barion nor the card issuer was aware of the nature of the subsequent payments. &lt;br /&gt;
&lt;br /&gt;
This funding source can be either a card or an e-money wallet and this is up to the payer to choose. In case the payer chooses to fund the payment from their e-money wallet there is no further need for extra security. On the other hand, when it comes to card payment the authentication process changed with the new Strong Customer Authentication directive and the 3DS v2 protocol.&lt;br /&gt;
&lt;br /&gt;
= Changes =&lt;br /&gt;
To make sure that the payer has more control over these token scenarios and the card issuer knows more about the payment scenarios several things need to be changed. &lt;br /&gt;
&lt;br /&gt;
== Token payment scenarios ==&lt;br /&gt;
&lt;br /&gt;
First of all the merchant has to decide what kind of token payment scenario is suitable. These scenarios are the following:&lt;br /&gt;
* &#039;&#039;&#039;One-click payment&#039;&#039;&#039;: The payer clicks on the &amp;quot;Purchase&amp;quot; button but the charge happens in the background without the payer leaving the merchant&#039;s site.&lt;br /&gt;
* &#039;&#039;&#039;Recurring payment&#039;&#039;&#039;: The payer authorizes the merchant (at the initial payment) to charge their card periodically without being present with the same amount.&lt;br /&gt;
* &#039;&#039;&#039;Merchant initiated payment&#039;&#039;&#039;: The payer authorizes the merchant to charge their card without restrictions (eg. amounts can vary).&lt;br /&gt;
&lt;br /&gt;
To decide on a suitable scenario, please [[Token_payment_3D_Secure#Token_payment_scenarios|read this detailed description]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=The intended scenario must be specified in the new [[RecurrenceType|RecurrenceType]] property (located in the [[Payment-Start-v2|Payment/Start]] request)|color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
== Usage of TraceId ==&lt;br /&gt;
&lt;br /&gt;
3DS authentication requires another identifier. This new identifier is used to differentiate these token payment scenarios and help the issuer control what is a non-fraudulent transaction.&lt;br /&gt;
&lt;br /&gt;
So from now on, there will be two IDs for every payer-not-present scenario:&lt;br /&gt;
* &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; for the funding source: this identifies the source of the money (could be card or wallet)&lt;br /&gt;
* &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; (new) for the &#039;&#039;nature of the charge:&#039;&#039; this identifies the type of token payment scenario the merchant is conducting.&lt;br /&gt;
&lt;br /&gt;
This new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is generated and stored by the card issuer. The Id is available in the [[Payment-GetPaymentState-v2|GetPaymentState]] response once the charge is successfully completed.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=The TraceId must processed from the [[Payment-GetPaymentState-v2|GetPaymentState]] response and must be attached to the payment in merchant&#039;s system. |color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
Once the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is acquired it must be sent in the [[Payment-Start-v2|Payment/Start]] request to identify the scenario. This is crucial for the card transactions otherwise they could be declined. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=The TraceId must specified in the [[Payment-Start-v2|Payment/Start]] for the subsequent token charges. |color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
== 3DS v2 authentication ==&lt;br /&gt;
&lt;br /&gt;
The new more secure 3DS v2 authentication must be conducted for every online card payment. These token payment scenarios also need to use these new secure way of authentication. &lt;br /&gt;
The initial payment must be authenticated every time although the subsequent payments may be exempted in certain cases. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Technical changes required =&lt;br /&gt;
The technical changes depend on what type of token scenario is needed for the business. It is important to notice that these scenarios can be implemented beside each other, a merchant is not required to choose only one type of token payment. The main goal is to appropriately use each scenario.&lt;br /&gt;
&lt;br /&gt;
== Technical changes for Recurring payments ==&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039; For the token registration&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request the new properties have to be specified:&lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;RecurringPayment&amp;quot;&amp;lt;/code&amp;gt; to indicate the scenario&lt;br /&gt;
#* &amp;lt;code&amp;gt;PurchaseInformation.RecurringExpiry&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;PurchaseInformation.RecurringFrequency&amp;lt;/code&amp;gt; for the limitations &amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt; &lt;br /&gt;
#Once the callback is received get the response of [[Payment-GetPaymentState-v2|GetPaymentState]]. In case the charge was successful, there will be a &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; property for the payment. The value of it must be saved and attached to the payment.  &lt;br /&gt;
#&#039;&#039;&#039;For subsequent payments&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request specify the &lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;RecurringPayment&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
#* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; you received for the initial payment.&lt;br /&gt;
&lt;br /&gt;
== Technical changes for Merchant initiated payments ==&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039; For the token registration&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request the new property has to be specified:&lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;MerchantInitiatedPayment&amp;quot;&amp;lt;/code&amp;gt; to indicate the scenario&lt;br /&gt;
#Once the callback is received get the response of [[Payment-GetPaymentState-v2|GetPaymentState]]. In case the charge was successful, there will be a &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; property for the payment. The value of it must be saved and attached to the payment.  &lt;br /&gt;
#&#039;&#039;&#039;For subsequent payments&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request specify the &lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;MerchantInitiatedPayment&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
#* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; you received for the initial payment.&lt;br /&gt;
&lt;br /&gt;
== Technical changes for One-click payments ==&lt;br /&gt;
&lt;br /&gt;
This modification needs the most attention since the merchant has to implement client-side functionality and add a new step at the end of the flow.&lt;br /&gt;
&lt;br /&gt;
#&#039;&#039;&#039; For the token registration&#039;&#039;&#039; in the [[Payment-Start-v2|Payment/Start]] request the new property has to be specified:&lt;br /&gt;
#* &amp;lt;code&amp;gt;&amp;quot;RecurrenceType&amp;quot; : &amp;quot;OneClickPayment&amp;quot;&amp;lt;/code&amp;gt; to indicate the scenario&lt;br /&gt;
#&#039;&#039;&#039;For subsequent payments&#039;&#039;&#039; the merchant has to integrate the barion.offsitegw.js to be able to authenticate the payer via 3DS v2 on the merchant&#039;s site. To do this read the tutorial on [[Token_payment_3D_Secure#OneClick payment|how to integrate this]].&lt;br /&gt;
# After a successful authentication a new Barion API endpoint ([[Payment-Complete-v2|/Payment/Complete]]) must be called to finalize the process and charge the card&lt;br /&gt;
&lt;br /&gt;
Please notice that in case this scenario is used there is no need to use the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; since the 3DS authentication will be performed every time.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=CHANGE|text=In case of one-click token scenario the merchant has to authenticate every card payment with 3DS v2|color=#20c400}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What happens if the merchant doesn&#039;t upgrade its implementation ==&lt;br /&gt;
&lt;br /&gt;
There will be a two-phase ramp-up period to make sure that integrations can be upgraded.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Until December 31, 2020&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In this period the integrations that are not up-to-date and are not capable to handle 3DS v2 transactions &#039;&#039;&#039;will work&#039;&#039;&#039;. &lt;br /&gt;
* New tokens can be initiated (without RecurrenceType and TraceId) and the 3DSv2 authentication will be performed by the Barion Smart Gateway.&lt;br /&gt;
* Subsequent payments can use existing tokens (RecurrenceId) without specifying the TraceId.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Between January 1 and January 31, 2021 &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
In this period the integrations that are not up-to-date and are not capable to handle 3DS v2 transactions &#039;&#039;&#039;will work&#039;&#039;&#039;. However, to comply with the card scheme mandates Barion has to substitute the missing information.&lt;br /&gt;
* New tokens can be initiated (without RecurrenceType and TraceId) and the 3DSv2 authentication will be performed by the Barion Smart Gateway. The payment will be marked as an initial MIT transaction. The MerchantInitiatedPayment RecurrenceType will be used as a fallback.&lt;br /&gt;
* Subsequent payments can use existing tokens (RecurrenceId) without specifying the TraceId. They will be handled as the subsequent MIT payment of the initial transaction. The TraceId will be filled in by Barion.&lt;br /&gt;
* This period allows all merchants to finish upgrading their integrations, receive TraceIds during subsequent payments, and send it back with the next subsequent payment, so Barion doesn&#039;t have to substitute it with a static value anymore.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;From February 1, 2021&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Until this date, all integrations must be upgraded. &lt;br /&gt;
* New tokens can only be initiated with the appropriate 3DSv2 information (RecurrenceType set). Otherwise, the payment/start will result in a validation error.&lt;br /&gt;
* Subsequent payments can use existing tokens (RecurrenceId) without specifying the TraceId. They will be handled as the subsequent MIT payment of the initial transaction. The TraceId will be filled in by Barion. This can be used until the card schemes allow this kind of TraceId substitution.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=SUPPORT|text=In case you have difficulties with the upgrade please contact our developers at devsupport@barion.com |color=#1993c7}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3751</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=3751"/>
		<updated>2022-11-17T07:59:15Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| rt&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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_release_notes_-_2022.11.21&amp;diff=3750</id>
		<title>Barion release notes - 2022.11.21</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_release_notes_-_2022.11.21&amp;diff=3750"/>
		<updated>2022-11-16T08:42:54Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion release notes - 2022.11.21}}&lt;br /&gt;
=Short summary=&lt;br /&gt;
We are publishing some new features in this release:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Virtual IBAN&#039;&#039;&#039; feature for bank transfer top-ups,&lt;br /&gt;
* &#039;&#039;&#039;Barion Wallet API key&#039;&#039;&#039; as a new method of API authentication.&lt;br /&gt;
&lt;br /&gt;
=Virtual IBAN=&lt;br /&gt;
&lt;br /&gt;
Your Barion Wallet now has Virtual IBAN numbers for USD, HUF, and EUR currencies. Instead of manually entering top-up codes, topping up becomes smoother and more error-free. You can check your IBAN numbers in the [https://secure.barion.com/TopUp/Wire Top Up menu].&lt;br /&gt;
&lt;br /&gt;
Why is this great news? Here’s a quick laundry list:&lt;br /&gt;
*&#039;&#039;&#039;Forget top-up codes&#039;&#039;&#039;: Having dedicated virtual IBAN account numbers can immediately identify all your top-ups. &lt;br /&gt;
*&#039;&#039;&#039;Less manual errors&#039;&#039;&#039;: The era of entering uniquely generated top-up codes in the comment field is over. You don’t need to type anything manually, just top-up your Wallet and we take care of the rest. &lt;br /&gt;
*&#039;&#039;&#039;One IBAN number for each currency&#039;&#039;&#039;: If you have several currencies in your Barion Wallet, we’ll dedicate a unique virtual IBAN number to every currency. As for HUF-based accounts, you’ll also get a GIRO number.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text= If you top up Czech crowns (CZK), these improvements will not affect your Barion Wallet. Use your top-up code to transfer CZK to your Barion Wallet. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
=Barion Wallet API key=&lt;br /&gt;
&lt;br /&gt;
The Wallet level API authentication method is changing, from now on the supported authentication method is via API key. The following endpoints are affected:&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; [[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;
For more details, please read our documentation about [[Barion_Wallet_Authentication| Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text= Previous integrations will not be affected yet, as [[Basic authentication]] will still be available until 2023 May/June. Further notice will be sent to integrators, who need to switch to the new authentication method. |color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3749</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=3749"/>
		<updated>2022-11-15T18:23:00Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| 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;
| rt&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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3748</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=3748"/>
		<updated>2022-11-15T18:18:23Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| 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;
| rt&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 3-letter country code of the organization representative&#039;s phone number (eg. HUN for Hungary, CZE 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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3747</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=3747"/>
		<updated>2022-11-15T17:23:51Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| 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;
| 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;
| rt&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 3-letter country code of the organization representative&#039;s phone number (eg. HUN for Hungary, CZE 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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3746</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=3746"/>
		<updated>2022-11-15T17:23:29Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| oc&lt;br /&gt;
| string&lt;br /&gt;
| The 3-letter iso code of the headquarters address country.&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;
| 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;
| rt&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 3-letter country code of the organization representative&#039;s phone number (eg. HUN for Hungary, CZE 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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3745</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=3745"/>
		<updated>2022-11-15T17:17:37Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| 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;
| 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;
| rt&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 3-letter country code of the organization representative&#039;s phone number (eg. HUN for Hungary, CZE 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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3744</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=3744"/>
		<updated>2022-11-15T17:00:55Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| 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;
|}&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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Registration_with_pre-filled_values&amp;diff=3743</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=3743"/>
		<updated>2022-11-15T16:59:21Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Query string parameters for registering as an organization */&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;
==Query string parameters for registering as an individual==&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=NaturalPerson&amp;amp;m=user%40example.com&amp;amp;isEmailLocked=true&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Query string parameters for registering as an organization==&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;
| 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 (only available for organizations)&lt;br /&gt;
| bool&lt;br /&gt;
| Indicates, whether the headquarters and the postal address match.&lt;br /&gt;
|-&lt;br /&gt;
| ocat (only available for organizations)&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 (only available for organizations)&lt;br /&gt;
| string&lt;br /&gt;
| The registration number of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| otn (only available for organizations)&lt;br /&gt;
| string&lt;br /&gt;
| The tax number of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| pc (only available for organizations)&lt;br /&gt;
| string&lt;br /&gt;
| The postal country of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| ppa(only available for organizations)&lt;br /&gt;
| string&lt;br /&gt;
| The postal zip code of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| pt (only available for organizations)&lt;br /&gt;
| string&lt;br /&gt;
| The postal city of the organization.&lt;br /&gt;
|-&lt;br /&gt;
| phn (only available for organizations)&lt;br /&gt;
| string&lt;br /&gt;
| The postal house number of the organization.&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=Organization&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 E-mail address OR 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=NaturalPerson&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_release_notes_-_2022.11.21&amp;diff=3742</id>
		<title>Barion release notes - 2022.11.21</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_release_notes_-_2022.11.21&amp;diff=3742"/>
		<updated>2022-11-15T13:04:55Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Short summary */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion release notes - 2022.11.21}}&lt;br /&gt;
=Short summary=&lt;br /&gt;
We are publishing some new features in this release:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Virtual IBAN&#039;&#039;&#039; feature for bank transfer top-ups,&lt;br /&gt;
* &#039;&#039;&#039;Barion Wallet API key&#039;&#039;&#039; as a new method of API authentication.&lt;br /&gt;
* &#039;&#039;&#039;DelayedCapture&#039;&#039;&#039; - 2 emails are sent (previously only 1 was sent during authorization):&lt;br /&gt;
** when the payer authorizes the charge (payer enters the card details on the payment gateway, clicks pay, and the process succeeds)&lt;br /&gt;
** when the payment is captured ([[Payment-Capture-v2|Capture]] endpoint is called)&lt;br /&gt;
&lt;br /&gt;
=Virtual IBAN=&lt;br /&gt;
&lt;br /&gt;
Your Barion Wallet now has Virtual IBAN numbers for USD, HUF, and EUR currencies. Instead of manually entering top-up codes, topping up becomes smoother and more error-free. You can check your IBAN numbers in the [https://secure.barion.com/TopUp/Wire Top Up menu].&lt;br /&gt;
&lt;br /&gt;
Why is this great news? Here’s a quick laundry list:&lt;br /&gt;
*&#039;&#039;&#039;Forget top-up codes&#039;&#039;&#039;: Having dedicated virtual IBAN account numbers can immediately identify all your top-ups. &lt;br /&gt;
*&#039;&#039;&#039;Less manual errors&#039;&#039;&#039;: The era of entering uniquely generated top-up codes in the comment field is over. You don’t need to type anything manually, just top-up your Wallet and we take care of the rest. &lt;br /&gt;
*&#039;&#039;&#039;One IBAN number for each currency&#039;&#039;&#039;: If you have several currencies in your Barion Wallet, we’ll dedicate a unique virtual IBAN number to every currency. As for HUF-based accounts, you’ll also get a GIRO number.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text= If you top up Czech crowns (CZK), these improvements will not affect your Barion Wallet. Use your top-up code to transfer CZK to your Barion Wallet. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
=Barion Wallet API key=&lt;br /&gt;
&lt;br /&gt;
The Wallet level API authentication method is changing, from now on the supported authentication method is via API key. The following endpoints are affected:&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; [[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;
For more details, please read our documentation about [[Barion_Wallet_Authentication| Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text= Previous integrations will not be affected yet, as [[Basic authentication]] will still be available until 2023 May/June. Further notice will be sent to integrators, who need to switch to the new authentication method. |color=#FF7A3D}}&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Responsive_web_payment&amp;diff=3684</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=3684"/>
		<updated>2022-11-14T12:22:23Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Possible error responses */&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 your 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-2.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 transaction (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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=3637</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=3637"/>
		<updated>2022-11-03T16:10:01Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* 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;
[[3DS_FAQ#What_is_a_soft_decline.3F|What is a soft decline?]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&#039;&#039;&#039;If you are not sending an exemption the charge will succeed.&#039;&#039;&#039;&amp;lt;br/&amp;gt;&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=3636</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=3636"/>
		<updated>2022-11-03T16:09:31Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* 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;
[[3DS_FAQ#What_is_a_soft_decline.3F|What is a soft decline?]]&amp;lt;br/&amp;gt;&lt;br /&gt;
If you are not sending an exemption the charge will succeed.&amp;lt;br/&amp;gt;&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=3635</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=3635"/>
		<updated>2022-11-03T16:08:58Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* 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;
[[3DS_FAQ#What_is_a_soft_decline.3F|What is a soft decline?]]&lt;br /&gt;
If you are not sending an exemption the charge will succeed.&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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=3634</id>
		<title>3DS FAQ</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=3634"/>
		<updated>2022-11-03T16:05:35Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* What is a soft decline? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
== Upon starting the payments which properties are required? ==&lt;br /&gt;
&amp;lt;div&amp;gt;The new properties marked with {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request are highly recommended. (Read: error won&#039;t be thrown, when sent without these properties). These content of these fields are optional. Payments undergo Transaction Risk Analysis on the card issuer side based on these data as well, deciding if the payment should be challenged or not.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Are TraceId required for earlier initialized token payments after 2021.02.01? ==&lt;br /&gt;
TraceIds are not required for OneClick payments. For an interim period (until 2021.02.01) TraceIds will be required for all MerhcantInitiatedPayments and RecurringPayments.&lt;br /&gt;
&lt;br /&gt;
== We&#039;ve received TraceId in the following format: &amp;lt;code&amp;gt;0MHSGZRZ1G0118       0&amp;lt;/code&amp;gt;==&lt;br /&gt;
The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact. You can read more about the TraceId [[Token_payment_3D_Secure#TraceId|here]]&lt;br /&gt;
&lt;br /&gt;
== Can we skip the additional data in subsequent payments that were required for 3DS authentication in the first Token Payment? ==&lt;br /&gt;
Additional data can&#039;t be ignored! The difference between the initial and subsequent token payment is that 3DS authentication is only required for the first, initial payment. More info can be found [[Token_payment_3D_Secure|here]]&lt;br /&gt;
&lt;br /&gt;
== Do we have to generate the TraceId in the first [[Payment-Start-v2|Payment/Start]], or is it generated by Barion? ==&lt;br /&gt;
TraceId is generated by the Card Issuer, so it is not required in the initial [[Payment-Start-v2|Payment/Start]] request. You have to store the TraceId, received in the [[Payment-GetPaymentState-v2|GetPaymentState]] response, and send it in all subsequent payments. You can read more [[Token_payment_3D_Secure#1.3_Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|here]]. The exceptions are the subsequent payments of an already initialized token payments without 3DS. More info can be found [[Token_payment_3D_Secure#Changing_the_token_payment_scenario_with_an_existing_token|here]]&lt;br /&gt;
&lt;br /&gt;
== When the amount of the first payment is different than the rest, I have to use [[RecurrenceType|MechantInitiatedPayment]] and not [[RecurrenceType|RecurringPayment]]. Right? ==&lt;br /&gt;
Yes, RecurringPayment can only be used, when the amounts of all the subsequent payments are the same or less. If only 1 is different (eg. you give discount/free for the first month), only MechantInitiatedPayment can be used. You can find more info [[Token_payment_3D_Secure#Token_payment_scenarios|here]].&lt;br /&gt;
&lt;br /&gt;
== What is a soft decline? ==&lt;br /&gt;
When an exemption is requested (MIT, REC, TRA), the card issuer reserves the right to decline the charge with the exemption (could be identified by &amp;lt;code&amp;gt;ScaSoftDeclined&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;FundingInformation&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;ProcessResult&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; response). In this case, a full 3ds authentication is required (hence the name &amp;quot;soft decline&amp;quot;), and the charge could be attempted again.&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=3633</id>
		<title>3DS FAQ</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=3633"/>
		<updated>2022-11-03T16:05:04Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
== Upon starting the payments which properties are required? ==&lt;br /&gt;
&amp;lt;div&amp;gt;The new properties marked with {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request are highly recommended. (Read: error won&#039;t be thrown, when sent without these properties). These content of these fields are optional. Payments undergo Transaction Risk Analysis on the card issuer side based on these data as well, deciding if the payment should be challenged or not.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Are TraceId required for earlier initialized token payments after 2021.02.01? ==&lt;br /&gt;
TraceIds are not required for OneClick payments. For an interim period (until 2021.02.01) TraceIds will be required for all MerhcantInitiatedPayments and RecurringPayments.&lt;br /&gt;
&lt;br /&gt;
== We&#039;ve received TraceId in the following format: &amp;lt;code&amp;gt;0MHSGZRZ1G0118       0&amp;lt;/code&amp;gt;==&lt;br /&gt;
The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact. You can read more about the TraceId [[Token_payment_3D_Secure#TraceId|here]]&lt;br /&gt;
&lt;br /&gt;
== Can we skip the additional data in subsequent payments that were required for 3DS authentication in the first Token Payment? ==&lt;br /&gt;
Additional data can&#039;t be ignored! The difference between the initial and subsequent token payment is that 3DS authentication is only required for the first, initial payment. More info can be found [[Token_payment_3D_Secure|here]]&lt;br /&gt;
&lt;br /&gt;
== Do we have to generate the TraceId in the first [[Payment-Start-v2|Payment/Start]], or is it generated by Barion? ==&lt;br /&gt;
TraceId is generated by the Card Issuer, so it is not required in the initial [[Payment-Start-v2|Payment/Start]] request. You have to store the TraceId, received in the [[Payment-GetPaymentState-v2|GetPaymentState]] response, and send it in all subsequent payments. You can read more [[Token_payment_3D_Secure#1.3_Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|here]]. The exceptions are the subsequent payments of an already initialized token payments without 3DS. More info can be found [[Token_payment_3D_Secure#Changing_the_token_payment_scenario_with_an_existing_token|here]]&lt;br /&gt;
&lt;br /&gt;
== When the amount of the first payment is different than the rest, I have to use [[RecurrenceType|MechantInitiatedPayment]] and not [[RecurrenceType|RecurringPayment]]. Right? ==&lt;br /&gt;
Yes, RecurringPayment can only be used, when the amounts of all the subsequent payments are the same or less. If only 1 is different (eg. you give discount/free for the first month), only MechantInitiatedPayment can be used. You can find more info [[Token_payment_3D_Secure#Token_payment_scenarios|here]].&lt;br /&gt;
&lt;br /&gt;
== What is a soft decline? ==&lt;br /&gt;
When an exemption is requested (MIT, REC, TRA), the card issuer reserves the right to decline the charge with the exemption (could be identified by &amp;lt;code&amp;gt;ScaSoftDeclined&amp;lt;/code&amp;gt; as the &amp;lt;code&amp;gt;FundingInformation&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;ProcessResult&amp;lt;/code&amp;gt; int the &amp;lt;code&amp;gt;GetPaymentState&amp;lt;/code&amp;gt; response). In this case, a full 3ds authentication is required (hence the name &amp;quot;soft decline&amp;quot;), and the charge could be attempted again.&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=3632</id>
		<title>3DS FAQ</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=3632"/>
		<updated>2022-11-03T15:49:06Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Are TraceId required for earlier initialized token payments after 2021.02.01? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
== Upon starting the payments which properties are required? ==&lt;br /&gt;
&amp;lt;div&amp;gt;The new properties marked with {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request are highly recommended. (Read: error won&#039;t be thrown, when sent without these properties). These content of these fields are optional. Payments undergo Transaction Risk Analysis on the card issuer side based on these data as well, deciding if the payment should be challenged or not.&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Are TraceId required for earlier initialized token payments after 2021.02.01? ==&lt;br /&gt;
TraceIds are not required for OneClick payments. For an interim period (until 2021.02.01) TraceIds will be required for all MerhcantInitiatedPayments and RecurringPayments.&lt;br /&gt;
&lt;br /&gt;
== We&#039;ve received TraceId in the following format: &amp;lt;code&amp;gt;0MHSGZRZ1G0118       0&amp;lt;/code&amp;gt;==&lt;br /&gt;
The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact. You can read more about the TraceId [[Token_payment_3D_Secure#TraceId|here]]&lt;br /&gt;
&lt;br /&gt;
== Can we skip the additional data in subsequent payments that were required for 3DS authentication in the first Token Payment? ==&lt;br /&gt;
Additional data can&#039;t be ignored! The difference between the initial and subsequent token payment is that 3DS authentication is only required for the first, initial payment. More info can be found [[Token_payment_3D_Secure|here]]&lt;br /&gt;
&lt;br /&gt;
== Do we have to generate the TraceId in the first [[Payment-Start-v2|Payment/Start]], or is it generated by Barion? ==&lt;br /&gt;
TraceId is generated by the Card Issuer, so it is not required in the initial [[Payment-Start-v2|Payment/Start]] request. You have to store the TraceId, received in the [[Payment-GetPaymentState-v2|GetPaymentState]] response, and send it in all subsequent payments. You can read more [[Token_payment_3D_Secure#1.3_Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|here]]. The exceptions are the subsequent payments of an already initialized token payments without 3DS. More info can be found [[Token_payment_3D_Secure#Changing_the_token_payment_scenario_with_an_existing_token|here]]&lt;br /&gt;
&lt;br /&gt;
== When the amount of the first payment is different than the rest, I have to use [[RecurrenceType|MechantInitiatedPayment]] and not [[RecurrenceType|RecurringPayment]]. Right? ==&lt;br /&gt;
Yes, RecurringPayment can only be used, when the amounts of all the subsequent payments are the same or less. If only 1 is different (eg. you give discount/free for the first month), only MechantInitiatedPayment can be used. You can find more info [[Token_payment_3D_Secure#Token_payment_scenarios|here]].&lt;/div&gt;</summary>
		<author><name>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3631</id>
		<title>Apple Pay</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3631"/>
		<updated>2022-11-03T15:45:57Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Shopper */&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] - this can be checked by calling the [https://developer.apple.com/documentation/apple_pay_on_the_web/applepaysession/1778000-canmakepaymentswithactivecard ApplePaySession.canMakePaymentsWithActiveCard] method with your Barion Shop Public Id as a parameter&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.oncancel = 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>Stankovicsa</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3630</id>
		<title>Apple Pay</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Apple_Pay&amp;diff=3630"/>
		<updated>2022-11-03T15:43:06Z</updated>

		<summary type="html">&lt;p&gt;Stankovicsa: /* Subscribe to the oncancel event */&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.oncancel = 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>Stankovicsa</name></author>
	</entry>
</feed>