New API Request

  • Hello,

    since we have changed our PayPal email (we have left the old one but switched to another primary email) I wanted to ask for new credentials following a suggestion received from in another post here.

    There are 3 possible options when you ask for the API:

    – Pre-built payment solution
    – Braintree SDK integration
    – NVP/SOAP API integration (Classic)

    The first option is if you use a platform like Shopify and Magento, but WC is not mentioned, the second one is clear, the third one is pretty generic and could fit the case as much as the first option, stating: “You or your developer integrated NVP/SOAP (or “Classic”) APIs that allow you to accept payments via PayPal.”

    Since the guides didn’t mention this passage and I didn’t remember what I did month ago, I’ve felt lucky and tried for the third option.

    If you select the third option (NVP/SOAP API integration) there are other two options

    – Request an API signature if your shopping cart or solution provider has asked for an API username, password and signature, or if you’re developing a custom shopping cart.

    or

    – Request an API certificate if your shopping cart or solution provider requires a file-based certificate.

    also here, without having instruction in the guide I’ve just assumed that since the plungin is asking for username, pass and signature, the right option would the first one.

    So I did it, all good but even if I have previously deleted and removed the old credentials, the API user is still the old one, that one generated with the old email used to register the PayPal account which now is not anymore the primary address.

    What’s next? I mean, why I did all of this if in the end the API user is based on the old email address? (notice that I’ve logged using the new primary email not the old one which not is saved in the account but not as primary)

    Thank you

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter icks13

    (@icks13)

    I think that I really need a guide to make this process because is pretty confusing.

    The process described above, has been done by clicking on “this tool” as part of this sentence:

    “Get your live account API credentials from your PayPal account profile
    or by using this tool.”

    Now I wanted to change the credentials for the Sandbox and so I’ve clicked on “PayPal developer account” as part of this sentence:

    “The sandbox is PayPal’s test environment and is only for use with sandbox accounts created within your PayPal developer account.”

    This second link brings to a different page than the first one “this tool”. Here you can switch from sandbox and live with a button at the top right in order to have the various credentials, however this credentials are called in a different way from the plungin backend.

    In the plugin backend for both, sandbox and live you have:

    API User Name
    API Password
    API Signature

    here instead you have:

    Paypal account
    Client ID
    Secret

    also, this page describe better what is NVP/SOAP API integration, and it seems to be for adaptive payments. besides this I do not understand neither how to cancel the developer account ’cause there’s no delete button, meh I think you could include this steps in this page https://www.angelleye.com/paypal-express-checkout-for-woocommerce-setup-guide/

    Thread Starter icks13

    (@icks13)

    For sandbox API I may have solved, in spite of the fact that I have the whole dashboard in German just because I live here. Isn’t any option to change it like in the live account?

    About the live API the two problems are still there, no matter how much I look, nowhere is written what should be the option to pick between:

    – Pre-built payment solution
    – NVP/SOAP API integration (Classic)

    and for some reason I can’t remove the old API, every time I click here https://www.paypal.com/us/cgi-bin/webscr?cmd=_login-api-run

    I’m redirected to a page that show me:

    For preconfigured shopping carts: Copy and paste the API username, password, and signature into your shopping cart configuration or administration screen.

    For building custom shopping carts: Store the following credential information in a secure location with limited access.

    Credential API Signature
    API Username Show

    Signature Show

    and signature and API username are always the same one, even if I clicked “remove” on them multiple time

    Thread Starter icks13

    (@icks13)

    Ok, I have some problem with sandbox too. I can’t do an Express Checkout Payment without having a PayPal account, I mean neither test it actually.

    I think that the reason this time it’s because when I’ve created the sandbox account I have specified Germany as country of the business (sucking choice since I live here but I do not speak German -_-)

    I wanted to test a payment like the other times using a fake customer profile I’ve registered with my personal hotmail address, unfortunately, even if the checkout is marked to allow guests, it’s not working, is forcing the login into a PayPal account.

    https://ibb.co/js8gxo

    Plugin Contributor angelleyesupport

    (@angelleyesupport)

    Hi There,
    You seems to be a lot more confused about that, We apologize about that. Allow me to simplify that for you.
    In you PayPal Business account under profile ans settings , go to My selling tool and then click on API access, You may see a screen like this ( https://prntscr.com/jtrpxn ) if you have not setup your Business account already. From the screenshot Select : Setup an API access when you go LIVE. Clicking on that will show you 2 options as you mentioned above.

    You need to choose : – NVP/SOAP API integration (Classic)
    Then it will show you something like this: https://prntscr.com/jtrt4w

    Click to show those API credentials then put them In you site > WC settings > Payments > PayPal express Checkout > Live API details.

    This way you will be good to start accepting payments on your site.

    let me know if you still have any other questions or concerns.

    [ Signature deleted ]

    • This reply was modified 6 years, 9 months ago by Jan Dembowski.
    Thread Starter icks13

    (@icks13)

    Hello Oliver,

    thank you for your reply.

    Well I’m confuse ’cause I’m missing information, I don’t know how I did it the first time ’cause I remember was much super fast.

    – When you say “in your PayPal business account” you mean the business account created withing the sandbox?

    Ok, then I will choose NVP/SOAP API, I can get there by clicking on the link in your plugin:
    https://www.paypal.com/us/cgi-bin/webscr?cmd=_login-api-run

    The problem is that it will shows me this:

    https://prnt.sc/jtu13g

    the API username and signature are OLD. The belongs to the old email address we have used to register our PayPal account, now we have a new primary address.
    In a previous thread here, you have said to use the new email address to get the API details.

    Apparently I can’t, because like I’ve preivously said, I’ve clicked on remove many times, but these API are not removed, they are always there and I’m sure, because the old email was ending with @gmail.com and that API username is still ending with gmail.com instead with our store domain and does not matter if I remove and then I select NVP/SOAP API integration (Classic), the signature will change but the API username will remain the old one.

    There is also the problem connected with my last update and related to this screenshot https://ibb.co/js8gxo where even if the guest checkout is enabled, customer is forced to create a PayPal account

    ty

    Thread Starter icks13

    (@icks13)

    in relation of this:

    There is also the problem connected with my last update and related to this screenshot https://ibb.co/js8gxo where even if the guest checkout is enabled, customer is forced to create a PayPal account

    the above part is solved but I have to say that your guide seems based on the following principle:

    “as soon as the user leave the plugin to interact with PayPal I will not provide further explanation in the guide”

    also I think you should consider that while you are based in USA this plugin is used everywhere around the world and some stuff may not match, for example I have no clue where is this “website references” indicated on mouse over close to the checkbox the allow customer for guest checkout. PayPal account sandbox? PayPal account use to receive the payments? well, for sure is not in the paypal account I use to receive payments.

    Remains to understand why the API username remains the same with @gmail at the end.

    Thanks

    Plugin Contributor angelleye

    (@angelleye)

    @icks13, I agree we need to update our documentation based on some changes that PayPal has made. It’s difficult because depending on your location and what version of PayPal account you’re on…and whether you’re part of their split testing…people see different screens.

    As you mentioned, the link we provided for “this tool” in the settings does take you directly to the Signature credentials, which is what you want. The username is something that gets created the first time you set them up, and it uses the current email address as part of that value it generates. If you change your email later, the API username will not change. Otherwise it would break any integrations you have. So don’t worry about the value itself. It could be complete gibberish and it would still work as long as it matches what they’re giving you there.

    What’s interesting to me is that it’s not showing an API Password in the screenshot you provided. You should see username, password, and signature, but I only see username and signature in your screenshot. If it’s not giving you a password you’re going to need to contact PayPal about that as that is not something I’ve ever seen before.

    So again, the API credentials cannot really be “old”. They are what they are, and it doesn’t matter if it looks like it’s based on an old email address. It will still work fine. You do need all three values, though, so again, you may need to reach out to PayPal about that.

    Hopefully that helps but let me know if you have any other questions or concerns.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘New API Request’ is closed to new replies.