Seeking guidance, help.
My current instance of Salesforce B2C Commerce is leveraging a third party payment processor/gateway (e.g. Paypal, Stripe, Adyen etc...). Experiencing an issue on certain orders only, where orders are being created but no actual payment transaction. Now this happens to certain orders only, and I am unable to troubleshoot it as there aren't any error logs in Business Manager nor the payment processor/gateway logs.
Anyone experienced the same? Where else could I check for orders sitting in "created" state without an actual payment transaction?
Checked on the following things:
Tested with bad test payment methods like credit cards
Tested with last minute stock changes
Validated webhooks and looked for errors relating to "time-outs" (couldn't find any)
Checked the actual order in business manager
Related
I have a PayPal application that I just got to live mode using the developer console in PayPal
In this application I will using my PayPal application to transfer money between our users.
So far so good and the transactions are working , the money is getting passed between our users,
I just cannot see any indications or records any where in PayPal user interface.
I tried to create reports using the activity log here : https://www.paypal.com/activities
but I cannot see anything related to the transactions of our users
where I can see the records of all the transactions that are been made in my PayPal application using their Interface ?
If the transaction is not between your account (but rather between users' PayPal accounts), there will be no reporting available on such transactions for you in PayPal.com account nor the transaction reporting API of that account..
To use the transaction reporting API on behalf of third parties (without a client id and secret from their account) requires being a PayPal partner.
If you are facilitating transactions between users, the solution is to record the successful capture in your own database for reporting purposes.
I am working with paypal first time.
I have a product and I want to integrate paypal with it.
I want to achieve the following tasks :
Client comes to my website and select a plan,which is a monthly recurring plan.
Then client is redirected to Paypal for payment.
Client makes payment.
Return backs to home page.
I have gone through the documentation of paypal and I have the following questions.
What should I use REST API or Classic Sdk, as I want to create Recurring Profile,Work with EXPRESS-CHECKOUT and REFERENCE TRANSACTIONS.
I have customers all over globe and it is stated in the documentation that, for the customers in Germany and China , I have to use REFERENCE TRANSACTION.
Some where in the documentation of Merchant SDK it is stated that the classic API's will be deprecated, so is it a good approach to use Classic SDK
I also wanted to track the transactions(payment) made by user, so that I can show him the amount that is deducted in each month in his profile details.
Please suggest a feasible solution to my problem.
Thanks in advance.
Here's what I use. I went to Web Payments Standard and created a Subscription button. (I like the unencrypted variety, but you can encrypt if you want.) In there, you set the terms of the subscription, as well as where to post the IPN message. When the IPN message comes back, you deal with it. You'll get a subscr_signup at the start along with a subscr_payment. Then, on renewals, you'll get a subscr_payment again. What I like to do is store every verified IPN message in the database for my customer.
For handling the management of those subscriptions for things like tracking info, refunds, subscription cancellations, and voids, you'll need to use NVP API, which is a very simple API. If you stored in a database every IPN message with all those fields, then you should be able to pass certain fields of those to the NVP API in order to get what you need done.
If you're worried about longevity of the APIs, then don't. All they do when they deprecate APIs is stop giving you good docs on them. They still let those older versions run. If they didn't, there would be major upheaval on the web with web commerce products breaking all over the place. However, that said, if you want to prepare for the future, then get on the Braintree Payments API because PayPal bought Braintree and that's the future of their API.
I am testing the PayPal REST API for subscriptions in the sandbox environment, and have noticed that, when going to the approval URL returned after creating an agreement, no price is shown under the order summary pane on the left of the page. A description is shown but no price/tax etc.
The plan id is passed to the call to create an agreement, which contains the information that I would expect to see as a user when approving the payment. Is this a bug or is there something that I am supposed to enable in the merchant account, or perhaps something additional that needs to be sent when creating the agreement? I've read other posts regarding this on stack overflow (although they predate the creation of the subscriptions REST API) talking about passing a transaction field, but this isn't valid in the subscriptions create agreement schema.
Your observations are (currently) correct. As REST API based Billing Plans are based on Express Checkout Recurring Payments, you're going to see a similar behavior.
Right now, there are two options:
You populate the description with more agreement details.
You pass a regular description and make sure the customer is aware of the billing terms before your execute the agreement.
Going forward, we're likely going to include this info in some later updates. I'm following up with that to make sure a user story is filed for this.
I need some help with a very annoying problem. We have a Paypal Payments Pro account and use the Paypal_Merchant_SDK (.NET) to process direct payments on our site via API calls using the live credentials we got from paypal.com. We have been live for several months, transactions processing successfully.
Now we want a small change to way we accept payments. We want to reject transactions with wrong CV2 code. So after calls with Paypal support we were told we needed Advanced Fraud protection added to our manager account (manager.paypal.com). So we added it and set the "CSC Failure" fraud filter to reject transactions on non-matches and deployed it to live (active mode). All status messages say it was deployed successfully. We waited for several hours and tested, it didn't work - still processes transactions with wrong CV2 code and we get this message "This transaction was approved. However, the Card Security Code provided had too few, too many, or invalid character types but, as per your account option settings, was not required in the approval process."
Can anyone tell me why the CSC failure setting is not working and how to get it working?
EDIT: Ok, on the phone with paypal support again and they say that I will have to use the manager.paypal.com login credentials as part of each transaction in the API calls. Does anyone know where I would do that? I only see fields for API credentials.
I'm getting this intermittent message on checkout in BigCommerce.
Your financial institution has indicated that it could not successfully authenticate this transaction. To protect against unauthorized use, this card cannot be used to complete your purchase. You may complete the purchase by selecting another form of payment or use a different card.
My API is correct with Paypal Payments Pro, Check out works and then doesn't work. Tried a few cards, sometimes the card worked, and sometimes it didn't. Here is the error message.
Your financial institution has indicated that it could not successfully authenticate this transaction. To protect against unauthorized use, this card cannot be used to complete your purchase. You may complete the purchase by selecting another form of payment or use a different card.
I have the same account setup on another BigCommerce site and never had a problem.
If you have another BigCommerce site and are using the PayPal account, make sure that your starting invoice numbers are far enough apart, otherwise you will be sending duplicate invoice numbers to PayPal and end they'll return an error. I was getting the same error, and I just set had to set one of my store's starting invoice number (under store settings/misc) to a really high number. This fixed the problem. Thanks BigCommerce tech support guy!
(You should be able to see what error you are getting by going through your store logs)