Skorzystaj z tych zasob\u00f3w, aby przetestowa\u0107 integracj\u0119 w r\u00f3\u017cnych scenariuszach.<\/p>\n\n\n\n
Skonsultuj si\u0119 ze swoim Opiekunem, aby rozpocz\u0105\u0107 proces wdra\u017cania.<\/p>\n\n\n\n
Po zako\u0144czeniu tego procesu otrzymasz dane uwierzytelniaj\u0105ce do test\u00f3w:<\/p>\n\n\n\n
Po uzyskaniu tych danych, mo\u017cna rozpocz\u0105\u0107 proces integracji.<\/p>\n\n\n\n
W \u015brodowisku testowym mo\u017cesz:<\/p>\n\n\n\n
Pami\u0119taj, \u017ce konto testowe pozwala na zapoznanie si\u0119 z integracjami SIBS, ale nie gwarantuje przetwarzania p\u0142atno\u015bci na \u017cywo.<\/p>\n\n\n\n
Przed wdro\u017ceniem przetwarzania p\u0142atno\u015bci na \u017cywo masz mo\u017cliwo\u015b\u0107 skorzystania z podanych danych karty na tej stronie w celach testowych. <\/p>\n\n\n\n
Nale\u017cy pami\u0119ta\u0107, \u017ce dane te maj\u0105 zastosowanie wy\u0142\u0105cznie na naszej platformie testowej i nie obejmuj\u0105 rzeczywistych transakcji ani transferu jakichkolwiek \u015brodk\u00f3w.<\/p>\n\n\n\n
Oto kilka kart testowych, kt\u00f3rych mo\u017cesz u\u017cy\u0107:<\/p>\n\n\n\n Kody odpowiedzi zapewniaj\u0105 cenny wgl\u0105d w wynik \u017c\u0105dania API (FULL CODE) Ta strona zawiera kompleksowy opis potencjalnych kod\u00f3w odpowiedzi, kt\u00f3re mo\u017cna napotka\u0107.<\/p>\n\n\n\n Protok\u00f3\u0142 HTTP definiuje zestaw czterdziestu standardowych kod\u00f3w stanu, kt\u00f3re komunikuj\u0105 wyniki \u017c\u0105dania klienta. Te kody stanu s\u0105 podzielone na pi\u0119\u0107 nast\u0119puj\u0105cych grup:<\/p>\n\n\n\n Odmowa obejmuje zar\u00f3wno r\u00f3\u017cne statusy HTTP (400, 401, 403, 405, 429, 500 i 503)returnStatus.statusCode other than „000”<\/mark> , jak i returnStatus.StatusDescription<\/mark> powi\u0105zane z r\u00f3\u017cnymi opisami b\u0142\u0119d\u00f3w.<\/p>\n\n\n\n Interfejsy API SIBS Stargate wykorzystuj\u0105 predefiniowane kody statusu, kt\u00f3re odnosz\u0105 si\u0119 do potencjalnych przyczyn nieudanej odpowiedzi. Poni\u017csza tabela przedstawia r\u00f3\u017cne kody odrzuce\u0144 (statusCode<\/mark>), opisu(StatusDescription<\/mark>) i przyczyn\u0119 potencjalnego odrzucenia.<\/p>\n\n\n\n Poni\u017csza tabela zawiera r\u00f3\u017cne kody statusu, odpowiadaj\u0105ce im opisy i sugerowane dzia\u0142ania w celu rozwi\u0105zania b\u0142\u0119d\u00f3w<\/p>\n\n\n\n Aby sprawdzi\u0107, czy obs\u0142uga b\u0142\u0119d\u00f3w w integracji dzia\u0142a dobrze, mo\u017cesz zasymulowa\u0107 konkretne scenariusze odrzucenia p\u0142atno\u015bci BLIK i kart\u0105. Poni\u017cej znajdziesz przyk\u0142ady test\u00f3w z u\u017cyciem nieprawid\u0142owych 6-cyfrowych kod\u00f3w (BLIK) i z g\u00f3ry ustalonych kwot transakcji, kt\u00f3re powoduj\u0105 konkretne odpowiedzi o odrzuceniu.<\/p>\n\n\n\n Kody s\u0142u\u017c\u0105 jako kluczowe identyfikatory w r\u00f3\u017cnych domenach, w tym w sferze p\u0142atno\u015bci.<\/p>\n\n\n\n Poni\u017cej znajduj\u0105 si\u0119 kody ISO u\u017cywane dla:<\/p>\n\n\n\nMarka<\/th> Numer karty<\/th> Data wyga\u015bni\u0119cia<\/th> CVC\/CVV<\/th> 3DS<\/th> Has\u0142o uwierzytelniania 3DS<\/th><\/tr><\/thead> Visa<\/td> 4176660000000100<\/td> 12\/28<\/td> 597<\/td> Tak (Wyzwanie)<\/td> 123456<\/td><\/tr> Visa<\/td> 4761340000000035<\/td> 12\/28<\/td> 536<\/td> Nie<\/td> –<\/td><\/tr> Mastercard<\/td> 5185520050000010<\/td> 12\/28<\/td> 001<\/td> Tak (Wyzwanie)<\/td> 123456<\/td><\/tr> Mastercard<\/td> 5204740000001002<\/td> 12\/28<\/td> 100<\/td> Tak (bez tarcia)<\/td> –<\/td><\/tr> Mastercard<\/td> 5206361000001351<\/td> 12\/28<\/td> 536<\/td> Nie<\/td> –<\/td><\/tr> Cartes Bancaires Visa<\/td> 4970 4178 0960 9823<\/td> 12\/28<\/td> 914<\/td> Tak (Wyzwanie)<\/td> 123456<\/td><\/tr> Cartes Bancaires MasterCard<\/td> 5134 1486 5519 7817<\/td> 12\/28<\/td> 419<\/td> Tak (Wyzwanie)<\/td> 123456<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Obs\u0142uga opdowiedzi<\/h3>\n\n\n\n
Kody statusu HTTP<\/h5>\n\n\n\n
Kategoria<\/th> Description<\/th> Szczeg\u00f3\u0142y<\/th><\/tr><\/thead> 1xx<\/td> Informacje<\/td> Przekazuje informacje na poziomie protoko\u0142u transferu.<\/td><\/tr> 2xx<\/td> Sukces<\/td> Wskazuje, \u017ce \u017c\u0105danie klienta zosta\u0142o pomy\u015blnie zaakceptowane.<\/td><\/tr> 3xx<\/td> Przekierowanie<\/td> Wskazuje, \u017ce klient musi podj\u0105\u0107 dodatkowe dzia\u0142ania w celu uko\u0144czenia \u017c\u0105dania.<\/td><\/tr> 4xx<\/td> B\u0142\u0105d Klienta<\/td> Ta kategoria kod\u00f3w statusu b\u0142\u0119du wskazuje palcem na klient\u00f3w.<\/td><\/tr> 5xx<\/td> B\u0142\u0105d serwera<\/td> Serwer bierze odpowiedzialno\u015b\u0107 za te kody statusu b\u0142\u0119du.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Code<\/th> Description<\/th> Detail and Action<\/th><\/tr><\/thead> 200<\/td> OK<\/td> It indicates that the REST API successfully carried out whatever action the client requested and that no more specific code in the 2xx series is appropriate.
Unlike the 204 status code, a 200 response should include a response body.The information returned with the response is dependent on the method used in the request, for example:
GET<\/mark> an entity corresponding to the requested resource is sent in the response;
HEAD<\/mark> the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST<\/mark> an entity describing or containing the result of the action;
TRACE<\/mark> an entity containing the request message as received by the end server. <\/td><\/tr>201<\/td> Created<\/td> A REST API responds with the 201 status code whenever a resource is created inside a collection. There may also be times when a new resource is created as a result of some controller action, in which case 201 would also be an appropriate response.
The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field.
The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with a 202 (Accepted) response instead.<\/td><\/tr>202<\/td> Accepted<\/td> A 202 response is typically used for actions that take a long while to process. It indicates that the request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, or even maybe disallowed when processing occurs.
Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent\u2019s connection to the server persist until the process is completed.
The entity returned with this response SHOULD include an indication of the request\u2019s current status and either a pointer to a status monitor (job queue location) or some estimate of when the user can expect the request to be fulfilled.<\/td><\/tr>204<\/td> No Content<\/td> The 204 status code is usually sent out in response to a PUT<\/mark>, POST<\/mark>, or DELETE<\/mark> request when the REST API declines to send back any status message or representation in the response message\u2019s body.
An API may also send 204 in conjunction with a GET<\/mark> request to indicate that the requested resource exists, but has no state representation to include in the body.
If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent\u2019s active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent\u2019s active view.
The 204 response MUST NOT include a message-body and thus is always terminated by the first empty line after the header fields<\/td><\/tr>205<\/td> Reset Content<\/td> The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.<\/td><\/tr> 206<\/td> Partial Content<\/td> The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.<\/td><\/tr> 300<\/td> Multiple Choices<\/td> Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.<\/td><\/tr> 301<\/td> Moved Permanently<\/td> The 301 status code indicates that the REST API\u2019s resource model has been significantly redesigned, and a new permanent URI has been assigned to the client\u2019s requested resource. The REST API should specify the new URI in the response\u2019s Location header, and all future requests should be directed to the given URI.
You will hardly use this response code in your API as you can always use the API versioning for new API while retaining the old one.<\/td><\/tr>302<\/td> Found<\/td> The HTTP response status code 302 Found is a common way of performing URL redirection. An HTTP response with this status code will additionally provide a URL in the Location header field. The user agent (e.g., a web browser) is invited by a response with this code to make a second. Otherwise identical, request to the new URL specified in the location field.
Many web browsers implemented this code in a manner that violated this standard, changing the request type of the new request to GET<\/mark>, regardless of the type employed in the original request (e.g., POST). RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client.<\/td><\/tr>303<\/td> See Other<\/td> A 303 response indicates that a controller resource has finished its work, but instead of sending a potentially unwanted response body, it sends the client the URI of a response resource. The response can be the URI of the temporary status message, or the URI to some already existing, more permanent, resource.
Generally speaking, the 303 status code allows a REST API to send a reference to a resource without forcing the client to download its state. Instead, the client may send a GET<\/mark> request to the value of the Location header.
The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.<\/td><\/tr>304<\/td> Not Modified<\/td> This status code is similar to 204 (\u201cNo Content\u201d) in that the response body must be empty. The critical distinction is that 204 is used when there is nothing to send in the body, whereas 304 is used when the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.
In such a case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.
Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client.<\/td><\/tr>307<\/td> Temporary Redirect<\/td> A 307 response indicates that the REST API is not going to process the client\u2019s request. Instead, the client should resubmit the request to the URI specified by the response message\u2019s Location header. However, future requests should still use the original URI.
A REST API can use this status code to assign a temporary URI to the client\u2019s requested resource. For example, a 307 response can be used to shift a client request over to another host.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD<\/mark>, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s). If the 307 status code is received in response to a request other than GET<\/mark> or HEAD<\/mark>, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.<\/td><\/tr>400<\/td> Bad Request<\/td> 400 is the generic client-side error status, used when no other 4xx error code is appropriate. Errors can be like malformed request syntax, invalid request message parameters, or deceptive request routing etc.
The client SHOULD NOT repeat the request without modifications.<\/td><\/tr>401<\/td> Unauthorized<\/td> A 401 error response indicates that the client tried to operate on a protected resource without providing the proper authorization. It may have provided the wrong credentials or none at all. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
The client MAY repeat the request with a suitable Authorization header field. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information.<\/td><\/tr>402<\/td> Payment Required<\/td> Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed, and this code is not widely used.<\/td><\/tr> 403<\/td> Forbidden<\/td> A 403 error response indicates that the client\u2019s request is formed correctly, but the REST API refuses to honor it, i.e. the user does not have the necessary permissions for the resource. A 403 response is not a case of insufficient client credentials; that would be 401 (\u201cUnauthorized\u201d).
Authentication will not help, and the request SHOULD NOT be repeated. Unlike a 401 Unauthorized response, authenticating will make no difference.<\/td><\/tr>404<\/td> Not Found<\/td> The 404 error status code indicates that the REST API can\u2019t map the client\u2019s URI to a resource but may be available in the future. Subsequent requests by the client are permissible.
No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.<\/td><\/tr>405<\/td> Method Not Allowed<\/td> The API responds with a 405 error to indicate that the client tried to use an HTTP method that the resource does not allow. For instance, a read-only resource could support only GET<\/mark> and HEAD<\/mark>, while a controller resource might allow GET<\/mark> and POST<\/mark>, but not PUT<\/mark> or DELETE<\/mark>.<\/td><\/tr> 406<\/td> Not Acceptable<\/td> The 406 error response indicates that the API is not able to generate any of the client\u2019s preferred media types, as indicated by the Accept request header. For example, a client request for data formatted as application\/xml will receive a 406 response if the API is only willing to format data as application\/json.
If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.<\/td><\/tr>407<\/td> Proxy Authentication Required<\/td> The client must first authenticate itself with the proxy.<\/td><\/tr> 408<\/td> Request Timeout<\/td> The server timed out waiting for the request. According to HTTP specifications: „The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.<\/td><\/tr> 409<\/td> Conflict<\/td> Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.<\/td><\/tr> 410<\/td> Gone<\/td> Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a „404 Not Found” may be used instead.<\/td><\/tr> 411<\/td> Length Required<\/td> The request did not specify the length of its content, which is required by the requested resource<\/td><\/tr> 412<\/td> Precondition Failed<\/td> The 412 error response indicates that the client specified one or more preconditions in its request headers, effectively telling the REST API to carry out its request only if certain conditions were met. A 412 response indicates that those conditions were not met, so instead of carrying out the request, the API sends this status code.<\/td><\/tr> 413<\/td> Payload Too Large<\/td> The request is larger than the server is willing or able to process. Previously called „Request Entity Too Large”<\/td><\/tr> 414<\/td> URI Too Long<\/td> The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET<\/mark> request, in which case it should be converted to a POST<\/mark> request. Called „Request-URI Too Long” previously<\/td><\/tr> 415<\/td> Unsupported Media Type<\/td> The 415 error response indicates that the API is not able to process the client\u2019s supplied media type, as indicated by the Content-Type request header. For example, a client request including data formatted as application\/xml will receive a 415 response if the API is only willing to process data formatted as application\/json.
For example, the client uploads an image as image\/svg+xml, but the server requires that images use a different format.<\/td><\/tr>416<\/td> Range Not Satisfiable<\/td> The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. Called „Requested Range Not Satisfiable” previously.<\/td><\/tr> 417<\/td> Expectation Failed<\/td> The server cannot meet the requirements of the Expect request-header field.<\/td><\/tr> 421<\/td> Misdirected Request<\/td> The server cannot meet the requirements of the Expect request-header field.<\/td><\/tr> 422<\/td> Unprocessable Entity<\/td> The request was well-formed but was unable to be followed due to semantic errors.<\/td><\/tr> 423<\/td> Locked<\/td> The resource that is being accessed is locked.<\/td><\/tr> 424<\/td> Failed Dependency<\/td> The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).<\/td><\/tr> 425<\/td> Too Early<\/td> Indicates that the server is unwilling to risk processing a request that might be replayed.<\/td><\/tr> 426<\/td> Upgrade Required<\/td> The client should switch to a different protocol such as TLS\/1.0, given in the Upgrade header field.<\/td><\/tr> 428<\/td> Precondition Required<\/td> The origin server requires the request to be conditional. Intended to prevent the 'lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.<\/td><\/tr> 429<\/td> Too Many Requests<\/td> The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.<\/td><\/tr> 431<\/td> Request Header Fields Too Large<\/td> The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.<\/td><\/tr> 451<\/td> Unavailable For Legal Reasons <\/td> A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.<\/td><\/tr> 500<\/td> Internal Server Error<\/td> 500 is the generic REST API error response. Most web frameworks automatically respond with this response status code whenever they execute some request handler code that raises an exception.
A 500 error is never the client\u2019s fault, and therefore, it is reasonable for the client to retry the same request that triggered this response and hope to get a different response.
API response is the generic error message, given when an unexpected condition was encountered and no more specific message is suitable.<\/td><\/tr>501<\/td> Not Implemented<\/td> The server either does not recognize the request method, or it lacks the ability to fulfill the request. Usually, this implies future availability (e.g., a new feature of a web-service API).<\/td><\/tr> 502<\/td> Bad Gateway<\/td> The server was acting as a gateway or proxy and received an invalid response from the upstream server.<\/td><\/tr> 503<\/td> Service Unavailable<\/td> The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.<\/td><\/tr> 504<\/td> Gateway Timeout<\/td> The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.<\/td><\/tr> 505<\/td> HTTP Version Not Supported<\/td> The server does not support the HTTP protocol version used in the request.<\/td><\/tr> 506<\/td> 506 Variant Also Negotiates<\/td> Transparent content negotiation for the request results in a circular reference.<\/td><\/tr> 507<\/td> Insufficient Storage<\/td> The server is unable to store the representation needed to complete the request.<\/td><\/tr> 508<\/td> Loop Detected
<\/td>The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).<\/td><\/tr> 510<\/td> Not Extended<\/td> Further extensions to the request are required for the server to fulfil it.<\/td><\/tr> 511<\/td> Network Authentication Required<\/td> The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., „captive portals” used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Kody odmowy<\/h3>\n\n\n\n
statusCode<\/th> StatusDescription<\/th> Decline Reason<\/th> Suggested action<\/th><\/tr><\/thead> E0101<\/td> Nieprawid\u0142owe \u017c\u0105danie, brakuje danych lub s\u0105 one nieprawid\u0142owe<\/td> Dane wprowadzone dla transakcji nie s\u0105 poprawne, wi\u0119c transakcja nie mog\u0142a zosta\u0107 zainicjowana lub pomy\u015blnie zako\u0144czona.<\/td> Sprawd\u017a, czy dane wprowadzone dla transakcji s\u0105 prawid\u0142owe i dok\u0142adne.
Upewnij si\u0119, \u017ce dane takie jak informacje o karcie, informacje o kliencie i dane mandatu SEPA DD s\u0105 prawid\u0142owe.<\/td><\/tr>E0102<\/td> Nieprawid\u0142owe lub brakuj\u0105ce dane dla typu p\u0142atno\u015bci<\/td> Nie mo\u017cna by\u0142o zweryfikowa\u0107 typu p\u0142atno\u015bci i danych<\/td> Sprawd\u017a poprawno\u015b\u0107 danych p\u0142atno\u015bci (dotyczy Blik i kart).<\/td><\/tr> E0103<\/td> Uwierzytelnianie 3D Secure nie powiod\u0142o si\u0119<\/td> Proces uwierzytelniania 3DS nie zosta\u0142 pomy\u015blnie zako\u0144czony przez kupuj\u0105cego<\/td> Terminal powinien mie\u0107 aktywne 3DS i
karta u\u017cywana podczas transakcji powinna r\u00f3wnie\u017c obs\u0142ugiwa\u0107 3DS.<\/td><\/tr>E0104<\/td> Przekroczony limit kwoty<\/td> Kwota transakcji (w tym upowa\u017cnienie SEPA DD) nie spe\u0142nia limit\u00f3w sieci akceptacji<\/td> Dla SEPA DD:
Verify the transaction limits imposed by the bank.
Upewnij si\u0119, \u017ce polecenie zap\u0142aty SEPA jest poprawnie skonfigurowane.
Dla BLIK:
Kupuj\u0105cy powinien sprawdzi\u0107 limity i saldo konta BLIK.
Dla kart:
Sprawd\u017a limity transakcji dla danej transakcji.<\/td><\/tr>E0105<\/td> Autoryzowana p\u0142atno\u015b\u0107 – Nieprawid\u0142owa metoda p\u0142atno\u015bci<\/td> Sprzedawca albo nie ma dost\u0119pnej metody p\u0142atno\u015bci, albo nie skonfigurowa\u0142 jej poprawnie do przetwarzania transakcji.<\/td> Sprawd\u017a w SIBS Backoffice, czy istnieje dost\u0119pna umowa dla wybranej metody p\u0142atno\u015bci, aby upewni\u0107 si\u0119, \u017ce transakcja si\u0119 powiedzie.<\/td><\/tr> E0106<\/td> Niepoprawny terminal.<\/td> \u017b\u0105dana transakcja nie jest obs\u0142ugiwana przez terminal<\/td> Sprawd\u017a, za po\u015brednictwem SIBS Backoffice, ustawienia terminala, kt\u00f3ry zosta\u0142 u\u017cyty do przeprowadzenia transakcji.<\/td><\/tr> E0107<\/td> Autoryzowana p\u0142atno\u015b\u0107 Nieznany<\/td> Autoryzacja p\u0142atno\u015bci nie powiod\u0142a si\u0119 lub jej status jest nieokre\u015blony.<\/td> Sprawd\u017a status transakcji w SIBS Backoffice.<\/td><\/tr> E0108<\/td> Nieprawid\u0142owa konfiguracja webhook<\/td> Ustawienia webhook zosta\u0142y skonfigurowane nieprawid\u0142owo<\/td> Sprawd\u017a w menu SIBS Backoffice Webhook, czy ustawienia webhook s\u0105 prawid\u0142owo zdefiniowane.<\/td><\/tr> E0109<\/td> B\u0142\u0105d walidacji wiadomo\u015bci<\/td> Nieprawid\u0142owe \u017c\u0105danie, wymaga uwierzytelnienia<\/td> Transakcj\u0119 nale\u017cy zainicjowa\u0107 na terminalu 3DS.<\/td><\/tr> E0201<\/td> Odrzucono, p\u0142atno\u015b\u0107 cykliczna jest nieaktywna<\/td> P\u0142atno\u015b\u0107 cykliczna mo\u017ce zosta\u0107 odrzucona, dezaktywowana lub nie by\u0107 obs\u0142ugiwana przez sprzedawc\u0119.<\/td> Please review the checkout details to verify the payment information.
Upewnij si\u0119, \u017ce wszystkie niezb\u0119dne pola p\u0142atno\u015bci s\u0105 dok\u0142adnie wype\u0142nione, w tym numer karty, data wa\u017cno\u015bci, CVV, adres rozliczeniowy i wszelkie inne wymagane informacje.<\/td><\/tr>E0202<\/td> Operacja odrzucona<\/td> P\u0142atno\u015b\u0107 nie zosta\u0142a zaakceptowana\/odrzucona lub system zarz\u0105dzania oszustwami nie zatwierdzi\u0142 transakcji.<\/td> Skontaktuj si\u0119 z SIBS, aby dowiedzie\u0107 si\u0119, dlaczego transakcja zosta\u0142a odrzucona przez system wykrywania oszustw (dotyczy kart i BLIK).<\/td><\/tr> E0301<\/td> B\u0142\u0105d po\u015bwiadcze\u0144 sprzedawcy<\/td> Niepowodzenie w uzyskaniu po\u015bwiadcze\u0144 aplikacji dla sprzedawcy<\/td> Upewnij si\u0119, \u017ce podane dane uwierzytelniaj\u0105ce dla wywo\u0142a\u0144 API s\u0105 prawid\u0142owe, a je\u015bli problem nadal wyst\u0119puje, skontaktuj si\u0119 z pomoc\u0105 techniczn\u0105 SIBS.<\/td><\/tr> E0302<\/td> Nie znaleziono porozumienia<\/td> Niewa\u017cna umowa dotycz\u0105ca okre\u015blonego produktu finansowego<\/td> Sprawd\u017a w menu SIBS Backoffice, czy umowy finansowe s\u0105 prawid\u0142owo zdefiniowane.<\/td><\/tr> E0303<\/td> Operacja nie jest obs\u0142ugiwana<\/td> Nie uda\u0142o si\u0119 wygenerowa\u0107 transakcji w okre\u015blonej us\u0142udze (na przyk\u0142ad: Link to Pay, Split Payout).<\/td> Podaj identyfikator transakcji zespo\u0142owi wsparcia SIBS, aby zrozumie\u0107, dlaczego transakcja ko\u0144czy si\u0119 niepowodzeniem.<\/td><\/tr> E0304<\/td> Transakcja zosta\u0142a ju\u017c sfinalizowana<\/td> Bie\u017c\u0105cy przep\u0142yw transakcji zosta\u0142 ju\u017c zako\u0144czony, podobna transakcja mog\u0142a ju\u017c zosta\u0107 niedawno przes\u0142ana.<\/td> Potwierdzenie w SIBS Backoffice statusu transakcji z danym identyfikatorem transakcji.<\/td><\/tr> E0305<\/td> Nie znaleziono transakcji<\/td> Je\u015bli nie uda si\u0119 uzyska\u0107 informacji o transakcji, nale\u017cy sprawdzi\u0107 identyfikator transakcji.<\/td> Potwierd\u017a status transakcji w SIBS Backoffice.<\/td><\/tr> E0306<\/td> Nieprawid\u0142owa parametryzacja metody p\u0142atno\u015bci<\/td> Nieprawid\u0142owa parametryzacja metody p\u0142atno\u015bci (kwota, data wyga\u015bni\u0119cia, token, kod sprzedawcy lub kod terminala)<\/td> Sprawd\u017a, czy w metodzie p\u0142atno\u015bci nie ma nieprawid\u0142owych parametr\u00f3w, zapewniaj\u0105c dok\u0142adno\u015b\u0107 w polach takich jak kwota, data wyga\u015bni\u0119cia, token, kod sprzedawcy lub kod terminala.<\/td><\/tr> E0307<\/td> Nieprawid\u0142owa parametryzacja typu p\u0142atno\u015bci<\/td> Nieprawid\u0142owa parametryzacja w typie p\u0142atno\u015bci (dotyczy autoryzacji, zakupu, przechwycenia lub zwrotu).<\/td> Zaktualizuj parametryzacj\u0119 typu p\u0142atno\u015bci, aby upewni\u0107 si\u0119, \u017ce dok\u0142adnie odpowiada zamierzonej funkcji, niezale\u017cnie od tego, czy jest to autoryzacja, zakup, przechwytywanie czy zwrot.<\/td><\/tr> E0900<\/td> Nieprawid\u0142owe dane uwierzytelniania lub autoryzacji<\/td> Utworzenie tokena nie powiod\u0142o si\u0119 z powodu nieprawid\u0142owych danych<\/td> Potwierd\u017a dane informacyjne tokena.<\/td><\/tr> E0901<\/td> Nieprawid\u0142owe dane akceptanta, wierzyciela, rachunku lub upowa\u017cnienia<\/td> Mandat SEPA DD nie zosta\u0142 poprawnie skonfigurowany<\/td> Potwierd\u017a ustawienia upowa\u017cnienia SEPA DD.<\/td><\/tr> E0902<\/td> Nieprawid\u0142owa kwota<\/td> Kwota p\u0142atno\u015bci jest nieprawid\u0142owa lub przekracza dozwolon\u0105 kwot\u0119.<\/td> Sprawd\u017a szczeg\u00f3\u0142y tokena SEPA DD.<\/td><\/tr> E0903<\/td> Nieprawid\u0142owa waluta<\/td> The terminal does not support or accepts the transaction currency<\/td> Sprawd\u017a szczeg\u00f3\u0142y tokena SEPA DD.<\/td><\/tr> E0904<\/td> Nieprawid\u0142owy link do p\u0142atno\u015bci<\/td> Nieprawid\u0142owe ustawienia Link to Pay (wygas\u0142e, zduplikowane lub nieaktywne)<\/td> Sprawd\u017a w SIBS Backoffice, w menu Link to Pay, czy ustawienia \u0142\u0105cza s\u0105 prawid\u0142owo zdefiniowane.<\/td><\/tr> E0905<\/td> Nieprawid\u0142owa data upowa\u017cnienia<\/td> Termin p\u0142atno\u015bci upowa\u017cnienia do polecenia zap\u0142aty SEPA przekracza 15 dni, przekraczaj\u0105c limit czasowy.<\/td> Potwierd\u017a ustawienia upowa\u017cnienia SEPA DD (data).<\/td><\/tr> E0906<\/td> Nieprawid\u0142owy kod sprzedawcy lub terminala<\/td> Dane dotycz\u0105ce kwoty, daty wyga\u015bni\u0119cia, tokena, kodu sprzedawcy lub kodu terminala nie s\u0105 prawid\u0142owo zdefiniowane.<\/td> Sprawd\u017a w SIBS Backoffice, czy dane sprzedawcy, sklepu i terminala s\u0105 prawid\u0142owo zdefiniowane.<\/td><\/tr> E0908<\/td> Nieprawid\u0142owe punkty rozliczeniowe<\/td> Punkty rozliczeniowe s\u0105 nieprawid\u0142owo zdefiniowane lub nie mo\u017cna ich zlokalizowa\u0107.<\/td> Sprawd\u017a zar\u00f3wno w SIBS Backoffice, jak i Checkout API, czy ustawienia punkt\u00f3w rozliczeniowych s\u0105 prawid\u0142owo zdefiniowane.<\/td><\/tr> T999<\/td> Tymczasowy b\u0142\u0105d SIBS<\/td> Wyst\u0105pi\u0142 wewn\u0119trzny b\u0142\u0105d SIBS Gateway. Skontaktuj si\u0119 z pomoc\u0105 techniczn\u0105, aby uzyska\u0107 pomoc.<\/td> Skontaktuj si\u0119 z pomoc\u0105 techniczn\u0105 SIBS.<\/td><\/tr> E999<\/td> B\u0142\u0105d wewn\u0119trzny SIBS<\/td> Wyst\u0105pi\u0142 wewn\u0119trzny b\u0142\u0105d SIBS Gateway. Skontaktuj si\u0119 z pomoc\u0105 techniczn\u0105, aby uzyska\u0107 pomoc.<\/td> Skontaktuj si\u0119 z pomoc\u0105 techniczn\u0105 SIBS.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Negatywne scenariusze testowe<\/h3>\n\n\n\n
Metoda p\u0142atno\u015bci<\/th> Pow\u00f3d odmowy \u2013 BLIK<\/th> statusCode<\/th> Szczeg\u00f3\u0142y powodu odmowy<\/th> 6-cyfrowy kod<\/th><\/tr><\/thead> BLIK<\/td> ALIAS_DECLINED<\/td> E0110<\/td> Bank odm\u00f3wi\u0142 realizacji transakcji podanym tokenem. Zap\u0142a\u0107 przy u\u017cyciu kodu T6.<\/td> 912 111<\/td><\/tr> BLIK<\/td> TAS_DECLINED<\/td> E0201<\/td> Transakcja zosta\u0142a odrzucona przez BLIK.<\/td> 927 111<\/td><\/tr> BLIK<\/td> USER_DECLINED<\/td> E0110<\/td> U\u017cytkownik odrzuci\u0142 transakcj\u0119 w swojej aplikacji bankowej.<\/td> 934 111<\/td><\/tr> BLIK<\/td> SEC_DECLINED<\/td> E0110<\/td> Transakcja odrzucona przez bank z powod\u00f3w bezpiecze\u0144stwa.<\/td> 969 111<\/td><\/tr> BLIK<\/td> SYSTEM_ERROR<\/td> E0110<\/td> B\u0142\u0105d wewn\u0119trzny SIBS<\/td> 956 111<\/td><\/tr> BLIK<\/td> GENERAL_ERROR<\/td> E9999<\/td> B\u0142\u0105d wewn\u0119trzny SIBS<\/td> 961 111<\/td><\/tr> BLIK<\/td> INSUFFICIENT_FUNDS<\/td> E0112<\/td> Transakcja odrzucona ze wzgl\u0119du na niewystarczaj\u0105ce \u015brodki.<\/td> 960 111<\/td><\/tr> BLIK<\/td> TIMEOUT<\/td> E0111<\/td> Brak powiadomienia autoryzacyjnego z banku w zadanym czasie.<\/td> 989 111<\/td><\/tr> BLIK<\/td> LIMIT_EXCEEDED<\/td> E0112<\/td> Kwota transakcji jest wy\u017csza ni\u017c ustawiony limit w banku. <\/td> 990 111<\/td><\/tr> BLIK<\/td> USER_TIMEOUT<\/td> E0111<\/td> U\u017cytkownik nie autoryzowa\u0142 transakcji w zadanym czasie.<\/td> 949 111<\/td><\/tr> BLIK<\/td> ISSUER_DECLINED<\/td> E0110<\/td> Transakcja zosta\u0142a odrzucona przez BANK.<\/td> 902 111<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Marka<\/th> Pow\u00f3d odmowy \u2013 karta<\/th> statusCode<\/th> Szczeg\u00f3\u0142y powodu odmowy<\/th> Kwota<\/th><\/tr><\/thead> Visa & Mastercard<\/td> Exceeds withdrawal frequency (Przekroczona cz\u0119stotliwo\u015b\u0107 wycofania)<\/td> E0109<\/td> Nieprawid\u0142owe \u017c\u0105danie, wymagane uwierzytelnienie.<\/td> 65.65<\/td><\/tr> Mastercard<\/td> Exceeds withdrawal limit (Przekroczony limit wycofania)<\/td> E0761<\/td> Kwota transakcji jest wy\u017csza ni\u017c limit ustawiony w banku.<\/td> 40<\/td><\/tr> Visa<\/td> Suspected fraud (Podejrzenie oszustwa)<\/td> E0759<\/td> Transakcja odrzucona ze wzgl\u0119du na podejrzenie oszustwa.<\/td> 15<\/td><\/tr> Mastercard<\/td> Invalid transaction (Nieprawid\u0142owa transakcja)<\/td> E0712<\/td> Transakcja nie jest dozwolona zgodnie z warunkami lub ustawieniami karty.<\/td> 120<\/td><\/tr> Mastercard<\/td> Suspected fraud (Podejrzenie oszustwa)<\/td> E0759<\/td> Transakcja zosta\u0142a odrzucona z powodu podejrzenia oszustwa.<\/td> 144<\/td><\/tr> Visa & Mastercard<\/td> Incorrect PIN (Niew\u0142a\u015bciwy PIN)<\/td> E0755<\/td> W\u0142a\u015bciciel karty wprowadzi\u0142 niepoprawny PIN.<\/td> 110<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Kody referencyjne<\/h3>\n\n\n\n