Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 2 years ago.
Improve this question
Moving from sandbox to live
I have Password, Username and Signature and my sandbox implementation working fine.
but when i change it to live i did not find any Password, Username and Signature here I have Client ID, Secret and Paypal account.
Am I missing something here?
Are they same ?
Password => Client ID;
Username => Paypal account;
Signature => Secret;
https://api-3t.sandbox.paypal.com/nvp
They are not the same, Client/Secret is for the new REST APIs.
To obtain your live Username/Password/Signature for older Classic APIs, go to http://www.paypal.com/api -> Classic NVP/SOAP Credentials
And of course, when using live credentials, remove "sandbox." from the domain of all endpoints you are connecting/redirecting to.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
Have a bit of a sticky situation, working on upgrading an existing codebase to use the v2 REST API from PayPal for an ecommerce checkout and would like to replace billing/shipping info with the (verified) address data from the response after authorizing the requested payment total. However, I would need to recalculate real-time shipping costs and taxes based on the address returned from PayPal if it does not match the address supplied in our checkout flow. Is there a way I can modify the requested amount with new costs after the initial authorization without voiding the original? The documentation isn't the most clear, and seems to randomly jump between v1 and v2 API docs.
Yes. Submit the modified amount(s) in your v2/orders capture call.
All I needed to do was run a GET request to /v2/checkout/orders/(paypal order token) after returning from PayPal in order to pull in the address they supplied prior to the authorization request to compare against the original address and recalculate/update the order as needed, and run a PATCH to the order endpoint to set the new value before completing the authorization request.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
i searched many times but all of sites says that it will be in settings / security tab, but it's not there! why?
i just created my Facebook account.
It looks like FB is not currently using security questions. This is from FB:
If there ever comes a time where you can’t log into your Facebook account, we need ways to get in touch with you and make sure the account is yours. Here are some things you can do to help make sure you never get locked out of your account:
Add another email address to your account so you always have a
backup.
Make sure you and only you can access the email addresses listed on your Facebook account. Anyone with access to one of the email
addresses listed on your account can request a new password for your
Facebook account. If you lose access to one of your extra email
addresses, be sure to remove it from your Facebook account.
Add your mobile number to your account. We can also send things (ex: a code to reset your password) to your mobile phone.
Use your real name and date of birth on your account so we can find your timeline if you ever loose access to it.
You can find more details on this security features page.
facebook now does not offer any security questions for account safety. It uses now two-factor security model and sms authentication code. Don't go in that deeply.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have developed a website that allows users to subscribe to a service using their Facebook credentials.
How do we create test Facebook accounts that can be used to execute end-user test cases for this feature?
You can create test users via the Graph API. You shouldn't refer to them as "fake" users because that has some negative connotations; Facebook actively peruses and shut's down fake accounts. I believe what you are talking about though is accounts to test Facebook applications...
The documentation details how to create test users via the api -
https://graph.facebook.com/APP_ID/accounts/test-users?
installed=true
&name=FULL_NAME
&locale=en_US
&permissions=read_stream
&method=post
&access_token=APP_ACCESS_TOKEN
You'll need to substitute all your own data in the request and the response you'll get back should look something like this -
{
"id": "1234...",
"access_token":"1234567..." ,
"login_url":"https://www.facebook.com/platform/test_account..."
"email": "example...#tfbnw.net",
"password": "1234..."
}
You can then use that users credentials to test your applications authentication process and functionality.
In addition to creating test accounts via the api, you can also use the interface within the application's dashboard under the "Roles" section - https://developers.facebook.com/apps/APP_ID/roles
Had the test accounts set up with no problem. Finally found the parameter I was missing to get the accounts to interact with the website properly.
Cheers.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
I have implemented all of the purchases and created the test user accounts - yet when I come to test; it says that I need to be signed in as a test user, obviously. The problem is I'm not sure how to log in as my 'test account' as the it's not an official account technically. I'm unsure of where I need to go to get access to the test user?
As #shabzco said you should log out with Settings --> iTunes & App Stores --> Logout.
However, you should not log in again using this page with your test account or iTunes will ask you to 'verify payment information' which you can't do as it's a test account.
Instead, run your app, make your test purchase and when the IAP popup appears enter your test user details.
Note the popup will say 'Environment: Sandbox' which indicates that it's a test purchase and no-one will be charged.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
In my country apple does not support subscription, I can't make an app that can purchase monthly or period of time subscription, any alternatives?
Contact Apple and ask if this is a temporary or constant condition. If it's temporary, wait it out.
Otherwise, you can implement login screens and authentication mechanisms as you would have them in a WebApp. The latest Developer Agreements allow for this (as opposed to the previous agreements where you had to offer inAppPurchase as well). The caveat is that according to the agreement, you may not link to your 3rd party payment/signup site from within the app.
Set up payment processing with the provider of your choice (e.g. PayPal) and manage your own database of registered users. Then, when a user starts the app, ask them to log-in by supplying a username and password. Send those to your server (e.g. using a regular POST request), verify them and deliver the contents to the user if he is authenticated.
Make sure to keep the user logged in after that to avoid annoyance.
The main challenge with this approach will be to let users find out about your service in the first place as you are not allowed to openly send them over in the first place. Then again, if Apple doesn't offer the functionality in your country, you may be able to get through review with it.
In either case, contact Apple, then act accordingly.