Transaction exceeded the individual limit of 0$ - paypal

When I am trying to make payments to my Sandbox test store I keep getting this error. It was working fine a few days back.

Related

Paypal adaptive payments blocking payment because of regulatory requirements

I've suddenly been getting this error since yesterday when paying multiple accounts: "Invalid request: We had to block this payment because it didn't comply with regulatory requirements".
This was working fine last week (and have been so for a long time) but started returning this error yesterday. I can't find any info about it and what needs to be done, can anyone help?
Without more information about the accounts involved and the full error message returned, it's only possible to guess that it might have to do with the country or currency of the accounts involved.
Contact PayPal for support

Paypal Sandbox giving 10623_AUTH while reauthorisation

We are trying to re-authorize an amount from paypal sandbox account. This feature is working fine in one of our paypal sandbox accounts.
But some of our other client sandbox accounts, are not allowing us to re-authorize any amount. It is giving us an error 10623 stating, max number of retries reached, though we have tried it for the first time only.
Are we missing something here, any insights on what needs to be taken care of here will be highly appreciated.
Regards.

Payout in Sandbox

Paypal newbie here. I am using the .net sdk to call PayPal's rest api in the Sandbox environment. I am trying to test a batch payout(Mass Payment).
Issue 1. The sandbox "facilitator" account which came pre-created has a zero balance. I cant seem to find any way to get some money in the account so that i can test payouts. If i create a new business account, i get to specify an opening balance, but when i try to do payouts using this new account, i get back a 403 forbidden response when i try to payout even though i am able to get a token successfully.
Issue 2: Using the facilitator account, i am able to submit a payout request, but its behavior seems to have changed since a couple of day ago. A few days ago, all payout request used to be DECLINED and would show up on the transactions list on the sandbox site. I assumed they were getting DECLINED because the balance was zero. Since yesterday, all payout transactions via the facilitator account stays in PENDING stage and they do not show up on the transaction list. A Payment/Get request for the payout_batch_id always returns back as pending even aftter a day, but theres no sign of those transactions on the sandbox site.
1 - Creating a fresh account and giving it an opening balance is correct, and that should work just fine for you to test MassPay. If you're getting a 403 error that sounds like a problem with your API endpoint or something. Need to see a sample of the API request/response to know more on that.
2 - Again, need to see a sample of the API request/response that you're getting to know more here. My MassPay transactions in the sandbox work just fine. Here's an example. You'll see the request and response data there, showing it was successful. Then when I go look at the separate accounts I see the money as expected.

PayPal Adaptive Payments login fails

My website uses the PayPal Adaptive Payments API with the Embedded Payments flow and simple payments. On my checkout page I execute a Pay API call, receive successful response, then call SetPaymentOptions and again get successful response. The customer then reviews the order form and upon confirmation of the order is redirected to https://www.paypal.com/webapps/adaptivepayment/flow/pay in the PPDGFrame iFrame with expType set to "light" and the paykey received from the Pay API call.
I have successfully tested it in a sandbox and rolled it out to production. The application worked great for a day or two and then stopped working, with buyers now receiving a "Please try again later" error when trying to login. I am still getting successful responses on both the Pay and the SetPaymentOptions API calls and the customer is successfully redirected to the PayPal login screen. The customer enters the login credentials, clicks the Login button and a couple seconds later gets the "Please try again later" message.
Now here are some really odd behaviours if I've ever seen odd... This problem first appeared about 4 days ago. Since PayPal advised me that it will take them "several weeks" to get back to me, I have tried the checkout again two days ago and experienced the same problem. I have then tried a guest checkout and it worked! Next I tried a regular user checkout and it was successful as well so I thought to myself that the problem has somehow resolved itself.
Yesterday morning I tried the checkout again, and got the same problem as before. Again I tried to checkout as guest, which again was successful, and then immediately after I have tried regular checkout and again this time I was able to login successfully.
Today the flow is broken again. What gives? Nothing is changing on my site. Why does it sometimes work and sometimes doesn't, and how is it that a guest checkout seems to be able to temporarily resolve the issue?
The problem has been resolved with no action on my part and no change to the website or application code. After a couple weeks of the API simply not working, it started working intermittently with gradually improving success rate while my support ticket with PayPal was sitting in a "Waiting" status. I was told that the "engineering team" is waiting for a server code roll-out. The intermittent nature of the problem and a gradually improving situation suggests that PayPal was rolling out a fix to their servers in a staged approach and outcome of the API operation depended on which server the PayPal load balancer happened to send the request to. After about a week of that, the problem was resolved completely. PayPal of course maintains that they have not made any server changes.

Testing Paypal errors, Always Transaction Response code always 36

I'm trying to test a few failure conditions using the test version of our pay-pal api. Specifically a recuring payment with an initial payment. Therefor I'm using the recurring payment adding an additional transaction. When testing for success (amounts less than $1000 for both recuring and initial transaction) everything works as expexted. According to the paypal documentation using amounts over $1000 should result in a response code that is the amount over $1000. regarless ov the amount I use the response code is 36.
I've also tried amounts over $2000 which should result in a response code of 12. However I still get 36.
The only details changing between the call that works as expected and those that don't is the amount.
Update
Upon further investigation, the recurring transaction response is 12, as expected. However the transaction response, which I'm assuming is what I need for the additional transaction is still 36. This is what I need to be testing against.
I've also tried different test card numbers as supplied by pay-apl.
On a side note... I realise this is not a programing question per-se, but I've been bounced here by pay-pal as their "Forum"!!!
Further Information
I am using the .net api(SDK) as provided by paypal