I'm trying to integrate PayPal PayflowPro / PayflowLink within our system, and in testing everything is working as expected. When we switched over to live credentials, we are able to create a secure token, using the live merchant details; but when attempted to redirect to a hosted checkout page, we are receiving a new error, which we haven't seen before.
Error invalid Required Domain
We have searched for hours, with no reference in PayPal's official documentation or the internet. Can someone who has worked with PayPal, explain what this error means?
Willing to give up some rep to figure this out.
Please check your referrer URL, see if it is valid domain.
They generally check if incoming host url is valid or not.
Related
TL;DR : I am getting a "12600: Authorisation Denied (12600)" error and can't find what that means in Netbanx/Paysafe's documentation.
Background:
I am using the Netbanx credit card services.
The request is built server-side to obtain a url, which is then embedded in an iframe on the application for clients to pay.
It works like a charm in test mode; the iframe displays Netbanx' form, the client enters their info, clicks "Pay", and the payment is authorized. So far so good.
Now, I've moved to live mode. Configurations (account numbers, API key and API secret) are all valid and used on other projects. The payment request is still correctly built, I obtain a url from Netbanx and it correctly displays the payment form. I enter valid credit card information, click pay, and then, boom: failure page, with error 12600: Authorization denied. I cannot find any info related to that error code. Has this occured to anyone? What does this code mean? Any details would be appreciated!
Thanks!
I believe the issue here relates to Paysafe test API credentials being used on the production environment. These credentials do not translate from test > production as a separate set would need to be used for security reasons.
If you believe that you are ready to go live, you can login to the BackOffice "https://login.test.netbanx.com/" and click the "Go Live" button to start the process!
Trying to get login with PayPal into prestashop, all seem to be done corectly accorting to installation guide but getting this error:
Relying Party Validation error: redirect_uri provided in the request
does not match with the registered redirect_uri. Please check the
request.
What is the problem?
There are two modes for any application on Paypal developers website (i.e. Live and Sandbox mode), please confirm that you are using the same API data that you have configured.
Yes, taking all data from live mode of the app.
Reading the documentation at developer.paypal.com/docs/classic/ipn/gs_IPN, I see the following picture about the
PayPal IPN authentication flow that I can't attach.
However, the IPN payment notification system of Paypal has recently changed a bit for security reasons: look here. And I suspect that the documentation above is not updated accordingly (but maybe I'm just wrong)
With respect to that picture and that PayPal change, I'd like to understand the following:
1) Is the connection in Step 2 now done via HTTP or HTTPS?
2) Is the connection in Step 3 now done via HTTP or HTTPS?
Thanks in advance.
It would actually be Step 4. When your URL POSTs data back to PayPal for verification of the data you will need to make sure you're using https:// on that URL and not just http:// or PayPal won't accept the request at all.
Has anyone had luck getting Login With PayPal to work with MVC4? I've tried creating an extension of OAuth2Client, as well as a separate extension of OpenIdClient. Both had the same problem, which was also the problem that occurs directly from a browser.
I copy/paste the endpoint URL (with querystring) into the browser, but it always goes directly to the callback URL without displaying any PayPal-hosted login form. I can verify that the endpoint is correct by removing or altering the redirect_uri (which results in a PayPal error page.)
I am logged out of PayPal through the browser before attempting the tests, and I've tested with Chrome and IE9.
Any ideas? Thank you!
Apparently, PayPal OpenId Connect does not support the "openid" scope. This was verified for my application by using the Login With PayPal button creator and seeing "invalid scope" appended to the redirect's querystring.
The solution (remove "openid" from the scope) presents its own conundrum. According to the spec for OpenId, this scope is REQUIRED. According to the documentation for PayPal, this scope should be sent at a minimum. This looks like a problem that will be fixed, but if fixed, will the attribute be required and therefore break my application? Or will they opt to make the attribute optional.
I am trying to add the paypal gateway to spree, but am a bit confused what the different fields mean: server, login, password, signature. are login/password supposed to be those that i use to login to paypal? what about server and signature?
Found some info here:
http://guides.spreecommerce.com/payment_gateways.html
server can either be "test" or "live". Not sure why they have this here (as well as a tickbox) but thats the rule anyway!
The signature you get from paypal, as an API signature. If your using developer.paypal.com its pretty easy to get one. After logging in just click "API Credentials" on the left.