I got a problem with the Facebook App Review. I have to verify my Business Account, but the last step "Contract signed" won't be confirmed. I accepted the Supplemental Terms via mail and I also got a confirmation mail from Facebook that I accepted it.
Do I have to wait? Did I forget something?
Greetings Basti
Searching my email I noticed there is a seperate "Supplemental Terms" to be signed.
After signing both documents the app is queued for review again - at least that's what I think is going on given the alert message they display on the report a bug page:
We have detected that this app is currently queued for review. Please
be aware that reviews are undergoing heavy delays while we work to
clear the large backlog of submissions. We appreciate your patience,
and your app will be reviewed.
I was unsure if was in really in queue, since the App Review page does not make it clear. However, an hour or so after signing the second document the App Review page was updated:
Your contract is under review and your status will be updated upon completion.
You need to accept Supplemental Terms and Tech Provider Agreement. They are sent in 2 separate emails.
Once you accept and sign both agreements, your review status page will show
And then you wait for Facebook to review the signed agreements.
Related
Im working on moodle paypal enrollment feature. I saw that lessons were not getting enrolled to the student even after the successful paypal payemnt. Because the Paypal 'Payment review' setting was set to ON so all the payments are were in pending. I have turned OFF that setting. now I can see the payment complete.
but I do not see an option to accept the 'pending' transaction in sandbox/developer account as seller? Also when seller approves the payment will it trigger IPN simulator and update the payment status to my website?
When payment accepted manually will that call IPN url http://example.com.com/availability/condition/paypal/ipn.php for moodle lessons?
please help me
The Payment Review feature identifies high-risk transactions and notifies merchants of the review so they can hold shipments until PayPal has evaluated the transaction risk.
Yes, you will receive one more notification, when the transaction review will be resolved.
With status:
payment_status: Completed (If the transaction succeeded and the payment was accepted)
payment_status: Reversed (If the transaction failed and the payment was rejected)
You'll find all the notifications here:
https://www.sandbox.paypal.com/de/cgi-bin/webscr?cmd=_display-ipns-history
My understanding is that you just can't any more. I took this up with PayPal when they redesigned the Transaction Details screen because in the old version, there were indeed Accept/Deny actions as the help page that Ivan has provided a link to.
The support rep's response was "yes, this is an omission which I'll take up with development. For now, you can use the old interface, where you should find those options".
Now, that's probably 2 or more years ago (say 2019) and I haven't seen these Accept/Deny options appear in any transaction details page in the current version, and now there's no option to revert to the old version which did have them.
As a developer, I find PayPal's UI and feature set a set of moving goalposts that it's nigh on impossible to keep up with. I now can't even access my old support tickets to find out what the exact response was. I personally detest the platform.
I have created and submitted a Paypal application ( using the classic API). The application is in a conditionally approved state. Paypal reached out and asked additional questions which I responded back with details. The application does not use the Paypal API to make payments. It only reads transactions related data and shows useful reports and insights for users. The API permissions requested are
1.Obtain transaction specific information.
2.Obtain your paypal account balance
3.Search your transaction specific information.
4.Search your transactions for items that match specific criteria and display the results
I was able to get a live app id and also have the API username, password and API signature. However since our app uses Paypal oauth, the permissions part doesn't work . My guess is this is because the app is conditionally approved. Is this the right assumption? Also what is the typical timeline for an app to get approved? My Paypal account from which I created and submitted the app is a verified account. I have sent messages from within my developer portal to support but I haven't heard anything back.
So far we have been working with a sandbox account. The live application I created is in a different account than the sandbox account. I am not sure if this is an issue.Would be great if someone who has been through the process can confirm.
Unfortunately there is not really a "typical" time frame for app approvals as too many factors go into the approval process. The best thing would be to call in to PayPal to inquire on the status.
Hi there!
I recently created a paypal app in paypal developer, I entered informations on the app but still a warning is shown in the 'accept payments' area (see picture). Whats the error? ...there's no description at all!
There is an issue currently where users aren't able to submit new apps on Developer.PayPal.com. There are a couple potential workarounds that you may want to check.
Ensure that your Developer.PayPal.com account has a first and last name associated with it and that you have a "facilitator" account saved in the "Sandbox accounts" section. If you don't have a "facilitator" account you can add one by just creating a new account with the e-mail address formatted like this - xy-facilitator#domain.com
I'll update this thread again when a fix is released or if more information is provided.
Edit: The issue where valid accounts were unable to submit an application should be fixed now. Make sure that the account you're requesting an app for is on this list and you should be good to go: https://developer.paypal.com/webapps/developer/docs/integration/direct/rest_api_payment_country_currency_support/
I recently done this on developer paypal portal.i had also this mark on my app but after filling the information and we need to include mass payment in our app so we just contacted paypal to enable this feature as this is disabled by default and developer needs to contact paypal to enable this.So now i have approved status on my app and no alert mark for any info.
We're very close to launching our app and we want to test the dispute/refund process. We've made several successful test payments however we're hesitant to dispute them. Will our app get flagged? What is the best way to test the dispute/refund process?
They've listed all the documents for it here:
https://developers.facebook.com/docs/howtos/payments/disputesrefunds/
I'm sure if you put in the dispute reason "This is a test for the developer: please ignore" or something or contacted Facebook and asked them they'd find a way. There is though, at present, no public method of testing dispute handling.
While you cannot test the flow end to end, you can test the integration with your backend by manually executing a POST request to /PAYMENT_ID/refunds with an app access token and the amount to be refunded (could be total or partial). There is no need to start a dispute through FB to be able to refund it from your app.
If a dispute justifies a refund, you can award one using the transactions's ID and making a post to the /PAYMENT_ID/refunds with an ~app access token~ and the amount to be refunded [...] The dispute status will automatically be set to resolved with the refunded_in_cash reason.
A payment doesn't necessarily have to be disputed by the consumer for you to be able to refund it. If a user contacts you directly, you can issue a refund for the payment as long as the refundable_amount is greater than the amount you're trying to refund. This functionality is also helpful when you are testing your app.
Source: https://developers.facebook.com/docs/games_payments/fulfillment/disputes
I'm writing an iPhone app. The question is regarding the new rules restricting purchases inside the app.
So: the user charges their account up with 'credits' on the associated website using real money via a payment provider. The user installs the app and logs in using the same account as is used on the website: they cannot use the app without first logging in [edit: although they can register an account without adding any credits.].
The purpose of the app is to build up a report about a property, which can then be emailed out, or exported to their account to appear on the website. The report can be built up without using any credits. However, to export the report to the website or email it out, these credits must be expended by contacting the server and debiting X amount from the user's credits.
Here's the question:
The user's account is debited whenever they do this export. Only if/when the user's account is out of credit does the app complain that credits are low (otherwise it doesn't mention them), and it tells the user to go to the website to top-up their account to proceed. Remember that they can't login without an account, which can only be created on the website, and the website explains this.
From the guidelines:
11.13 Apps that link to external mechanisms for purchases or subscriptions to be used in the app, such as a “buy” button that goes
to a web site to purchase a digital book, will be rejected
So, my app does not provide a link to the website when explaining that their account is low on credits, it just says that this is what is needed to proceed. The export function, however, does require that the user has topped up their account, so in a sense this does fall foul of the next rule:
Apps that unlock or enable additional features or functionality with mechanisms other than the App Store will be rejected
I'm somewhat worried that this credit currency will fall foul of these recently-tightened rules, does anyone want to please reassure me (or, break the bad news)?
P.s. Spotify requires that users pay a subscription (on their website) to use the iPhone app. The difference between them and the above is that their subscription is unlimited-use whereas the above has a per-use charge.
Thanks in advance,
Ian
When you submit your app, include a tester username / password to the App Store. Fuel this account with a few million credits so they don't see the reference to Credits Low. There are many apps that get rejected just for having a login - if you make the reviewer's job easier by having a user/pw they can use, it'll increase your chance of acception.
If you app does get rejected, it means you have to change your model anyway. Actually - you might just be able to add 'Buy Credits' as an in-app purchase to appease Apple. Just make sure the credits in-app cost the same or less than externally - as far as I can tell, Apple will let you keep external purchases around as long as they cost the same or more than in-app purchasing.
Additionally, make sure your "low credits" alert doesn't link to an external page to buy more credits-- this may be frowned upon.
I'm sorry to break it to you but it definitely is a grey area and could potentially get your App rejected because you are asking the user to go to an external source to purchase credits which means Apple is cut out from any potential revenue.
I've had first had experience with this sort of rejection, all that was the issue was the description pointed to a web page where you could buy the product but Apple still had a hissy fit about it and added 2 months to the approval time and it ended up with me removing the link.
You could warn the User that their credits are running low, however pointing to the page to purchase them could potentially be the tipping scale.
On the other hand, there are some apps which make it through but there is no certainty. You are at the mercy of the reviewer in the end... You could potentially ask Apple Developer Support for any further information after describing your scenario.