Is it possible to process an authorization/payment through PayPal's API using the card magnetic stripe data rather than populating number and other fields? I'm aware that I can parse the track data and supply the fields they are requesting, but that is still processed as a card-not-present/eCommerce payment with a higher fee than if the payment was processed with the track data.
PayPal does have a POS API that allows you to send track data over to PayPal so it's treated as card-present, however, you don't get the lower fee. PayPal does. You still pay the 1.9 - 2.9 that you qualify for based on your volume.
Also, that API is only open to a few PayPal Partners. If you're an official PayPal Partner let me know and I can get you some more details.
Related
I am beating my head against the wall with this one. I am setting up a payment using the PayPal Adaptive Payments API, where one of my platform's users receives a payment from their customer. I need to be able to see the amount of the PayPal fee related to that transaction.
I'm familiar with and have tried using the PaymentDetails API operation, but unfortunately, the only quasi-relevant information that method (and the IPN) returns is fees_payer (who paid the fees), not the amount of the fee.
I've also looked into the GetTransactionDetails operation, but that appears to be only for Express Checkout and Website Payments Pro APIs, according to this document.
Any ideas how I can determine the fee amount on these transactions?
With Adaptive Payments the IPNNotificationURL specified in the Pay request would be an app specific IPN that won't provide much info about that payment itself.
If you setup IPN in the receiver account profile, then an additional IPN would be triggered that would be transaction specific and would include the fee.
Is it possible to update my card details stored in my PayPal account via a 3rd party app with the use of an API? I came across the below documentation but wasn't too sure in which scenarios it could be used?
"Update a stored credit card
Operation
PATCH /v1/vault/credit-cards/
Use this call to modify a credit card."
Any thoughts?
There is no API's available for updating the credit card on your PayPal account.
But, using Adaptive Payments, you can just add a new Payment Card using AddPaymentCard API.
Although, you would need to apply for an application at apps.paypal.com
The vault is for REST API which is used to store(encrypt) the buyer's credit card information and could be used for future transactions.The Vault API provides a secure way to store customer credit cards. By storing cards with PayPal, you can avoid storing them on your servers.
Is there any way to retrieve the transaction fee charged by Paypal using the REST API?
I've got a mobile application that makes a charge using the Paypal SDK, and then posts the transaction ID to the server. I'm trying to use this to get the transaction fee from Paypal.
Looking at the documentation, it looks like the fee should be returned as part of the details object, though it's not clear how to get this from the payment.
For example, if I get the payment using the following endpoint:
/v1/payments/payment/PAY-XXXXXXX
The response returns information about the transaction, including the amount and currency, but nothing about the Paypal fee.
I've also tried looking up the sale (/v1/payments/sale/XXXXXXX) but that doesn't return anything about the Paypal fees either.
Interestingly enough, I don't seem to be able to view this information either from the transactions grid in the web interface, but I'm sure this information was definitely available in the old version of the web interface (before the redesign).
Not sure if I'm missing something obvious here.
Unfortunately, despite being documented, it seems this hasn't been implemented. According to PayPal Merchant Technical Support, on 02/16/2015:
"Kindly take note that transaction fees will not be returned in REST APIs response and I am not being able to ensure whether this will be implemented in future."
I learned that fee tracking was a requirement for my company's PayPal implementation, and I ended up switching to SDKs as a result.
The details object of the amount object has a fee field, which when you look up the sale using the URL you mentioned above should be in each transaction in the transactions array.
This should return the value you are looking for.
I am using REST API to enable Paypal option on my site. To help the finance department for future taxation issues, I am trying to set up VAT rates based on the country.
After googling a bit and checking the documentation, found out Paypal's tools for setting the sales tax - https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/ProfileAndTools/#id08A9ED090WS
But after setting the value on the config page like this:
I still cant see any tax information while I am trying to buy some test items (I had to cover some parts of the screenshots :/ )
And after a successful test purchase, I get tax=0.00 in the IPN response.
Am I missing some points on the documentation about using the auto-tax calculator of Paypal? Even setting taxing data while sending request to Paypal does not let me see the taxing information and other details on the form.
PayPal's tax calculator is a free tool included with PayPal Payments Standard; it doesn't work with any of the API based products. You will need to calculate tax and pass it to PayPal in the API call.
I want to use PayPal Payment Advanced API to store the customer's credit card info on the PayPal's website the first time the customer enters the credit card info. For subsequent customer visits, i want to retrieve the Credit Card info from the PayPal's server. Is this possible? What does the PayPal server return me ( like a transaction id )that I can store in my database for that customer and then use it for subsequent requests.
Thanks
There is no API for Paypal payments advanced. From their tutorials:
PayPal Payments Advanced requires use of PayPal's hosted checkout template...
This means that you have to use their hosted pages (you can probably do so using an iframe if you want). The reason for that is that in order to collect credit-card details you have to be PCI compliant, meaning, you have to pass a series of security checks/tests. This process took my company almost two years and major development (and other) resources, so you probably don't want to go down that path.