I am working on upgrading the paypal API used in my application to the latest version from version 56.
From the documentation, it seems that AMT field has been deprecated and we have to use PAYMENTREQUEST_n_ITEMAMT instead.Each payment in the transaction has a limit of 10 000.00 and only up to 10 payments are allowed.
Please help me with these questions
Did the AMT field have any such limitation earlier for a transaction?
In the new version, every transaction has a limit of 100 000?
If the payment amount is in lakhs, how do we handle this case in the new version in a single transaction?
Related
I am using PayPal Pro on a Shopify webstore. Is there a way to use the PayPal API to query my account and get a list of incoming deposits that would show the customer name, total sale, the fee deducted, and the net deposit?
The exact call you need is: https://developer.paypal.com/docs/classic/api/merchant/GetTransactionDetails_API_Operation_NVP/
But first you need a general idea how to use the API: start with https://developer.paypal.com/docs/classic/api/gs_PayPalAPIs/
There may be other ways to do this, but I'm (mis)using the PayPal lib included with the PayPal module in PrestaShop 1.6.x, which is based on 106 of the API (current is 204, search for "PayPal AND 'API Version History'" for version details), and it's working fine - I was able to pull fees on my latest transactions.
I spent like four weeks coding a plugin to work with PayPal Express Checkout instant update. It was working perfectly in the end with shipping and taxes updating as expected.
However, two days ago, the checkout layout got changed automatically from the classic one to the mobile-responsive version. Previously when I had the callback for instant update defined it automatically used to switch from the mobile-friendly version to the classic version. Now that is no longer the case and the instant update features don't seem to work at all with the mobile-friendly checkout.
Is there anything I can do about it or has PayPal stopped supporting instant update just when I finished my plugin?
I have the same problem..
UPDATE..
After emailing PayPal tech support they finally replied..
Unsupported features
In-Context Express Checkout does not support:
Parallel payments or multi-seller payments
Callback / Instant Update API operations
Billing agreements that use the deprecated SetCustomerBillingAgreement API operation
Seamless checkout for a Log in with PayPal integration
So yes, they stopped supporting instant update with Express Checkout, though they haven't removed the documentation as of yet.
I'm using the Paypal Express Checkout NVP (Name Value Pair) API. When I add a Callback URL for instant update shipping cost the whole paypal user interface changes to an older version that isn't mobile friendly / responsive.
When I try to force the mobile UI with "_mobile-express-checkout" I'm getting an Error-Message that I'm using an outdated version. But I'm using version 204 that is the most up to date version.
Is there any chance to get the responsive layout together with instant update for shipping cost?
We are planning to integrate to PayPal with following requirements:
We collect card based payments for US customers.
We are planning to integrate with Payflow Gateway with "Sage" as our processor.
We will have customers who will allow us to charge them on a periodic
basis (replenishment with Card on file).
Questions:
Is Payflow Gateway suitable for our requirements?
Does Payflow Gateway has a REST based interface? How do we tokenize (card on file) without keeping card numbers with us?
If "reference transaction" is the only way to do Card on file operation, how do we overcome the expiry period (1 year) of referenced transaction?
Payflow will do this through the reference transaction feature. For a reference transaction, you will be storing the transaction ID in your database, and the next time you want to charge the customer you will use the same transaction ID instead of passing the card details again.
Usually any transaction ID at Payflow is valid for one year, as per the docs. So in order to overcome that one year restriction, you are supposed to update your database every time with the latest transaction ID.
For example, a customer placed an order today, and you store the Payflow transaction ID in the database. Now suppose you need to charge the customer again after 7 months, then you will get a new transaction ID. This time, update your database with the new transaction ID for the same customer, and this way it will be valid again for another year.
You can do reference transactions (using the returned PNREF) but, like you said, they expire in 1 year. The only workaround for this I've found is to issue a zero-dollar authorization (ZDA) to get a new PNREF but there is some confusion about this with some reports saying that the new PNREF created by the ZDA will only work for 14 days.
The online version of the Payflow Pro Guide now states that the PNREF is good for reference transactions for "12 months and possibly up to 15 months". Unfortunately, that is pretty ambiguous wording that doesn't clear up very much.
Payment via PayPal credit/debit cards apparently ceased to function entirely on my website since a month ago.
I see the version specified in the code is 94.0 whereas the current version is (99.0). Can this be the reason why payments don't work anymore?