Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paypal email recipt has no description and always Qty 1. #76

Open
st8st8 opened this issue Aug 4, 2014 · 4 comments
Open

Paypal email recipt has no description and always Qty 1. #76

st8st8 opened this issue Aug 4, 2014 · 4 comments
Labels

Comments

@st8st8
Copy link

st8st8 commented Aug 4, 2014

Whatever I buy from my Oscar shop, the email receipt that Paypal sends (both the customer and the merchant) has Qty 1 and no item descriptions, whatever I buy.

I wonder if this is because Paypal recommend that you send the same set of parameters for DoExpressCheckout as they list for SetExpressCheckout? At the moment, Django-oscar-paypal only sends a small set.

https://developer.paypal.com/docs/classic/api/merchant/DoExpressCheckoutPayment_API_Operation_NVP/

The example below is the email that Paypal sends when I make a purchase of two things costing 49p.


Dear NAME,

You sent a payment of £0.98 GBP to Steve Bradshaw's Test Store.

It may take a few moments for this transaction to appear in your account.


Merchant:
Steve Bradshaw's Test Store
[email protected]

Instructions to merchant:
You haven't entered any instructions.


Purchase Details

Description: , No shipping required:
Unit price: 0.98 GBP
Qty: 1
Amount: 0.98 GBP

Subtotal: 0.98 GBP
Postage and packaging£0.00 GBP
Insurance£0.00 GBP

Insurance£0.00 GBP

Total: 0.98 GBP

Payment: 0.98 GBP
Payment sent to: [email protected]


@codeinthehole
Copy link
Contributor

By jove you're right! If I manually force an item name within the do_txn method, then it does appear in the confirmation email. This seems like a bug with PayPal to me as they have all the information they need for the email - it seems silly to send it all again when confirming the payment. That email also has weird formatting glitches around the insurance totals.

We can of course work around this but it breaks several function signatures as the basket isn't passed around. Not sure when I will get round to this though.

@davethecipo
Copy link

Is there any solution to this problem?

@st8st8
Copy link
Author

st8st8 commented May 22, 2018

I'm playing with an experimental fix to this:

st8st8@6894e13

if you want to take a look...

@mortlind
Copy link

I too experience this problem. Does the fix by @st8st8 work? Are there any other workarounds or fixes around?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants