<?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=Bozag</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=Bozag"/>
	<link rel="alternate" type="text/html" href="https://docs.barion.com/Special:Contributions/Bozag"/>
	<updated>2026-11-21T01:27:27Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://docs.barion.com/index.php?title=Token_payment_3D_Secure&amp;diff=4052</id>
		<title>Token payment 3D Secure</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Token_payment_3D_Secure&amp;diff=4052"/>
		<updated>2023-05-19T12:04:16Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Changing funding source or token scenarios */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Token Payment with 3D Secure}}&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This payment scenario allows the integrator shop to register a token for a customer (and a funding source) in the Barion system and then, later on, using this token, charge the customer without redirecting her to the Barion Smart Gateway UI. The user may be present at the site of the merchant or she can be off-session as well, so the merchant can charge her e.g. for subscriptions. This means that the customer authorizes the shop to charge her card or Barion balance without typing in the card information or Barion login again.&lt;br /&gt;
&lt;br /&gt;
[[File:3ds-recurring.png|1500px]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=Premium feature|text=If you want to use this scenario, you have to specifically request it from Barion.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
= Token payment scenarios =&lt;br /&gt;
Token payment can be used in three use cases: &lt;br /&gt;
* &#039;&#039;&#039;Customer Initiated Payments&#039;&#039;&#039;: when the user is present on the website of the merchant and she decides to pay :&lt;br /&gt;
** &#039;&#039;&#039;OneClick payment&#039;&#039;&#039;: the user is charged upon her request initiated on the website of the merchant. Subsequent payments are subject to PSD2 SCA and as the user is present, she has to go through the authentication process.&lt;br /&gt;
* &#039;&#039;&#039;Merchant Initiated Payments&#039;&#039;&#039;: when the merchant initiates the payment without the user being present. It has two subtypes:&lt;br /&gt;
** &#039;&#039;&#039;Recurring payment&#039;&#039;&#039;: the user is charged with the same amount on a regular basis, typically in case of subscriptions. Subsequent payments are exempted from PSD2 SCA, but liability still shifts to the card issuer.&lt;br /&gt;
** &#039;&#039;&#039;MIT (merchant-initiated transaction)&#039;&#039;&#039;: the user is charged on an irregular basis and/or with a different amount. Subsequent payments of this type are excluded from PSD2 SCA, the liability is on the merchant.&lt;br /&gt;
&lt;br /&gt;
== Customer participation ==&lt;br /&gt;
&lt;br /&gt;
Since the token scenario is suitable for both customer and merchant-initiated payments here is a comparison about who starts the payment. This includes the regular, non-tokenized payment scenario as well:&lt;br /&gt;
&lt;br /&gt;
{|class=wikitable&lt;br /&gt;
|-&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; | Scenario&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Initial payment&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subsequent payments&lt;br /&gt;
|-&lt;br /&gt;
! Customer present&lt;br /&gt;
! Customer at Barion Smart GW &lt;br /&gt;
! Customer present&lt;br /&gt;
! Customer at Barion Smart GW&lt;br /&gt;
|-&lt;br /&gt;
| Non token (regular) payment || YES || YES || YES || YES &lt;br /&gt;
|-&lt;br /&gt;
| OneClick payment || YES || YES/NO&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; || YES || style=&amp;quot;background:#FFE2C4&amp;quot; | NO &lt;br /&gt;
|-&lt;br /&gt;
| Recurring payment || YES || YES/NO&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; || style=&amp;quot;background:#FFE2C4&amp;quot; | NO || style=&amp;quot;background:#FFE2C4&amp;quot; | NO &lt;br /&gt;
|-&lt;br /&gt;
| MIT || YES || YES/NO&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; || style=&amp;quot;background:#FFE2C4&amp;quot; | NO || style=&amp;quot;background:#FFE2C4&amp;quot; | NO &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: 1px solid #aaa; background-color:#eee; font-size: 0.8em; padding:5px 10px; display:inline-block;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; Token payment scenarios can be initiated with already registered &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; as well, in this case, the customer may remain on the merchant&#039;s site. &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements for the scenarios ==&lt;br /&gt;
&lt;br /&gt;
These token payment scenarios have different requirements, the table below summarizes the key differences.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Scenario&lt;br /&gt;
! Payment amount&lt;br /&gt;
! Payment frequency&lt;br /&gt;
! Liability in case of fraud&lt;br /&gt;
|-&lt;br /&gt;
| One-click payment || Various || Various || Card issuer&lt;br /&gt;
|-&lt;br /&gt;
| Recurring payment || Subsequent amounts must be equal or less than the initial amount  || Initial payment must define a minimum amount of days to wait between charges || Card issuer &lt;br /&gt;
|-&lt;br /&gt;
| Merchant initiated payment || Various  || Various || Merchant&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 3DS authentication of the payer ==&lt;br /&gt;
&lt;br /&gt;
The new more secure 3DS v2 authentication must be performed for every online card payment. These token payment scenarios also have to use this new secure way of authentication. &lt;br /&gt;
The initial payment of a token scenario must be authenticated every time although the subsequent payments may be exempted in certain cases. &lt;br /&gt;
&lt;br /&gt;
Here is a table to compare the 3DS authentication requirements:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Scenario&lt;br /&gt;
! Initial payment&lt;br /&gt;
! Subsequent payments&lt;br /&gt;
|-&lt;br /&gt;
| One-click payment || ✔️ || ✔️&lt;br /&gt;
|-&lt;br /&gt;
| Recurring payment || ✔️ || &lt;br /&gt;
|-&lt;br /&gt;
| Merchant initiated payment || ✔️ || &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;IMPORTANT:&#039;&#039; When performing subsequent One-click payments with the &amp;lt;code&amp;gt;ChallengePreference&amp;lt;/code&amp;gt; parameter set to &amp;lt;code&amp;gt;NoChallengeNeeded&amp;lt;/code&amp;gt; (indicating a request for Transaction Risk Analysis), only a fraud analysis is performed, and the customer is not required to undergo a 3DS challenge.&lt;br /&gt;
&lt;br /&gt;
== Real life examples ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Phone bill&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The payer has a usage-based phone subscription that wants to pay without being present for every charge. They authorize the phone company to charge her card every month.&lt;br /&gt;
* Scenario: Merchant Initiated Transaction&lt;br /&gt;
* Explanation: Despite the frequency of the charges is monthly, the amount of the subsequent payments may exceed the initial payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV subscription&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Payer subscribes to online streaming of a television channel. She authorizes the tv company to charge her card every month. The subscription fee is the same for every month.&lt;br /&gt;
* Scenario: Recurring payment&lt;br /&gt;
* Explanation: The amount of the subsequent payments will not exceed the initial payment and the charge is regularly monthly-based.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookclub with &amp;quot;free first month&amp;quot; bonus&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Payer subscribes to a book renting service. he authorizes the book club to charge her card for a selection of books each month. The subscription fee is the same for every month however, the first month is free. To ensure the subscription the service requires her to register her card details.&lt;br /&gt;
* Scenario: Merchant Initiated Transaction&lt;br /&gt;
* Explanation: Despite the frequency of the charges is monthly, and the fee will stay the same, the initial payment is zero. So the amount of the next payment will exceed the initial payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Online food delivery service&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The food delivery company wants to provide a quick and easy experience for its customer. They decide that the order will be quicker if the customers don&#039;t leave the website to pay for the goods.&lt;br /&gt;
* Scenario: OneClick payment&lt;br /&gt;
* Explanation: The customer will always be there so the other two scenarios are not available.&lt;br /&gt;
&lt;br /&gt;
== How to decide ==&lt;br /&gt;
&lt;br /&gt;
To help you decide on a suitable scenario, please use the decision graph below:&lt;br /&gt;
&lt;br /&gt;
[[File:3ds-recurrencetype-decision.png|520px]]&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 a USD account created in your wallet.&lt;br /&gt;
* To make sure every corner case scenario works for your webshop it is best to top up 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 this: [[Calling_the_API|Calling the API]]&lt;br /&gt;
&lt;br /&gt;
= The payment process =&lt;br /&gt;
&lt;br /&gt;
The process is divided into two major steps:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
   &amp;lt;li&amp;gt;[[#Step 1:  Creating the funding source token|Creating the token]] that represents one of the customer&#039;s funding sources (credit card or e-money wallet)&lt;br /&gt;
      &amp;lt;ol&amp;gt;&lt;br /&gt;
         &amp;lt;li&amp;gt;Preparing the payment via the Barion API&amp;lt;/li&amp;gt;&lt;br /&gt;
         &amp;lt;li&amp;gt;Redirecting the customer to the Barion Smart Gateway to select a funding source&amp;lt;/li&amp;gt;&lt;br /&gt;
         &amp;lt;li&amp;gt;Processing the callback and requesting information about the result of the payment&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;/ol&amp;gt;&lt;br /&gt;
   &amp;lt;/li&amp;gt;&lt;br /&gt;
   &amp;lt;li&amp;gt;[[#Step 2: Using the token|Using the registered token]] to charge the customer&amp;lt;/li&amp;gt;&lt;br /&gt;
   &lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Step 1:  Creating the funding source token ==&lt;br /&gt;
To be able to use a token payment scenario first the merchant has to register the token with Barion. The merchant has to make sure that the customer is well aware of the fact that they are giving consent to a tokenized payment. The Barion Smart Gateway UI does not indicate in any way that the payment is a token payment.&lt;br /&gt;
&lt;br /&gt;
The token is registered to the shop and not to the merchant&#039;s Barion account. So if the merchant has multiple shops in its Barion account, the registered tokens can not be shared among them even if the customer is the same. If you want to use tokens in multiple shops, please contact Barion in the Customer center.&lt;br /&gt;
&lt;br /&gt;
=== 1.1 Preparing the payment===&lt;br /&gt;
&lt;br /&gt;
The token registration is basically a [[Responsive_web_payment|normal payment]] with three extra properties in the [[Payment-Start-v2|Payment/Start]] request:&lt;br /&gt;
* InitiateRecurrence&lt;br /&gt;
* RecurrenceId&lt;br /&gt;
* RecurrenceType&lt;br /&gt;
&lt;br /&gt;
==== InitiateRecurrence====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; is a bool property. If you set it to &#039;&#039;&#039;true&#039;&#039;&#039; then the payment gateway will consider the payment as a token registration. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;This happens even if the customer is already has a registered token, so you are able to re-register a funding source or even a customer. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==== RecurrenceId ====&lt;br /&gt;
The next required property for a token registration is the token itself. This is generated by the shop and has to be unique for every registration. The token should be specified in the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; property of the [[Payment-Start-v2|Payment/Start]] request. This token must be saved in the webshops database. A &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; token represents the funding source (bank card or Barion balance) of a customer. Since a customer can have multiple cards and accounts as a funding source make sure that in the webshop&#039;s system multiple tokens can belong to a single customer.&lt;br /&gt;
&lt;br /&gt;
==== RecurrenceType ====&lt;br /&gt;
The third required property is the [[RecurrenceType|Recurrence Type]]. This specifies the scenario. In case of Recurring Payment &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; must also be set.&lt;br /&gt;
&lt;br /&gt;
==== Example JSON request for a Merchant Initiated Payment scenario ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-7&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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;InitiateRecurrence&amp;quot;: true,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;MerchantInitiatedPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 25.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Subscription fee for the first month&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Website subscription&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Website subscription for one month&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&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;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The response will be the same as to a [[Responsive_web_payment#Processing_the_successful_response|basic &#039;&#039;&#039;Immediate&#039;&#039;&#039; scenario]]. The &amp;lt;code&amp;gt;RecurrenceResult&amp;lt;/code&amp;gt; property at this point is &#039;&#039;&#039;None&#039;&#039;&#039; since the token is not registered to a funding source yet.&lt;br /&gt;
&lt;br /&gt;
==== Example JSON request for a Recurring Payment scenario ====&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Recurring Payment&#039;&#039;&#039; scenario has some extra restrictions. The merchant has to specify two additional properties in the [[Payment-Start-v2|Payment/Start]] request:&lt;br /&gt;
* &amp;lt;code&amp;gt;RecurringExpiry&amp;lt;/code&amp;gt;: The date after subsequent charges should not be accepted.&lt;br /&gt;
* &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt;: The minimum days the merchant has to wait between payments.&lt;br /&gt;
&lt;br /&gt;
Both properties are located in the [[PurchaseInformation]] property and must be specified if this scenario is selected.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-7, 30-33&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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;InitiateRecurrence&amp;quot;: true,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;RecurringPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 25.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Subscription fee for the first month&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Website subscription&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Website subscription for one month&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&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;
        }&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;PurchaseInformation&amp;quot;:{&lt;br /&gt;
        &amp;quot;RecurringFrequency&amp;quot;: 10,&lt;br /&gt;
        &amp;quot;RecurringExpiry&amp;quot;: &amp;quot;2022-10-01&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Possible error responses ====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| 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;
=== 1.2 Redirecting the customer to the Barion Smart Gateway to select a funding source ===&lt;br /&gt;
&lt;br /&gt;
After a successful payment preparation, the customer is redirected to the secure Barion Smart Gateway to choose a funding source. The funding source the customer selects will be registered to the token. The funding source can either be a Barion e-money balance or a bank card. This means that even though the customer may own multiple cards only the one that was registered to the token can be used for future token payments. To change the funding source attached to the token a new registration should be requested.&lt;br /&gt;
&lt;br /&gt;
=== 1.3 Processing the callback and requesting information about the result of the payment ===&lt;br /&gt;
&lt;br /&gt;
When the payment is completed (either successfully or unsuccessfully) a callback message is sent to the merchant&#039;s system. Once received a [[Payment-GetPaymentState-v2|GetPaymentState]] request must be sent to the Barion API. On how to implement this please read the article about the  [[Callback_mechanism|Callback mechanism]].&lt;br /&gt;
&lt;br /&gt;
The full response of the GetPaymentState request depends on the payment scenario and the structure of the payment. When it comes to token payment there are several properties to look out for. &lt;br /&gt;
* In case the &amp;lt;code&amp;gt;Status&amp;lt;/code&amp;gt; is &#039;&#039;&#039;Succeeded&#039;&#039;&#039; the funding source token is registered and ready to use.&lt;br /&gt;
* The &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; contains the ID of the token process. This specifies the nature of the token payment. &lt;br /&gt;
&lt;br /&gt;
==== TraceId ====&lt;br /&gt;
&lt;br /&gt;
In case of Recurring payment or Merchant initiated payment scenarios the [[Payment-GetPaymentState-v2|GetPaymentState]] response returns an additional field called &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;. The value of this property is generated by the card issuer and is up to a 100 characters, and should be left intact (whitespaces and 0s can&#039;t be trimmed). The merchant has to save it and submit it in all subsequent Recurring or Merchant initiated payments of the same type, otherwise, the payments can be declined by the issuer. The &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; represents the first, customer-present payment and helps the issuer to connect subsequent payments to this initial payment.&lt;br /&gt;
&lt;br /&gt;
====Example GetPaymentState response====&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;8, 11-12&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;2a9f3260bc2feb118bc3001dd8b71cc4&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001&amp;quot;,&lt;br /&gt;
    &amp;quot;OrderNumber&amp;quot;: null,&lt;br /&gt;
    &amp;quot;POSId&amp;quot;: &amp;quot;[[SHOPS_PUBLIC_KEY]]&amp;quot;,&lt;br /&gt;
    &amp;quot;POSName&amp;quot;: &amp;quot;[[MERCHANTS_BARION_SHOPNAME]]&amp;quot;,&lt;br /&gt;
    &amp;quot;POSOwnerEmail&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentType&amp;quot;: &amp;quot;Immediate&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSource&amp;quot;: &amp;quot;BankCard&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;MerchantInitiatedPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;FGTRR55322843442124780&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingInformation&amp;quot;: {&lt;br /&gt;
        &amp;quot;BankCard&amp;quot;: {&lt;br /&gt;
            &amp;quot;MaskedPan&amp;quot;: &amp;quot;0425&amp;quot;,&lt;br /&gt;
            &amp;quot;BankCardType&amp;quot;: &amp;quot;Visa&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruYear&amp;quot;: &amp;quot;2020&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruMonth&amp;quot;: &amp;quot;12&amp;quot;&lt;br /&gt;
        },&lt;br /&gt;
        &amp;quot;AuthorizationCode&amp;quot;: &amp;quot;512244&amp;quot;,&lt;br /&gt;
        &amp;quot;ProcessResult&amp;quot;: &amp;quot;Successful&amp;quot;&lt;br /&gt;
    },&lt;br /&gt;
    &amp;quot;AllowedFundingSources&amp;quot;: [&lt;br /&gt;
        &amp;quot;All&amp;quot;&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;GuestCheckout&amp;quot;: true,&lt;br /&gt;
    &amp;quot;CreatedAt&amp;quot;: &amp;quot;2020-11-26T07:52:48.9Z&amp;quot;,&lt;br /&gt;
    &amp;quot;ValidUntil&amp;quot;: &amp;quot;2020-11-26T08:22:48.9Z&amp;quot;,&lt;br /&gt;
    &amp;quot;CompletedAt&amp;quot;: &amp;quot;2020-11-26T08:11:54.118Z&amp;quot;,&lt;br /&gt;
    &amp;quot;ReservedUntil&amp;quot;: null,&lt;br /&gt;
    &amp;quot;DelayedCaptureUntil&amp;quot;: null,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
           ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;Total&amp;quot;: 25.20,&lt;br /&gt;
    &amp;quot;SuggestedLocale&amp;quot;: &amp;quot;hu-HU&amp;quot;,&lt;br /&gt;
    &amp;quot;FraudRiskScore&amp;quot;: null,&lt;br /&gt;
    &amp;quot;RedirectUrl&amp;quot;: &amp;quot;https://merchanturl/Redirect?paymentId=2a9f3260bc2feb118bc3001dd8b71cc4&amp;quot;,&lt;br /&gt;
    &amp;quot;CallbackUrl&amp;quot;: &amp;quot;https://merchanturl/Callback?paymentId=2a9f3260bc2feb118bc3001dd8b71cc4&amp;quot;,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&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;
==== Displaying the funding source in a GUI ====&lt;br /&gt;
We strongly advise saving the complete response for future reference. The &amp;lt;code&amp;gt;FundingSource&amp;lt;/code&amp;gt; field tells if the funding source is a Barion balance or a card. If it is a card, it is useful to save [[FundingInformation]] for displaying it for the user, when requesting future payments. The usual way to display funding sources is to show the last 4 digits of the card, with 4 stars, eg: *** 1234. The card used can be obtained from FundingInformation&#039;s [[BankCard]] field. The [[CardType]] field can be used to display the appropriate card logo. You can even show, if the card is expired, and offer to register another one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; FundingInformation part of the GetPaymentState response &#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
    &amp;quot;FundingInformation&amp;quot;: {&lt;br /&gt;
        &amp;quot;BankCard&amp;quot;: {&lt;br /&gt;
            &amp;quot;MaskedPan&amp;quot;: &amp;quot;0425&amp;quot;,&lt;br /&gt;
            &amp;quot;BankCardType&amp;quot;: &amp;quot;Visa&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruYear&amp;quot;: &amp;quot;2020&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruMonth&amp;quot;: &amp;quot;12&amp;quot;&lt;br /&gt;
        },&lt;br /&gt;
        &amp;quot;AuthorizationCode&amp;quot;: &amp;quot;512244&amp;quot;,&lt;br /&gt;
        &amp;quot;ProcessResult&amp;quot;: &amp;quot;Successful&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This can be displayed for example as &amp;lt;code&amp;gt;VISA **** 0425 (12/20)&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is a request-response diagram of the token registration process:&lt;br /&gt;
 &lt;br /&gt;
[[File:Token_payment_initiation.jpg]]&lt;br /&gt;
&lt;br /&gt;
= Step 2: Using the token =&lt;br /&gt;
&lt;br /&gt;
To use an already registered token for a payment, you have to use the same [[Payment-Start-v2|/Payment/Start]] API endpoint but the &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; should be set to &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;. This tells the Barion API to use the token for payment instead of only registering it. The token should be specified in the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; property. To be able to use a token, the initial payment must be in a successful state.&lt;br /&gt;
&lt;br /&gt;
At this point, the merchant has to decide whether this subsequent payment is used for the same token payment scenario or something changed. This is important because the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; can only be used for the same scenario, otherwise, the card issuer will decline the charge.&lt;br /&gt;
A &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; can only be used again if:&lt;br /&gt;
* the funding source is the same (technically the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; is the same)&lt;br /&gt;
* the token payment scenario is the same (technically the &amp;lt;code&amp;gt;RecurrenceType&amp;lt;/code&amp;gt; is the same)&lt;br /&gt;
* this subsequent request complies with the scenario restrictions (eg: in case of recurring payment the amount of the subsequent payment does not exceed the initial amount)&lt;br /&gt;
&lt;br /&gt;
If the funding source changes, new &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; must be requested. The process to do that is [[#Changing the funding source|described in detail here]]. If the funding source stays the same but the scenario changes or the restrictions are no longer met new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; must be requested. The process to do that is [[#Changing the token payment scenario with an existing token|described here]].&lt;br /&gt;
&lt;br /&gt;
== Subsequent payments in case of Recurring payment scenario ==&lt;br /&gt;
&lt;br /&gt;
In this case, three extra conditions must be met:&lt;br /&gt;
* the amount of the subsequent payment must not be higher than the initial amount&lt;br /&gt;
* at least that much days must be spent as defined in the initial &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt; property&lt;br /&gt;
* the date of the payment must not exceed the day specified in the initial &amp;lt;code&amp;gt;RecurringExpiry&amp;lt;/code&amp;gt; property&lt;br /&gt;
&lt;br /&gt;
Please be aware that in case any of these are no longer valid the merchant has to request a new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; as [[#Changing the token payment scenario with an existing token|described here]]. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=These conditions are not enforced by the Barion system so the violation of them will result in a declined charge.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
Payment/start must not include the &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;RecurringExpiry&amp;lt;/code&amp;gt; properties (since they are already fixed during the initial payment).&lt;br /&gt;
&lt;br /&gt;
==== Example payment/start of a subsequent Recurring payment ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-8&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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-002&amp;quot;,&lt;br /&gt;
    &amp;quot;InitiateRecurrence&amp;quot;: false,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;RecurringPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;FGTRR55322843442124780&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 25.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Subscription fee for the second month&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Website subscription&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Website subscription for one month&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&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-02&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Example response to this request ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;4,8,11&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;fb582913dc2feb11a49f309c23734b1c&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;Successful&amp;quot;,&lt;br /&gt;
    &amp;quot;ThreeDSAuthClientData&amp;quot;: null,&lt;br /&gt;
     ...&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;FGTRR55322843442124780&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;
The structure of the response is the same as the normal &amp;lt;tt&amp;gt;/Payment/Start&amp;lt;/tt&amp;gt; response just the statuses will be different. In this case&lt;br /&gt;
* the payment level &amp;lt;code&amp;gt;Status&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Succeeded&#039;&#039;&#039; instead of &#039;&#039;&#039;Prepared&#039;&#039;&#039;&lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceResult&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Successful&#039;&#039;&#039; (or &#039;&#039;&#039;Failed&#039;&#039;&#039;) instead of &#039;&#039;&#039;None&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The value of the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; will be the same as in the request.&lt;br /&gt;
&lt;br /&gt;
== Subsequent payments in case of Merchant Initiated Payment scenario ==&lt;br /&gt;
&lt;br /&gt;
In this scenario there are no restrictions.&lt;br /&gt;
&lt;br /&gt;
==== Example payment/start of a subsequent Merchant Initiated Payment ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-8&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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-002&amp;quot;,&lt;br /&gt;
    &amp;quot;InitiateRecurrence&amp;quot;: false,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;MerchantInitiatedPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;KBYRR55322844552124780&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 75,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Usage fee for 2020/12&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Phone bill&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Usage fee for 2020/12&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&amp;quot;,&lt;br /&gt;
                    &amp;quot;UnitPrice&amp;quot;: 75,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 75,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-02&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Example response to this request ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;4,8,11&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;fb582913dc2feb11a49f309c23734b1c&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;Successful&amp;quot;,&lt;br /&gt;
    &amp;quot;ThreeDSAuthClientData&amp;quot;: null,&lt;br /&gt;
     ...&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;KBYRR55322844552124780&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;
The structure of the response is the same as the normal &amp;lt;tt&amp;gt;/Payment/Start&amp;lt;/tt&amp;gt; response just the statuses will be different. In this case&lt;br /&gt;
* the payment level &amp;lt;code&amp;gt;Status&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Succeeded&#039;&#039;&#039; instead of &#039;&#039;&#039;Prepared&#039;&#039;&#039;&lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceResult&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Successful&#039;&#039;&#039; (or &#039;&#039;&#039;Failed&#039;&#039;&#039;) instead of &#039;&#039;&#039;None&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The value of the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; will be the same as in the request.&lt;br /&gt;
&lt;br /&gt;
== Subsequent payments in case of OneClick Payment scenario ==&lt;br /&gt;
&lt;br /&gt;
In this scenario, the merchant has to prepare to perform the [[#Off-site 3DS v2 authentication|off-site 3DS v2 authentication]] of the payer. 3DS authentication is not required in the following cases:&lt;br /&gt;
* the token (&amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt;) was requested before 3DS came into effect,&lt;br /&gt;
* the original payment was not initialized by bank card,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is not used in this scenario since the payer is present during the transaction. &lt;br /&gt;
&lt;br /&gt;
==== Example payment/start of a subsequent OneClick Payment ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-7&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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-002&amp;quot;,&lt;br /&gt;
    &amp;quot;InitiateRecurrence&amp;quot;: false,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;OneClickPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 17,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Book: How to shop online&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;How to shop online&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Book about shopping online&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;: 17,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 17,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-02&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Example response to this request ====&lt;br /&gt;
&lt;br /&gt;
In this scenario, the response contains the &amp;lt;code&amp;gt;ThreeDSAuthClientData&amp;lt;/code&amp;gt; property that is used to perform an [[#Off-site 3DS v2 authentication|off-site 3DS v2 authentication]].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;4,8-9&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;fb582913dc2feb11a49f309c23734b1c&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;Successful&amp;quot;,&lt;br /&gt;
    &amp;quot;ThreeDSAuthClientData&amp;quot;: &amp;quot;ewoJIkNhcmRQdWJs...WZXJzaW9uIjogIjIuMS4wIgp9Cg==&amp;quot;,&lt;br /&gt;
     ...&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;
== 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. The payment s 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 use 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 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 not fully activated.&lt;br /&gt;
|-&lt;br /&gt;
|UserCantMakeOutgoingTransaction || The payee specified in the transaction is not allowed to make payeetransactions 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;
This is the request-response diagram of the subsequent payments:&lt;br /&gt;
&lt;br /&gt;
[[File:Token_payment_2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; when requesting Transaction Risk Analysis (TRA) during a subsequent payment, and all conditions have been met, challenge is not shown to the user.&lt;br /&gt;
&lt;br /&gt;
== RecurrenceResult: ThreeDSAuthenticationRequired ==&lt;br /&gt;
&lt;br /&gt;
In response to a subsequent payment, this RecurrenceResult can be received. This means that the payment can not be processed due to the lack of 3DS v2 information. &lt;br /&gt;
&lt;br /&gt;
This can happen if the initial payment was successfully authenticated via 3DS v2 but the subsequent payment does not refer to the original authentication with the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
To fix this, request and store the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; of the initial payment and then specify it in the subsequent [[Payment-Start-v2]].&lt;br /&gt;
&lt;br /&gt;
To learn the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; of a previous payment just simply request the payment information via the [[Payment-GetPaymentState-v2]] endpoint.&lt;br /&gt;
&lt;br /&gt;
= Changing funding source or token scenarios =&lt;br /&gt;
&lt;br /&gt;
==Changing the funding source==&lt;br /&gt;
&lt;br /&gt;
This could happen if the funding source becomes invalid for some reason (card gets deleted or expires) or the merchant decides to use that token for another payment. In this case, the merchant has to register the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; again. &lt;br /&gt;
To do this a new payment must be started and in the [[Payment-Start-v2|Payment/Start]] request the following setup should be specified:&lt;br /&gt;
* the &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; field has to be set to &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; &lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; has to be specified.&lt;br /&gt;
* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; should not be specified.&lt;br /&gt;
&lt;br /&gt;
[[File:Funding-source-change.png|1500px]]&lt;br /&gt;
&lt;br /&gt;
Since the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is bound to the payer and the process if the funding source changes new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; will be generated. This new ID must be saved to this payment and must be used from this moment on for subsequent payments.&lt;br /&gt;
&lt;br /&gt;
==Changing the token payment scenario with an existing token==&lt;br /&gt;
&lt;br /&gt;
This could occur when the merchant wants to get authorization from the payer to a new token scenario for the already registered funding source. To be able to do this the merchant has to have a valid and registered &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt;.&lt;br /&gt;
Let&#039;s see some examples when this may be necessary:&lt;br /&gt;
* The payer subscribed to the merchant&#039;s service beforehand and the merchant decided to use the recurring payment token scenario. The payer wants to subscribe to another service and this requires a different payment schedule. This means that the &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt; that was specified initially can not be maintained so it is required to acquire a new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;&lt;br /&gt;
* The payer bought something on the merchant&#039;s website and uses the one-click feature for subsequent fast non-redirect payments. After a while, the payer decides to subscribe to a service provided by this same merchant. This means that the merchant has to create a new token scenario (not a one-click payment but a recurring payment). For this, the merchant has to acquire a new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;. This can be done without redirecting the payer to Barion using the existing &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; and performing a 3DS authentication on the merchant&#039;s website.&lt;br /&gt;
&lt;br /&gt;
To do these a new payment must be started and in the [[Payment-Start-v2|Payment/Start]] request the following setup should be specified:&lt;br /&gt;
* the &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; field has to be set to &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; &lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; has to be specified.&lt;br /&gt;
* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; should not be specified.&lt;br /&gt;
&lt;br /&gt;
After this, a 3DS authentication has to be completed to acquire a new trace ID. This can be done on the merchant&#039;s site if the merchant implements the barion.offsitegw.js for off-site 3DS authentication.&lt;br /&gt;
&lt;br /&gt;
This means that it can be achieved to acquire different Trace IDs for different scenarios with only one &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt;.&lt;br /&gt;
This is basically categorizing the different token scenarios as opposed to using every subsequent payment as an unmarked charge.&lt;br /&gt;
&lt;br /&gt;
[[File:Mutiple-traceid.png|1500px]]&lt;br /&gt;
&lt;br /&gt;
= Off-site 3DS v2 authentication =&lt;br /&gt;
&lt;br /&gt;
In certain scenarios, the payer has to be authenticated to lower the risk of the card transaction. This can be either performed &lt;br /&gt;
* on the Barion Smart Gateway (on-site) by redirecting the customer to Barion &lt;br /&gt;
* or on the merchant&#039;s website (off-site) by integrating the Barion Off-site client library.&lt;br /&gt;
&lt;br /&gt;
This section describes how to integrate the Barion off-site authentication library into the merchant&#039;s site.&lt;br /&gt;
&lt;br /&gt;
== Step 1 : Initialize the off-site authentication library  ==&lt;br /&gt;
You have to include the following css and javascript files in the code of your site. &lt;br /&gt;
&amp;lt;source lang=html&amp;gt;&lt;br /&gt;
&amp;lt;link href=&amp;quot;https://secure.barion.com/static/barion.offsitegw.min.css&amp;quot; rel=&amp;quot;stylesheet&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;script src=&amp;quot;https://secure.barion.com/static/barion.offsitegw.min.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/source &amp;gt;&lt;br /&gt;
These files include all the necessary javascript code and styling to handle the 3DS authentication and display the challenge if necessary.&lt;br /&gt;
&lt;br /&gt;
Then you have to initialize the Barion javascript client. To do that, you have to define a configuration object that specifies your functions that handle the off-site authentication events. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Authentication events&#039;&#039;&#039;&lt;br /&gt;
* &amp;lt;code&amp;gt;onAuthenticationSucceeded&amp;lt;/code&amp;gt;: the 3DS v2 authentication successfully completed&lt;br /&gt;
* &amp;lt;code&amp;gt;onAuthenticationFailed&amp;lt;/code&amp;gt;:  the 3DS v2 authentication failed&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
const configuration = {&lt;br /&gt;
    onAuthenticationSucceeded: function () {&lt;br /&gt;
        // handle successful authentication by calling the Barion API via merchant&#039;s backend&lt;br /&gt;
        // Call the v2/payment/complete endpoint&lt;br /&gt;
    },&lt;br /&gt;
    onAuthenticationFailed: function () {&lt;br /&gt;
        // Handle unsuccessful authentication result, no charge was made.&lt;br /&gt;
        // The payment might be still valid only the authentication failed&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then you have to pass this config object to the library.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
const gw = new Barion.OffsiteGw(configuration);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once the DOM is loaded you have to initialize the library:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
document.addEventListener(&amp;quot;DOMContentLoaded&amp;quot;, function () {&lt;br /&gt;
    // Initiate the Barion Offiste GW library&lt;br /&gt;
    gw.init();&lt;br /&gt;
});&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Step 2: Start the authentication process ==&lt;br /&gt;
Once the &amp;lt;code&amp;gt;ThreeDSAuthClientData&amp;lt;/code&amp;gt; is acquired from the payment/start you can start the authentication process by calling the &amp;lt;code&amp;gt;authenticate()&amp;lt;/code&amp;gt; method of the library.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
gw.authenticate(threeDsClientData);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will start the authentication process and present the challenge if needed. Visually this will create a modal window over the merchant&#039;s site and show the payer every necessary information.&lt;br /&gt;
Once the authentication process finished (either with or without a challenge) the appropriate event will be fired.&lt;br /&gt;
&lt;br /&gt;
== Step 3: Completing the payment ==&lt;br /&gt;
&lt;br /&gt;
In case of successful authentication, you have to call our [[Payment-Complete-v3|/Payment/Complete]] endpoint, where the actual charge will happen.&lt;br /&gt;
&lt;br /&gt;
=== Possible error responses for the subsequent payment requests ===&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
== Suggested implementation flow for off-site authentication ==&lt;br /&gt;
&lt;br /&gt;
Ideally, an off-site authentication should be part of a client-side experience without any postbacks or page reloads. This is our recommendation to achieve this:&lt;br /&gt;
&lt;br /&gt;
# After the customer clicks on the &amp;quot;Pay&amp;quot; button make an AJAX call from your client-side code to your back-end. &lt;br /&gt;
# Have your backend make a request to our payment/start endpoint (with the appropriate settings for the desired token scenario)&lt;br /&gt;
# Have your backend process the response and pass the value of the &amp;lt;code&amp;gt;ThreeDSAuthClientData&amp;lt;/code&amp;gt; property to your client-side code.&lt;br /&gt;
# Use the Barion off-site library to perform the authentication&lt;br /&gt;
# Once the authentication succeeds send another AJAX request from your client-side code to your back-end.&lt;br /&gt;
# Have your back-end code call our [[Payment-Complete-v3|/Payment/Complete]]&lt;br /&gt;
# Have your backend process the response and pass the result to your client-side code.&lt;br /&gt;
# Display the result for the customer&lt;br /&gt;
&lt;br /&gt;
= Testing the integration =&lt;br /&gt;
&lt;br /&gt;
3D Secure has no environment for end-to-end testing, therefore merchants have to split their testings into two parts: Testing the payment flow with and without challenge. Getting a challenge is only possible with real-life cards, merchants have to use their own (there will be no real charging at the end on the Sandbox of the Payment Gateway, but using a real card will result initiating a real 3DS authentication).&lt;br /&gt;
&lt;br /&gt;
== Testing the whole payment flow, without challenge ==&lt;br /&gt;
&lt;br /&gt;
Use the [[https://docs.barion.com/Sandbox#Test_cards Barion test cards]], they will always get a &amp;quot;frictionless&amp;quot; flow, where the 3DS process is presented on the UI, but you will never see a challenge screen. &lt;br /&gt;
&lt;br /&gt;
This is good for testing your integration itself because it will lead to a successful charge, and you will get a TraceId as well.&lt;br /&gt;
&lt;br /&gt;
== Testing the challenge itself ==&lt;br /&gt;
&lt;br /&gt;
Use your own card, and let the card issuer decide whether your payment will get a challenge or not during the 3DS authentication procedure. Your payment will fail at the end, and you won&#039;t get the TraceId. &lt;br /&gt;
&lt;br /&gt;
This is good to test, how the challenge screens look like in your shop - especially when you integrated OneClick payment directly to your shop. You might also check how your customers see your checkout flow on popular devices.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DSecure&amp;diff=4051</id>
		<title>3DSecure</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DSecure&amp;diff=4051"/>
		<updated>2023-05-18T12:17:59Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Known issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=3DSecure}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3D Secure ([https://en.wikipedia.org/wiki/3-D_Secure|3DS, Three-Domain Secure]) is a messaging protocol developed by [https://www.emvco.com EMVCo] that provides a more secure online card payment process. It enables consumers to authenticate themselves with their card issuer when making card-not-present (CNP) e-commerce purchases. &lt;br /&gt;
If the card is enrolled into 3DS authentication, additional information is required to decide whether the purchase is fraudulent or not. This decision is made by the card issuer (the bank or other institution that issued the card), not by the Barion system. &lt;br /&gt;
&lt;br /&gt;
There are two major versions of the protocol: &lt;br /&gt;
* &#039;&#039;&#039;3D Secure 1&#039;&#039;&#039; is an HTTP redirect-based scenario where the customer almost always needs to provide some extra proof for the transaction. The verification is usually a password or SMS code. Card schemes decommissioned 3D Secure 1 in 2021/2022. Barion does not support this old protocol.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;3D Secure 2&#039;&#039;&#039; is more sophisticated and uses additional information about the purchase, the shop, and the cardholder to make the decision. This requires more input data but provides better flow with less friction. The card issuer may verify the shopper&#039;s identity using passive, biometric, and two-factor authentication approaches. According to the [https://en.wikipedia.org/wiki/Strong_customer_authentication Strong Customer Authentication (SCA) rules of PSD2 RTS] every card issued in the EU has to be authenticated. 3D Secure 2 complies with the regulation.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=If the shopper completes a 3DSecure authentication successfully, the liability shifts from the merchant to the card issuer in case of fraud.|color=#FF7A3D}}&lt;br /&gt;
==Liability shift rules==&lt;br /&gt;
If a merchant implements 3D Secure authentication, they can avoid liability for chargebacks in case of fraud (that is, chargeback claims because of lost or stolen cards). This is called a liability shift.&lt;br /&gt;
In general, if a shopper completes a 3D Secure challenge authentication flow successfully, the liability for fraudulent chargebacks shifts from the merchant to the card issuer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Transaction type&lt;br /&gt;
!Liability shift to card issuer?&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions with challenge.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;card issuer applies a PSD2 exemption&#039;&#039;&#039; without the merchant requesting it. For example, issuer TRA.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 PSD2 SCA out-of-scope transactions: shopper&#039;s issuer is outside of the EEA, anonymous prepaid cards up to 150€ or merchant-initiated transactions.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;merchant or acquirer requests for a PSD2 exemption&#039;&#039;&#039; and the issuer grants an exemption.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==The payment process==&lt;br /&gt;
&lt;br /&gt;
The payment follows these steps:&lt;br /&gt;
# You check out your purchase from the merchant&#039;s website and select to pay via Barion.&lt;br /&gt;
# You are redirected to the Barion Smart Gateway.&lt;br /&gt;
# You input your card details and click &#039;&#039;&#039;Pay&#039;&#039;&#039;. &lt;br /&gt;
# Barion checks whether the card you used is a 3DSecure capable card and also the version the issuer supports. If the card is not &#039;&#039;&#039;3DSecure capable&#039;&#039;&#039;, the card authorization (charge) goes along without any extra steps. &lt;br /&gt;
# If the card is 3D Secure capable with 3DSecure 2, the flow changes:&lt;br /&gt;
#*# Barion starts the 3DS authentication in the background and sends the relevant information about the purchase to the card issuer. From this information, the issuer decides whether the payment is secure or if you should be challenged in some form.&lt;br /&gt;
#*# If the result is that you &#039;&#039;&#039;should not be challenged&#039;&#039;&#039; (this is the frictionless flow) your card is charged and the payment flow continues.&lt;br /&gt;
#*# If the result is that the issuer &#039;&#039;&#039;needs more proof&#039;&#039;&#039; from you, a popup window is displayed. In this window, the issuer displays &#039;&#039;something&#039;&#039; for you. The content varies according to the issuer, and it allows you to provide proof (SMS, token, question).&lt;br /&gt;
#*# After you successfully complete the challenge, the card is authenticated and the payment flow continues with the authorization of the card. The card can still be declined after successful 3DS authentication.&lt;br /&gt;
# At the end of the payment you are redirected to the merchant&#039;s website.&lt;br /&gt;
&lt;br /&gt;
== 3D Secure 2 ==&lt;br /&gt;
&lt;br /&gt;
The reason behind the second version was to provide a way to achieve the same level of security for authentication but with less friction. For this, a lot more information is required (or at least it is strongly recommended to provide them). This information comes from different sources:&lt;br /&gt;
* merchant&#039;s data about the customer (purchase behavior, addresses, and so on)&lt;br /&gt;
* customer&#039;s browser information (screen size, timezone, language, and so on)&lt;br /&gt;
* customer provided data (card information, e-mail address) &lt;br /&gt;
* Barion&#039;s data about the merchant, the purchase, and the customer (merchant&#039;s MCC code, name of the shop, and so on)&lt;br /&gt;
&lt;br /&gt;
The card issuer receives this information package and calculates the risk of the transaction. The result of this calculation specifies the flow:&lt;br /&gt;
* Frictionless flow: The customer is not presented with any challenge screen, no more information is needed, and authorization can take place.&lt;br /&gt;
* Challenge flow: The information is not sufficient, an additional challenge is needed to make sure that the card is not stolen.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
To achieve the frictionless flow the merchant has to provide as much information as possible about the purchase and the customer. This must be provided during the [[Payment-Start-v2-3DS|v2/payment/start]] API call. The properties marked as {{3dsfield}} must be specified. However, there are scenarios where not all of this data is available. In these cases, there are ways to indicate the lack of information. If the merchant does not provide the necessary data, the payment typically falls into the challenge flow. Ideally, we should avoid this as it causes friction and may result in the customer leaving the payment.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Although providing this data enhances the possibility of frictionless flow, it does not make it certain. This decision is up to the card issuer, Barion does not influence it. In case of challenge flow the card issuer provides a challenge screen that the customer must complete. This can be various things: one-time passwords sent via text, secret passwords, biometric identification, and so on.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
* If the user is challenged, additional user interaction is required, which results in increased abandonment. We recommend the following to reduce the churn:&lt;br /&gt;
** Send all available fields marked with the {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request.&lt;br /&gt;
** Request [[ChallengePreference|TRA]] exemption. &amp;lt;br /&amp;gt; &#039;&#039;&#039;Note&#039;&#039;&#039;: If you apply for this option, you are held liable in case of fraud.&lt;br /&gt;
&lt;br /&gt;
== Additional resources ==&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[Token_payment_upgrade_to_3DS|How to upgrade old token payment implementations to comply with 3DS]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_release_notes_-_2023r2&amp;diff=4044</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=4044"/>
		<updated>2023-05-15T14:23:31Z</updated>

		<summary type="html">&lt;p&gt;Bozag: Created page with &amp;quot;__NOTOC__ {{PageTitle|title=Barion release notes - 2023.05.23}}  =Short summary= Barion is rolling out a new update that changes bank transfers from your Wallet to a Barion vI...&amp;quot;&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 rolling out a new update that changes bank transfers from your Wallet to a Barion vIBAN to a direct money transfer instead. We also roll out the following new API endpoints for improved point of sale (POS) creation for your customers who already have a Barion Wallet.&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;
=Creating a new POS=&lt;br /&gt;
The [[Pos-Create-v1|Create a POS]] endpoint allows you to create a new POS using an API call, provided that you already created a Barion Wallet and you are familiar with how to [[Calling_the_API|call the Barion API]].&lt;br /&gt;
&lt;br /&gt;
=Querying POS details=&lt;br /&gt;
The [[Pos-GetState-v1|Query all details of a POS]] endpoint allows you to query all details of a POS that is attached to a Barion Wallet.&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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_releases&amp;diff=4043</id>
		<title>Barion releases</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_releases&amp;diff=4043"/>
		<updated>2023-05-15T14:10:51Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Barion releases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Barion releases=&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
These are the public release notes of the Barion production environment.&lt;br /&gt;
&lt;br /&gt;
{|  class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Date&lt;br /&gt;
! Release notes&lt;br /&gt;
! Short description&lt;br /&gt;
|-&lt;br /&gt;
| 2023.05.23&lt;br /&gt;
|[[Barion_release_notes_-_2023r2|Detailed release notes]]&lt;br /&gt;
|We are publishing some new features in this release:&lt;br /&gt;
&lt;br /&gt;
*API-based POS creation and querying,&lt;br /&gt;
*Direct money transfer if transferring from your Wallet to a Barion vIBAN or GIRO number.&lt;br /&gt;
|-&lt;br /&gt;
| 2023.04.04&lt;br /&gt;
|N/A&lt;br /&gt;
|This release includes several updates and improvements to the Barion system. While there are fewer customer-facing features in this release, these changes are essential to the stability and efficiency of our service.&lt;br /&gt;
&lt;br /&gt;
Here are some of the key updates and improvements:&lt;br /&gt;
* Expanded our payment processing capabilities&lt;br /&gt;
* Streamlined onboarding processes with automated background checks&lt;br /&gt;
* Improved our current integrations to make bank transfer wallet top-ups faster&lt;br /&gt;
|-&lt;br /&gt;
| 2022.11.21&lt;br /&gt;
|[[Barion_release_notes_-_2022.11.21|Detailed release notes]]&lt;br /&gt;
|We are publishing some new features in this release:&lt;br /&gt;
&lt;br /&gt;
*Virtual IBAN feature for bank transfer top-ups,&lt;br /&gt;
*Barion Wallet API key as a new method of API authentication.&lt;br /&gt;
|-&lt;br /&gt;
| 2022.08.29&lt;br /&gt;
|[[Barion_release_notes_-_2022.08.29|Detailed release notes]]&lt;br /&gt;
|We are publishing some new features and user interface improvements in this release. The following features and updates are rolled out:&lt;br /&gt;
&lt;br /&gt;
*Profile menu&lt;br /&gt;
*Wallet menu changes&lt;br /&gt;
*New shop creating and editing flow&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DSecure&amp;diff=4041</id>
		<title>3DSecure</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DSecure&amp;diff=4041"/>
		<updated>2023-05-11T14:25:22Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* The payment process */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=3DSecure}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3D Secure ([https://en.wikipedia.org/wiki/3-D_Secure|3DS, Three-Domain Secure]) is a messaging protocol developed by [https://www.emvco.com EMVCo] that provides a more secure online card payment process. It enables consumers to authenticate themselves with their card issuer when making card-not-present (CNP) e-commerce purchases. &lt;br /&gt;
If the card is enrolled into 3DS authentication, additional information is required to decide whether the purchase is fraudulent or not. This decision is made by the card issuer (the bank or other institution that issued the card), not by the Barion system. &lt;br /&gt;
&lt;br /&gt;
There are two major versions of the protocol: &lt;br /&gt;
* &#039;&#039;&#039;3D Secure 1&#039;&#039;&#039; is an HTTP redirect-based scenario where the customer almost always needs to provide some extra proof for the transaction. The verification is usually a password or SMS code. Card schemes decommissioned 3D Secure 1 in 2021/2022. Barion does not support this old protocol.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;3D Secure 2&#039;&#039;&#039; is more sophisticated and uses additional information about the purchase, the shop, and the cardholder to make the decision. This requires more input data but provides better flow with less friction. The card issuer may verify the shopper&#039;s identity using passive, biometric, and two-factor authentication approaches. According to the [https://en.wikipedia.org/wiki/Strong_customer_authentication Strong Customer Authentication (SCA) rules of PSD2 RTS] every card issued in the EU has to be authenticated. 3D Secure 2 complies with the regulation.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=If the shopper completes a 3DSecure authentication successfully, the liability shifts from the merchant to the card issuer in case of fraud.|color=#FF7A3D}}&lt;br /&gt;
==Liability shift rules==&lt;br /&gt;
If a merchant implements 3D Secure authentication, they can avoid liability for chargebacks in case of fraud (that is, chargeback claims because of lost or stolen cards). This is called a liability shift.&lt;br /&gt;
In general, if a shopper completes a 3D Secure challenge authentication flow successfully, the liability for fraudulent chargebacks shifts from the merchant to the card issuer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Transaction type&lt;br /&gt;
!Liability shift to card issuer?&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions with challenge.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;card issuer applies a PSD2 exemption&#039;&#039;&#039; without the merchant requesting it. For example, issuer TRA.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 PSD2 SCA out-of-scope transactions: shopper&#039;s issuer is outside of the EEA, anonymous prepaid cards up to 150€ or merchant-initiated transactions.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;merchant or acquirer requests for a PSD2 exemption&#039;&#039;&#039; and the issuer grants an exemption.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==The payment process==&lt;br /&gt;
&lt;br /&gt;
The payment follows these steps:&lt;br /&gt;
# You check out your purchase from the merchant&#039;s website and select to pay via Barion.&lt;br /&gt;
# You are redirected to the Barion Smart Gateway.&lt;br /&gt;
# You input your card details and click &#039;&#039;&#039;Pay&#039;&#039;&#039;. &lt;br /&gt;
# Barion checks whether the card you used is a 3DSecure capable card and also the version the issuer supports. If the card is not &#039;&#039;&#039;3DSecure capable&#039;&#039;&#039;, the card authorization (charge) goes along without any extra steps. &lt;br /&gt;
# If the card is 3D Secure capable with 3DSecure 2, the flow changes:&lt;br /&gt;
#*# Barion starts the 3DS authentication in the background and sends the relevant information about the purchase to the card issuer. From this information, the issuer decides whether the payment is secure or if you should be challenged in some form.&lt;br /&gt;
#*# If the result is that you &#039;&#039;&#039;should not be challenged&#039;&#039;&#039; (this is the frictionless flow) your card is charged and the payment flow continues.&lt;br /&gt;
#*# If the result is that the issuer &#039;&#039;&#039;needs more proof&#039;&#039;&#039; from you, a popup window is displayed. In this window, the issuer displays &#039;&#039;something&#039;&#039; for you. The content varies according to the issuer, and it allows you to provide proof (SMS, token, question).&lt;br /&gt;
#*# After you successfully complete the challenge, the card is authenticated and the payment flow continues with the authorization of the card. The card can still be declined after successful 3DS authentication.&lt;br /&gt;
# At the end of the payment you are redirected to the merchant&#039;s website.&lt;br /&gt;
&lt;br /&gt;
== 3D Secure 2 ==&lt;br /&gt;
&lt;br /&gt;
The reason behind the second version was to provide a way to achieve the same level of security for authentication but with less friction. For this, a lot more information is required (or at least it is strongly recommended to provide them). This information comes from different sources:&lt;br /&gt;
* merchant&#039;s data about the customer (purchase behavior, addresses, and so on)&lt;br /&gt;
* customer&#039;s browser information (screen size, timezone, language, and so on)&lt;br /&gt;
* customer provided data (card information, e-mail address) &lt;br /&gt;
* Barion&#039;s data about the merchant, the purchase, and the customer (merchant&#039;s MCC code, name of the shop, and so on)&lt;br /&gt;
&lt;br /&gt;
The card issuer receives this information package and calculates the risk of the transaction. The result of this calculation specifies the flow:&lt;br /&gt;
* Frictionless flow: The customer is not presented with any challenge screen, no more information is needed, and authorization can take place.&lt;br /&gt;
* Challenge flow: The information is not sufficient, an additional challenge is needed to make sure that the card is not stolen.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
To achieve the frictionless flow the merchant has to provide as much information as possible about the purchase and the customer. This must be provided during the [[Payment-Start-v2-3DS|v2/payment/start]] API call. The properties marked as {{3dsfield}} must be specified. However, there are scenarios where not all of this data is available. In these cases, there are ways to indicate the lack of information. If the merchant does not provide the necessary data, the payment typically falls into the challenge flow. Ideally, we should avoid this as it causes friction and may result in the customer leaving the payment.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Although providing this data enhances the possibility of frictionless flow, it does not make it certain. This decision is up to the card issuer, Barion does not influence it. In case of challenge flow the card issuer provides a challenge screen that the customer must complete. This can be various things: one-time passwords sent via text, secret passwords, biometric identification, and so on.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
* If the shopper has no phone number registered, and no sms can be sent, the authentication fails.&lt;br /&gt;
* If the user is challenged, additional user interaction is required, which results in increased abandonment. We recommend the following to reduce the churn:&lt;br /&gt;
** Send all available fields marked with the {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request..&lt;br /&gt;
** Request [[ChallengePreference|TRA]] exemption. &amp;lt;br /&amp;gt; &#039;&#039;&#039;Note&#039;&#039;&#039;: If you apply for this option, you are held liable in case of fraud.&lt;br /&gt;
&lt;br /&gt;
== Additional resources ==&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[Token_payment_upgrade_to_3DS|How to upgrade old token payment implementations to comply with 3DS]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4040</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=4040"/>
		<updated>2023-05-11T14:04:59Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Top-up from wallet with a partner card */&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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4039</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=4039"/>
		<updated>2023-05-11T14:04:52Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Reverse partner card top-up */&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;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4038</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=4038"/>
		<updated>2023-05-11T14:04:44Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Issue a partner card */&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;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4037</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=4037"/>
		<updated>2023-05-11T14:04:37Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Change PIN on a partner card */&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;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The username and password of the card owner were incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4036</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=4036"/>
		<updated>2023-05-11T14:04:30Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Paying with a partner card */&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;
== [[PartnerCard_ChangePin_v2|Change PIN]] on a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| NewPinEqualsToCurrent || The new PIN code equals to current one.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardPin || The current PIN is incorrect, and did not match the stored version.&lt;br /&gt;
|-&lt;br /&gt;
| PinChangeFailed || A fatal system error occurred during the process.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The username and password of the card owner were incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4035</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=4035"/>
		<updated>2023-05-11T14:04:22Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Activate a partner card */&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;
== [[Payment_PayWithPartnerCard_v2|Paying]] with a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_ChangePin_v2|Change PIN]] on a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| NewPinEqualsToCurrent || The new PIN code equals to current one.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardPin || The current PIN is incorrect, and did not match the stored version.&lt;br /&gt;
|-&lt;br /&gt;
| PinChangeFailed || A fatal system error occurred during the process.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The username and password of the card owner were incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4034</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=4034"/>
		<updated>2023-05-11T14:04:15Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Preparing a partner card */&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;
== [[PartnerCard_Activate_v2|Activate]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Payment_PayWithPartnerCard_v2|Paying]] with a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_ChangePin_v2|Change PIN]] on a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| NewPinEqualsToCurrent || The new PIN code equals to current one.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardPin || The current PIN is incorrect, and did not match the stored version.&lt;br /&gt;
|-&lt;br /&gt;
| PinChangeFailed || A fatal system error occurred during the process.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The username and password of the card owner were incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4019</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=4019"/>
		<updated>2023-05-11T12:03:58Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* 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;
== [[PartnerCard_Prepare_v2|Preparing]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| CardPreparationNotAllowed || If the card number is already registered (attached to a wallet) a new preparation is not allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Activate_v2|Activate]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Payment_PayWithPartnerCard_v2|Paying]] with a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_ChangePin_v2|Change PIN]] on a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| NewPinEqualsToCurrent || The new PIN code equals to current one.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardPin || The current PIN is incorrect, and did not match the stored version.&lt;br /&gt;
|-&lt;br /&gt;
| PinChangeFailed || A fatal system error occurred during the process.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The username and password of the card owner were incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4018</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=4018"/>
		<updated>2023-05-11T12:02:48Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &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;
== [[PartnerCard_Prepare_v2|Preparing]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| CardPreparationNotAllowed || If the card number is already registered (attached to a wallet) a new preparation is not allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Activate_v2|Activate]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Payment_PayWithPartnerCard_v2|Paying]] with a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_ChangePin_v2|Change PIN]] on a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| NewPinEqualsToCurrent || The new PIN code equals to current one.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardPin || The current PIN is incorrect, and did not match the stored version.&lt;br /&gt;
|-&lt;br /&gt;
| PinChangeFailed || A fatal system error occurred during the process.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The username and password of the card owner were incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given top-up transaction was not found in the database.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner.&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The top-up process could not be completed due to an unknown error (contact developer support).&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno transaction is illegal because the original top-up was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-FromWalletWithPartnerCard-v2|Top-up from wallet with a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| UserCantMakeOutgoingTransaction || The source of the transfer, the facilitator user is not allowed to make outgoing transactions. Probably suspended.&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| InvalidUser || Something is seriously broken with an account in the transaction.&lt;br /&gt;
|-&lt;br /&gt;
| TopUpFailed || The top-up process failed because of a system error. &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 || 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-GetState-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-GetState-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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Token_payment_3D_Secure&amp;diff=4017</id>
		<title>Token payment 3D Secure</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Token_payment_3D_Secure&amp;diff=4017"/>
		<updated>2023-05-11T11:48:48Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Token Payment with 3D Secure}}&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
This payment scenario allows the integrator shop to register a token for a customer (and a funding source) in the Barion system and then, later on, using this token, charge the customer without redirecting her to the Barion Smart Gateway UI. The user may be present at the site of the merchant or she can be off-session as well, so the merchant can charge her e.g. for subscriptions. This means that the customer authorizes the shop to charge her card or Barion balance without typing in the card information or Barion login again.&lt;br /&gt;
&lt;br /&gt;
[[File:3ds-recurring.png|1500px]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=Premium feature|text=If you want to use this scenario, you have to specifically request it from Barion.|color=#1993c7}}&lt;br /&gt;
&lt;br /&gt;
= Token payment scenarios =&lt;br /&gt;
Token payment can be used in three use cases: &lt;br /&gt;
* &#039;&#039;&#039;Customer Initiated Payments&#039;&#039;&#039;: when the user is present on the website of the merchant and she decides to pay :&lt;br /&gt;
** &#039;&#039;&#039;OneClick payment&#039;&#039;&#039;: the user is charged upon her request initiated on the website of the merchant. Subsequent payments are subject to PSD2 SCA and as the user is present, she has to go through the authentication process.&lt;br /&gt;
* &#039;&#039;&#039;Merchant Initiated Payments&#039;&#039;&#039;: when the merchant initiates the payment without the user being present. It has two subtypes:&lt;br /&gt;
** &#039;&#039;&#039;Recurring payment&#039;&#039;&#039;: the user is charged with the same amount on a regular basis, typically in case of subscriptions. Subsequent payments are exempted from PSD2 SCA, but liability still shifts to the card issuer.&lt;br /&gt;
** &#039;&#039;&#039;MIT (merchant-initiated transaction)&#039;&#039;&#039;: the user is charged on an irregular basis and/or with a different amount. Subsequent payments of this type are excluded from PSD2 SCA, the liability is on the merchant.&lt;br /&gt;
&lt;br /&gt;
== Customer participation ==&lt;br /&gt;
&lt;br /&gt;
Since the token scenario is suitable for both customer and merchant-initiated payments here is a comparison about who starts the payment. This includes the regular, non-tokenized payment scenario as well:&lt;br /&gt;
&lt;br /&gt;
{|class=wikitable&lt;br /&gt;
|-&lt;br /&gt;
! rowspan=&amp;quot;2&amp;quot; | Scenario&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Initial payment&lt;br /&gt;
! colspan=&amp;quot;2&amp;quot; | Subsequent payments&lt;br /&gt;
|-&lt;br /&gt;
! Customer present&lt;br /&gt;
! Customer at Barion Smart GW &lt;br /&gt;
! Customer present&lt;br /&gt;
! Customer at Barion Smart GW&lt;br /&gt;
|-&lt;br /&gt;
| Non token (regular) payment || YES || YES || YES || YES &lt;br /&gt;
|-&lt;br /&gt;
| OneClick payment || YES || YES/NO&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; || YES || style=&amp;quot;background:#FFE2C4&amp;quot; | NO &lt;br /&gt;
|-&lt;br /&gt;
| Recurring payment || YES || YES/NO&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; || style=&amp;quot;background:#FFE2C4&amp;quot; | NO || style=&amp;quot;background:#FFE2C4&amp;quot; | NO &lt;br /&gt;
|-&lt;br /&gt;
| MIT || YES || YES/NO&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; || style=&amp;quot;background:#FFE2C4&amp;quot; | NO || style=&amp;quot;background:#FFE2C4&amp;quot; | NO &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;border: 1px solid #aaa; background-color:#eee; font-size: 0.8em; padding:5px 10px; display:inline-block;&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt; Token payment scenarios can be initiated with already registered &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; as well, in this case, the customer may remain on the merchant&#039;s site. &lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Requirements for the scenarios ==&lt;br /&gt;
&lt;br /&gt;
These token payment scenarios have different requirements, the table below summarizes the key differences.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Scenario&lt;br /&gt;
! Payment amount&lt;br /&gt;
! Payment frequency&lt;br /&gt;
! Liability in case of fraud&lt;br /&gt;
|-&lt;br /&gt;
| One-click payment || Various || Various || Card issuer&lt;br /&gt;
|-&lt;br /&gt;
| Recurring payment || Subsequent amounts must be equal or less than the initial amount  || Initial payment must define a minimum amount of days to wait between charges || Card issuer &lt;br /&gt;
|-&lt;br /&gt;
| Merchant initiated payment || Various  || Various || Merchant&lt;br /&gt;
|- &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 3DS authentication of the payer ==&lt;br /&gt;
&lt;br /&gt;
The new more secure 3DS v2 authentication must be performed for every online card payment. These token payment scenarios also have to use this new secure way of authentication. &lt;br /&gt;
The initial payment of a token scenario must be authenticated every time although the subsequent payments may be exempted in certain cases. &lt;br /&gt;
&lt;br /&gt;
Here is a table to compare the 3DS authentication requirements:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Scenario&lt;br /&gt;
! Initial payment&lt;br /&gt;
! Subsequent payments&lt;br /&gt;
|-&lt;br /&gt;
| One-click payment || ✔️ || ✔️&lt;br /&gt;
|-&lt;br /&gt;
| Recurring payment || ✔️ || &lt;br /&gt;
|-&lt;br /&gt;
| Merchant initiated payment || ✔️ || &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;IMPORTANT:&#039;&#039; When performing subsequent One-click payments with the &amp;lt;code&amp;gt;ChallengePreference&amp;lt;/code&amp;gt; parameter set to &amp;lt;code&amp;gt;NoChallengeNeeded&amp;lt;/code&amp;gt; (indicating a request for Transaction Risk Analysis), only a fraud analysis is performed, and the customer is not required to undergo a 3DS challenge.&lt;br /&gt;
&lt;br /&gt;
== Real life examples ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Phone bill&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The payer has a usage-based phone subscription that wants to pay without being present for every charge. They authorize the phone company to charge her card every month.&lt;br /&gt;
* Scenario: Merchant Initiated Transaction&lt;br /&gt;
* Explanation: Despite the frequency of the charges is monthly, the amount of the subsequent payments may exceed the initial payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TV subscription&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Payer subscribes to online streaming of a television channel. She authorizes the tv company to charge her card every month. The subscription fee is the same for every month.&lt;br /&gt;
* Scenario: Recurring payment&lt;br /&gt;
* Explanation: The amount of the subsequent payments will not exceed the initial payment and the charge is regularly monthly-based.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Bookclub with &amp;quot;free first month&amp;quot; bonus&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Payer subscribes to a book renting service. he authorizes the book club to charge her card for a selection of books each month. The subscription fee is the same for every month however, the first month is free. To ensure the subscription the service requires her to register her card details.&lt;br /&gt;
* Scenario: Merchant Initiated Transaction&lt;br /&gt;
* Explanation: Despite the frequency of the charges is monthly, and the fee will stay the same, the initial payment is zero. So the amount of the next payment will exceed the initial payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Online food delivery service&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The food delivery company wants to provide a quick and easy experience for its customer. They decide that the order will be quicker if the customers don&#039;t leave the website to pay for the goods.&lt;br /&gt;
* Scenario: OneClick payment&lt;br /&gt;
* Explanation: The customer will always be there so the other two scenarios are not available.&lt;br /&gt;
&lt;br /&gt;
== How to decide ==&lt;br /&gt;
&lt;br /&gt;
To help you decide on a suitable scenario, please use the decision graph below:&lt;br /&gt;
&lt;br /&gt;
[[File:3ds-recurrencetype-decision.png|520px]]&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 a USD account created in your wallet.&lt;br /&gt;
* To make sure every corner case scenario works for your webshop it is best to top up 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 this: [[Calling_the_API|Calling the API]]&lt;br /&gt;
&lt;br /&gt;
= The payment process =&lt;br /&gt;
&lt;br /&gt;
The process is divided into two major steps:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
   &amp;lt;li&amp;gt;[[#Step 1:  Creating the funding source token|Creating the token]] that represents one of the customer&#039;s funding sources (credit card or e-money wallet)&lt;br /&gt;
      &amp;lt;ol&amp;gt;&lt;br /&gt;
         &amp;lt;li&amp;gt;Preparing the payment via the Barion API&amp;lt;/li&amp;gt;&lt;br /&gt;
         &amp;lt;li&amp;gt;Redirecting the customer to the Barion Smart Gateway to select a funding source&amp;lt;/li&amp;gt;&lt;br /&gt;
         &amp;lt;li&amp;gt;Processing the callback and requesting information about the result of the payment&amp;lt;/li&amp;gt;&lt;br /&gt;
      &amp;lt;/ol&amp;gt;&lt;br /&gt;
   &amp;lt;/li&amp;gt;&lt;br /&gt;
   &amp;lt;li&amp;gt;[[#Step 2: Using the token|Using the registered token]] to charge the customer&amp;lt;/li&amp;gt;&lt;br /&gt;
   &lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Step 1:  Creating the funding source token ==&lt;br /&gt;
To be able to use a token payment scenario first the merchant has to register the token with Barion. The merchant has to make sure that the customer is well aware of the fact that they are giving consent to a tokenized payment. The Barion Smart Gateway UI does not indicate in any way that the payment is a token payment.&lt;br /&gt;
&lt;br /&gt;
The token is registered to the shop and not to the merchant&#039;s Barion account. So if the merchant has multiple shops in its Barion account, the registered tokens can not be shared among them even if the customer is the same. If you want to use tokens in multiple shops, please contact Barion in the Customer center.&lt;br /&gt;
&lt;br /&gt;
=== 1.1 Preparing the payment===&lt;br /&gt;
&lt;br /&gt;
The token registration is basically a [[Responsive_web_payment|normal payment]] with three extra properties in the [[Payment-Start-v2|Payment/Start]] request:&lt;br /&gt;
* InitiateRecurrence&lt;br /&gt;
* RecurrenceId&lt;br /&gt;
* RecurrenceType&lt;br /&gt;
&lt;br /&gt;
==== InitiateRecurrence====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; is a bool property. If you set it to &#039;&#039;&#039;true&#039;&#039;&#039; then the payment gateway will consider the payment as a token registration. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;This happens even if the customer is already has a registered token, so you are able to re-register a funding source or even a customer. &#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==== RecurrenceId ====&lt;br /&gt;
The next required property for a token registration is the token itself. This is generated by the shop and has to be unique for every registration. The token should be specified in the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; property of the [[Payment-Start-v2|Payment/Start]] request. This token must be saved in the webshops database. A &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; token represents the funding source (bank card or Barion balance) of a customer. Since a customer can have multiple cards and accounts as a funding source make sure that in the webshop&#039;s system multiple tokens can belong to a single customer.&lt;br /&gt;
&lt;br /&gt;
==== RecurrenceType ====&lt;br /&gt;
The third required property is the [[RecurrenceType|Recurrence Type]]. This specifies the scenario. In case of Recurring Payment &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; must also be set.&lt;br /&gt;
&lt;br /&gt;
==== Example JSON request for a Merchant Initiated Payment scenario ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-7&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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;InitiateRecurrence&amp;quot;: true,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;MerchantInitiatedPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 25.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Subscription fee for the first month&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Website subscription&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Website subscription for one month&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&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;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The response will be the same as to a [[Responsive_web_payment#Processing_the_successful_response|basic &#039;&#039;&#039;Immediate&#039;&#039;&#039; scenario]]. The &amp;lt;code&amp;gt;RecurrenceResult&amp;lt;/code&amp;gt; property at this point is &#039;&#039;&#039;None&#039;&#039;&#039; since the token is not registered to a funding source yet.&lt;br /&gt;
&lt;br /&gt;
==== Example JSON request for a Recurring Payment scenario ====&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Recurring Payment&#039;&#039;&#039; scenario has some extra restrictions. The merchant has to specify two additional properties in the [[Payment-Start-v2|Payment/Start]] request:&lt;br /&gt;
* &amp;lt;code&amp;gt;RecurringExpiry&amp;lt;/code&amp;gt;: The date after subsequent charges should not be accepted.&lt;br /&gt;
* &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt;: The minimum days the merchant has to wait between payments.&lt;br /&gt;
&lt;br /&gt;
Both properties are located in the [[PurchaseInformation]] property and must be specified if this scenario is selected.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-7, 30-33&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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;InitiateRecurrence&amp;quot;: true,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;RecurringPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 25.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Subscription fee for the first month&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Website subscription&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Website subscription for one month&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&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;
        }&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;PurchaseInformation&amp;quot;:{&lt;br /&gt;
        &amp;quot;RecurringFrequency&amp;quot;: 10,&lt;br /&gt;
        &amp;quot;RecurringExpiry&amp;quot;: &amp;quot;2022-10-01&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Possible error responses ====&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| 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;
=== 1.2 Redirecting the customer to the Barion Smart Gateway to select a funding source ===&lt;br /&gt;
&lt;br /&gt;
After a successful payment preparation, the customer is redirected to the secure Barion Smart Gateway to choose a funding source. The funding source the customer selects will be registered to the token. The funding source can either be a Barion e-money balance or a bank card. This means that even though the customer may own multiple cards only the one that was registered to the token can be used for future token payments. To change the funding source attached to the token a new registration should be requested.&lt;br /&gt;
&lt;br /&gt;
=== 1.3 Processing the callback and requesting information about the result of the payment ===&lt;br /&gt;
&lt;br /&gt;
When the payment is completed (either successfully or unsuccessfully) a callback message is sent to the merchant&#039;s system. Once received a [[Payment-GetPaymentState-v2|GetPaymentState]] request must be sent to the Barion API. On how to implement this please read the article about the  [[Callback_mechanism|Callback mechanism]].&lt;br /&gt;
&lt;br /&gt;
The full response of the GetPaymentState request depends on the payment scenario and the structure of the payment. When it comes to token payment there are several properties to look out for. &lt;br /&gt;
* In case the &amp;lt;code&amp;gt;Status&amp;lt;/code&amp;gt; is &#039;&#039;&#039;Succeeded&#039;&#039;&#039; the funding source token is registered and ready to use.&lt;br /&gt;
* The &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; contains the ID of the token process. This specifies the nature of the token payment. &lt;br /&gt;
&lt;br /&gt;
==== TraceId ====&lt;br /&gt;
&lt;br /&gt;
In case of Recurring payment or Merchant initiated payment scenarios the [[Payment-GetPaymentState-v2|GetPaymentState]] response returns an additional field called &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;. The value of this property is generated by the card issuer and is up to a 100 characters, and should be left intact (whitespaces and 0s can&#039;t be trimmed). The merchant has to save it and submit it in all subsequent Recurring or Merchant initiated payments of the same type, otherwise, the payments can be declined by the issuer. The &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; represents the first, customer-present payment and helps the issuer to connect subsequent payments to this initial payment.&lt;br /&gt;
&lt;br /&gt;
====Example GetPaymentState response====&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;8, 11-12&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;2a9f3260bc2feb118bc3001dd8b71cc4&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-001&amp;quot;,&lt;br /&gt;
    &amp;quot;OrderNumber&amp;quot;: null,&lt;br /&gt;
    &amp;quot;POSId&amp;quot;: &amp;quot;[[SHOPS_PUBLIC_KEY]]&amp;quot;,&lt;br /&gt;
    &amp;quot;POSName&amp;quot;: &amp;quot;[[MERCHANTS_BARION_SHOPNAME]]&amp;quot;,&lt;br /&gt;
    &amp;quot;POSOwnerEmail&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentType&amp;quot;: &amp;quot;Immediate&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSource&amp;quot;: &amp;quot;BankCard&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;MerchantInitiatedPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;FGTRR55322843442124780&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingInformation&amp;quot;: {&lt;br /&gt;
        &amp;quot;BankCard&amp;quot;: {&lt;br /&gt;
            &amp;quot;MaskedPan&amp;quot;: &amp;quot;0425&amp;quot;,&lt;br /&gt;
            &amp;quot;BankCardType&amp;quot;: &amp;quot;Visa&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruYear&amp;quot;: &amp;quot;2020&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruMonth&amp;quot;: &amp;quot;12&amp;quot;&lt;br /&gt;
        },&lt;br /&gt;
        &amp;quot;AuthorizationCode&amp;quot;: &amp;quot;512244&amp;quot;,&lt;br /&gt;
        &amp;quot;ProcessResult&amp;quot;: &amp;quot;Successful&amp;quot;&lt;br /&gt;
    },&lt;br /&gt;
    &amp;quot;AllowedFundingSources&amp;quot;: [&lt;br /&gt;
        &amp;quot;All&amp;quot;&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;GuestCheckout&amp;quot;: true,&lt;br /&gt;
    &amp;quot;CreatedAt&amp;quot;: &amp;quot;2020-11-26T07:52:48.9Z&amp;quot;,&lt;br /&gt;
    &amp;quot;ValidUntil&amp;quot;: &amp;quot;2020-11-26T08:22:48.9Z&amp;quot;,&lt;br /&gt;
    &amp;quot;CompletedAt&amp;quot;: &amp;quot;2020-11-26T08:11:54.118Z&amp;quot;,&lt;br /&gt;
    &amp;quot;ReservedUntil&amp;quot;: null,&lt;br /&gt;
    &amp;quot;DelayedCaptureUntil&amp;quot;: null,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
           ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;Total&amp;quot;: 25.20,&lt;br /&gt;
    &amp;quot;SuggestedLocale&amp;quot;: &amp;quot;hu-HU&amp;quot;,&lt;br /&gt;
    &amp;quot;FraudRiskScore&amp;quot;: null,&lt;br /&gt;
    &amp;quot;RedirectUrl&amp;quot;: &amp;quot;https://merchanturl/Redirect?paymentId=2a9f3260bc2feb118bc3001dd8b71cc4&amp;quot;,&lt;br /&gt;
    &amp;quot;CallbackUrl&amp;quot;: &amp;quot;https://merchanturl/Callback?paymentId=2a9f3260bc2feb118bc3001dd8b71cc4&amp;quot;,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&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;
==== Displaying the funding source in a GUI ====&lt;br /&gt;
We strongly advise saving the complete response for future reference. The &amp;lt;code&amp;gt;FundingSource&amp;lt;/code&amp;gt; field tells if the funding source is a Barion balance or a card. If it is a card, it is useful to save [[FundingInformation]] for displaying it for the user, when requesting future payments. The usual way to display funding sources is to show the last 4 digits of the card, with 4 stars, eg: *** 1234. The card used can be obtained from FundingInformation&#039;s [[BankCard]] field. The [[CardType]] field can be used to display the appropriate card logo. You can even show, if the card is expired, and offer to register another one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; FundingInformation part of the GetPaymentState response &#039;&#039;&#039;&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
    &amp;quot;FundingInformation&amp;quot;: {&lt;br /&gt;
        &amp;quot;BankCard&amp;quot;: {&lt;br /&gt;
            &amp;quot;MaskedPan&amp;quot;: &amp;quot;0425&amp;quot;,&lt;br /&gt;
            &amp;quot;BankCardType&amp;quot;: &amp;quot;Visa&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruYear&amp;quot;: &amp;quot;2020&amp;quot;,&lt;br /&gt;
            &amp;quot;ValidThruMonth&amp;quot;: &amp;quot;12&amp;quot;&lt;br /&gt;
        },&lt;br /&gt;
        &amp;quot;AuthorizationCode&amp;quot;: &amp;quot;512244&amp;quot;,&lt;br /&gt;
        &amp;quot;ProcessResult&amp;quot;: &amp;quot;Successful&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This can be displayed for example as &amp;lt;code&amp;gt;VISA **** 0425 (12/20)&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is a request-response diagram of the token registration process:&lt;br /&gt;
 &lt;br /&gt;
[[File:Token_payment_initiation.jpg]]&lt;br /&gt;
&lt;br /&gt;
= Step 2: Using the token =&lt;br /&gt;
&lt;br /&gt;
To use an already registered token for a payment, you have to use the same [[Payment-Start-v2|/Payment/Start]] API endpoint but the &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; should be set to &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;. This tells the Barion API to use the token for payment instead of only registering it. The token should be specified in the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; property. To be able to use a token, the initial payment must be in a successful state.&lt;br /&gt;
&lt;br /&gt;
At this point, the merchant has to decide whether this subsequent payment is used for the same token payment scenario or something changed. This is important because the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; can only be used for the same scenario, otherwise, the card issuer will decline the charge.&lt;br /&gt;
A &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; can only be used again if:&lt;br /&gt;
* the funding source is the same (technically the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; is the same)&lt;br /&gt;
* the token payment scenario is the same (technically the &amp;lt;code&amp;gt;RecurrenceType&amp;lt;/code&amp;gt; is the same)&lt;br /&gt;
* this subsequent request complies with the scenario restrictions (eg: in case of recurring payment the amount of the subsequent payment does not exceed the initial amount)&lt;br /&gt;
&lt;br /&gt;
If the funding source changes, new &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; must be requested. The process to do that is [[#Changing the funding source|described in detail here]]. If the funding source stays the same but the scenario changes or the restrictions are no longer met new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; must be requested. The process to do that is [[#Changing the token payment scenario with an existing token|described here]].&lt;br /&gt;
&lt;br /&gt;
== Subsequent payments in case of Recurring payment scenario ==&lt;br /&gt;
&lt;br /&gt;
In this case, three extra conditions must be met:&lt;br /&gt;
* the amount of the subsequent payment must not be higher than the initial amount&lt;br /&gt;
* at least that much days must be spent as defined in the initial &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt; property&lt;br /&gt;
* the date of the payment must not exceed the day specified in the initial &amp;lt;code&amp;gt;RecurringExpiry&amp;lt;/code&amp;gt; property&lt;br /&gt;
&lt;br /&gt;
Please be aware that in case any of these are no longer valid the merchant has to request a new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; as [[#Changing the token payment scenario with an existing token|described here]]. &lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=These conditions are not enforced by the Barion system so the violation of them will result in a declined charge.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
Payment/start must not include the &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;RecurringExpiry&amp;lt;/code&amp;gt; properties (since they are already fixed during the initial payment).&lt;br /&gt;
&lt;br /&gt;
==== Example payment/start of a subsequent Recurring payment ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-8&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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-002&amp;quot;,&lt;br /&gt;
    &amp;quot;InitiateRecurrence&amp;quot;: false,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;RecurringPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;FGTRR55322843442124780&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 25.2,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Subscription fee for the second month&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Website subscription&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Website subscription for one month&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&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-02&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Example response to this request ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;4,8,11&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;fb582913dc2feb11a49f309c23734b1c&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;Successful&amp;quot;,&lt;br /&gt;
    &amp;quot;ThreeDSAuthClientData&amp;quot;: null,&lt;br /&gt;
     ...&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;FGTRR55322843442124780&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;
The structure of the response is the same as the normal &amp;lt;tt&amp;gt;/Payment/Start&amp;lt;/tt&amp;gt; response just the statuses will be different. In this case&lt;br /&gt;
* the payment level &amp;lt;code&amp;gt;Status&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Succeeded&#039;&#039;&#039; instead of &#039;&#039;&#039;Prepared&#039;&#039;&#039;&lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceResult&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Successful&#039;&#039;&#039; (or &#039;&#039;&#039;Failed&#039;&#039;&#039;) instead of &#039;&#039;&#039;None&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The value of the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; will be the same as in the request.&lt;br /&gt;
&lt;br /&gt;
== Subsequent payments in case of Merchant Initiated Payment scenario ==&lt;br /&gt;
&lt;br /&gt;
In this scenario there are no restrictions.&lt;br /&gt;
&lt;br /&gt;
==== Example payment/start of a subsequent Merchant Initiated Payment ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-8&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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-002&amp;quot;,&lt;br /&gt;
    &amp;quot;InitiateRecurrence&amp;quot;: false,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;MerchantInitiatedPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;KBYRR55322844552124780&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 75,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Usage fee for 2020/12&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;Phone bill&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Usage fee for 2020/12&amp;quot;,&lt;br /&gt;
                    &amp;quot;Quantity&amp;quot;: 1,&lt;br /&gt;
                    &amp;quot;Unit&amp;quot;: &amp;quot;month&amp;quot;,&lt;br /&gt;
                    &amp;quot;UnitPrice&amp;quot;: 75,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 75,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-02&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Example response to this request ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;4,8,11&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;fb582913dc2feb11a49f309c23734b1c&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;Successful&amp;quot;,&lt;br /&gt;
    &amp;quot;ThreeDSAuthClientData&amp;quot;: null,&lt;br /&gt;
     ...&lt;br /&gt;
    &amp;quot;TraceId&amp;quot;: &amp;quot;KBYRR55322844552124780&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;
The structure of the response is the same as the normal &amp;lt;tt&amp;gt;/Payment/Start&amp;lt;/tt&amp;gt; response just the statuses will be different. In this case&lt;br /&gt;
* the payment level &amp;lt;code&amp;gt;Status&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Succeeded&#039;&#039;&#039; instead of &#039;&#039;&#039;Prepared&#039;&#039;&#039;&lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceResult&amp;lt;/code&amp;gt; will be &#039;&#039;&#039;Successful&#039;&#039;&#039; (or &#039;&#039;&#039;Failed&#039;&#039;&#039;) instead of &#039;&#039;&#039;None&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The value of the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; will be the same as in the request.&lt;br /&gt;
&lt;br /&gt;
== Subsequent payments in case of OneClick Payment scenario ==&lt;br /&gt;
&lt;br /&gt;
In this scenario, the merchant has to prepare to perform the [[#Off-site 3DS v2 authentication|off-site 3DS v2 authentication]] of the payer. 3DS authentication is not required in the following cases:&lt;br /&gt;
* the token (&amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt;) was requested before 3DS came into effect,&lt;br /&gt;
* the original payment was not initialized by bank card,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is not used in this scenario since the payer is present during the transaction. &lt;br /&gt;
&lt;br /&gt;
==== Example payment/start of a subsequent OneClick Payment ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;5-7&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;POSKey&amp;quot;: &amp;quot;[[SECRET_POS_KEY]]&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-002&amp;quot;,&lt;br /&gt;
    &amp;quot;InitiateRecurrence&amp;quot;: false,&lt;br /&gt;
    &amp;quot;RecurrenceId&amp;quot;: &amp;quot;SHOP-XMLP-TOKEN-ABC-123&amp;quot;,&lt;br /&gt;
    &amp;quot;RecurrenceType&amp;quot;: &amp;quot;OneClickPayment&amp;quot;,&lt;br /&gt;
    &amp;quot;FundingSources&amp;quot;: [&amp;quot;All&amp;quot;],&lt;br /&gt;
    &amp;quot;GuestCheckOut&amp;quot; : true,&lt;br /&gt;
    &amp;quot;Currency&amp;quot;: &amp;quot;EUR&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        {&lt;br /&gt;
            &amp;quot;POSTransactionId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002/TR001&amp;quot;,&lt;br /&gt;
            &amp;quot;Payee&amp;quot;: &amp;quot;[[MERCHANTS_BARION_EMAIL]]&amp;quot;,&lt;br /&gt;
            &amp;quot;Total&amp;quot;: 17,&lt;br /&gt;
            &amp;quot;Comment&amp;quot;: &amp;quot;Book: How to shop online&amp;quot;,&lt;br /&gt;
            &amp;quot;Items&amp;quot;: [&lt;br /&gt;
                {&lt;br /&gt;
                    &amp;quot;Name&amp;quot;: &amp;quot;How to shop online&amp;quot;,&lt;br /&gt;
                    &amp;quot;Description&amp;quot;: &amp;quot;Book about shopping online&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;: 17,&lt;br /&gt;
                    &amp;quot;ItemTotal&amp;quot;: 17,&lt;br /&gt;
                    &amp;quot;SKU&amp;quot;: &amp;quot;EXMPLSHOP/SKU/PHC-02&amp;quot;&lt;br /&gt;
                }&lt;br /&gt;
            ]&lt;br /&gt;
        }&lt;br /&gt;
    ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Example response to this request ====&lt;br /&gt;
&lt;br /&gt;
In this scenario, the response contains the &amp;lt;code&amp;gt;ThreeDSAuthClientData&amp;lt;/code&amp;gt; property that is used to perform an [[#Off-site 3DS v2 authentication|off-site 3DS v2 authentication]].&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json line highlight=&amp;quot;4,8-9&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
    &amp;quot;PaymentId&amp;quot;: &amp;quot;fb582913dc2feb11a49f309c23734b1c&amp;quot;,&lt;br /&gt;
    &amp;quot;PaymentRequestId&amp;quot;: &amp;quot;EXMPLSHOP-PM-002&amp;quot;,&lt;br /&gt;
    &amp;quot;Status&amp;quot;: &amp;quot;Succeeded&amp;quot;,&lt;br /&gt;
    &amp;quot;Transactions&amp;quot;: [&lt;br /&gt;
        ...&lt;br /&gt;
    ],&lt;br /&gt;
    &amp;quot;RecurrenceResult&amp;quot;: &amp;quot;Successful&amp;quot;,&lt;br /&gt;
    &amp;quot;ThreeDSAuthClientData&amp;quot;: &amp;quot;ewoJIkNhcmRQdWJs...WZXJzaW9uIjogIjIuMS4wIgp9Cg==&amp;quot;,&lt;br /&gt;
     ...&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;
== 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. The payment s 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 use 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 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 not fully activated.&lt;br /&gt;
|-&lt;br /&gt;
|UserCantMakeOutgoingTransaction || The payee specified in the transaction is not allowed to make payeetransactions 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;
This is the request-response diagram of the subsequent payments:&lt;br /&gt;
&lt;br /&gt;
[[File:Token_payment_2.png]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; when requesting Transaction Risk Analysis (TRA) during a subsequent payment, and all conditions have been met, challenge is not shown to the user.&lt;br /&gt;
&lt;br /&gt;
== RecurrenceResult: ThreeDSAuthenticationRequired ==&lt;br /&gt;
&lt;br /&gt;
In response to a subsequent payment, this RecurrenceResult can be received. This means that the payment can not be processed due to the lack of 3DS v2 information. &lt;br /&gt;
&lt;br /&gt;
This can happen if the initial payment was successfully authenticated via 3DS v2 but the subsequent payment does not refer to the original authentication with the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
To fix this, request and store the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; of the initial payment and then specify it in the subsequent [[Payment-Start-v2]].&lt;br /&gt;
&lt;br /&gt;
To learn the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; of a previous payment just simply request the payment information via the [[Payment-GetPaymentState-v2]] endpoint.&lt;br /&gt;
&lt;br /&gt;
= Changing funding source or token scenarios =&lt;br /&gt;
&lt;br /&gt;
==Changing the funding source==&lt;br /&gt;
&lt;br /&gt;
This could happen if the funding source becomes invalid for some reason (card gets deleted or expires) or the merchant decides to use that token for another payer. In this case, the merchant has to register the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; again. &lt;br /&gt;
To do this a new payment must be started and in the [[Payment-Start-v2|Payment/Start]] request the following setup should be specified:&lt;br /&gt;
* the &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; field has to be set to &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; &lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; has to be specified.&lt;br /&gt;
* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; should not be specified.&lt;br /&gt;
&lt;br /&gt;
[[File:Funding-source-change.png|1500px]]&lt;br /&gt;
&lt;br /&gt;
Since the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; is bound to the payer and the process if the funding source changes new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; will be generated. This new ID must be saved to this payment and must be used from this moment on for subsequent payments.&lt;br /&gt;
&lt;br /&gt;
==Changing the token payment scenario with an existing token==&lt;br /&gt;
&lt;br /&gt;
This could occur when the merchant wants to get authorization from the payer to a new token scenario for the already registered funding source. To be able to do this the merchant has to have a valid and registered &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt;.&lt;br /&gt;
Let&#039;s see some examples when this may be necessary:&lt;br /&gt;
* The payer subscribed to the merchant&#039;s service beforehand and the merchant decided to use the recurring payment token scenario. The payer wants to subscribe to another service and this requires a different payment schedule. This means that the &amp;lt;code&amp;gt;RecurringFrequency&amp;lt;/code&amp;gt; that was specified initially can not be maintained so it is required to acquire a new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;&lt;br /&gt;
* The payer bought something on the merchant&#039;s website and uses the one-click feature for subsequent fast non-redirect payments. After a while, the payer decides to subscribe to a service provided by this same merchant. This means that the merchant has to create a new token scenario (not a one-click payment but a recurring payment). For this, the merchant has to acquire a new &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt;. This can be done without redirecting the payer to Barion using the existing &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; and performing a 3DS authentication on the merchant&#039;s website.&lt;br /&gt;
&lt;br /&gt;
To do these a new payment must be started and in the [[Payment-Start-v2|Payment/Start]] request the following setup should be specified:&lt;br /&gt;
* the &amp;lt;code&amp;gt;InitiateRecurrence&amp;lt;/code&amp;gt; field has to be set to &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; &lt;br /&gt;
* the &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt; has to be specified.&lt;br /&gt;
* and the &amp;lt;code&amp;gt;TraceId&amp;lt;/code&amp;gt; should not be specified.&lt;br /&gt;
&lt;br /&gt;
After this, a 3DS authentication has to be completed to acquire a new trace ID. This can be done on the merchant&#039;s site if the merchant implements the barion.offsitegw.js for off-site 3DS authentication.&lt;br /&gt;
&lt;br /&gt;
This means that it can be achieved to acquire different Trace IDs for different scenarios with only one &amp;lt;code&amp;gt;RecurrenceId&amp;lt;/code&amp;gt;.&lt;br /&gt;
This is basically categorizing the different token scenarios as opposed to using every subsequent payment as an unmarked charge.&lt;br /&gt;
&lt;br /&gt;
[[File:Mutiple-traceid.png|1500px]]&lt;br /&gt;
&lt;br /&gt;
= Off-site 3DS v2 authentication =&lt;br /&gt;
&lt;br /&gt;
In certain scenarios, the payer has to be authenticated to lower the risk of the card transaction. This can be either performed &lt;br /&gt;
* on the Barion Smart Gateway (on-site) by redirecting the customer to Barion &lt;br /&gt;
* or on the merchant&#039;s website (off-site) by integrating the Barion Off-site client library.&lt;br /&gt;
&lt;br /&gt;
This section describes how to integrate the Barion off-site authentication library into the merchant&#039;s site.&lt;br /&gt;
&lt;br /&gt;
== Step 1 : Initialize the off-site authentication library  ==&lt;br /&gt;
You have to include the following css and javascript files in the code of your site. &lt;br /&gt;
&amp;lt;source lang=html&amp;gt;&lt;br /&gt;
&amp;lt;link href=&amp;quot;https://secure.barion.com/static/barion.offsitegw.min.css&amp;quot; rel=&amp;quot;stylesheet&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;script src=&amp;quot;https://secure.barion.com/static/barion.offsitegw.min.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;br /&gt;
&amp;lt;/source &amp;gt;&lt;br /&gt;
These files include all the necessary javascript code and styling to handle the 3DS authentication and display the challenge if necessary.&lt;br /&gt;
&lt;br /&gt;
Then you have to initialize the Barion javascript client. To do that, you have to define a configuration object that specifies your functions that handle the off-site authentication events. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Authentication events&#039;&#039;&#039;&lt;br /&gt;
* &amp;lt;code&amp;gt;onAuthenticationSucceeded&amp;lt;/code&amp;gt;: the 3DS v2 authentication successfully completed&lt;br /&gt;
* &amp;lt;code&amp;gt;onAuthenticationFailed&amp;lt;/code&amp;gt;:  the 3DS v2 authentication failed&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
const configuration = {&lt;br /&gt;
    onAuthenticationSucceeded: function () {&lt;br /&gt;
        // handle successful authentication by calling the Barion API via merchant&#039;s backend&lt;br /&gt;
        // Call the v2/payment/complete endpoint&lt;br /&gt;
    },&lt;br /&gt;
    onAuthenticationFailed: function () {&lt;br /&gt;
        // Handle unsuccessful authentication result, no charge was made.&lt;br /&gt;
        // The payment might be still valid only the authentication failed&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then you have to pass this config object to the library.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
const gw = new Barion.OffsiteGw(configuration);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Once the DOM is loaded you have to initialize the library:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
document.addEventListener(&amp;quot;DOMContentLoaded&amp;quot;, function () {&lt;br /&gt;
    // Initiate the Barion Offiste GW library&lt;br /&gt;
    gw.init();&lt;br /&gt;
});&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Step 2: Start the authentication process ==&lt;br /&gt;
Once the &amp;lt;code&amp;gt;ThreeDSAuthClientData&amp;lt;/code&amp;gt; is acquired from the payment/start you can start the authentication process by calling the &amp;lt;code&amp;gt;authenticate()&amp;lt;/code&amp;gt; method of the library.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=javascript&amp;gt;&lt;br /&gt;
gw.authenticate(threeDsClientData);&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will start the authentication process and present the challenge if needed. Visually this will create a modal window over the merchant&#039;s site and show the payer every necessary information.&lt;br /&gt;
Once the authentication process finished (either with or without a challenge) the appropriate event will be fired.&lt;br /&gt;
&lt;br /&gt;
== Step 3: Completing the payment ==&lt;br /&gt;
&lt;br /&gt;
In case of successful authentication, you have to call our [[Payment-Complete-v3|/Payment/Complete]] endpoint, where the actual charge will happen.&lt;br /&gt;
&lt;br /&gt;
=== Possible error responses for the subsequent payment requests ===&lt;br /&gt;
TODO&lt;br /&gt;
&lt;br /&gt;
== Suggested implementation flow for off-site authentication ==&lt;br /&gt;
&lt;br /&gt;
Ideally, an off-site authentication should be part of a client-side experience without any postbacks or page reloads. This is our recommendation to achieve this:&lt;br /&gt;
&lt;br /&gt;
# After the customer clicks on the &amp;quot;Pay&amp;quot; button make an AJAX call from your client-side code to your back-end. &lt;br /&gt;
# Have your backend make a request to our payment/start endpoint (with the appropriate settings for the desired token scenario)&lt;br /&gt;
# Have your backend process the response and pass the value of the &amp;lt;code&amp;gt;ThreeDSAuthClientData&amp;lt;/code&amp;gt; property to your client-side code.&lt;br /&gt;
# Use the Barion off-site library to perform the authentication&lt;br /&gt;
# Once the authentication succeeds send another AJAX request from your client-side code to your back-end.&lt;br /&gt;
# Have your back-end code call our [[Payment-Complete-v3|/Payment/Complete]]&lt;br /&gt;
# Have your backend process the response and pass the result to your client-side code.&lt;br /&gt;
# Display the result for the customer&lt;br /&gt;
&lt;br /&gt;
= Testing the integration =&lt;br /&gt;
&lt;br /&gt;
3D Secure has no environment for end-to-end testing, therefore merchants have to split their testings into two parts: Testing the payment flow with and without challenge. Getting a challenge is only possible with real-life cards, merchants have to use their own (there will be no real charging at the end on the Sandbox of the Payment Gateway, but using a real card will result initiating a real 3DS authentication).&lt;br /&gt;
&lt;br /&gt;
== Testing the whole payment flow, without challenge ==&lt;br /&gt;
&lt;br /&gt;
Use the [[https://docs.barion.com/Sandbox#Test_cards Barion test cards]], they will always get a &amp;quot;frictionless&amp;quot; flow, where the 3DS process is presented on the UI, but you will never see a challenge screen. &lt;br /&gt;
&lt;br /&gt;
This is good for testing your integration itself because it will lead to a successful charge, and you will get a TraceId as well.&lt;br /&gt;
&lt;br /&gt;
== Testing the challenge itself ==&lt;br /&gt;
&lt;br /&gt;
Use your own card, and let the card issuer decide whether your payment will get a challenge or not during the 3DS authentication procedure. Your payment will fail at the end, and you won&#039;t get the TraceId. &lt;br /&gt;
&lt;br /&gt;
This is good to test, how the challenge screens look like in your shop - especially when you integrated OneClick payment directly to your shop. You might also check how your customers see your checkout flow on popular devices.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Error_codes_notifications&amp;diff=4016</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=4016"/>
		<updated>2023-05-11T09:11:05Z</updated>

		<summary type="html">&lt;p&gt;Bozag: Created page with &amp;quot;{{PageTitle|title= Barion error codes and notifications}}  This page serves as a repository for the Barion error codes and notifications you can encounter when using or integr...&amp;quot;&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;
== [[PartnerCard_Prepare_v2|Preparing]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| CardPreparationNotAllowed || If the card number is already registered (attached to a wallet) a new preparation is not allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Activate_v2|Activate]] a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Payment_PayWithPartnerCard_v2|Paying]] with a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_ChangePin_v2|Change PIN]] on a partner card ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| NewPinEqualsToCurrent || The new PIN code equals to current one.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardPin || The current PIN is incorrect, did not match the stored version.&lt;br /&gt;
|-&lt;br /&gt;
| PinChangeFailed || A fatal system error occured during the process.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[PartnerCard_Issue_v2|Issue a partner card]] ==&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! Error code || Description&lt;br /&gt;
|-&lt;br /&gt;
| AuthenticationFailed || The user name and password of the card owner was incorrect.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardKey|| The card key provided either doesn&#039;t belong to a card or the card is already issued.&lt;br /&gt;
|-&lt;br /&gt;
| InvalidCardOwner || The owner specified is not a registered Barion user or the user is not available for card registration.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== [[Topup-StornoPartnerCardTopup-v2|Reverse]] partner card top-up ==&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;
| NotExistingTransactionId || The given topup transaction was not found in the database&lt;br /&gt;
|-&lt;br /&gt;
| SourceAccountNotAllowedForPartner || The originally specified source Barion wallet was not connected to the trusted partner&lt;br /&gt;
|-&lt;br /&gt;
| StornoTopupFailed || The topup process could not be completed due to an unknown error (contact the developer support)&lt;br /&gt;
|-&lt;br /&gt;
| MultipleStornoNotAllowed || The storno stransaction is illegeal because the original topup was already rolled back. &lt;br /&gt;
|-&lt;br /&gt;
|}&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;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=4015</id>
		<title>3DS FAQ</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=4015"/>
		<updated>2023-05-11T08:24:18Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=3DSecure FAQ}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
Here, you can find the frequently asked questions related to the Barion 3D Secure solution. The content of this page is updated if any issues surface or clarifications are needed.&lt;br /&gt;
&lt;br /&gt;
If you have any questions related to 3D Secure not covered in this FAQ, reach out to us at [mailto:devsupport@barion.com devsupport@barion.com], where we can provide more in-depth, case-specific answers, depending on the issue you encountered.&lt;br /&gt;
&lt;br /&gt;
== Upon starting the payments which properties are required? ==&lt;br /&gt;
We highly recommend using the properties marked with {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request. There is no &#039;&#039;Read: error&#039;&#039; thrown when sent without these properties. The content of these fields is 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.&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 are 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 (for example, 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=4014</id>
		<title>3DS FAQ</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DS_FAQ&amp;diff=4014"/>
		<updated>2023-05-11T08:24:01Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=3DSecure}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
Here, you can find the frequently asked questions related to the Barion 3D Secure solution. The content of this page is updated if any issues surface or clarifications are needed.&lt;br /&gt;
&lt;br /&gt;
If you have any questions related to 3D Secure not covered in this FAQ, reach out to us at [mailto:devsupport@barion.com devsupport@barion.com], where we can provide more in-depth, case-specific answers, depending on the issue you encountered.&lt;br /&gt;
&lt;br /&gt;
== Upon starting the payments which properties are required? ==&lt;br /&gt;
We highly recommend using the properties marked with {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request. There is no &#039;&#039;Read: error&#039;&#039; thrown when sent without these properties. The content of these fields is 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.&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 are 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 (for example, 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DSecure&amp;diff=4013</id>
		<title>3DSecure</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DSecure&amp;diff=4013"/>
		<updated>2023-05-11T08:07:52Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=3DSecure}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3D Secure ([https://en.wikipedia.org/wiki/3-D_Secure|3DS, Three-Domain Secure]) is a messaging protocol developed by [https://www.emvco.com EMVCo] that provides a more secure online card payment process. It enables consumers to authenticate themselves with their card issuer when making card-not-present (CNP) e-commerce purchases. &lt;br /&gt;
If the card is enrolled into 3DS authentication, additional information is required to decide whether the purchase is fraudulent or not. This decision is made by the card issuer (the bank or other institution that issued the card), not by the Barion system. &lt;br /&gt;
&lt;br /&gt;
There are two major versions of the protocol: &lt;br /&gt;
* &#039;&#039;&#039;3D Secure 1&#039;&#039;&#039; is an HTTP redirect-based scenario where the customer almost always needs to provide some extra proof for the transaction. The verification is usually a password or SMS code. Card schemes decommissioned 3D Secure 1 in 2021/2022. Barion does not support this old protocol.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;3D Secure 2&#039;&#039;&#039; is more sophisticated and uses additional information about the purchase, the shop, and the cardholder to make the decision. This requires more input data but provides better flow with less friction. The card issuer may verify the shopper&#039;s identity using passive, biometric, and two-factor authentication approaches. According to the [https://en.wikipedia.org/wiki/Strong_customer_authentication Strong Customer Authentication (SCA) rules of PSD2 RTS] every card issued in the EU has to be authenticated. 3D Secure 2 complies with the regulation.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=If the shopper completes a 3DSecure authentication successfully, the liability shifts from the merchant to the card issuer in case of fraud.|color=#FF7A3D}}&lt;br /&gt;
==Liability shift rules==&lt;br /&gt;
If a merchant implements 3D Secure authentication, they can avoid liability for chargebacks in case of fraud (that is, chargeback claims because of lost or stolen cards). This is called a liability shift.&lt;br /&gt;
In general, if a shopper completes a 3D Secure challenge authentication flow successfully, the liability for fraudulent chargebacks shifts from the merchant to the card issuer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Transaction type&lt;br /&gt;
!Liability shift to card issuer?&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions with challenge.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;card issuer applies a PSD2 exemption&#039;&#039;&#039; without the merchant requesting it. For example, issuer TRA.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 PSD2 SCA out-of-scope transactions: shopper&#039;s issuer is outside of the EEA, anonymous prepaid cards up to 150€ or merchant-initiated transactions.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;merchant or acquirer requests for a PSD2 exemption&#039;&#039;&#039; and the issuer grants an exemption.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==The payment process==&lt;br /&gt;
&lt;br /&gt;
The payment follows these steps:&lt;br /&gt;
# You check out your purchase from the merchant&#039;s website and select to pay via Barion.&lt;br /&gt;
# You are redirected to the Barion Smart Gateway.&lt;br /&gt;
# You input your card details and click &#039;&#039;&#039;Pay&#039;&#039;&#039;. &amp;lt;br/&amp;gt;--- Until this point, there is no difference in the workflow ---&lt;br /&gt;
# Barion checks whether the card you used is a 3DSecure capable card and also the version the issuer supports. If the card is not &#039;&#039;&#039;3DSecure capable&#039;&#039;&#039;, the card authorization (charge) goes along without any extra steps. &lt;br /&gt;
# If the card is 3D Secure capable with 3DSecure 2, the flow changes:&lt;br /&gt;
#*# Barion starts the 3DS authentication in the background and sends the relevant information about the purchase to the card issuer. From this information, the issuer decides whether the payment is secure or if you should be challenged in some form.&lt;br /&gt;
#*# If the result is that you &#039;&#039;&#039;should not be challenged&#039;&#039;&#039; (this is the frictionless flow) your card is charged and the payment flow continues.&lt;br /&gt;
#*# If the result is that the issuer &#039;&#039;&#039;needs more proof&#039;&#039;&#039; from you, a popup window is displayed. In this window, the issuer displays &#039;&#039;something&#039;&#039; for you. The content varies according to the issuer, and it allows you to provide proof (SMS, token, question).&lt;br /&gt;
#*# After you successfully complete the challenge, the card is authenticated and the payment flow continues with the authorization of the card. The card can still be declined after successful 3DS authentication.&lt;br /&gt;
# At the end of the payment you are redirected to the merchant&#039;s website.&lt;br /&gt;
&lt;br /&gt;
== 3D Secure 2 ==&lt;br /&gt;
&lt;br /&gt;
The reason behind the second version was to provide a way to achieve the same level of security for authentication but with less friction. For this, a lot more information is required (or at least it is strongly recommended to provide them). This information comes from different sources:&lt;br /&gt;
* merchant&#039;s data about the customer (purchase behavior, addresses, and so on)&lt;br /&gt;
* customer&#039;s browser information (screen size, timezone, language, and so on)&lt;br /&gt;
* customer provided data (card information, e-mail address) &lt;br /&gt;
* Barion&#039;s data about the merchant, the purchase, and the customer (merchant&#039;s MCC code, name of the shop, and so on)&lt;br /&gt;
&lt;br /&gt;
The card issuer receives this information package and calculates the risk of the transaction. The result of this calculation specifies the flow:&lt;br /&gt;
* Frictionless flow: The customer is not presented with any challenge screen, no more information is needed, and authorization can take place.&lt;br /&gt;
* Challenge flow: The information is not sufficient, an additional challenge is needed to make sure that the card is not stolen.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
To achieve the frictionless flow the merchant has to provide as much information as possible about the purchase and the customer. This must be provided during the [[Payment-Start-v2-3DS|v2/payment/start]] API call. The properties marked as {{3dsfield}} must be specified. However, there are scenarios where not all of this data is available. In these cases, there are ways to indicate the lack of information. If the merchant does not provide the necessary data, the payment typically falls into the challenge flow. Ideally, we should avoid this as it causes friction and may result in the customer leaving the payment.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Although providing this data enhances the possibility of frictionless flow, it does not make it certain. This decision is up to the card issuer, Barion does not influence it. In case of challenge flow the card issuer provides a challenge screen that the customer must complete. This can be various things: one-time passwords sent via text, secret passwords, biometric identification, and so on.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
* If the shopper has no phone number registered, and no sms can be sent, the authentication fails.&lt;br /&gt;
* If the user is challenged, additional user interaction is required, which results in increased abandonment. We recommend the following to reduce the churn:&lt;br /&gt;
** Send all available fields marked with the {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request..&lt;br /&gt;
** Request [[ChallengePreference|TRA]] exemption. &amp;lt;br /&amp;gt; &#039;&#039;&#039;Note&#039;&#039;&#039;: If you apply for this option, you are held liable in case of fraud.&lt;br /&gt;
&lt;br /&gt;
== Additional resources ==&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[Token_payment_upgrade_to_3DS|How to upgrade old token payment implementations to comply with 3DS]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=4011</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=4011"/>
		<updated>2023-05-09T11:38:46Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Output 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) that will be displayed on the Barion Smart Gateway. If the intended name is already taken, you must provide a new one.&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;
|| A brief description of the product or service provided by the POS. This is required for shop approval.&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 logo of the POS, which is displayed on the gateway and is required for shop approval. Do not use stock photos downloaded from the internet. The 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;
|| The category or categories to which the POS belongs. 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 details 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 details of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The contact details of your customer service desk, where your customers can contact you.&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;
|| The expected Barion turnover in the primary currency.&lt;br /&gt;
&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;
|| The 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;
| FullPixelImplemented || bool || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| Specifies whether Barion Full Pixel is implemented.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UseForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set to True if the shop is used 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 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 a wallet to distinguish shops arriving through different channels. To obtain the top-up code for a particular Barion wallet, simply visit this link: &amp;lt;code&amp;gt;https://secure.barion.com/Referral&amp;lt;/code&amp;gt;, and log in using your Barion account credentials. The 9-digit number at the end of the link, which appears as the query string parameter, identifies the specific wallet you wish to refer to.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
&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.&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 css 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;
| 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;
| Payee || guid|| The email address of the shop owner.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| GooglePayMerchantId || string || 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;
|-&lt;br /&gt;
&lt;br /&gt;
| PixelId || string || This is referenced when integrating our Barion Pixel.&lt;br /&gt;
&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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=4010</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=4010"/>
		<updated>2023-05-09T11:25:52Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=4009</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=4009"/>
		<updated>2023-05-09T11:25:49Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Output 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) that will be displayed on the Barion Smart Gateway. If the intended name is already taken, you must provide a new one.&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;
|| A brief description of the product or service provided by the POS. This is required for shop approval.&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 logo of the POS, which is displayed on the gateway and is required for shop approval. Do not use stock photos downloaded from the internet. The 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;
|| The category or categories to which the POS belongs. 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 details 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 details of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The contact details of your customer service desk, where your customers can contact you.&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;
|| The expected Barion turnover in the primary currency.&lt;br /&gt;
&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;
|| The 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;
| FullPixelImplemented || bool || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| Specifies whether Barion Full Pixel is implemented.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UseForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set to True if the shop is used 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 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 a wallet to distinguish shops arriving through different channels. To obtain the top-up code for a particular Barion wallet, simply visit this link: &amp;lt;code&amp;gt;https://secure.barion.com/Referral&amp;lt;/code&amp;gt;, and log in using your Barion account credentials. The 9-digit number at the end of the link, which appears as the query string parameter, identifies the specific wallet you wish to refer to.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
&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.&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 css 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;
| 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;
| Payee || guid|| The email address of the shop owner.&lt;br /&gt;
&lt;br /&gt;
| GooglePayMerchantId || string || 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 || string || This is referenced when integrating our Barion Pixel.&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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=4008</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=4008"/>
		<updated>2023-05-09T10:57:23Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Output 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) that will be displayed on the Barion Smart Gateway. If the intended name is already taken, you must provide a new one.&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;
|| A brief description of the product or service provided by the POS. This is required for shop approval.&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 logo of the POS, which is displayed on the gateway and is required for shop approval. Do not use stock photos downloaded from the internet. The 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;
|| The category or categories to which the POS belongs. 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 details 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 details of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The contact details of your customer service desk, where your customers can contact you.&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;
|| The expected Barion turnover in the primary currency.&lt;br /&gt;
&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;
|| The 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;
| FullPixelImplemented || bool || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| Specifies whether Barion Full Pixel is implemented.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UseForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set to True if the shop is used 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 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 a wallet to distinguish shops arriving through different channels. To obtain the top-up code for a particular Barion wallet, simply visit this link: &amp;lt;code&amp;gt;https://secure.barion.com/Referral&amp;lt;/code&amp;gt;, and log in using your Barion account credentials. The 9-digit number at the end of the link, which appears as the query string parameter, identifies the specific wallet you wish to refer to.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
&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.&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 css 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;
| 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopStatus&amp;diff=4007</id>
		<title>ShopStatus</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopStatus&amp;diff=4007"/>
		<updated>2023-05-09T10:49:52Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Property list */&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-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;
| Unspecified&lt;br /&gt;
| string &lt;br /&gt;
| The shop status has not been specified.&lt;br /&gt;
|-&lt;br /&gt;
| NewUnderApproval&lt;br /&gt;
| string &lt;br /&gt;
&lt;br /&gt;
| The shop is newly created and is being approved.&lt;br /&gt;
|-&lt;br /&gt;
| NewForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop is pending approval.&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 a modification is under approval.&lt;br /&gt;
|-&lt;br /&gt;
| OpenModificationForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop is open, and a modification you sent for approval has been rejected.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosed&lt;br /&gt;
| string&lt;br /&gt;
| The shop is temporarily closed.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosedWaitForModificationApproval&lt;br /&gt;
| string&lt;br /&gt;
| The shop is temporarily closed while awaiting approval for a modification.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosedModificationForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop is temporarily closed, and its properties cannot be modified.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosed&lt;br /&gt;
| string&lt;br /&gt;
| The shop is closed permanently.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosedByUser&lt;br /&gt;
| string&lt;br /&gt;
| The shop owner closed the shop.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosedByOfficer&lt;br /&gt;
| string&lt;br /&gt;
| A Barion officer closed the shop permanently.&lt;br /&gt;
|-&lt;br /&gt;
| ClosedByOfficer&lt;br /&gt;
| string&lt;br /&gt;
| A Barion officer closed the shop.&lt;br /&gt;
|-&lt;br /&gt;
| ReOpen_WaitingForApproval&lt;br /&gt;
| string&lt;br /&gt;
| The shop is being reopened and awaiting approval.&lt;br /&gt;
|-&lt;br /&gt;
| Draft&lt;br /&gt;
| string&lt;br /&gt;
| The shop is in draft state.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopStatus&amp;diff=4006</id>
		<title>ShopStatus</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopStatus&amp;diff=4006"/>
		<updated>2023-05-09T10:46:43Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Property list */&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-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;
| Unspecified&lt;br /&gt;
| string &lt;br /&gt;
| The shop status has not been specified.&lt;br /&gt;
|-&lt;br /&gt;
| NewUnderApproval&lt;br /&gt;
| string &lt;br /&gt;
&lt;br /&gt;
| The shop is newly created and is being approved.&lt;br /&gt;
|-&lt;br /&gt;
| NewForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop is newly created, but it is forbidden from conducting Barion operations.&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 a modification is under approval.&lt;br /&gt;
|-&lt;br /&gt;
| OpenModificationForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop is open, and its properties cannot be modified.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosed&lt;br /&gt;
| string&lt;br /&gt;
| The shop is temporarily closed.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosedWaitForModificationApproval&lt;br /&gt;
| string&lt;br /&gt;
| The shop is temporarily closed while awaiting approval for a modification.&lt;br /&gt;
|-&lt;br /&gt;
| TemporaryClosedModificationForbidden&lt;br /&gt;
| string&lt;br /&gt;
| The shop is temporarily closed, and its properties cannot be modified.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosed&lt;br /&gt;
| string&lt;br /&gt;
| The shop is closed permanently.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosedByUser&lt;br /&gt;
| string&lt;br /&gt;
| The shop owner closed the shop.&lt;br /&gt;
|-&lt;br /&gt;
| PermanentlyClosedByOfficer&lt;br /&gt;
| string&lt;br /&gt;
| A Barion officer closed the shop permanently.&lt;br /&gt;
|-&lt;br /&gt;
| ClosedByOfficer&lt;br /&gt;
| string&lt;br /&gt;
| A Barion officer closed the shop.&lt;br /&gt;
|-&lt;br /&gt;
| ReOpen_WaitingForApproval&lt;br /&gt;
| string&lt;br /&gt;
| The shop is being reopened and awaiting approval.&lt;br /&gt;
|-&lt;br /&gt;
| Draft&lt;br /&gt;
| string&lt;br /&gt;
| The shop is in draft state.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=4005</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=4005"/>
		<updated>2023-05-08T10:56:43Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Going live}}&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;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/general-terms/ Terms &amp;amp; Conditions] in online registration, there is no paperwork or similar hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited to this account immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register an account at [https://secure.barion.com/Registration our Registration page].&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, avoid mixing up Live and Sandbox accounts. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. We only allow shops that are legal and comply with our [https://www.barion.com/en/general-terms/ Terms &amp;amp; Conditions]. We do not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, contact us through chat on [https://www.barion.com/ Barion.com] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you are asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you are asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payments must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://secure.barion.com/Remark experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
We recommend making these parameters, so you can easily switch between the sandbox and live servers. To go live, make the following changes to the payment solution. &lt;br /&gt;
*Change the API endpoint URL to Live (https://api.test.barion.com -&amp;gt; https://api.barion.com).&lt;br /&gt;
*Change the payment GUI redirect URL to Live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay).&lt;br /&gt;
*Change POSKey to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here).&lt;br /&gt;
*If you are using your own sandbox shop, change the return URL.&lt;br /&gt;
*If you are using your own sandbox shop, change the callback URL.&lt;br /&gt;
*Check e-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if it is different in sandbox.&lt;br /&gt;
*Change certificates, if you are checking server certificates.&lt;br /&gt;
*If using token payment, keep in mind that sandbox tokens do not work in the live system.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your chosen price package. Refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps with placement. Follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
An example for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
*for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
*for Hungary and other countries at:  https://download.barion.com/barion/barion-smart-payment-banners.zip&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff checks it and only approves shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Refer to [[Support|Getting support]] for more information.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=4004</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=4004"/>
		<updated>2023-05-08T10:56:05Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
{| 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;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system supports TLS v1.2 / v1.3|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only either GET or POST requests - there are no universal endpoints available.&lt;br /&gt;
Each API endpoint reference page lists the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support HTTP method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Ensure your API requests meet these requirements:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Explicitly specify &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32-character string representation, for example &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used for example to identify payments. For security and compatibility reasons the GUID is used without hyphens for most of our API.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, for example &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Avoid integer or byte evaluation when constructing the request JSON.&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Always double-check that you are connecting to the proper environment.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, major updates to an API endpoint raise the API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. Check the reference page of a given API endpoint to see available versions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), we recommend always specifying the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
For every request sent to the Barion API, you have to authenticate yourself. Use a different type of authentication depending on the type of endpoint.&lt;br /&gt;
&lt;br /&gt;
==== Shop-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
Shop-level endpoints can be authenticated using the shop&#039;s unique &amp;lt;tt&amp;gt;POSKey&amp;lt;/tt&amp;gt;. For more details on using and obtaining the POS key, see [[Barion Shop Authentication]].&lt;br /&gt;
&lt;br /&gt;
==== Wallet-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
You can authenticate yourself to endpoints requiring wallet-level authentication via an API key called a &amp;lt;tt&amp;gt;Wallet key&amp;lt;/tt&amp;gt;. For more information on using this API key, see [[Barion Wallet Authentication]].&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however you can find one property in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId ||  If the error is related to a business process that involves a given payment, the public identifier of the payment is supplied here. This property is not present for all errors.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The following example shows an error case where the shop does not have an account with the currency it specified when trying to create a payment.&lt;br /&gt;
This is a validation error, so the payment identifier is not applicable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingCurrency&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;Payment is not supported&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;Payment is not supported. The POS doesn’t have an account that supports EUR!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following example shows a case where after several successful token charges, the customer deleted their payment card from the Barion system, so the subsequent attempt failed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;OriginalPaymentCardDoesNotExist&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The original payment card does not exist!&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The payment card that was used for the original payment with recurrence ID &#039;TEST-01&#039; no longer exists in the system!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Refer to the [[Security Measures]] for more information on IT security before starting to code.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Creating_a_shop&amp;diff=4003</id>
		<title>Creating a shop</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Creating_a_shop&amp;diff=4003"/>
		<updated>2023-05-08T10:55:34Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Creating a shop 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;
Creating a shop is mandatory for managing payments via the Barion API.&lt;br /&gt;
This article guides you through the creation of a shop in the Barion system.&lt;br /&gt;
&lt;br /&gt;
== How to create a shop in Barion ==&lt;br /&gt;
&lt;br /&gt;
# Login to your Barion wallet on the website. Barion also offers a Sandbox environment for testing purposes - learn more about the Sandbox [[Sandbox|here]].&lt;br /&gt;
# Click &#039;&#039;&#039;Manage my shops&#039;&#039;&#039; &amp;gt; &#039;&#039;&#039;Create new shop&#039;&#039;&#039;.&lt;br /&gt;
# Fill out the displayed form with [[#Shop properties|the relevant properties]]. You can save your shop in draft mode at any time. You receive a confirmation email about your newly opened shop, which contains your POSKey. This is the authentication key you need to send a request to the Barion API.&lt;br /&gt;
# After you filled out &#039;&#039;&#039;all&#039;&#039;&#039; fields, send your shop for approval. In the Sandbox environment, you still have to press this button even though shops are approved instantly.&lt;br /&gt;
# In the Live environment, the Barion staff approves your shop shortly.&lt;br /&gt;
# After your shop is approved and open, you can send requests to the API.&lt;br /&gt;
&lt;br /&gt;
== Shop properties ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Property&lt;br /&gt;
! Description&lt;br /&gt;
|-&lt;br /&gt;
| Shop name&lt;br /&gt;
| The name of the shop. Must be unique in the Barion system, and must be compliant with your organization or business. Generic names like &#039;&#039;&amp;quot;my test shop&amp;quot;&#039;&#039;, &#039;&#039;&amp;quot;online jewelry store&amp;quot;&#039;&#039; or &#039;&#039;&amp;quot;postal service&amp;quot;&#039;&#039; are not accepted.&lt;br /&gt;
|-&lt;br /&gt;
| Shop description&lt;br /&gt;
| A short description of the shop. This is to help the Barion staff identify the shop as a valid business. &lt;br /&gt;
|-&lt;br /&gt;
| Shop URL&lt;br /&gt;
| The URL to the owner&#039;s website, or the webshop itself, if applicable.&lt;br /&gt;
|-&lt;br /&gt;
| Avatar&lt;br /&gt;
| An image representing the organization or business. This should be your company logo. Avoid stock photos and such - if the image is misleading or irrelevant to your business, your shop will not be approved!&lt;br /&gt;
|-&lt;br /&gt;
| Category&lt;br /&gt;
| Set appropriate categories that apply to your business. If your business does not fall into the selected categories, your shop will not be approved!&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Creating_an_account&amp;diff=4002</id>
		<title>Creating an account</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Creating_an_account&amp;diff=4002"/>
		<updated>2023-05-08T10:55:15Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Creating an account 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;
This article contains information about creating an account in the Barion system.&lt;br /&gt;
&lt;br /&gt;
To register, visit the Barion website and click &#039;&#039;&#039;Sign up now&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=If you are a developer, we recommend creating an account in the Sandbox environment first.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Individual, business ==&lt;br /&gt;
&lt;br /&gt;
You can register yourself as an individual, or a business entity (non-profit organization should register a business account). Make sure you have chosen the proper registration type (that is, do not register as an individual if you have a company running your business). Failing to do so results in difficulties validating yourself through our KYC process.&lt;br /&gt;
&lt;br /&gt;
== Different currencies ==&lt;br /&gt;
&lt;br /&gt;
Select one from these currencies upon registration:&lt;br /&gt;
* CZK (Czech crown)&lt;br /&gt;
* EUR (Euro)&lt;br /&gt;
* HUF (Hungarian forint)&lt;br /&gt;
* USD (U.S. dollar)&lt;br /&gt;
&lt;br /&gt;
You can manually add the other ones later on the &#039;&#039;&#039;My currencies&#039;&#039;&#039; page.&lt;br /&gt;
&lt;br /&gt;
== Anonimity and limits == &lt;br /&gt;
&lt;br /&gt;
When you create an account as an individual, you have the option to be completely anonymous in the system. In such case, you only have to provide your email address and a password. You can use your personal account with an email only up to the balance of HUF 65 000. You must fill in your personal data to lift this limit. &lt;br /&gt;
If you register as a business or non-profit organization, you must provide additional data related to your business.&lt;br /&gt;
&lt;br /&gt;
At the end of the registration process with all the fields filled in, your account is in an unverified status. This means there are several limits applied to your account. These limits are described in detail in the [https://www.barion.com/en/support/what-limits-are-in-barion-and-why-are-these-necessary/ Barion FAQ on limits].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To disable these limits, you must undergo our KYC procedure to verify your account.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=4001</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=4001"/>
		<updated>2023-05-08T10:54:53Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Limitations in functionality */&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;
{| 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;
=Sandbox server=&lt;br /&gt;
Although Barion payments are very easy to integrate, we strongly advise all developers to use our Sandbox server for development and testing before going live. &lt;br /&gt;
&lt;br /&gt;
There are numerous advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is always available, you can even start working at night or during weekends. However, keep in mind 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 you can use the same email address in both (careful, do not mix up the enviroments).&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 developer 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 a 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 to this account immediately after payment. &lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Always double-check your environment 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;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 one, 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.2 / 1.3 - earlier 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. A standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well-known brand has been chosen. This does not affect 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. If you make several payments to a merchant, the account can reach a balance where another level of KYC is required, and the account is temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Drop a mail to support if run into this, or cannot avoid it. &lt;br /&gt;
&amp;lt;br&amp;gt;Each test card is represented with a 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 environment, with the following exceptions:&lt;br /&gt;
*A black bar is present at the top, displaying the &amp;quot;sandbox server&amp;quot; message&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 accepts test cards, 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 emails are actually sent out in the Sandbox environment as well, so DO NOT use any real email address that does not belong to you. Use your own personal or development email address, or if you do not care about the email itself, use the @example.com email 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 it 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 email address when logging into the app. The title bar of the app turns green to help differentiate it 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=4000</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=4000"/>
		<updated>2023-05-08T10:54:44Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &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;
{| 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;
=Sandbox server=&lt;br /&gt;
Although Barion payments are very easy to integrate, we strongly advise all developers to use our Sandbox server for development and testing before going live. &lt;br /&gt;
&lt;br /&gt;
There are numerous advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is always available, you can even start working at night or during weekends. However, keep in mind 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 you can use the same email address in both (careful, do not mix up the enviroments).&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 a 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 to this account immediately after payment. &lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Always double-check your environment 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;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 one, 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.2 / 1.3 - earlier 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. A standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well-known brand has been chosen. This does not affect 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. If you make several payments to a merchant, the account can reach a balance where another level of KYC is required, and the account is temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Drop a mail to support if run into this, or cannot avoid it. &lt;br /&gt;
&amp;lt;br&amp;gt;Each test card is represented with a 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 environment, with the following exceptions:&lt;br /&gt;
*A black bar is present at the top, displaying the &amp;quot;sandbox server&amp;quot; message&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 accepts test cards, 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 emails are actually sent out in the Sandbox environment as well, so DO NOT use any real email address that does not belong to you. Use your own personal or development email address, or if you do not care about the email itself, use the @example.com email 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 it 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 email address when logging into the app. The title bar of the app turns green to help differentiate it 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Getting_started&amp;diff=3999</id>
		<title>Getting started</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Getting_started&amp;diff=3999"/>
		<updated>2023-05-08T10:54:20Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Getting started - overview of Barion payments}}&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;
==Time needed==&lt;br /&gt;
Working with the Barion API is a no-brainer. Depending on the circumstances (your needs, business expectations, system architecture, business process management and available resources), you can integrate Barion within a few hours. Typically though the basic integration and testing are accomplished in a couple of days.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=We recommend reading the documentation first. As developers, we are very much aware that you prefer jumping in, but consider that as a payment system, implementing Barion requires discipline. Also, we would rather spare you any unnecessary hassle. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Feature overview==&lt;br /&gt;
Barion is a provider of online electronic payments. Our payment services include:&lt;br /&gt;
*payment with debit and credit cards&lt;br /&gt;
*payment with prepaid Barion wallet&lt;br /&gt;
&lt;br /&gt;
We have several payment solutions, based on the above payment types:&lt;br /&gt;
*Responsive Web Payment, which works in desktop and mobile browsers&lt;br /&gt;
*Mobile App Payment, which works in native mobile apps in two scenarios:&lt;br /&gt;
**If the Barion Mobile App is installed on the customer&#039;s device, a simple and quick payment works with the Barion Mobile App&lt;br /&gt;
**If the Barion Mobile App is not installed on the customer&#039;s device, the Responsive Web Payment solves the payment&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|800px]]&lt;br /&gt;
&lt;br /&gt;
==The payment process==&lt;br /&gt;
Paying through the Barion Smart Gateway follows these simple steps:&lt;br /&gt;
#Customer chooses to pay.&lt;br /&gt;
#The merchant&#039;s server initiates the payment by calling the [[Payment-Start-v2|/Payment/Start]] API and using POSKey for authentication. Barion returns a Payment ID. Shop records the transaction.&lt;br /&gt;
#Merchant&#039;s website redirects the user to the Barion payment gateway UI, which can be either:&lt;br /&gt;
##A responsive web user interface.&lt;br /&gt;
##The Barion mobile app, if the customer uses their mobile for the purchase and the Barion app is installed. Our app is available on Android and iOS platforms.&lt;br /&gt;
#The customer completes the payment.&lt;br /&gt;
##If the customer has no Barion account, they must provide card data.&lt;br /&gt;
##If the customer has a Barion wallet (account), they log in and can choose to pay using a card on file, a new card, or alternatively from their Barion balance.&lt;br /&gt;
#In case of a change in the payment status (e.g. successful payment happened or the customer rejected the payment), the [[Callback_mechanism|Barion server notifies]] the shop. Upon receiving the notification the shop must call [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]] to see if the payment was successful or not. &lt;br /&gt;
#The merchant&#039;s server records the result of the transaction.&lt;br /&gt;
#The user is redirected by Barion to the merchant&#039;s return URL.&lt;br /&gt;
[[file:Process-overview.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
==Flow of funds==&lt;br /&gt;
*Guest payment with card – available for any cardholder with a card capable of making VPOS payments. The debit or credit card is charged and the merchant&#039;s Barion account is topped up with the equivalent amount. No need for Barion registration or previous top-up.&lt;br /&gt;
&lt;br /&gt;
*Payment with card on file – available for any card holder with a card capable of making VPOS payments that previously registered with Barion and chose to store card data in their Barion wallet. The debit or credit card is charged and the merchant&#039;s Barion account is topped up with the equivalent amount. Card data is stored in a PCI DSS-compliant card vault. No CVC is stored. No need for a previous top-up.&lt;br /&gt;
&lt;br /&gt;
*Payment with prepaid Barion balance – available for any user that previously registered with Barion and has a balance in their Barion wallet. Money is transferred to the merchant&#039;s account. This payment does not involve cards. Customer wallets can be topped up via bank transfer. &lt;br /&gt;
&lt;br /&gt;
*Top-up – available for all Barion users from a bank account. By wiring funds to Barion with a personal top-up code in the comment, Barion balance is topped up in the appropriate currency.&lt;br /&gt;
&lt;br /&gt;
*Withdrawal - available for all Barion users. Funds are transferred from a Barion wallet to any bank account via wire transfer.&lt;br /&gt;
&lt;br /&gt;
[[file:Accounts-fundingsources-withdraw.png|800px]]&lt;br /&gt;
&lt;br /&gt;
==Extra services==&lt;br /&gt;
We also provide extra services that can be combined with the above payment technologies:&lt;br /&gt;
*[[Token_payment|Token payment]] for automatic payments, such as One-Click or recurring payments&lt;br /&gt;
*[[C2C_Payments|Sharing economy features]], such as:&lt;br /&gt;
**Payment to 3rd parties or C2C (Consumer to Consumer) payments&lt;br /&gt;
**Deducting commission from C2C payments&lt;br /&gt;
**Escrow services for C2C payments&lt;br /&gt;
&lt;br /&gt;
Other services augmenting the above payments:&lt;br /&gt;
*[[Payment-Refund-v2|Refunding payments]] to the original funding source (card or balance) from GUI or API&lt;br /&gt;
*[[Withdraw-BankTransfer-v2|Withdrawing funds]] to bank accounts from GUI or API&lt;br /&gt;
*Free and real-time [[Transfer-Send-v1|money sending]] between Barion accounts from GUI or API&lt;br /&gt;
&lt;br /&gt;
==Sandbox and live==&lt;br /&gt;
Barion maintains a clone of the live Barion secure server as a sandbox or test environment, where developers can experiment with their solutions. The sandbox works with &amp;quot;test&amp;quot; money instead of real, so there is no risk when playing around. Sandbox is open, all you need is to register, read the documentation and you can start playing.  For more information on differences in the live and sandbox servers, read [[Sandbox|Setting up the Sandbox environment and testing payments]].&lt;br /&gt;
&lt;br /&gt;
==Skills and tools required==&lt;br /&gt;
All you need is an intermediate level of web back-end development with the ability and tools to call a REST API. Although there are no specific competency or tool requirements, an up-to-date development environment, and toolbox is essential. We balance compatibility and security when picking which latest technology to use. For more information, read [[Calling_the_API|Calling the Barion API]].&lt;br /&gt;
&lt;br /&gt;
==Supported currencies==&lt;br /&gt;
* CZK (Czech crown)&lt;br /&gt;
* EUR (Euro)&lt;br /&gt;
* HUF (Hungarian forint)&lt;br /&gt;
* USD (U.S. dollar)&lt;br /&gt;
&lt;br /&gt;
To use the Barion Smart Gateway and the Barion API in a given currency, you must have an active account with that currency.&lt;br /&gt;
&lt;br /&gt;
=SSL=&lt;br /&gt;
Barion servers use &amp;lt;code&amp;gt;https://&amp;lt;/code&amp;gt; protocol to communicate. We recommend using a REST library that can verify the identity of our server when calling the Barion API. Always use TLS version 1.2 or newer.&lt;br /&gt;
&lt;br /&gt;
For more information on differences in SSL certificates on the live and sandbox servers, read [[Sandbox|Setting up the Sandbox environment and testing payments]].&lt;br /&gt;
&lt;br /&gt;
==PCI DSS certification==&lt;br /&gt;
Barion is Payment Card Industry Data Security Standard (PCI DSS) certified. Since you, as a merchant do not handle cardholder data, PCI DSS certification for merchants using Barion payment is not mandatory. The PCI DSS is an information security standard for organizations that handle branded credit cards. If you handle credit cards, even temporarily, PCI DSS certification is mandatory.&lt;br /&gt;
&lt;br /&gt;
For more information, read [[Legal_accounting|Legal and accounting information]].&lt;br /&gt;
&lt;br /&gt;
==Going live==&lt;br /&gt;
When your payment solution is working properly in the sandbox, you are ready to go live. Using the live server requires a real contract and an approved shop, so prepare in advance. Read the [[Going_live|Going live]] guide thoroughly and follow the instructions before going live.&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Follow the Barion Logo Guidelines and place the appropriate logo on your page. Using the logo is a requirement for all Barion price packages, omitting it results in rejecting live shops. Our experience shows that it is important for customers to show they can pay with Barion on your website. We also think that keeping the logo consistent across all Barion merchants helps the entire Barion community.&lt;br /&gt;
&lt;br /&gt;
If you choose the [https://www.barion.com/en/merchants/merchant-price-packages/ Clever, Smart, or Genius price package], you have to provide us with detailed cart content. Use the [[Item]] structure within the &#039;&#039;&#039;Items[]&#039;&#039;&#039; property of the [[PaymentTransaction]] structure of the &#039;&#039;&#039;Transactions&#039;&#039;&#039; property of the [[Payment-Start-v2|/Payment/Start]] API endpoint to pass data. The customers see the cart content during payment and later in their Barion wallet history.&lt;br /&gt;
&lt;br /&gt;
When providing cart content, follow the guidelines below:&lt;br /&gt;
*Use real product names, generics such as &amp;quot;product&amp;quot; or &amp;quot;drink&amp;quot; will not work. Follow these examples: &lt;br /&gt;
**&#039;&#039;Canon IXUS 110 Compact Digital Camera&#039;&#039;&lt;br /&gt;
**&#039;&#039;Heineken lager 5L party barrel&#039;&#039;&lt;br /&gt;
*Provide all items in one collection&lt;br /&gt;
*Use all fields of the [[Item]] structure&lt;br /&gt;
*You may add discounts as a separate item, subtotals are not checked, so you can use negative prices&lt;br /&gt;
*You may add packaging or shipping costs as a separate item&lt;br /&gt;
*Provide a link to the image of the product if available, we will use it later for enhancing the payment UX&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Currently, we do not allow placing the payment GUI in an &amp;lt;code&amp;gt;&amp;lt;iframe&amp;gt;&amp;lt;/code&amp;gt; or similar solution, due to security reasons.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Getting_started&amp;diff=3998</id>
		<title>Getting started</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Getting_started&amp;diff=3998"/>
		<updated>2023-05-08T10:53:26Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Getting started - overview of Barion payments}}&lt;br /&gt;
&lt;br /&gt;
==Time needed==&lt;br /&gt;
Working with the Barion API is a no-brainer. Depending on the circumstances (your needs, business expectations, system architecture, business process management and available resources), you can integrate Barion within a few hours. Typically though the basic integration and testing are accomplished in a couple of days.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=We recommend reading the documentation first. As developers, we are very much aware that you prefer jumping in, but consider that as a payment system, implementing Barion requires discipline. Also, we would rather spare you any unnecessary hassle. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Feature overview==&lt;br /&gt;
Barion is a provider of online electronic payments. Our payment services include:&lt;br /&gt;
*payment with debit and credit cards&lt;br /&gt;
*payment with prepaid Barion wallet&lt;br /&gt;
&lt;br /&gt;
We have several payment solutions, based on the above payment types:&lt;br /&gt;
*Responsive Web Payment, which works in desktop and mobile browsers&lt;br /&gt;
*Mobile App Payment, which works in native mobile apps in two scenarios:&lt;br /&gt;
**If the Barion Mobile App is installed on the customer&#039;s device, a simple and quick payment works with the Barion Mobile App&lt;br /&gt;
**If the Barion Mobile App is not installed on the customer&#039;s device, the Responsive Web Payment solves the payment&lt;br /&gt;
&lt;br /&gt;
[[file:payment-gui-montage.png|800px]]&lt;br /&gt;
&lt;br /&gt;
==The payment process==&lt;br /&gt;
Paying through the Barion Smart Gateway follows these simple steps:&lt;br /&gt;
#Customer chooses to pay.&lt;br /&gt;
#The merchant&#039;s server initiates the payment by calling the [[Payment-Start-v2|/Payment/Start]] API and using POSKey for authentication. Barion returns a Payment ID. Shop records the transaction.&lt;br /&gt;
#Merchant&#039;s website redirects the user to the Barion payment gateway UI, which can be either:&lt;br /&gt;
##A responsive web user interface.&lt;br /&gt;
##The Barion mobile app, if the customer uses their mobile for the purchase and the Barion app is installed. Our app is available on Android and iOS platforms.&lt;br /&gt;
#The customer completes the payment.&lt;br /&gt;
##If the customer has no Barion account, they must provide card data.&lt;br /&gt;
##If the customer has a Barion wallet (account), they log in and can choose to pay using a card on file, a new card, or alternatively from their Barion balance.&lt;br /&gt;
#In case of a change in the payment status (e.g. successful payment happened or the customer rejected the payment), the [[Callback_mechanism|Barion server notifies]] the shop. Upon receiving the notification the shop must call [[Payment-GetPaymentState-v2|/Payment/GetPaymentState]] to see if the payment was successful or not. &lt;br /&gt;
#The merchant&#039;s server records the result of the transaction.&lt;br /&gt;
#The user is redirected by Barion to the merchant&#039;s return URL.&lt;br /&gt;
[[file:Process-overview.png|1000px]]&lt;br /&gt;
&lt;br /&gt;
==Flow of funds==&lt;br /&gt;
*Guest payment with card – available for any cardholder with a card capable of making VPOS payments. The debit or credit card is charged and the merchant&#039;s Barion account is topped up with the equivalent amount. No need for Barion registration or previous top-up.&lt;br /&gt;
&lt;br /&gt;
*Payment with card on file – available for any card holder with a card capable of making VPOS payments that previously registered with Barion and chose to store card data in their Barion wallet. The debit or credit card is charged and the merchant&#039;s Barion account is topped up with the equivalent amount. Card data is stored in a PCI DSS-compliant card vault. No CVC is stored. No need for a previous top-up.&lt;br /&gt;
&lt;br /&gt;
*Payment with prepaid Barion balance – available for any user that previously registered with Barion and has a balance in their Barion wallet. Money is transferred to the merchant&#039;s account. This payment does not involve cards. Customer wallets can be topped up via bank transfer. &lt;br /&gt;
&lt;br /&gt;
*Top-up – available for all Barion users from a bank account. By wiring funds to Barion with a personal top-up code in the comment, Barion balance is topped up in the appropriate currency.&lt;br /&gt;
&lt;br /&gt;
*Withdrawal - available for all Barion users. Funds are transferred from a Barion wallet to any bank account via wire transfer.&lt;br /&gt;
&lt;br /&gt;
[[file:Accounts-fundingsources-withdraw.png|800px]]&lt;br /&gt;
&lt;br /&gt;
==Extra services==&lt;br /&gt;
We also provide extra services that can be combined with the above payment technologies:&lt;br /&gt;
*[[Token_payment|Token payment]] for automatic payments, such as One-Click or recurring payments&lt;br /&gt;
*[[C2C_Payments|Sharing economy features]], such as:&lt;br /&gt;
**Payment to 3rd parties or C2C (Consumer to Consumer) payments&lt;br /&gt;
**Deducting commission from C2C payments&lt;br /&gt;
**Escrow services for C2C payments&lt;br /&gt;
&lt;br /&gt;
Other services augmenting the above payments:&lt;br /&gt;
*[[Payment-Refund-v2|Refunding payments]] to the original funding source (card or balance) from GUI or API&lt;br /&gt;
*[[Withdraw-BankTransfer-v2|Withdrawing funds]] to bank accounts from GUI or API&lt;br /&gt;
*Free and real-time [[Transfer-Send-v1|money sending]] between Barion accounts from GUI or API&lt;br /&gt;
&lt;br /&gt;
==Sandbox and live==&lt;br /&gt;
Barion maintains a clone of the live Barion secure server as a sandbox or test environment, where developers can experiment with their solutions. The sandbox works with &amp;quot;test&amp;quot; money instead of real, so there is no risk when playing around. Sandbox is open, all you need is to register, read the documentation and you can start playing.  For more information on differences in the live and sandbox servers, read [[Sandbox|Setting up the Sandbox environment and testing payments]].&lt;br /&gt;
&lt;br /&gt;
==Skills and tools required==&lt;br /&gt;
All you need is an intermediate level of web back-end development with the ability and tools to call a REST API. Although there are no specific competency or tool requirements, an up-to-date development environment, and toolbox is essential. We balance compatibility and security when picking which latest technology to use. For more information, read [[Calling_the_API|Calling the Barion API]].&lt;br /&gt;
&lt;br /&gt;
==Supported currencies==&lt;br /&gt;
* CZK (Czech crown)&lt;br /&gt;
* EUR (Euro)&lt;br /&gt;
* HUF (Hungarian forint)&lt;br /&gt;
* USD (U.S. dollar)&lt;br /&gt;
&lt;br /&gt;
To use the Barion Smart Gateway and the Barion API in a given currency, you must have an active account with that currency.&lt;br /&gt;
&lt;br /&gt;
=SSL=&lt;br /&gt;
Barion servers use &amp;lt;code&amp;gt;https://&amp;lt;/code&amp;gt; protocol to communicate. We recommend using a REST library that can verify the identity of our server when calling the Barion API. Always use TLS version 1.2 or newer.&lt;br /&gt;
&lt;br /&gt;
For more information on differences in SSL certificates on the live and sandbox servers, read [[Sandbox|Setting up the Sandbox environment and testing payments]].&lt;br /&gt;
&lt;br /&gt;
==PCI DSS certification==&lt;br /&gt;
Barion is Payment Card Industry Data Security Standard (PCI DSS) certified. Since you, as a merchant do not handle cardholder data, PCI DSS certification for merchants using Barion payment is not mandatory. The PCI DSS is an information security standard for organizations that handle branded credit cards. If you handle credit cards, even temporarily, PCI DSS certification is mandatory.&lt;br /&gt;
&lt;br /&gt;
For more information, read [[Legal_accounting|Legal and accounting information]].&lt;br /&gt;
&lt;br /&gt;
==Going live==&lt;br /&gt;
When your payment solution is working properly in the sandbox, you are ready to go live. Using the live server requires a real contract and an approved shop, so prepare in advance. Read the [[Going_live|Going live]] guide thoroughly and follow the instructions before going live.&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Follow the Barion Logo Guidelines and place the appropriate logo on your page. Using the logo is a requirement for all Barion price packages, omitting it results in rejecting live shops. Our experience shows that it is important for customers to show they can pay with Barion on your website. We also think that keeping the logo consistent across all Barion merchants helps the entire Barion community.&lt;br /&gt;
&lt;br /&gt;
If you choose the [https://www.barion.com/en/merchants/merchant-price-packages/ Clever, Smart, or Genius price package], you have to provide us with detailed cart content. Use the [[Item]] structure within the &#039;&#039;&#039;Items[]&#039;&#039;&#039; property of the [[PaymentTransaction]] structure of the &#039;&#039;&#039;Transactions&#039;&#039;&#039; property of the [[Payment-Start-v2|/Payment/Start]] API endpoint to pass data. The customers see the cart content during payment and later in their Barion wallet history.&lt;br /&gt;
&lt;br /&gt;
When providing cart content, follow the guidelines below:&lt;br /&gt;
*Use real product names, generics such as &amp;quot;product&amp;quot; or &amp;quot;drink&amp;quot; will not work. Follow these examples: &lt;br /&gt;
**&#039;&#039;Canon IXUS 110 Compact Digital Camera&#039;&#039;&lt;br /&gt;
**&#039;&#039;Heineken lager 5L party barrel&#039;&#039;&lt;br /&gt;
*Provide all items in one collection&lt;br /&gt;
*Use all fields of the [[Item]] structure&lt;br /&gt;
*You may add discounts as a separate item, subtotals are not checked, so you can use negative prices&lt;br /&gt;
*You may add packaging or shipping costs as a separate item&lt;br /&gt;
*Provide a link to the image of the product if available, we will use it later for enhancing the payment UX&lt;br /&gt;
&lt;br /&gt;
==Limitations==&lt;br /&gt;
Currently, we do not allow placing the payment GUI in an &amp;lt;code&amp;gt;&amp;lt;iframe&amp;gt;&amp;lt;/code&amp;gt; or similar solution, due to security reasons.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Sandbox&amp;diff=3997</id>
		<title>Sandbox</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Sandbox&amp;diff=3997"/>
		<updated>2023-05-08T09:30:38Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &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 very easy to integrate, we strongly advise all developers to use our Sandbox server for development and testing before going live. &lt;br /&gt;
&lt;br /&gt;
There are numerous advantages of using the sandbox server for testing:&lt;br /&gt;
*Sandbox is always available, you can even start working at night or during weekends. However, keep in mind 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 you can use the same email address in both (careful, do not mix up the enviroments).&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 a 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 to this account immediately after payment. &lt;br /&gt;
&#039;&#039;&#039;Note&#039;&#039;&#039;: Always double-check your environment 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;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 one, 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.2 / 1.3 - earlier 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. A standard HTTPS certificate is used, instead of Extended Validation (EV), and a less well-known brand has been chosen. This does not affect 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. If you make several payments to a merchant, the account can reach a balance where another level of KYC is required, and the account is temporarily suspended. Suspended accounts can initiate payments, but can not send or withdraw money. Drop a mail to support if run into this, or cannot avoid it. &lt;br /&gt;
&amp;lt;br&amp;gt;Each test card is represented with a 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 environment, with the following exceptions:&lt;br /&gt;
*A black bar is present at the top, displaying the &amp;quot;sandbox server&amp;quot; message&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 accepts test cards, 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 emails are actually sent out in the Sandbox environment as well, so DO NOT use any real email address that does not belong to you. Use your own personal or development email address, or if you do not care about the email itself, use the @example.com email 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 it 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 email address when logging into the app. The title bar of the app turns green to help differentiate it 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Creating_an_account&amp;diff=3996</id>
		<title>Creating an account</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Creating_an_account&amp;diff=3996"/>
		<updated>2023-05-08T09:21:17Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Creating an account in Barion}}&lt;br /&gt;
&lt;br /&gt;
This article contains information about creating an account in the Barion system.&lt;br /&gt;
&lt;br /&gt;
To register, visit the Barion website and click &#039;&#039;&#039;Sign up now&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=If you are a developer, we recommend creating an account in the Sandbox environment first.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Individual, business ==&lt;br /&gt;
&lt;br /&gt;
You can register yourself as an individual, or a business entity (non-profit organization should register a business account). Make sure you have chosen the proper registration type (that is, do not register as an individual if you have a company running your business). Failing to do so results in difficulties validating yourself through our KYC process.&lt;br /&gt;
&lt;br /&gt;
== Different currencies ==&lt;br /&gt;
&lt;br /&gt;
Select one from these currencies upon registration:&lt;br /&gt;
* CZK (Czech crown)&lt;br /&gt;
* EUR (Euro)&lt;br /&gt;
* HUF (Hungarian forint)&lt;br /&gt;
* USD (U.S. dollar)&lt;br /&gt;
&lt;br /&gt;
You can manually add the other ones later on the &#039;&#039;&#039;My currencies&#039;&#039;&#039; page.&lt;br /&gt;
&lt;br /&gt;
== Anonimity and limits == &lt;br /&gt;
&lt;br /&gt;
When you create an account as an individual, you have the option to be completely anonymous in the system. In such case, you only have to provide your email address and a password. You can use your personal account with an email only up to the balance of HUF 65 000. You must fill in your personal data to lift this limit. &lt;br /&gt;
If you register as a business or non-profit organization, you must provide additional data related to your business.&lt;br /&gt;
&lt;br /&gt;
At the end of the registration process with all the fields filled in, your account is in an unverified status. This means there are several limits applied to your account. These limits are described in detail in the [https://www.barion.com/en/support/what-limits-are-in-barion-and-why-are-these-necessary/ Barion FAQ on limits].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To disable these limits, you must undergo our KYC procedure to verify your account.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Creating_a_shop&amp;diff=3995</id>
		<title>Creating a shop</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Creating_a_shop&amp;diff=3995"/>
		<updated>2023-05-08T08:57:09Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Creating a shop in Barion}}&lt;br /&gt;
&lt;br /&gt;
Creating a shop is mandatory for managing payments via the Barion API.&lt;br /&gt;
This article guides you through the creation of a shop in the Barion system.&lt;br /&gt;
&lt;br /&gt;
== How to create a shop in Barion ==&lt;br /&gt;
&lt;br /&gt;
# Login to your Barion wallet on the website. Barion also offers a Sandbox environment for testing purposes - learn more about the Sandbox [[Sandbox|here]].&lt;br /&gt;
# Click &#039;&#039;&#039;Manage my shops&#039;&#039;&#039; &amp;gt; &#039;&#039;&#039;Create new shop&#039;&#039;&#039;.&lt;br /&gt;
# Fill out the displayed form with [[#Shop properties|the relevant properties]]. You can save your shop in draft mode at any time. You receive a confirmation email about your newly opened shop, which contains your POSKey. This is the authentication key you need to send a request to the Barion API.&lt;br /&gt;
# After you filled out &#039;&#039;&#039;all&#039;&#039;&#039; fields, send your shop for approval. In the Sandbox environment, you still have to press this button even though shops are approved instantly.&lt;br /&gt;
# In the Live environment, the Barion staff approves your shop shortly.&lt;br /&gt;
# After your shop is approved and open, you can send requests to the API.&lt;br /&gt;
&lt;br /&gt;
== Shop properties ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Property&lt;br /&gt;
! Description&lt;br /&gt;
|-&lt;br /&gt;
| Shop name&lt;br /&gt;
| The name of the shop. Must be unique in the Barion system, and must be compliant with your organization or business. Generic names like &#039;&#039;&amp;quot;my test shop&amp;quot;&#039;&#039;, &#039;&#039;&amp;quot;online jewelry store&amp;quot;&#039;&#039; or &#039;&#039;&amp;quot;postal service&amp;quot;&#039;&#039; are not accepted.&lt;br /&gt;
|-&lt;br /&gt;
| Shop description&lt;br /&gt;
| A short description of the shop. This is to help the Barion staff identify the shop as a valid business. &lt;br /&gt;
|-&lt;br /&gt;
| Shop URL&lt;br /&gt;
| The URL to the owner&#039;s website, or the webshop itself, if applicable.&lt;br /&gt;
|-&lt;br /&gt;
| Avatar&lt;br /&gt;
| An image representing the organization or business. This should be your company logo. Avoid stock photos and such - if the image is misleading or irrelevant to your business, your shop will not be approved!&lt;br /&gt;
|-&lt;br /&gt;
| Category&lt;br /&gt;
| Set appropriate categories that apply to your business. If your business does not fall into the selected categories, your shop will not be approved!&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Going_live&amp;diff=3994</id>
		<title>Going live</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Going_live&amp;diff=3994"/>
		<updated>2023-05-08T08:50:16Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title= Going live}}&lt;br /&gt;
&lt;br /&gt;
=Contracting=&lt;br /&gt;
To make real payments, you need a contract with Barion. Contracting is done by accepting the [https://www.barion.com/en/general-terms/ Terms &amp;amp; Conditions] in online registration, there is no paperwork or similar hassle. Each merchant needs a Barion account, or Wallet, as we call it. Payments are credited to this account immediately after payment. &lt;br /&gt;
&lt;br /&gt;
You can register an account at [https://secure.barion.com/Registration our Registration page].&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
*[[Creating_an_account|Creating an account]]&lt;br /&gt;
*[[Creating_a_shop|Creating a shop]]&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check which server you are using, avoid mixing up Live and Sandbox accounts. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Approval &amp;amp; KYC==&lt;br /&gt;
Barion is a regulated business, many of our processes are bound by laws. We are mandated to check each shop and approve it manually. We only allow shops that are legal and comply with our [https://www.barion.com/en/general-terms/ Terms &amp;amp; Conditions]. We do not support gambling and adult content, even if it is legal. If you are in a risky business or not sure, contact us through chat on [https://www.barion.com/ Barion.com] before starting development. &lt;br /&gt;
&lt;br /&gt;
Upon approval, you are asked to provide additional information (such as company papers) about your shop. Providing inaccurate information may delay the approval of your shop. Upon reaching certain limits, or by the decision of our staff, you are asked to go through a process called KYC (Know Your Customer), which is the identification process mandated by Anti Money Laundering (AML) laws.&lt;br /&gt;
&lt;br /&gt;
==Optional recurring==&lt;br /&gt;
Token or recurring payments must be further approved. Since token payment basically allows you to carry out payments at will, this option is only available for trustworthy companies. Contact our [https://secure.barion.com/Remark experts] well in advance, if you plan to use this option.&lt;br /&gt;
&lt;br /&gt;
==Change URL and POSKey and it works==&lt;br /&gt;
We recommend making these parameters, so you can easily switch between the sandbox and live servers. To go live, make the following changes to the payment solution. &lt;br /&gt;
*Change the API endpoint URL to Live (https://api.test.barion.com -&amp;gt; https://api.barion.com).&lt;br /&gt;
*Change the payment GUI redirect URL to Live (https://secure.test.barion.com/pay -&amp;gt; https://secure.barion.com/pay).&lt;br /&gt;
*Change POSKey to the live and approved shop&#039;s POSKey (a common mistake to leave the sandbox here).&lt;br /&gt;
*If you are using your own sandbox shop, change the return URL.&lt;br /&gt;
*If you are using your own sandbox shop, change the callback URL.&lt;br /&gt;
*Check e-mail addresses of &amp;lt;tt&amp;gt;Payee&amp;lt;/tt&amp;gt;s used in [[PaymentTransaction]] structure in [[Payment-Start-v2|/Payment/Start]] call, if it is different in sandbox.&lt;br /&gt;
*Change certificates, if you are checking server certificates.&lt;br /&gt;
*If using token payment, keep in mind that sandbox tokens do not work in the live system.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Always double-check this list before calling support, it is easy to mix up live and sandbox data. |color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
==Requirement for Smart Package==&lt;br /&gt;
Make sure you fulfill all requirements of your chosen price package. Refer to [[Getting_started|Getting started]] for requirements.&lt;br /&gt;
&lt;br /&gt;
==Logo placement==&lt;br /&gt;
Logos are available in many formats and sizes (PNG, WMF, AI, PDF, CDR, SVG) and a PDF guide helps with placement. Follow the guide and do not make changes to the official logo.&lt;br /&gt;
&lt;br /&gt;
An example for Hungary:&lt;br /&gt;
&lt;br /&gt;
[[File:Barion-card-strip-intl_large.png]]&lt;br /&gt;
&lt;br /&gt;
Find the banner guide and logos&lt;br /&gt;
&lt;br /&gt;
*for Slovakia and Czech Republic at: https://download.barion.com/barion/barion-smart-payment-banners-cs.zip&lt;br /&gt;
&lt;br /&gt;
*for Hungary and other countries at:  https://download.barion.com/barion/barion-smart-payment-banners.zip&lt;br /&gt;
&lt;br /&gt;
==T&amp;amp;C requirements==&lt;br /&gt;
You must include Barion payment in your own Terms &amp;amp; Conditions. Our staff checks it and only approves shops with properly formulated legal texts.&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Refer to the [[Security Measures]] page for more information on IT security before going live.&lt;br /&gt;
&lt;br /&gt;
==Contact and support==&lt;br /&gt;
Refer to [[Support|Getting support]] for more information.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Support&amp;diff=3993</id>
		<title>Support</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Support&amp;diff=3993"/>
		<updated>2023-05-08T08:38:36Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title= Getting support}}&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;
=Before you contact is=&lt;br /&gt;
We are IT guys, too, we know it is a lot easier to write an email. Help us save time and effort and check all available documentation before asking for help, specifically, read the [[Getting_started|Getting started]] and the [[troubleshooting|Troubleshooting]] parts.&lt;br /&gt;
&lt;br /&gt;
=E-mail=&lt;br /&gt;
Send your support requests to [mailto:devsupport@barion.com devsupport@barion.com]&lt;br /&gt;
&lt;br /&gt;
Include the following so we can provide the most effective support:&lt;br /&gt;
*Detailed description of your issue.&lt;br /&gt;
*Any IDs you have, such as account e-mail, shop name, transaction ID, and so on.&lt;br /&gt;
*Whether you are using Live or Sandbox environment.&lt;br /&gt;
*The JSON that you submitted and did not work.&lt;br /&gt;
*A screenshot, if relevant.&lt;br /&gt;
*Your phone number or Skype/Zoom, so we can call you with questions.&lt;br /&gt;
&lt;br /&gt;
=Account management for business=&lt;br /&gt;
With business or legal questions, contact our experts listed at the bottom of the [https://www.barion.com/en/merchants/ merchant page].&lt;br /&gt;
&lt;br /&gt;
=Facebook group=&lt;br /&gt;
Our international developer group with several hundreds of members is at [https://www.facebook.com/groups/bariondevelopers the Developers page]&lt;br /&gt;
&lt;br /&gt;
=Barion status page=&lt;br /&gt;
If you want to see the real-time status of Barion, subscribe to updates at [https://status.barion.com our status page]&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=3DSecure&amp;diff=3992</id>
		<title>3DSecure</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=3DSecure&amp;diff=3992"/>
		<updated>2023-05-08T08:31:51Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=3DSecure}}&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3D Secure (3DS, Three-Domain Secure) is a messaging protocol developed by [https://www.emvco.com EMVCo] to provide a more secure online card payment process. It enables consumers to authenticate themselves with their card issuer when making card-not-present (CNP) e-commerce purchases. &lt;br /&gt;
If the card is enrolled into 3DS authentication, additional information is required to decide whether the purchase is fraudulent or not. This decision is made by the card issuer (the bank or other institution that issued the card), not by the Barion system. &lt;br /&gt;
&lt;br /&gt;
There are two major versions of the protocol: &lt;br /&gt;
* &#039;&#039;&#039;3D Secure 1&#039;&#039;&#039; is an HTTP redirect-based scenario where the customer almost always needs to provide some extra proof for the transaction. The verification is usually a password or SMS code. Card schemes will decommission 3D Secure 1 by 2021/2022. Barion does not support this old protocol.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;3D Secure 2&#039;&#039;&#039; is more sophisticated and uses additional information about the purchase, the shop, and the cardholder to make the decision. This requires more input data but provides better flow with less friction. The card issuer may verify the shopper&#039;s identity using passive, biometric, and two-factor authentication approaches. According to the [https://en.wikipedia.org/wiki/Strong_customer_authentication Strong Customer Authentication (SCA) rules of PSD2 RTS] every card issued in the EU has to be authenticated. 3D Secure 2 complies with the regulation.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=If the shopper completes a 3DSecure authentication successfully, the liability shifts from the merchant to the card issuer in case of fraud.|color=#FF7A3D}}&lt;br /&gt;
==Liability shift rules==&lt;br /&gt;
If a merchant implements 3D Secure authentication, they can avoid liability for chargebacks in case of fraud (that is, chargeback claims because of lost or stolen cards). This is called a liability shift.&lt;br /&gt;
In general, if a shopper completes a 3D Secure challenge authentication flow successfully, the liability for fraudulent chargebacks shifts from the merchant to the card issuer.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!Transaction type&lt;br /&gt;
!Liability shift to card issuer?&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions with challenge.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;card issuer applies a PSD2 exemption&#039;&#039;&#039; without the merchant requesting it. For example, issuer TRA.||style=&amp;quot;text-align:center;&amp;quot; |Yes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 PSD2 SCA out-of-scope transactions: shopper&#039;s issuer is outside of the EEA, anonymous prepaid cards up to 150€ or merchant-initiated transactions.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3D Secure 2 transactions where &#039;&#039;&#039;merchant or acquirer requests for a PSD2 exemption&#039;&#039;&#039; and the issuer grants an exemption.||style=&amp;quot;text-align:center;&amp;quot; |No&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==The payment process==&lt;br /&gt;
&lt;br /&gt;
The payment follows these steps:&lt;br /&gt;
# The shopper checks out from the merchant&#039;s website and decides to pay for the goods via Barion.&lt;br /&gt;
# Shopper is redirected to the Barion Smart Gateway.&lt;br /&gt;
# Shopper inputs card details and clicks the &#039;&#039;&#039;Pay&#039;&#039;&#039; button. &amp;lt;br/&amp;gt;--- Until this point, there is no difference in the workflow ---&lt;br /&gt;
# Barion checks whether the card the shopper used is a 3DSecure capable card and also the version the issuer supports. If the card is not &#039;&#039;&#039;3DSecure capable&#039;&#039;&#039;, the card authorization (charge) goes along without any extra steps. &lt;br /&gt;
# If the card is 3D Secure capable with 3DSecure 2, the v2 flow is started:&lt;br /&gt;
#*# Barion starts the 3DS authentication in the background and sends the relevant information about the purchase to the card issuer. From this information, the issuer decides whether the payment is secure or if the customer should be challenged in some form.&lt;br /&gt;
#*# If the result is that the customer &#039;&#039;&#039;should not be challenged&#039;&#039;&#039; (it is called frictionless flow) the customer&#039;s card is charged and the payment flow continues.&lt;br /&gt;
#*# If the result is that the issuer &#039;&#039;&#039;needs more proof&#039;&#039;&#039; from the customer a popup window is displayed. In this window, the issuer displays &#039;&#039;something&#039;&#039; for the customer. The content varies according to the issuer, and it allows the customer to provide proof (SMS, token, question).&lt;br /&gt;
#*# After the customer successfully completed the challenge the card is authenticated and the payment flow continues with the authorization of the card. The card still can be declined after successful 3DS authentication.&lt;br /&gt;
# At the end of the payment the customer is redirected to the merchant&#039;s website.&lt;br /&gt;
&lt;br /&gt;
== 3D Secure 2 ==&lt;br /&gt;
&lt;br /&gt;
The reason behind the second version was to provide a way to achieve the same level of security for authentication but with less friction. For this, a lot more information is required (or at least it is strongly recommended to provide them). This information comes from different sources:&lt;br /&gt;
* merchant&#039;s data about the customer (purchase behavior, addresses, and so on)&lt;br /&gt;
* customer&#039;s browser information (screen size, timezone, language, and so on)&lt;br /&gt;
* customer provided data (card information, e-mail address) &lt;br /&gt;
* Barion&#039;s data about the merchant, the purchase, and the customer (merchant&#039;s MCC code, name of the shop, and so on)&lt;br /&gt;
&lt;br /&gt;
The card issuer receives this information package and calculates the risk of the transaction. The result of this calculation specifies the flow:&lt;br /&gt;
* Frictionless flow: The customer is not presented with any challenge screen, no more information is needed, and authorization can take place.&lt;br /&gt;
* Challenge flow: The information is not sufficient, an additional challenge is needed to make sure that the card is not stolen.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div&amp;gt;&lt;br /&gt;
To achieve the frictionless flow the merchant has to provide as much information as possible about the purchase and the customer. This must be provided during the [[Payment-Start-v2-3DS|v2/payment/start]] API call. The properties marked as {{3dsfield}} must be specified. However, there are scenarios where not all of this data is available. In these cases there are ways to indicate the lack of information. If the merchant does not provide the necessary data the payment typically falls into the challenge flow. Ideally, we should avoid this as it causes friction and may result in the customer leaving the payment.&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Although providing this data enhances the possibility of the frictionless flow it does not make it certain. This decision is up to the card issuer, Barion does not influence it. In case of challenge flow the card issuer will provide a challenge screen that the customer must complete. This can be various things: one-time password sent via text, secret password, biometric identification, and so on.&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
* If the shopper has no phone number registered, and no sms can be sent, the authentication fails.&lt;br /&gt;
* If the user is challenged, additional user interaction is required, which results in increased abandonment. We recommend the following to reduce the churn:&lt;br /&gt;
** Send all available fields marked with the {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request&lt;br /&gt;
** Request [[ChallengePreference|TRA]] exemption. &#039;&#039;&#039;Note&#039;&#039;&#039;: If you apply for this option, you will be held liable in case of fraud.&lt;br /&gt;
&lt;br /&gt;
== Additional resources ==&lt;br /&gt;
*[[Token_payment_3D_Secure|3DSecure Token payment]]&lt;br /&gt;
*[[Token_payment_upgrade_to_3DS|How to upgrade old token payment implementations to comply with 3DS]]&lt;br /&gt;
*[[3DS_FAQ|3DSecure FAQ]]&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3991</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3991"/>
		<updated>2023-05-08T07:17:29Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* API URLs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system supports TLS v1.2 / v1.3|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only either GET or POST requests - there are no universal endpoints available.&lt;br /&gt;
Each API endpoint reference page lists the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support HTTP method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Ensure your API requests meet these requirements:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Explicitly specify &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32-character string representation, for example &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used for example to identify payments. For security and compatibility reasons the GUID is used without hyphens for most of our API.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, for example &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Avoid integer or byte evaluation when constructing the request JSON.&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Always double-check that you are connecting to the proper environment.|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, major updates to an API endpoint raise the API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. Check the reference page of a given API endpoint to see available versions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), we recommend always specifying the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
For every request sent to the Barion API, you have to authenticate yourself. Use a different type of authentication depending on the type of endpoint.&lt;br /&gt;
&lt;br /&gt;
==== Shop-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
Shop-level endpoints can be authenticated using the shop&#039;s unique &amp;lt;tt&amp;gt;POSKey&amp;lt;/tt&amp;gt;. For more details on using and obtaining the POS key, see [[Barion Shop Authentication]].&lt;br /&gt;
&lt;br /&gt;
==== Wallet-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
You can authenticate yourself to endpoints requiring wallet-level authentication via an API key called a &amp;lt;tt&amp;gt;Wallet key&amp;lt;/tt&amp;gt;. For more information on using this API key, see [[Barion Wallet Authentication]].&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however you can find one property in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId ||  If the error is related to a business process that involves a given payment, the public identifier of the payment is supplied here. This property is not present for all errors.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The following example shows an error case where the shop does not have an account with the currency it specified when trying to create a payment.&lt;br /&gt;
This is a validation error, so the payment identifier is not applicable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingCurrency&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;Payment is not supported&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;Payment is not supported. The POS doesn’t have an account that supports EUR!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following example shows a case where after several successful token charges, the customer deleted their payment card from the Barion system, so the subsequent attempt failed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;OriginalPaymentCardDoesNotExist&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The original payment card does not exist!&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The payment card that was used for the original payment with recurrence ID &#039;TEST-01&#039; no longer exists in the system!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Refer to the [[Security Measures]] for more information on IT security before starting to code.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3990</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3990"/>
		<updated>2023-05-08T07:15:48Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Data and content types */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system supports TLS v1.2 / v1.3|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only either GET or POST requests - there are no universal endpoints available.&lt;br /&gt;
Each API endpoint reference page lists the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support HTTP method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Ensure your API requests meet these requirements:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Explicitly specify &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32-character string representation, for example &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used for example to identify payments. For security and compatibility reasons the GUID is used without hyphens for most of our API.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, for example &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Avoid integer or byte evaluation when constructing the request JSON.&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Always double-check that you are connecting to the proper environment.&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, major updates to an API endpoint raise the API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. Check the reference page of a given API endpoint to see available versions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), we recommend always specifying the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
For every request sent to the Barion API, you have to authenticate yourself. Use a different type of authentication depending on the type of endpoint.&lt;br /&gt;
&lt;br /&gt;
==== Shop-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
Shop-level endpoints can be authenticated using the shop&#039;s unique &amp;lt;tt&amp;gt;POSKey&amp;lt;/tt&amp;gt;. For more details on using and obtaining the POS key, see [[Barion Shop Authentication]].&lt;br /&gt;
&lt;br /&gt;
==== Wallet-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
You can authenticate yourself to endpoints requiring wallet-level authentication via an API key called a &amp;lt;tt&amp;gt;Wallet key&amp;lt;/tt&amp;gt;. For more information on using this API key, see [[Barion Wallet Authentication]].&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however you can find one property in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId ||  If the error is related to a business process that involves a given payment, the public identifier of the payment is supplied here. This property is not present for all errors.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The following example shows an error case where the shop does not have an account with the currency it specified when trying to create a payment.&lt;br /&gt;
This is a validation error, so the payment identifier is not applicable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingCurrency&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;Payment is not supported&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;Payment is not supported. The POS doesn’t have an account that supports EUR!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following example shows a case where after several successful token charges, the customer deleted their payment card from the Barion system, so the subsequent attempt failed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;OriginalPaymentCardDoesNotExist&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The original payment card does not exist!&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The payment card that was used for the original payment with recurrence ID &#039;TEST-01&#039; no longer exists in the system!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Refer to the [[Security Measures]] for more information on IT security before starting to code.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3989</id>
		<title>Calling the API</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Calling_the_API&amp;diff=3989"/>
		<updated>2023-05-08T07:07:55Z</updated>

		<summary type="html">&lt;p&gt;Bozag: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Calling the Barion API}}&lt;br /&gt;
&lt;br /&gt;
== The Barion API ==&lt;br /&gt;
&lt;br /&gt;
Barion offers you a RESTful API service to communicate with your web or mobile merchant services. Learn more about RESTful behavior [https://en.wikipedia.org/wiki/Representational_state_transfer in the original Wikipedia article].&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=All communication must be done over HTTPS. The Barion system supports TLS v1.2 / v1.3|color=#FF7A3D}}&lt;br /&gt;
&lt;br /&gt;
== Protocols and communication ==&lt;br /&gt;
&lt;br /&gt;
The Barion API communicates via standard &#039;&#039;&#039;HTTP1.1&#039;&#039;&#039; GET or POST requests. A given API endpoint accepts only either GET or POST requests - there are no universal endpoints available.&lt;br /&gt;
Each API endpoint reference page lists the path of the API endpoint and the HTTP method it accepts.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If the caller uses an incorrect method, the system responds with a JSON error message.&lt;br /&gt;
&lt;br /&gt;
Example: calling a POST endpoint with a GET request&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;json&amp;quot;&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Message&amp;quot;: &amp;quot;The requested resource does not support HTTP method &#039;GET&#039;.&amp;quot;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Data and content types ==&lt;br /&gt;
&lt;br /&gt;
The API sends and receives all content in standard &#039;&#039;&#039;JSON&#039;&#039;&#039; (JavaScript Object Notation) string format.&lt;br /&gt;
&lt;br /&gt;
Ensure your API requests meet these requirements:&lt;br /&gt;
* JSON strings are UTF-8 encoded.&lt;br /&gt;
* The MIME type of the request sent to the API is defined as &amp;lt;code&amp;gt;application/json&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Explicitly specify &amp;lt;code&amp;gt;Content-length&amp;lt;/code&amp;gt; in all HTTP request headers.&lt;br /&gt;
&lt;br /&gt;
The data types used in the API communication are the following:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Data type&lt;br /&gt;
! Type description&lt;br /&gt;
|-&lt;br /&gt;
| string&lt;br /&gt;
| Standard character string. The Barion API uses UTF-8 encoding.&lt;br /&gt;
|-&lt;br /&gt;
| int&lt;br /&gt;
| 32-bit signed integer format&lt;br /&gt;
|-&lt;br /&gt;
| GUID (Global Unique Identifier)&lt;br /&gt;
| A 128-bit long hexadecimal identifier with 32-character string representation, for example &#039;&#039;21EC2020-3AEA-4069-A2DD-08002B30309D&#039;&#039;. Its value is always unique in the Barion system. This is used for example to identify payments. For security and compatibility reasons the GUID is used without hyphens for most of our API.&lt;br /&gt;
|-&lt;br /&gt;
| DateTime&lt;br /&gt;
| Date and time values, represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, for example &#039;&#039;2014-12-06T08:35:46Z&#039;&#039;. All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| TimeSpan&lt;br /&gt;
| A time range value represented in a string format of the &#039;&#039;&#039;ISO-8601&#039;&#039;&#039; standard, like this: &#039;&#039;3.14:15:28&#039;&#039; (three days, fourteen hours, fifteen minutes, twenty-eight seconds). All API call responses contain datetimes as strings.&lt;br /&gt;
|-&lt;br /&gt;
| bool&lt;br /&gt;
| Boolean &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; values. &lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Avoid integer or byte evaluation when constructing the request JSON!&lt;br /&gt;
|-&lt;br /&gt;
| byte&lt;br /&gt;
| Byte representation of an enumeration value. This is only for internal use in the Barion system, API call responses always contain the string representation.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== API URLs ==&lt;br /&gt;
&lt;br /&gt;
The base URL for the Barion API depends on the environment you are connecting to.&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Live (production)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.barion.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Base URL for API requests in the &#039;&#039;&#039;Sandbox (test)&#039;&#039;&#039; environment: &amp;lt;code&amp;gt;https://api.test.barion.com&amp;lt;/code&amp;gt; (learn more about the Sandbox environment [[Sandbox|here]])&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Always double-check that you are connecting to the proper environment.&lt;br /&gt;
&lt;br /&gt;
== API versioning ==&lt;br /&gt;
&lt;br /&gt;
To avoid breaking changes, major updates to an API endpoint raise the API version. At the moment, the Barion API offers two different API versions (noted &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt;). Some API endpoints are only available in v1 or v2. Check the reference page of a given API endpoint to see available versions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Though version numbers can be omitted from the endpoint path (such requests always fall back to &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt;), we recommend always specifying the API version when sending requests to the Barion API to avoid confusion.&lt;br /&gt;
&lt;br /&gt;
Example paths:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/Transaction/List&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - implicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint (version number is omitted from path)&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v1/Transfer/Send&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v1&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;https://api.barion.com/v2/Payment/Start&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; - explicit call to a &amp;lt;code&amp;gt;v2&amp;lt;/code&amp;gt; endpoint&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
For every request sent to the Barion API, you have to authenticate yourself. Use a different type of authentication depending on the type of endpoint.&lt;br /&gt;
&lt;br /&gt;
==== Shop-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
Shop-level endpoints can be authenticated using the shop&#039;s unique &amp;lt;tt&amp;gt;POSKey&amp;lt;/tt&amp;gt;. For more details on using and obtaining the POS key, see [[Barion Shop Authentication]].&lt;br /&gt;
&lt;br /&gt;
==== Wallet-level endpoints ====&lt;br /&gt;
&lt;br /&gt;
You can authenticate yourself to endpoints requiring wallet-level authentication via an API key called a &amp;lt;tt&amp;gt;Wallet key&amp;lt;/tt&amp;gt;. For more information on using this API key, see [[Barion Wallet Authentication]].&lt;br /&gt;
&lt;br /&gt;
== Handling the response ==&lt;br /&gt;
The structure of the response varies from endpoint to endpoint however you can find one property in all of them. Every API response contains an &amp;lt;code&amp;gt;Errors&amp;lt;/code&amp;gt; array. If this array is empty then the request was processed successfully. This array can contain multiple errors so make sure that the integration is prepared for this. The errors have the following fields:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
! FieldName || Description&lt;br /&gt;
|-&lt;br /&gt;
| ErrorCode || The error code of the payment, can be interpreted as an error Id.&lt;br /&gt;
|-&lt;br /&gt;
| Title|| The title of the error, is a more readable form of the error.&lt;br /&gt;
|-&lt;br /&gt;
| Description|| The description of the error, more information about the error.&lt;br /&gt;
|-&lt;br /&gt;
| EndPoint || The URL of the API endpoint to help the reproduction of the error scenario.&lt;br /&gt;
|-&lt;br /&gt;
| AuthData || The e-mail address of the caller to help the reproduction of the error scenario. &lt;br /&gt;
|-&lt;br /&gt;
| HappenedAt || The timestamp of the response.&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId ||  If the error is related to a business process that involves a given payment, the public identifier of the payment is supplied here. This property is not present for all errors.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example error response&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The following example shows an error case where the shop does not have an account with the currency it specified when trying to create a payment.&lt;br /&gt;
This is a validation error, so the payment identifier is not applicable.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;NotExistingCurrency&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;Payment is not supported&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;Payment is not supported. The POS doesn’t have an account that supports EUR!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following example shows a case where after several successful token charges, the customer deleted their payment card from the Barion system, so the subsequent attempt failed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=json&amp;gt;&lt;br /&gt;
{&lt;br /&gt;
  &amp;quot;Errors&amp;quot;: [&lt;br /&gt;
    {&lt;br /&gt;
      &amp;quot;ErrorCode&amp;quot;: &amp;quot;OriginalPaymentCardDoesNotExist&amp;quot;,&lt;br /&gt;
      &amp;quot;Title&amp;quot;: &amp;quot;The original payment card does not exist!&amp;quot;,&lt;br /&gt;
      &amp;quot;Description&amp;quot;: &amp;quot;The payment card that was used for the original payment with recurrence ID &#039;TEST-01&#039; no longer exists in the system!&amp;quot;,&lt;br /&gt;
      &amp;quot;EndPoint&amp;quot;: &amp;quot;https://api.barion.com/v2/Payment/Start&amp;quot;,&lt;br /&gt;
      &amp;quot;AuthData&amp;quot;: &amp;quot;shop@example.com&amp;quot;,&lt;br /&gt;
      &amp;quot;HappenedAt&amp;quot;: &amp;quot;2017-02-06T09:48:13.7694921Z&amp;quot;&lt;br /&gt;
    }&lt;br /&gt;
  ]&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Security==&lt;br /&gt;
Refer to the [[Security Measures]] for more information on IT security before starting to code.&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3988</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=3988"/>
		<updated>2023-05-03T06:44:38Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* 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) that will be displayed on the Barion Smart Gateway. If the intended name is already taken, you must provide a new one.&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;
|| A brief description of the product or service provided by the POS. This is required for shop approval.&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 logo of the POS, which is displayed on the gateway and is required for shop approval. Do not use stock photos downloaded from the internet. The 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;
|| The category or categories to which the POS belongs. 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 details 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 details of the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact || [[CustomerServiceContact]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| The contact details of your customer service desk, where your customers can contact you.&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;
|| The expected Barion turnover in the primary currency.&lt;br /&gt;
&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;
|| The 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;
| FullPixelImplemented || bool || &lt;br /&gt;
* Required&lt;br /&gt;
&lt;br /&gt;
|| Specifies whether Barion Full Pixel is implemented.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| UseForEInvoicing || bool || &lt;br /&gt;
* Required&lt;br /&gt;
|| Set to True if the shop is used 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 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 a wallet to distinguish shops arriving through different channels. To obtain the top-up code for a particular Barion wallet, simply visit this link: &amp;lt;code&amp;gt;https://secure.barion.com/Referral&amp;lt;/code&amp;gt;, and log in using your Barion account credentials. The 9-digit number at the end of the link, which appears as the query string parameter, identifies the specific wallet you wish to refer to.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| NoteForApproval || String || &lt;br /&gt;
&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.&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 css 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ExpectedTurnover&amp;diff=3978</id>
		<title>ExpectedTurnover</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ExpectedTurnover&amp;diff=3978"/>
		<updated>2023-05-02T14:08:40Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Property list */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Expected Turnover structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the details for the expected income 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;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| ExpectedTurnover&lt;br /&gt;
| int&lt;br /&gt;
| The possible values are:&lt;br /&gt;
For CZK:&lt;br /&gt;
* 1 - 8,000 CZK / month&lt;br /&gt;
* 8,001 - 80,000 CZK / month&lt;br /&gt;
* 80,001 - 800,000 CZK / month&lt;br /&gt;
* 800,001 - 2,200,000 CZK / month&lt;br /&gt;
* 2,200,001 - 7,700,000 CZK / month&lt;br /&gt;
* 7,700,001 CZK / month or more&lt;br /&gt;
&lt;br /&gt;
For EUR:&lt;br /&gt;
* 1 - 300 EUR / month&lt;br /&gt;
* 301 - 3,000 EUR / month&lt;br /&gt;
* 3,001 - 30,000 EUR / month&lt;br /&gt;
* 30,001 - 90,000 EUR / month&lt;br /&gt;
* 90,001 - 300,000 EUR / month&lt;br /&gt;
* 300,001 EUR / month or more&lt;br /&gt;
&lt;br /&gt;
For HUF: &lt;br /&gt;
* 1 - 100,000 HUF / month&lt;br /&gt;
* 100,001 – 1,000,000 HUF / month&lt;br /&gt;
* 1,000,001 – 10,000,000 HUF / month&lt;br /&gt;
* 10,000,001 – 29,000,000 HUF / month&lt;br /&gt;
* 29,000,001 – 99,000,000 HUF / month&lt;br /&gt;
* 99,000,001 HUF / month or more&lt;br /&gt;
&lt;br /&gt;
For USD:&lt;br /&gt;
* 1 - 350 USD / month&lt;br /&gt;
* 351 - 3,500 USD / month&lt;br /&gt;
* 3,501 - 35,000 USD / month&lt;br /&gt;
* 35,001 - 100,000 USD / month&lt;br /&gt;
* 100,001 - 345,000 USD / month&lt;br /&gt;
* 345,001 USD / month or more&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| Expected Barion turnover in the primary currency.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ShopCategory&amp;diff=3977</id>
		<title>ShopCategory</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ShopCategory&amp;diff=3977"/>
		<updated>2023-05-02T13:45:28Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* 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-GetState-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;
| 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=ExpectedTurnover&amp;diff=3976</id>
		<title>ExpectedTurnover</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=ExpectedTurnover&amp;diff=3976"/>
		<updated>2023-05-02T13:42:58Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* API usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Expected Turnover structure =&lt;br /&gt;
&lt;br /&gt;
This structure represents the details for the expected income 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;
&lt;br /&gt;
== Property list ==&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| ExpectedTurnover&lt;br /&gt;
| int&lt;br /&gt;
| The possible values are:&lt;br /&gt;
* 1-100 000 HUF / month&lt;br /&gt;
* 100 001 – 1 000 000 HUF / month&lt;br /&gt;
* 1 000 001 – 10 000 000 HUF / month&lt;br /&gt;
* 10 000 001 – 29 000 000 HUF / month&lt;br /&gt;
* 29 000 001 – 99 000 000 HUF / month&lt;br /&gt;
* 99 000 001 HUF / month or more&lt;br /&gt;
| Expected Barion turnover in the primary currency.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3975</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=3975"/>
		<updated>2023-05-02T13:41:03Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* Output 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 HTTP 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Create-v1&amp;diff=3973</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=3973"/>
		<updated>2023-05-02T13:40:38Z</updated>

		<summary type="html">&lt;p&gt;Bozag: /* 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 HTTP 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 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>Bozag</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Pos-Get-v1&amp;diff=3972</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=3972"/>
		<updated>2023-05-02T13:40:33Z</updated>

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

		<summary type="html">&lt;p&gt;Bozag: /* Output properties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
{{PageTitle|title=Barion API: Request the current state of a POS}}&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;margin-left:2em;&amp;quot; align=&amp;quot;right&amp;quot;&lt;br /&gt;
| __TOC__&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=GET&lt;br /&gt;
|uri=/v1/Pos/PosPublicKey&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Use the &amp;lt;code&amp;gt;Pos/ShopPublicKey&amp;lt;/code&amp;gt; API endpoint to query the details and current state of a point of sale (POS).&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[POS_create_v1|Creating a POS in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v1&amp;lt;/span&amp;gt; This API endpoint is available in &#039;&#039;&#039;API v1&#039;&#039;&#039; only.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Wallet Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Query string parameters for getting a shop&#039;s state ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| PublicKey &lt;br /&gt;
| string&lt;br /&gt;
| The public key of the POS.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Output properties ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable api-table&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Query string parameter&lt;br /&gt;
! Parameter type&lt;br /&gt;
! Parameter description&lt;br /&gt;
|-&lt;br /&gt;
| Name&lt;br /&gt;
| string&lt;br /&gt;
| The unique name of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| PublicKey &lt;br /&gt;
| Guid &lt;br /&gt;
| The public key of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| SecretKey &lt;br /&gt;
| Guid&lt;br /&gt;
| The secret POS key of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| Status &lt;br /&gt;
| [[ShopStatus]] &lt;br /&gt;
| The status of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| IsOpen &lt;br /&gt;
| bool &lt;br /&gt;
| Information on whether the shop is open.&lt;br /&gt;
|-&lt;br /&gt;
| Description&lt;br /&gt;
| string &lt;br /&gt;
| The short description of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| Logo &lt;br /&gt;
| string&lt;br /&gt;
| The logo of the shop, is sent as a URL.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| BusinessContact &lt;br /&gt;
| [[BusinessContact]]&lt;br /&gt;
| The business contact details of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| TechnicalContact &lt;br /&gt;
| [[TechnicalContact]]&lt;br /&gt;
| The technical contact details of the shop.&lt;br /&gt;
|-&lt;br /&gt;
| CustomerServiceContact &lt;br /&gt;
| [[CustomerServiceContact]]&lt;br /&gt;
| The contact details of your customer service desk, where your customers can contact you.&lt;br /&gt;
|-&lt;br /&gt;
| CallBackUrl  &lt;br /&gt;
| string &lt;br /&gt;
| The URL where Barion sends a request whenever the shop state changes.&lt;br /&gt;
|-&lt;br /&gt;
| ReferenceId &lt;br /&gt;
| string &lt;br /&gt;
| The top-up code of the wallet. Used to distinguish shops arriving through different channels.&lt;br /&gt;
|-&lt;br /&gt;
| CustomTemplate &lt;br /&gt;
| string &lt;br /&gt;
| The custom template you used to modify the displayed data.&lt;br /&gt;
|-&lt;br /&gt;
| CustomCSS &lt;br /&gt;
| string &lt;br /&gt;
| The custom CSS you used to modify the gateway design.&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bozag</name></author>
	</entry>
</feed>