<?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=Dezsit%40barion.dev</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=Dezsit%40barion.dev"/>
	<link rel="alternate" type="text/html" href="https://docs.barion.com/Special:Contributions/Dezsit@barion.dev"/>
	<updated>2026-11-22T05:46:11Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://docs.barion.com/index.php?title=Barion_Shop_Authentication&amp;diff=4960</id>
		<title>Barion Shop Authentication</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Barion_Shop_Authentication&amp;diff=4960"/>
		<updated>2026-10-28T09:12:42Z</updated>

		<summary type="html">&lt;p&gt;Dezsit@barion.dev: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= What is shop authentication? =&lt;br /&gt;
&lt;br /&gt;
The API endpoints related to handling a shop&#039;s payment flow are accessible using the shop&#039;s own unique API key, known as &amp;lt;i&amp;gt;POS key&amp;lt;/i&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
For a full list of such endpoints see [[List_of_API_endpoints|List of Barion API endpoints]].&lt;br /&gt;
&lt;br /&gt;
Optionally, the shop can also use an &amp;lt;i&amp;gt;HMAC key&amp;lt;/i&amp;gt; to sign its API requests and to verify the messages Barion sends to it. See [[#Message signature (HMAC)|Message signature (HMAC)]].&lt;br /&gt;
&lt;br /&gt;
= Using POS keys =&lt;br /&gt;
&lt;br /&gt;
To use an endpoint which requires shop-level authentication, pass your Barion shop&#039;s POS key as the &#039;&#039;&#039;x-pos-key&#039;&#039;&#039; header parameter.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=&amp;lt;tt&amp;gt;GET&amp;lt;/tt&amp;gt; API endpoints below v4 also accept the &amp;lt;code&amp;gt;PosKey&amp;lt;/code&amp;gt; property as a query parameter.|color=#038Ed3}}&lt;br /&gt;
== Errors ==&lt;br /&gt;
&lt;br /&gt;
An invalid key generates an &amp;lt;code&amp;gt;AuthenticationFailed&amp;lt;/code&amp;gt; error.&lt;br /&gt;
&lt;br /&gt;
= Managing POS keys =&lt;br /&gt;
&lt;br /&gt;
A POS key is automatically generated for your shop when you create it, and cannot be changed later. To obtain it, either&lt;br /&gt;
* get the key from the confirmation e-mail that was sent to you when you opened the shop, or&lt;br /&gt;
* go to the shop&#039;s detail page on the [https://secure.barion.com Barion secure site] and use the &amp;lt;i&amp;gt;Secret key&amp;lt;/i&amp;gt; value (Shops -&amp;gt; Actions -&amp;gt; Details)&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=The test and live environment are completely separate environments, you need to create different shops. Make sure that you use the POSkey and not the public key:&lt;br /&gt;
&lt;br /&gt;
[[File:Poskey.jpg]] |color=#038Ed3}}&lt;br /&gt;
&lt;br /&gt;
= Message signature (HMAC) =&lt;br /&gt;
&lt;br /&gt;
A shop can have an HMAC key in addition to its POS key. While the shop has an &amp;lt;b&amp;gt;active&amp;lt;/b&amp;gt; HMAC key:&lt;br /&gt;
* every API request authenticated with the shop&#039;s POS key &amp;lt;b&amp;gt;must be signed&amp;lt;/b&amp;gt; with the HMAC key, otherwise Barion rejects it,&lt;br /&gt;
* Barion signs its responses to these requests, and&lt;br /&gt;
* Barion signs the payment IPN (callback) messages it sends to the shop.&lt;br /&gt;
&lt;br /&gt;
This lets your server verify that a message really comes from Barion and was not changed on the way, and lets Barion verify that a request really comes from your shop.&lt;br /&gt;
&lt;br /&gt;
The signature is an HMAC-SHA512 computed with the shop&#039;s HMAC key. It is sent in HTTP headers, so the request and response bodies do not change.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=IMPORTANT|text=Activating a key takes effect &amp;lt;b&amp;gt;immediately&amp;lt;/b&amp;gt;: from that moment, every unsigned or wrongly signed request of the shop is rejected, payment start included. Signature headers are ignored while the shop has no active key, so start signing your requests &amp;lt;b&amp;gt;before&amp;lt;/b&amp;gt; you activate the key.|color=#D73E48}}&lt;br /&gt;
&lt;br /&gt;
== Managing HMAC keys ==&lt;br /&gt;
&lt;br /&gt;
HMAC keys are managed on the [https://secure.barion.com Barion secure site], on the shop&#039;s security page (Shops -&amp;gt; Actions -&amp;gt; Settings -&amp;gt; Security -&amp;gt; Manage).&lt;br /&gt;
&lt;br /&gt;
* A shop can have at most 2 HMAC keys. To generate a third one, delete one of the two first.&lt;br /&gt;
* A new key is created &amp;lt;b&amp;gt;inactive&amp;lt;/b&amp;gt;. Mark it as &amp;lt;i&amp;gt;Active&amp;lt;/i&amp;gt; when your server is ready.&lt;br /&gt;
* At most one key is active at a time. If no key is active, nothing is signed and no signature is checked.&lt;br /&gt;
* The active key cannot be deleted. Deactivate it, or activate the other key, first.&lt;br /&gt;
* The key is shown and copied as a base64 string. &amp;lt;b&amp;gt;Decode it from base64&amp;lt;/b&amp;gt; and use the resulting 64 bytes as the HMAC key.&lt;br /&gt;
&lt;br /&gt;
{{NotificationBox|title=NOTE|text=Keep the HMAC key on your server only, like the POS key. If you think a key is compromised, generate a new one, switch to it and delete the old one.|color=#038Ed3}}&lt;br /&gt;
&lt;br /&gt;
== Signature headers ==&lt;br /&gt;
&lt;br /&gt;
Every signed request and response carries these three headers:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Header !! Content&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;x-timestamp&#039;&#039;&#039; || The time of signing as a Unix timestamp in seconds (UTC), e.g. &amp;lt;code&amp;gt;1760968800&amp;lt;/code&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;x-nonce&#039;&#039;&#039; || A GUID, e.g. &amp;lt;code&amp;gt;3f2b6c1e-8d4a-4b9e-9a51-0c7d2e6f1a84&amp;lt;/code&amp;gt;. In a request it must be new for every request. In a response it is the nonce of the request being answered.&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;x-signature-sha512&#039;&#039;&#039; || The HMAC-SHA512 of the signed text (see below), base64-encoded.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== The signed text ==&lt;br /&gt;
&lt;br /&gt;
The signature is computed over a text made of the following parts, joined with a single line feed character (&amp;lt;code&amp;gt;\n&amp;lt;/code&amp;gt;, LF, no carriage return). The text is UTF-8 encoded before signing.&lt;br /&gt;
&lt;br /&gt;
=== Requests (your API requests and Barion&#039;s IPN) ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
{x-timestamp}\n{x-nonce}\n{HTTP method}\n{path and query}\n{body}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;HTTP method&#039;&#039;&#039;: in upper case, e.g. &amp;lt;code&amp;gt;POST&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;GET&amp;lt;/code&amp;gt;.&lt;br /&gt;
* &#039;&#039;&#039;path and query&#039;&#039;&#039;: the path and the query string of the URL as it appears on the request line, &#039;&#039;&#039;in lower case&#039;&#039;&#039;, e.g. &amp;lt;code&amp;gt;/v2/payment/start&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;/v2/payment/getpaymentstate?paymentid=...&amp;lt;/code&amp;gt;. The scheme, the host and the port are not part of it.&lt;br /&gt;
* &#039;&#039;&#039;body&#039;&#039;&#039;: the exact request body, byte for byte as it is sent. The body must be UTF-8 (a leading byte order mark is ignored). For a request without a body (e.g. &amp;lt;code&amp;gt;GET&amp;lt;/code&amp;gt;) it is an empty string, so the text ends with the line feed after the path.&lt;br /&gt;
&lt;br /&gt;
=== Responses (Barion&#039;s answers to your signed requests) ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
{x-timestamp}\n{x-nonce}\n{HTTP status code}\n{body}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;x-nonce&#039;&#039;&#039;: the nonce of &amp;lt;b&amp;gt;your request&amp;lt;/b&amp;gt; that the response answers. It is echoed back in the response&#039;s &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; header, and binds the response to your request.&lt;br /&gt;
* &#039;&#039;&#039;HTTP status code&#039;&#039;&#039;: as a number, e.g. &amp;lt;code&amp;gt;200&amp;lt;/code&amp;gt;.&lt;br /&gt;
* &#039;&#039;&#039;body&#039;&#039;&#039;: the exact response body as received.&lt;br /&gt;
&lt;br /&gt;
Responses are signed only when the request was signed correctly.&lt;br /&gt;
&lt;br /&gt;
== Signing your API requests ==&lt;br /&gt;
&lt;br /&gt;
# Generate a new GUID for &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; and take the current Unix time in seconds for &amp;lt;code&amp;gt;x-timestamp&amp;lt;/code&amp;gt;.&lt;br /&gt;
# Build the signed text from the timestamp, the nonce, the method, the path and query (in lower case), and the exact body you are going to send.&lt;br /&gt;
# Compute the HMAC-SHA512 of the UTF-8 text with the base64-decoded HMAC key, and base64-encode the result.&lt;br /&gt;
# Send the request with the &amp;lt;code&amp;gt;x-pos-key&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;x-timestamp&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;x-signature-sha512&amp;lt;/code&amp;gt; headers.&lt;br /&gt;
&lt;br /&gt;
Barion checks that:&lt;br /&gt;
* the timestamp is within 5 minutes of the server time, in either direction,&lt;br /&gt;
* the nonce has not been used by the shop before (so a captured request cannot be replayed),&lt;br /&gt;
* the signature matches the request signed with the active key.&lt;br /&gt;
&lt;br /&gt;
== Verifying Barion&#039;s messages ==&lt;br /&gt;
&lt;br /&gt;
For a response to your request, and for a payment IPN message:&lt;br /&gt;
# Read the &amp;lt;code&amp;gt;x-timestamp&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;x-signature-sha512&amp;lt;/code&amp;gt; headers.&lt;br /&gt;
# Build the signed text: for a response with the response&#039;s status code and body, for an IPN with &amp;lt;code&amp;gt;POST&amp;lt;/code&amp;gt;, the path and query of your callback URL as it was called (including the &amp;lt;code&amp;gt;paymentId&amp;lt;/code&amp;gt; query parameter), in lower case, and the request body.&lt;br /&gt;
# Compute the HMAC-SHA512 with your active key and compare it with &amp;lt;code&amp;gt;x-signature-sha512&amp;lt;/code&amp;gt;. Use a constant-time comparison.&lt;br /&gt;
# Reject the message if the signature does not match. We also recommend rejecting it if the timestamp is more than a few minutes off your server time, and, for an IPN, if you have already processed its nonce.&amp;lt;br /&amp;gt;&lt;br /&gt;
== Example ==&lt;br /&gt;
&lt;br /&gt;
Signing a request in C#:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
using System;&lt;br /&gt;
using System.Security.Cryptography;&lt;br /&gt;
using System.Text;&lt;br /&gt;
&lt;br /&gt;
static string Sign(string base64HmacKey, string timestamp, string nonce, string method, string pathAndQuery, string body)&lt;br /&gt;
{&lt;br /&gt;
    // The path and query are signed in lower case; the body is used as it is.&lt;br /&gt;
    string text = string.Join(&amp;quot;\n&amp;quot;, timestamp, nonce, method.ToUpperInvariant(), pathAndQuery.ToLowerInvariant(), body ?? &amp;quot;&amp;quot;);&lt;br /&gt;
&lt;br /&gt;
    using (var hmac = new HMACSHA512(Convert.FromBase64String(base64HmacKey)))&lt;br /&gt;
    {&lt;br /&gt;
        return Convert.ToBase64String(hmac.ComputeHash(Encoding.UTF8.GetBytes(text)));&lt;br /&gt;
    }&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
string timestamp = DateTimeOffset.UtcNow.ToUnixTimeSeconds().ToString();&lt;br /&gt;
string nonce = Guid.NewGuid().ToString();&lt;br /&gt;
string body = &amp;quot;{\&amp;quot;PaymentRequestId\&amp;quot;:\&amp;quot;...\&amp;quot;}&amp;quot;;&lt;br /&gt;
string signature = Sign(hmacKey, timestamp, nonce, &amp;quot;POST&amp;quot;, &amp;quot;/v2/Payment/Start&amp;quot;, body);&lt;br /&gt;
&lt;br /&gt;
// Send with the headers: x-pos-key, x-timestamp: {timestamp}, x-nonce: {nonce}, x-signature-sha512: {signature}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test vectors ==&lt;br /&gt;
&lt;br /&gt;
Use these known values to check your implementation. The bodies are made up and are not real requests or responses.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;HMAC key&#039;&#039;&#039; (base64): &amp;lt;code&amp;gt;AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1Njc4OTo7PD0+Pw==&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the signed texts below, &amp;lt;code&amp;gt;\n&amp;lt;/code&amp;gt; stands for a single line feed character (LF, no carriage return). It is shown at the end of the line where it belongs; the last line has none, unless the body is empty.&lt;br /&gt;
&lt;br /&gt;
=== 1. A request with a JSON body ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Method:        POST&lt;br /&gt;
URL:           https://api.barion.com/v2/Payment/Start&lt;br /&gt;
x-timestamp:   1760968800&lt;br /&gt;
x-nonce:       3f2b6c1e-8d4a-4b9e-9a51-0c7d2e6f1a84&lt;br /&gt;
Body:          {&amp;quot;PaymentRequestId&amp;quot;:&amp;quot;order-1001&amp;quot;,&amp;quot;Total&amp;quot;:10.50}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed text (note that the path is in lower case, and the body is used as it is):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
1760968800\n&lt;br /&gt;
3f2b6c1e-8d4a-4b9e-9a51-0c7d2e6f1a84\n&lt;br /&gt;
POST\n&lt;br /&gt;
/v2/payment/start\n&lt;br /&gt;
{&amp;quot;PaymentRequestId&amp;quot;:&amp;quot;order-1001&amp;quot;,&amp;quot;Total&amp;quot;:10.50}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed bytes: the UTF-8 encoding of the text above (118 bytes), in hex:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
313736303936383830300a33663262366331652d386434612d346239652d396135312d3063376432653666316138340a504f53540a2f76322f7061796d656e742f73746172740a7b225061796d656e74526571756573744964223a226f726465722d31303031222c22546f74616c223a31302e35307d&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
x-signature-sha512:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
AMm7BeXNw0JAs8pxAhemnOQzhlWDz+o/nB85yKPim0DYSCdgpswBQFyQlhFrDwb/MrPFWlcwgDGa+DFGsNJvuQ==&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 2. A GET request without a body ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Method:        GET&lt;br /&gt;
URL:           https://api.barion.com/v4/Payment/GetPaymentState?PaymentId=3F2B6C1E-8D4A-4B9E-9A51-0C7D2E6F1A84&lt;br /&gt;
x-timestamp:   1760968800&lt;br /&gt;
x-nonce:       9d6a1f0e-2b7c-4c35-8e19-5a4b3c2d1e0f&lt;br /&gt;
Body:          (none)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed text. The path and the whole query string are in lower case, including the value of &amp;lt;code&amp;gt;PaymentId&amp;lt;/code&amp;gt;. The text ends with the line feed after the query string, because the body is empty:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
1760968800\n&lt;br /&gt;
9d6a1f0e-2b7c-4c35-8e19-5a4b3c2d1e0f\n&lt;br /&gt;
GET\n&lt;br /&gt;
/v4/payment/getpaymentstate?paymentid=3f2b6c1e-8d4a-4b9e-9a51-0c7d2e6f1a84\n&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed bytes: the UTF-8 encoding of the text above (127 bytes), in hex:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
313736303936383830300a39643661316630652d326237632d346333352d386531392d3561346233633264316530660a4745540a2f76342f7061796d656e742f6765747061796d656e7473746174653f7061796d656e7469643d33663262366331652d386434612d346239652d396135312d3063376432653666316138340a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
x-signature-sha512:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
z8YFYV7YKs4OY4eVfd0BSc1LJMkbmBQRFuNXFO+KiAujB7eR1oHwicRTepgVSDqzHoHow/SDoKTdX2IpNMvB8A==&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 3. A response ===&lt;br /&gt;
&lt;br /&gt;
This is Barion&#039;s answer to the request in example 1. It carries the &amp;lt;b&amp;gt;nonce of the request&amp;lt;/b&amp;gt; in its &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; header, and it has its own timestamp.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
HTTP status:   200&lt;br /&gt;
x-timestamp:   1760968801&lt;br /&gt;
x-nonce:       3f2b6c1e-8d4a-4b9e-9a51-0c7d2e6f1a84&lt;br /&gt;
Body:          {&amp;quot;PaymentId&amp;quot;:&amp;quot;3f2b6c1e8d4a4b9e9a510c7d2e6f1a84&amp;quot;,&amp;quot;Status&amp;quot;:&amp;quot;Prepared&amp;quot;}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed text. There is no method and no path in a response, only the status code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
1760968801\n&lt;br /&gt;
3f2b6c1e-8d4a-4b9e-9a51-0c7d2e6f1a84\n&lt;br /&gt;
200\n&lt;br /&gt;
{&amp;quot;PaymentId&amp;quot;:&amp;quot;3f2b6c1e8d4a4b9e9a510c7d2e6f1a84&amp;quot;,&amp;quot;Status&amp;quot;:&amp;quot;Prepared&amp;quot;}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed bytes: the UTF-8 encoding of the text above (120 bytes), in hex:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
313736303936383830310a33663262366331652d386434612d346239652d396135312d3063376432653666316138340a3230300a7b225061796d656e744964223a223366326236633165386434613462396539613531306337643265366631613834222c22537461747573223a225072657061726564227d&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
x-signature-sha512:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
7C8tktY2Bs91dyw7L/fLKwDQCyriGiVOEvbrurn79sLkT2Q93KDVw7c/LEz4VWIqhZOpzLQbs7a6UCo5BZALyQ==&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 4. A payment IPN message ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Method:        POST&lt;br /&gt;
URL called:    https://shop.example/hu/DemoClub/Callback?paymentId=4d924e8da6cbf11199f4001dd8b71d1a&lt;br /&gt;
x-timestamp:   1760968802&lt;br /&gt;
x-nonce:       7b1e4d2a-6c3f-4a8b-9d50-1e2f3a4b5c6d&lt;br /&gt;
Body:          PaymentId=4d924e8da6cbf11199f4001dd8b71d1a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed text (the path is in lower case, the scheme and the host are not part of it):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
1760968802\n&lt;br /&gt;
7b1e4d2a-6c3f-4a8b-9d50-1e2f3a4b5c6d\n&lt;br /&gt;
POST\n&lt;br /&gt;
/hu/democlub/callback?paymentid=4d924e8da6cbf11199f4001dd8b71d1a\n&lt;br /&gt;
PaymentId=4d924e8da6cbf11199f4001dd8b71d1a&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Signed bytes: the UTF-8 encoding of the text above (160 bytes), in hex:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
313736303936383830320a37623165346432612d366333662d346138622d396435302d3165326633613462356336640a504f53540a2f68752f64656d6f636c75622f63616c6c6261636b3f7061796d656e7469643d34643932346538646136636266313131393966343030316464386237316431610a5061796d656e7449643d3464393234653864613663626631313139396634303031646438623731643161&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
x-signature-sha512:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
nwEdCk0K1LeDxLqF+4QnUgtmvl0BQPGqLUl+YawMMoJhcNXnJM9xT8JlmsNyWPwWktbJo2oy+yzx6cUMqUrRiA==&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Rotating the key ==&lt;br /&gt;
&lt;br /&gt;
# Generate a second key on the security page, but do not set it as Active. The current key keeps working.&lt;br /&gt;
# Prepare your server to use the newly generated key. It should be able to accept messages signed with the new key, but still use the old key for signing requests.&lt;br /&gt;
# Mark the new key as &amp;lt;i&amp;gt;Active&amp;lt;/i&amp;gt; on the security page. From that moment Barion signs with the new key and checks your requests against it. For the 24 hour change period Barion still accepts requests signed with the old key.&lt;br /&gt;
# Switch your server to use the new key for signing requests within this change period.&lt;br /&gt;
# Once your server uses the new key, we recommend that you &amp;lt;b&amp;gt;delete the old key&amp;lt;/b&amp;gt; on the security page right away. Barion then rejects requests signed with it immediately, instead of accepting them until the change period ends. Deleting it also frees a place for the next key.&lt;br /&gt;
&lt;br /&gt;
== Turning signing off ==&lt;br /&gt;
&lt;br /&gt;
Untick &amp;lt;i&amp;gt;Active&amp;lt;/i&amp;gt; on the active key. Barion stops signing its messages right away and no longer checks the signature of your requests. If your server rejects unsigned messages, it will reject Barion&#039;s IPN messages and responses too.&lt;br /&gt;
&lt;br /&gt;
== Errors ==&lt;br /&gt;
&lt;br /&gt;
If the shop has an active HMAC key and the signature check fails, the request is rejected with HTTP status &amp;lt;code&amp;gt;401&amp;lt;/code&amp;gt; and one of these errors:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Error code !! Meaning&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;MissingSignature&amp;lt;/code&amp;gt; || One or more of the &amp;lt;code&amp;gt;x-timestamp&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;x-signature-sha512&amp;lt;/code&amp;gt; headers is missing.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;InvalidNonce&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; is not a GUID.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;InvalidTimestamp&amp;lt;/code&amp;gt; || &amp;lt;code&amp;gt;x-timestamp&amp;lt;/code&amp;gt; is not a Unix timestamp in seconds, or is more than 5 minutes off the server time.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;InvalidSignature&amp;lt;/code&amp;gt; || The signature does not match the request signed with the shop&#039;s active HMAC key.&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;ReplayedRequest&amp;lt;/code&amp;gt; || A request with this &amp;lt;code&amp;gt;x-nonce&amp;lt;/code&amp;gt; has already been received.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Dezsit@barion.dev</name></author>
	</entry>
	<entry>
		<id>https://docs.barion.com/index.php?title=Payment-Start-v2&amp;diff=4905</id>
		<title>Payment-Start-v2</title>
		<link rel="alternate" type="text/html" href="https://docs.barion.com/index.php?title=Payment-Start-v2&amp;diff=4905"/>
		<updated>2026-06-16T15:13:22Z</updated>

		<summary type="html">&lt;p&gt;Dezsit@barion.dev: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{PageTitle|title=Barion API: Initialize a new payment}}&lt;br /&gt;
&lt;br /&gt;
{{TableOfContents}}&lt;br /&gt;
&lt;br /&gt;
{{api_callmethod&lt;br /&gt;
|method=POST&lt;br /&gt;
|uri=/v2/Payment/Start&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;/payment/start&amp;lt;/code&amp;gt; API endpoint is used to create a new payment in the Barion system.&lt;br /&gt;
&lt;br /&gt;
Prerequisites before use:&lt;br /&gt;
* [[Creating_an_account|Creating an account in Barion]]&lt;br /&gt;
* [[Creating_a_shop|Creating a shop in Barion]]&lt;br /&gt;
* [[Calling_the_API|Calling the Barion API]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;span class=&amp;quot;api-ver&amp;quot;&amp;gt;v2&amp;lt;/span&amp;gt; This API endpoint is available in &#039;&#039;&#039;API v2&#039;&#039;&#039; only.&lt;br /&gt;
&lt;br /&gt;
== Authentication ==&lt;br /&gt;
&lt;br /&gt;
[[Barion Shop Authentication]]&lt;br /&gt;
&lt;br /&gt;
== Use cases ==&lt;br /&gt;
&lt;br /&gt;
This API endpoint is designed to be used in the following scenarios:&lt;br /&gt;
* [[Responsive_web_payment|Responsive Web Payment]]&lt;br /&gt;
&lt;br /&gt;
== Input properties ==&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
|{{3dsfield}} || Properties marked with this must be provided to comply with 3D Secure authentication. The more attributes you provide the more chance you have to avoid the challenge flow.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; if the merchant does not provide 3DS-related properties, it doesn&#039;t mean that the payment will fail. It means that the payer will have a higher chance of getting a challenge during payment.&lt;br /&gt;
&lt;br /&gt;
{{api_input_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| POSKey || Guid || &lt;br /&gt;
* Required&lt;br /&gt;
|| The secret API key of the shop, generated by Barion. This lets the shop to authenticate through the Barion API, but does not provide access to the account owning the shop itself.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentType || [[PaymentType]] || &lt;br /&gt;
* Required&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;Immediate&amp;quot;&lt;br /&gt;
** &amp;quot;Reservation&amp;quot;&lt;br /&gt;
** &amp;quot;DelayedCapture&amp;quot; &lt;br /&gt;
|| The type of payment, which can be either immediate or a money reservation. Reservation means that the shop has a time window to finish the payment (even though the money transaction still takes place immediately). Reservation amounts can be modified during this time window unless the new amount is lower than the original. &lt;br /&gt;
Click here to learn more about reservation payments: [[Reservation_payment|Reservation payments]], and delayed capture: [[Delayed_Capture|Delayed capture]].&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ReservationPeriod || TimeSpan (d.hh:mm:ss) || &lt;br /&gt;
* Required only if PaymentType is &amp;quot;Reservation&amp;quot;&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: one year&lt;br /&gt;
* Default value: 30 minutes&lt;br /&gt;
|| Only makes sense at reservation payments. This is the time window that allows the shop to finish (finalize) the payment. If this does not happen within the time window, the system refunds the payment amount to the payer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| DelayedCapturePeriod || TimeSpan (d.hh:mm:ss) || &lt;br /&gt;
* Required only if PaymentType is &amp;quot;DelayedCapture&amp;quot;&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: 7 days (21 days in case of a Hungarian shop)&lt;br /&gt;
* Default value: seven days&lt;br /&gt;
|| This is the time window that allows the shop to complete (finalize) the payment. If this does not happen within the time window, the system releases the payment amount.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentWindow || TimeSpan (d.hh:mm:ss) || &lt;br /&gt;
* Optional&lt;br /&gt;
* Minimum value: one minute&lt;br /&gt;
* Maximum value: one week&lt;br /&gt;
* Default value: 30 minutes&lt;br /&gt;
|| Time window for the payment to be completed. The payer must execute the payment before this elapses, or else the payment will expire and can no longer be completed.&lt;br /&gt;
|-&lt;br /&gt;
| GuestCheckOut (obsolete) || bool || &lt;br /&gt;
* Required&lt;br /&gt;
* Value must be &amp;quot;true&amp;quot; or &amp;quot;false&amp;quot;, integer evaluation is not supported&lt;br /&gt;
|| Flag indicating whether the payment can be completed without a registered Barion wallet. Guest checkout can only be done with bank cards, and the payer must supply a valid e-mail address - this is necessary for fraud control.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| InitiateRecurrence || bool || &lt;br /&gt;
* Optional&lt;br /&gt;
|| This flag indicates that the shop would like to initialize a token payment. This means that the shop is authorized to charge the funding source of the payer in the future without redirecting her/him to the Barion Smart Gateway. It can be used for one-click and subscription payment scenarios. &lt;br /&gt;
Click here to learn more about token payments: [[Token_payment]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceId || string || &lt;br /&gt;
* Required when executing token payments&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
* Must be unique per shop and per user&lt;br /&gt;
* [https://docs.barion.com/Token_payment#Creating_the_token Generated by the shop]&lt;br /&gt;
|| A string used to identify a given token payment. Its purpose is determined by the value of the &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; property.&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; is &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, this property must contain a &amp;lt;u&amp;gt;new&amp;lt;/u&amp;gt; desired identifier for a new token payment. This should be generated and stored by the shop before calling the API. Also, the shop must ensure that this is unique per user in its own system.&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; is &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;, this property must contain an &amp;lt;u&amp;gt;existing&amp;lt;/u&amp;gt; identifier for a token payment. This should be used to charge a payer&#039;s funding source (either bank card or Barion wallet) that was already used successfully for a payment in the shop.&lt;br /&gt;
* multiple shops can use the same RecurrenceId. Should you be interested, please contact merchanthelpdesk@barion.com&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| FundingSources || [[FundingSources|string[]]] || &lt;br /&gt;
* Required&lt;br /&gt;
|| An array of strings containing the allowed funding sources that can be used to complete the payment.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentRequestId || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The unique identifier for the payment generated by the shop. This is so the shop can track its own payment identifiers. It is also useful for bookkeeping purposes since this shows up in the monthly account statement and the transaction history export, making identification of payments easier for the shop.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| PayerHint || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Optional, but recommended. &lt;br /&gt;
* If provided, must be a valid email format&lt;br /&gt;
* Maximum length: 256 characters&lt;br /&gt;
|| The shop can supply an e-mail address as a hint on who should complete the payment. This can be used if the shop is certain about that the payer has an active Barion wallet or the shop would like to help the guest payer with filling in the email field for her/him. If provided, the Barion Smart Gateway automatically fills out the e-mail address field in the Barion wallet login form and the guest payer form, speeding up the payment process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| CardHolderNameHint || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Optional, but recommended&lt;br /&gt;
* Between 2 and 45 characters&lt;br /&gt;
|| The shop can provide a hint for the customer&#039;s name on the card to speed up the payment flow. If a value is provided, the cardholder name input will be pre-filled with it and the customer can use the pre-filled value instead of typing it out on its own, which speeds up the payment process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceType || [[RecurrenceType]] || &lt;br /&gt;
* Required for {{3dsfield}}, when executing token payments&lt;br /&gt;
|| Describes the nature of the token payment.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TraceId || string || &lt;br /&gt;
* Required for {{3dsfield}}, when executing token payments&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| Identifies the nature of the token payment. &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string || &lt;br /&gt;
* Required &lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the payer should be redirected after the payment is completed or canceled. The payment identifier is added to the query string part of this URL in the &amp;lt;code&amp;gt;paymentId&amp;lt;/code&amp;gt; parameter.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallbackUrl || string || &lt;br /&gt;
* Required &lt;br /&gt;
* Maximum length: 2000 characters&lt;br /&gt;
|| The URL where the Barion system sends a request whenever there is a change in the state of the payment. The payment identifier is added to the query string part of this URL in the &amp;lt;code&amp;gt;paymentId&amp;lt;/code&amp;gt; parameter. Click here to learn more about the callback mechanism: [[Callback_mechanism|Payment callback mechanism (IPN)]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Transactions || [[PaymentTransaction]][] || &lt;br /&gt;
* Required&lt;br /&gt;
|| An array of payment transactions contained in the payment. A payment must contain at least one such transaction. See the [[PaymentTransaction]] page for the appropriate structure and syntax.&lt;br /&gt;
Defining multiple transactions allow the payment initiator to distribute the payment amount between multiple shops. See the following page to learn more: [[Facilitated payments]]&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| OrderNumber || string || &lt;br /&gt;
* Optional&lt;br /&gt;
* Maximum length: 100 characters&lt;br /&gt;
|| The order number generated by the shop. This is to aid the shop in identifying a given payment in its own system. This also shows up in generated monthly account statements and transaction history exports, so it also helps with bookkeeping.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ShippingAddress || [[ShippingAddress]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| The shipping address associated with the payment, if applicable. Providing this is recommended because it helps the automatic anti-fraud analysis get more accurate results. See the [[ShippingAddress]] page for the appropriate structure and syntax.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Locale || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Maximum length: 10 characters&lt;br /&gt;
* Accepted values: &lt;br /&gt;
** &amp;quot;cs-CZ&amp;quot; (Czech)&lt;br /&gt;
** &amp;quot;de-DE&amp;quot; (German)&lt;br /&gt;
** &amp;quot;en-US&amp;quot; (English)&lt;br /&gt;
** &amp;quot;es-ES&amp;quot; (Spanish)&lt;br /&gt;
** &amp;quot;fr-FR&amp;quot; (French)&lt;br /&gt;
** &amp;quot;hu-HU&amp;quot; (Hungarian)&lt;br /&gt;
** &amp;quot;sk-SK&amp;quot; (Slovak)&lt;br /&gt;
** &amp;quot;sl-SI&amp;quot; (Slovenian)&lt;br /&gt;
** &amp;quot;hr-HR&amp;quot; (Croatian)&lt;br /&gt;
** &amp;quot;ro-RO&amp;quot; (Romanian)&lt;br /&gt;
** &amp;quot;pl-PL&amp;quot; (Polish)&lt;br /&gt;
** &amp;quot;it-IT&amp;quot; (Italian)&lt;br /&gt;
** &amp;quot;bg-BG&amp;quot; (Bulgarian)&lt;br /&gt;
|| This indicates in which language the Barion Smart Gateway should display for the payer upon redirect. &lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Currency || string || &lt;br /&gt;
* Required&lt;br /&gt;
* Required length: 3 characters&lt;br /&gt;
Accepted values: &lt;br /&gt;
{{CurrencyList}}&lt;br /&gt;
|| The currency of the payment. Must be supplied in ISO 4217 format. This affects all transactions included in the payment; it is not possible to define multiple transactions in different currencies.&lt;br /&gt;
|-&lt;br /&gt;
| PayerPhoneNumber || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|| The number must be sent in the expected format, without + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| PayerWorkPhoneNumber || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|| The work phone of the payer. The number must be sent in the expected format, without + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| PayerHomeNumber || string || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
* Max length: 30 characters&lt;br /&gt;
* Expected format: 36701231234 (where 36 is the country code)&lt;br /&gt;
|| The home phone number of the payer. The number must be sent in the expected format, without + sign or leading zero(s).&lt;br /&gt;
|-&lt;br /&gt;
| BillingAddress || [[BillingAddress]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| The billing address associated with the payment, if applicable.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PayerAccountInformation|| [[PayerAccountInformation]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| Information about the account of the payer in the merchant&#039;s system.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PurchaseInformation|| [[PurchaseInformation]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| Information about current purchase.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ChallengePreference || [[ChallengePreference]] || &lt;br /&gt;
* Required for {{3dsfield}}&lt;br /&gt;
|| The merchant&#039;s preference of the 3DS challenge. Here you can specify what 3DS authentication should be utilized.&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Output properties ==&lt;br /&gt;
&lt;br /&gt;
{{api_output_table_header}}&lt;br /&gt;
|-&lt;br /&gt;
| PaymentId || Guid || The identifier of the newly initialized payment, generated by the Barion system.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| PaymentRequestId || string || The payment identifier supplied by the API caller in the request.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Status || [[PaymentStatus]]|| The status of the payment in the Barion system. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| QRUrl || string || URL for a QR code representing the payment. This is useful in physical real life situations where the payer uses a mobile device.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RecurrenceResult || RecurrenceResult || Indicates the result of an authorized payment scenario. The result depends on the values of the &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; and &#039;&#039;&#039;RecurrenceId&#039;&#039;&#039; properties supplied in the request.&lt;br /&gt;
&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; was &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, and a new authorized payment was successfully created, this will be &amp;lt;code&amp;gt;None&amp;lt;/code&amp;gt; (because no actual token charge took place yet)&lt;br /&gt;
&lt;br /&gt;
* If &#039;&#039;&#039;InitiateRecurrence&#039;&#039;&#039; was &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;, but a previously authorized payment identifier was supplied in &#039;&#039;&#039;RecurrenceId&#039;&#039;&#039;, the system will try to charge the funding source associated with the authorized payment. If this charge is successful, the result is &amp;lt;code&amp;gt;Successful&amp;lt;/code&amp;gt;. If the system could not charge the funding source, the result is &amp;lt;code&amp;gt;Failed&amp;lt;/code&amp;gt;. If the given identifier is invalid or does not exist, the result is &amp;lt;code&amp;gt;NotFound&amp;lt;/code&amp;gt;. In case the payment can not be processed due to lack of 3DS v2 information &amp;lt;code&amp;gt;ThreeDSAuthenticationRequired&amp;lt;/code&amp;gt; is returned. In this case, either offsite 3DS v2 authentication should be performed or the TraceId of the initial payment should be sent as well.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| Transactions || [[ProcessedTransaction]][] || An array containing all transactions associated with the payment. If the Barion system deducts fees from the shop after payments, this also contains these additional fee transactions beside the payment transactions that were sent in the request.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| GatewayUrl || string || The URL of the Barion Smart Gateway (including the payment identifier), where the API caller should redirect the payer.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| CallbackUrl || string || The URL (including the payment identifier) where the Barion system will send a request to whenever there is a change in the state of the payment. If an explicit URL was not supplied, this will be the callback URL associated with the shop that started the payment.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| RedirectUrl || string || The URL (including the payment identifier) where the payer gets redirected to after the payment is completed or cancelled. If an explicit URL was not supplied, this will be the redirect URL associated with the shop that started the payment.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| ThreeDSAuthClientData|| string || Encrypted client authentication data required for 3D Secure processing. This value can be used when the webshop first tried to complete the payment without user interaction, but the charge failed due to a 3D Secure challenge being mandatory.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| TraceId || string || A unique value generated by the card issuer to track a chain of [[Token_payment_3D_Secure|recurring or token payments that require 3D Secure authentication]]. This shall be used in such scenarios, otherwise it can be ignored.&lt;br /&gt;
&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Dezsit@barion.dev</name></author>
	</entry>
</feed>