How to solve the error 401 when calling paysafe server
0
When i call paysafe server to get the transaction details using the received token, i receive the error 401. Paysafe is blocking requests from https://localhost?? How to solve this problem, i don't have access to real server for development.
here is the code:
$.ajax
(
type: "POST",
url: "https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths",
dataType: 'json',
headers:
"Content-Type": "application/json",
"Authorization": "Basic " + "mycodehere"
,
data:
"merchantRefNum": "123456789",
"amount": 5000,
"settleWithAuth": true,
"dupCheck": false,
"card":
"paymentToken": result.token
,
success: function (data)
console.log(data);
);
Here is the answer:
jquery.js:9631 OPTIONS **https://api.test.paysafe.com/cardpayments/v1/accounts/99999999/auths 401 (Unauthorized)**
send @ jquery.js:9631
ajax @ jquery.js:9176
(anonymous) @ PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:734
i @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
i @ paysafe.min.js:1
e.onMessage @ paysafe.min.js:1
t @ paysafe.min.js:1
PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:1 Access to XMLHttpRequest at 'https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths' from origin 'https://localhost:8411' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
cors policy unauthorized paysafe
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
add a comment |
0
When i call paysafe server to get the transaction details using the received token, i receive the error 401. Paysafe is blocking requests from https://localhost?? How to solve this problem, i don't have access to real server for development.
here is the code:
$.ajax
(
type: "POST",
url: "https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths",
dataType: 'json',
headers:
"Content-Type": "application/json",
"Authorization": "Basic " + "mycodehere"
,
data:
"merchantRefNum": "123456789",
"amount": 5000,
"settleWithAuth": true,
"dupCheck": false,
"card":
"paymentToken": result.token
,
success: function (data)
console.log(data);
);
Here is the answer:
jquery.js:9631 OPTIONS **https://api.test.paysafe.com/cardpayments/v1/accounts/99999999/auths 401 (Unauthorized)**
send @ jquery.js:9631
ajax @ jquery.js:9176
(anonymous) @ PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:734
i @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
i @ paysafe.min.js:1
e.onMessage @ paysafe.min.js:1
t @ paysafe.min.js:1
PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:1 Access to XMLHttpRequest at 'https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths' from origin 'https://localhost:8411' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
cors policy unauthorized paysafe
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
See the answer at stackoverflow.com/questions/45405983/…. Your browser is sending a CORS preflight OPTIONS request before trying the POST request from your frontend code. And that preflight is failing because the server is requiring authentication for OPTIONS request. But browsers never send the Authorization request header or other credentials in the CORS preflight — so the server doesn’t receive any Authorization header for the OPTIONS request.
– sideshowbarker
Nov 15 '18 at 22:08
add a comment |
0
0
0
When i call paysafe server to get the transaction details using the received token, i receive the error 401. Paysafe is blocking requests from https://localhost?? How to solve this problem, i don't have access to real server for development.
here is the code:
$.ajax
(
type: "POST",
url: "https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths",
dataType: 'json',
headers:
"Content-Type": "application/json",
"Authorization": "Basic " + "mycodehere"
,
data:
"merchantRefNum": "123456789",
"amount": 5000,
"settleWithAuth": true,
"dupCheck": false,
"card":
"paymentToken": result.token
,
success: function (data)
console.log(data);
);
Here is the answer:
jquery.js:9631 OPTIONS **https://api.test.paysafe.com/cardpayments/v1/accounts/99999999/auths 401 (Unauthorized)**
send @ jquery.js:9631
ajax @ jquery.js:9176
(anonymous) @ PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:734
i @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
i @ paysafe.min.js:1
e.onMessage @ paysafe.min.js:1
t @ paysafe.min.js:1
PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:1 Access to XMLHttpRequest at 'https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths' from origin 'https://localhost:8411' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
cors policy unauthorized paysafe
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
When i call paysafe server to get the transaction details using the received token, i receive the error 401. Paysafe is blocking requests from https://localhost?? How to solve this problem, i don't have access to real server for development.
here is the code:
$.ajax
(
type: "POST",
url: "https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths",
dataType: 'json',
headers:
"Content-Type": "application/json",
"Authorization": "Basic " + "mycodehere"
,
data:
"merchantRefNum": "123456789",
"amount": 5000,
"settleWithAuth": true,
"dupCheck": false,
"card":
"paymentToken": result.token
,
success: function (data)
console.log(data);
);
Here is the answer:
jquery.js:9631 OPTIONS **https://api.test.paysafe.com/cardpayments/v1/accounts/99999999/auths 401 (Unauthorized)**
send @ jquery.js:9631
ajax @ jquery.js:9176
(anonymous) @ PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:734
i @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
(anonymous) @ paysafe.min.js:1
i @ paysafe.min.js:1
e.onMessage @ paysafe.min.js:1
t @ paysafe.min.js:1
PublicInvoice.aspx?id=93&CompanyId=020000001&Fr=1:1 Access to XMLHttpRequest at 'https://api.test.paysafe.com/cardpayments/v1/accounts/1001285700/auths' from origin 'https://localhost:8411' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
cors policy unauthorized paysafe
cors policy unauthorized paysafe
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
asked Nov 15 '18 at 18:00
Stephane RochonStephane Rochon
41
41
See the answer at stackoverflow.com/questions/45405983/…. Your browser is sending a CORS preflight OPTIONS request before trying the POST request from your frontend code. And that preflight is failing because the server is requiring authentication for OPTIONS request. But browsers never send the Authorization request header or other credentials in the CORS preflight — so the server doesn’t receive any Authorization header for the OPTIONS request.
– sideshowbarker
Nov 15 '18 at 22:08
add a comment |
See the answer at stackoverflow.com/questions/45405983/…. Your browser is sending a CORS preflight OPTIONS request before trying the POST request from your frontend code. And that preflight is failing because the server is requiring authentication for OPTIONS request. But browsers never send the Authorization request header or other credentials in the CORS preflight — so the server doesn’t receive any Authorization header for the OPTIONS request.
– sideshowbarker
Nov 15 '18 at 22:08
See the answer at stackoverflow.com/questions/45405983/…. Your browser is sending a CORS preflight OPTIONS request before trying the POST request from your frontend code. And that preflight is failing because the server is requiring authentication for OPTIONS request. But browsers never send the Authorization request header or other credentials in the CORS preflight — so the server doesn’t receive any Authorization header for the OPTIONS request.
– sideshowbarker
Nov 15 '18 at 22:08
See the answer at stackoverflow.com/questions/45405983/…. Your browser is sending a CORS preflight OPTIONS request before trying the POST request from your frontend code. And that preflight is failing because the server is requiring authentication for OPTIONS request. But browsers never send the Authorization request header or other credentials in the CORS preflight — so the server doesn’t receive any Authorization header for the OPTIONS request.
– sideshowbarker
Nov 15 '18 at 22:08
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325401%2fhow-to-solve-the-error-401-when-calling-paysafe-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325401%2fhow-to-solve-the-error-401-when-calling-paysafe-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
See the answer at stackoverflow.com/questions/45405983/…. Your browser is sending a CORS preflight OPTIONS request before trying the POST request from your frontend code. And that preflight is failing because the server is requiring authentication for OPTIONS request. But browsers never send the Authorization request header or other credentials in the CORS preflight — so the server doesn’t receive any Authorization header for the OPTIONS request.
– sideshowbarker
Nov 15 '18 at 22:08