Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Business-PayPal-API CPAN distribution.

Report information
The Basics
Id: 94376
Status: resolved
Priority: 0/
Queue: Business-PayPal-API

People
Owner: Nobody in particular
Requestors: racke [...] linuxia.de
melmothx [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: PaymentDetails on SetExpressCheckout
Date: Wed, 02 Apr 2014 10:19:31 +0200
To: bug-Business-PayPal-API [...] rt.cpan.org
From: Marco Pessotto <melmothx [...] gmail.com>
Hello and thanks for Business::PayPal::API I'm using the workflow described in the synopis of https://metacpan.org/pod/Business::PayPal::API::ExpressCheckout and it looks like I can't set the PaymentDetailsItem when doing the SetExpressCheckout. Unless I do the redirection to paypal with the parameter useraction=commit, the buyer can't even see the total she's going to pay. I've looked into the source, and it looks like the PaymentDetailsItem is supported only on DoExpressCheckoutPayment, i.e., when the buyer has already approved the transaction, so kind of too late for the buyer to review. Am I doing something wrong or the support for that is actually missing? Best wishes -- Marco
On Wed Apr 02 04:19:47 2014, melmothx@gmail.com wrote: Show quoted text
> > Hello and thanks for Business::PayPal::API > > I'm using the workflow described in the synopis of > https://metacpan.org/pod/Business::PayPal::API::ExpressCheckout and it > looks like I can't set the PaymentDetailsItem when doing the > SetExpressCheckout. > > Unless I do the redirection to paypal with the parameter > useraction=commit, the buyer can't even see the total she's going to > pay. > > I've looked into the source, and it looks like the PaymentDetailsItem is > supported only on DoExpressCheckoutPayment, i.e., when the buyer has > already approved the transaction, so kind of too late for the buyer to > review.
Hi Marco, As described in the workflow, what do you see when you dump %details: my %details = $pp->GetExpressCheckoutDetails($resp{Token}); use Data::Printer; p %details; You should have access to this *before* DoExpressCheckoutPayment, since all that is required is the token. Might be helpful if you could show some code to demonstrate the problem. Best, Olaf
Subject: Re: [rt.cpan.org #94376] PaymentDetails on SetExpressCheckout
Date: Wed, 02 Apr 2014 22:07:47 +0200
To: bug-Business-PayPal-API [...] rt.cpan.org
From: Marco Pessotto <melmothx [...] gmail.com>
"Olaf Alders via RT" <bug-Business-PayPal-API@rt.cpan.org> writes: Show quoted text
> As described in the workflow, what do you see when you dump %details: > > my %details = $pp->GetExpressCheckoutDetails($resp{Token}); > use Data::Printer; > p %details; > > You should have access to this *before* DoExpressCheckoutPayment, > since all that is required is the token. Might be helpful if you could > show some code to demonstrate the problem.
Hello Olaf and thanks for the quick answer. From the perl code point of view, everything looks fine. The problem is from the buyer's point of view. The problem (and the workaround) I found is exactly the same described here: http://stackoverflow.com/questions/8206175/missing-amount-and-order-summary-in-paypal-express-checkout The perl code sees the amount, but the buyer doesn't, unless the the parameter useraction=commit is passed to Paypal on redirection. It looks like PayPal doesn't show the amount if there is no detailed list of the items (or if there is no useraction=commit), so I was wondering if it was possible to add the items when creating the token with SetExpressCheckout. I'll post some code if needed, but it boils down to the synopsis of Business::PayPal::API::ExpressCheckout, and doesn't expose the problem (which is from the buyer point of view). Best wishes -- Marco
On Wed Apr 02 16:08:02 2014, melmothx@gmail.com wrote: Show quoted text
> "Olaf Alders via RT" <bug-Business-PayPal-API@rt.cpan.org> writes: >
> > As described in the workflow, what do you see when you dump %details: > > > > my %details = $pp->GetExpressCheckoutDetails($resp{Token}); > > use Data::Printer; > > p %details; > > > > You should have access to this *before* DoExpressCheckoutPayment, > > since all that is required is the token. Might be helpful if you > > could > > show some code to demonstrate the problem.
> > Hello Olaf and thanks for the quick answer. > > From the perl code point of view, everything looks fine. The problem > is > from the buyer's point of view. The problem (and the workaround) I > found > is exactly the same described here: > > http://stackoverflow.com/questions/8206175/missing-amount-and-order- > summary-in-paypal-express-checkout > > The perl code sees the amount, but the buyer doesn't, unless the the > parameter useraction=commit is passed to Paypal on redirection. It > looks > like PayPal doesn't show the amount if there is no detailed list of > the > items (or if there is no useraction=commit), so I was wondering if it > was possible to add the items when creating the token with > SetExpressCheckout. > > I'll post some code if needed, but it boils down to the synopsis of > Business::PayPal::API::ExpressCheckout, and doesn't expose the problem > (which is from the buyer point of view). > > Best wishes
Hi Marco, OK. I understand what you're saying now. The workflow I've always used has me presenting the details to the buyer on my own site, having them do the PayPal authentication and then letting them confirm the purchase on my end before I submit the payment. So, I've got control of the payment details etc in that case. To be honest, I got maint on this module for a very minor fix, so I haven't delved that deeply into the code. I'd be open to a pull request to add the functionality you've described though. I say this without having looked at the internals to see what would be involved. ;) Best, Olaf
Subject: Re: [rt.cpan.org #94376] PaymentDetails on SetExpressCheckout
Date: Wed, 02 Apr 2014 22:39:18 +0200
To: bug-Business-PayPal-API [...] rt.cpan.org
From: Marco Pessotto <melmothx [...] gmail.com>
"Olaf Alders via RT" <bug-Business-PayPal-API@rt.cpan.org> writes: Show quoted text
> Hi Marco, > > OK. I understand what you're saying now. The workflow I've always used > has me presenting the details to the buyer on my own site, having them > do the PayPal authentication and then letting them confirm the > purchase on my end before I submit the payment. So, I've got control > of the payment details etc in that case. > > To be honest, I got maint on this module for a very minor fix, so I > haven't delved that deeply into the code. I'd be open to a pull > request to add the functionality you've described though. I say this > without having looked at the internals to see what would be involved. > ;)
Ok, fair enough, at least now I know I'm not doing it totally wrong :-) I'll let you know if I'll patch the module (still unclear if really needed). Best wishes and thanks again for your time -- Marco
On Wed Apr 02 16:39:35 2014, melmothx@gmail.com wrote: Show quoted text
> "Olaf Alders via RT" <bug-Business-PayPal-API@rt.cpan.org> writes: >
> > Hi Marco, > > > > OK. I understand what you're saying now. The workflow I've always used > > has me presenting the details to the buyer on my own site, having them > > do the PayPal authentication and then letting them confirm the > > purchase on my end before I submit the payment. So, I've got control > > of the payment details etc in that case. > > > > To be honest, I got maint on this module for a very minor fix, so I > > haven't delved that deeply into the code. I'd be open to a pull > > request to add the functionality you've described though. I say this > > without having looked at the internals to see what would be involved. > > ;)
> > Ok, fair enough, at least now I know I'm not doing it totally wrong :-) > > I'll let you know if I'll patch the module (still unclear if really > needed). > > Best wishes and thanks again for your time
That sounds good. I'm going to close this ticket then. If you'd like to send a patch, we can track that on Github. :) Best, Olaf