I have tried to do the transaction between two UPI id (both was normal account, that is, not a merchant account).
I have tried to do the transaction with Phonepay, but Phone pay says,
For security reasons, you are not allowed to send money from your bank for this payment.
Maybe you need to check this:
Several major payment apps are looking to avoid fraud on UPI by doing
a strict check on the authenticity of payments. This makes these issues
appear more related to the lack of merchant signature in the current
version of the package. This is further seen in the following snippet
from the UPI deep linking specification which is about how a UPI
payment app should verify a UPI deep linking request (the ones made
through this package)
You can find more details on this issue or similar issues here
Related
I want to make a payment system in which users can connect their PayPal account to a website. In this step, login required.
When transaction occurs, without having to log in again, users can pay to the site.
This would be quite different from PayPal subscriptions -- just auto payment like upwork client account.
What you are looking seems to be a "Reference Transactions" solution. It can be tested in sandbox, but to use it in live, the business account would need to be approved for this feature by PayPal. To do this the account owner would need to contact their PayPal account manager or PayPal's general customer support (not MTS), and explain the business need for this feature.
As far as implementing the solution, the only public documentation I'm aware of is for classic APIs: https://developer.paypal.com/docs/classic/express-checkout/ec-set-up-reference-transactions/ . Any newer API or vault solution does not appear to be publicly available at this time, but you could always contact PayPal's support and ask if there's something they'd rather you implement than those classic APIs. The more significant hurdle is the business approval for the feature mentioned earlier.
Hi I am implementing paypal API on my website where different vendors come and sell their products.Currently I am using sandbox environment.Payments are working perfectly using paypal account but payments are not working using Credit Card.Getting following error:
We are sorry, we are experiencing temporary difficulties. Please try again later. If this error occurred while making a payment, avoid duplicate payments by checking your Account Overview before resending a payment.
For some browsers, this problem can be resolved by clearing or
deleting cookies.
Message 6838
Any ideas?
If this is an issue that is happening with every transaction, make certain that you are using live credentials with live endpoints.
If you are using Express Checkout make certain you have the correct API Signature credentials.
Below are two links for going live and correct API Endpoints:
PayPal Developer Site, Going Live
API Endpoints
If this is happening on only a handful of transactions it may be a technical issue.You can submit a ticket to PayPal Merchant Technical Support
I have what seems to be an uncommon situation. I need to accept payments on my website and send them to various merchants that do their business though my app.
So the payment flow is:
Payer -> My App -> My Customer
This flow seems to be exactly facilitated by paypal's adaptive payments api and while I have pored over all their integration guides, there doesn't seem to be any documentation for even simple email to account verification.
My question is, how can I verify that an email belongs to a verified paypal business account, or perform some other hand shake verification? Is there a way to do that, or even a good workaround? Thanks!
Found this API endpoint today:
https://developer.paypal.com/webapps/developer/docs/classic/api/adaptive-accounts/GetVerifiedStatus_API_Operation/
It seems to do what I wanted, and it at least indirectly test account existence and definitely tests the verified status.
One caveat that I would add for posterity is that in sandbox mode, you may only test against sandbox accounts that you have created for your app.
I am trying to find a method to implement chained payments, but where I am the secondary receiver, and am making the API call on behalf of another PayPal account, who would be the primary receiver. Is it possible to make this API call on behalf of another person? The other person would likely has a Verified Premiere account (rather than a Business Verified account).
One reason I am unsure that this is possible is because the documentation on chained payments clearly states 'The API caller must get permission from PayPal to use chained payments.' (via https://developer.paypal.com/webapps/developer/docs/classic/adaptive-payments/integration-guide/APIntro/), but it doesn't make it clear what that means. Does anyone know what the requirements are? Would both I and the primary receiver need this 'permission'? How does one go about getting this permission?
When you create an APP-ID in the developer.paypal.com center (see under Reviewing applications with Adaptive API calls) you set up which features your applications will use. Some features are considered "basic" and do not require any special permissions adn your app will have a status of "Approved Automatically" if your app needs some special features (such is chained payments) your app will have to got through review process and the status will be "Conditionally Approved" What this means you can use basic features (such as simple adaptive payments) but you cannot use special features, until it is approved. Furthermore when you create an APP ID you have to specify that you will use this feature (granting permissions to third party user) so that APP is enabled to use this feature
Edit: Worth to note that when create the sandbox account your application will have all features enabled and it wil not require any special permissions from Paypal, so don't be fooled by that; because once you go live it will throw an error if your APP-ID is not approved (or rather if it is conditionally approved). Review process can take weeks, so I will advise to plan in advance and not take assumptions that if it works in sandbox environment that it will work in live by default.
NOTE: I've already looked at reasons for paypal 10544 Gateway Decline error. This is happening in production for us.
We use DoDirectPayment and DoReferenceTransaction with our customers to set up a regular payment transactions and when we get failures, the vast majority of them are for this error code. I've asked for details for specific transactions before and was instructed to get our client to contact PayPal directly for security reasons, which is understandable.
But I was wondering if there was something more to this particular error than the rather vague description implies. E.g. is there some setting in the account settings that causes it to occur more often than it needs to? Is it because we are a Canadian merchant accepting credit cards from other currencies?
We don't really like asking our customers to contact PayPal about this because it feels like we're passing the buck.
This is a catch-all for a variety of messages that unfortunately aren't spelled out in the Payflow Gateway Developers Guide but do appear here Classic API Error Codes with a vague explanation of:
The transaction was declined by PayPal. Contact PayPal for more information.
We recently switched to Paypal from Paymentech (but still using Payflow Gateway). About 15 of our customers with monthly service billings began getting declined. These were all customers whose credit cards were approved for years on Paymentech.
Paypal told us that (for security reasons) the customer had to call Paypal directly for more information. One of our customers did that and reported that Paypal couldn't tell them what was up so they lifted the "ban" on that card. Another customer reported that Paypal support couldn't understand that this was a problem with a Merchant account, not a Personal. Yet another left us for the competition.
In the end, I wrote code to trap for this error and print the following message on our commerce site and email notification:
Our payment processor, PayPal, was unable to process your credit card. Please try a different card, or contact PayPal Support at 888.221.1161 to determine why your credit card wasn't accepted.
Furthermore, I've ask that this be escalated within Paypal because this is bit of a hack.
There is not a lot more specific reason for this error, it is vague due to the number of reasons that can cause this. Usually this is due to an issue with the buyers account or card, in which case the buyer would need to contact PayPal to resolve the issue.