{"action":"closed","issue":{"url":"https://api.github.com/repos/PayU/openpayu_php/issues/28","repository_url":"https://api.github.com/repos/PayU/openpayu_php","labels_url":"https://api.github.com/repos/PayU/openpayu_php/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/PayU/openpayu_php/issues/28/comments","events_url":"https://api.github.com/repos/PayU/openpayu_php/issues/28/events","html_url":"https://github.com/PayU/openpayu_php/issues/28","id":41364722,"number":28,"title":"Api 2.1 a unikalność extOrderId","user":{"login":"krzaczek","id":5773701,"avatar_url":"https://avatars.githubusercontent.com/u/5773701?v=3","gravatar_id":"","url":"https://api.github.com/users/krzaczek","html_url":"https://github.com/krzaczek","followers_url":"https://api.github.com/users/krzaczek/followers","following_url":"https://api.github.com/users/krzaczek/following{/other_user}","gists_url":"https://api.github.com/users/krzaczek/gists{/gist_id}","starred_url":"https://api.github.com/users/krzaczek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krzaczek/subscriptions","organizations_url":"https://api.github.com/users/krzaczek/orgs","repos_url":"https://api.github.com/users/krzaczek/repos","events_url":"https://api.github.com/users/krzaczek/events{/privacy}","received_events_url":"https://api.github.com/users/krzaczek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/PayU/openpayu_php/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2014-08-28T08:06:24Z","updated_at":"2016-05-27T17:57:20Z","closed_at":"2016-05-27T17:57:20Z","body":"Witam,\r\n\r\nNowa werjsa bibloteki wprowadza unikalność parametru extOrderId względem POS. Moje pytanie brzmi jak pozwolić użytkownikowi zapłacić \"ponownie\" za zamówienie jeśli np płatnośc zostanie anulowana lub wystąpi jakiś błąd.\r\n\r\nDo tej pory działaliśmy tak że w extOrderId przekazywaliśmy id zamówienia z naszego sklepu. Jeśli status płatności był np Anulowany pozwalaliśmy klientowi \"zapłać ponownie\". W nowym API jest to nie możliwe bo próba utworzenia nowej płatności z tym samym extOrderId kończy się błędem.\r\n\r\nERROR: OpenPayU_Result::__set_state(array( 'status' => 'ERROR_ORDER_NOT_UNIQUE', 'error' => '', 'success' => 0, 'request' => '', 'response' => stdClass::__set_state(array( 'orderId' => '7H1B6KQMBX140828GUEST000P01', 'extOrderId' => '11964', 'status' => stdClass::__set_state(array( 'statusCode' => 'ERROR_ORDER_NOT_UNIQUE', 'code' => '110', 'codeLiteral' => 'ORDER_NOT_UNIQUE', 'statusDesc' => 'Order with given extOrderId already exists', )), )), 'sessionId' => '', 'message' => '', 'countryCode' => '', 'reqId' => '', ))\r\n\r\nJak w takim przypadku pozwolić userowi zapłacić ponownie za to samo zamówienie lub dopłacić do zamówienia - w oby przypadkach pole extOrderId będzie takie same .. czyli będzie zawierać id zamówienia którego dotyczy płatność"}}
{"actor":{"display_login":"regdos"}}