I get the following error.
--- I do not have paypal pro.
--- I'm using PayPal Payment Pro ( VirtueMart )
--- I'm using a LiveAccount.
Is it required to have PayPal Payment Pro?
L_ERRORCODE0 - 10501
L_SHORTMESSAGE0 - Invalid Configuration
L_LONGMESSAGE0 - This transaction cannot be processed due to an invalid merchant configuration.
Thanks.
Based on that error it's expecting you to have Website Payments Pro 3.0 enabled on your PayPal account.
Related
I'm working on an integration between a shopping cart and PayPal. I'm using the SOAP API and Express Checkout. What I want to test is the behavior of the system when the shipping address of the buyer is unconfirmed. I've created a sandbox account which is not "Bank Verified Account" and its wallet is empty.
Anyway the address status is always "Confirmed" as seen in the snippet below:
<GetExpressCheckoutDetailsResponseDetails xmlns="urn:ebay:apis:eBLBaseComponents" xsi:type="ebl:GetExpressCheckoutDetailsResponseDetailsType">
...
<Token xsi:type="ebl:ExpressCheckoutTokenType">EC-17S48212F9774382J</Token>
...
<PayerInfo xsi:type="ebl:PayerInfoType">
...
<PayerStatus xsi:type="ebl:PayPalUserStatusCodeType">unverified</PayerStatus>
<PayerCountry xsi:type="ebl:CountryCodeType">DE</PayerCountry>
<Address xsi:type="ebl:AddressType">
<Name xsi:type="xs:string">...</Name>
<Street1 xsi:type="xs:string">...</Street1>
<Street2 xsi:type="xs:string"/>
<CityName xsi:type="xs:string">...</CityName>
<StateOrProvince xsi:type="xs:string"/>
<Country xsi:type="ebl:CountryCodeType">DE</Country>
<CountryName>Germany</CountryName>
<PostalCode xsi:type="xs:string">11111</PostalCode>
<AddressOwner xsi:type="ebl:AddressOwnerCodeType">PayPal</AddressOwner>
<AddressStatus xsi:type="ebl:AddressStatusCodeType">Confirmed</AddressStatus>
</Address>
</PayerInfo>
</GetExpressCheckoutDetailsResponseDetails>
How can I emulate unconfirmed addresses?
Unfortunately, for sandbox environment address will be confirmed. Only way is to test issuing live.
I'm trying to integrate the Login with PayPal module in my shop, but when I login it shows a blank page in:
http://www.myshop.com/index.php?route=m... 5YhZRcFVcj
In the error log I can see:
( [error] => invalid_authz_code [error_description] => Authorization
Code is invalid )
2015-10-09 9:44:51 - Log In with PayPal debug
(ModelModulePPLogin:getTokens) - cURL Response: stdClass Object (
[error] => invalid_authz_code [error_description] => Authorization
Code is invalid )
How do I address this?
"Login with PayPal" only returns the user_id unless updating the endpoint of the TokenService: $endpoint = 'https://api.paypal.com/v1/identity/openidconnect/tokenservice';
that module currently has a switch for sandbox-mode, but only input fields for one of both credentials (which might be the source of confusion). see Issue #3695.
I'm using PayPal Digital Goods checkout with the classic API (signature/password API credentials). Live transactions are working but sometime between Dec 27 and Jan 7 sandbox transactions stopped working, claiming "session expired" when trying to confirm the transaction. Following is the response to the Digital Goods checkout and the confirm invocations:
[08-Jan-2014 20:03:06 UTC] PayPal Checkout-Calling SetExpressCheckoutDG
[08-Jan-2014 20:03:07 UTC] PayPal Checkout Result. Results = TOKEN:EC-38C423050J138841W TIMESTAMP:2014-01-08T20:03:07Z CORRELATIONID:381d15bad3eaa ACK:Success VERSION:84 BUILD:9187650
[08-Jan-2014 20:03:07 UTC] RedirectToPayPalDG Header=https://www.sandbox.paypal.com/incontext?token=EC-38C423050J138841W
[08-Jan-2014 20:03:14 UTC] PAYPAL GetExpressCheckoutDetails TOKEN=EC-38C423050J138841W
[08-Jan-2014 20:03:15 UTC] PayPal Confirm--Failed. Results = TIMESTAMP:2014-01-08T20:03:15Z CORRELATIONID:2b45bb61f3787 ACK:Failure VERSION:84 BUILD:9187650 L_ERRORCODE0:10411 L_SHORTMESSAGE0:This Express Checkout session has expired. L_LONGMESSAGE0:This Express Checkout session has expired. Token value is no longer valid. L_SEVERITYCODE0:Error
Note the timestamps: the error return is 9 seconds after the checkout timestamp (when the user process started).
It looks like the classic API to the sandbox is broken. Anyone else seeing this, and if so is there a solution?
Its a different correlation or even a different session.
Problem solved--my error in managing credentials.
We had paypal setup all working for PayPal API and Payflow pro then we had to change from a Australian account to a UK account. But now the Pro side gives this error response. We've got limited access to the paypal account it self.
Partner: xxxxxxx Merchant Login(Vender): xxxxxxxxxxxx User: xxxxxxxxx
Password: xxxxxxxxxxxxxxxxxxx Host Address :payflowpro.paypal.com Host
port=443
This is the request we are sending to PayPal:
PARTNER=xxxxxxxx&VENDOR=xxxxxxx&USER=xxxxxx&PWD=xxxx&TENDER=C&TRXTYPE=R&ACTION=A&ACCT=xxxxXXXXXXXXxxxx&EXPDATE=xxxx&COMMENT1[16]=Regstration
- FS&START=02062014&TERM=0&CVV2=xxx&AMT=35.00&PAYPERIOD=MONT&MAXFAILPAYMENTS=0&RETRYNUMDAYS=2&PROFILENAME[14]=xxxxxxxxxxxxx&COMPANYNAME[2]=FS&NAME[12]=xxxx
xxxxxx&FIRSTNAME[6]=xxxxxx&LASTNAME[5]=xxxxx&PHONENUM=xx12345678&EMAIL[24]=xxxxxxxxxxxxxxxxxxxxxxxx&STREET[15]=xxxxxxxx
Street&CITY[7]=xxxxxxx&STATE[3]=NSW&ZIP=xxxx&COUNTRY=AU&OPTIONALTRX=S&OPTIONALTRXAMT=35.00
We are getting the following error response from PayPal:
RESULT=1000&RESPMSG=Generic processor error: 11581-Profile description
is invalid
Google has not really helped. I am hoping a few smart SO guys can assist.
Thank you,
Warren.
I'm seeing the following error message when attempting to perform a simple payment using the PayPal Adaptive Payments API and the Explicit Approval Payment Flow in the sandbox environment:
Proxy Error
The proxy server could not handle the request GET /webapps/adaptivepayment/flow/expresscheckoutincontextremembermeflow.
Reason: Error during SSL Handshake with remote server
As per this related post, this issue has supposedly been resolved, but I'm still unable to perform a simple payment in the sandbox environment.
The API call to generate a payKey is returning successfully:
{
'responseEnvelope': {
'ack': 'Success',
'timestamp': '2013-04-01T10:00:33.572-07:00',
'build': '5563463',
'correlationId': '9ddb6d34b8b31'
},
'paymentExecStatus': 'CREATED',
'payKey': 'AP-30241506EH984280M'
}
and the following series of redirects are occurring:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/pay?expType=light&paykey=AP-30241506EH984280M
redirects to:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/payinit?iframecookie=1364835660832&paykey=AP-30241506EH984280M&expType=light
which redirects to:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/corepay
which redirects to:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/expresscheckoutincontextremembermeflow
which gives the 500 proxy error after approximately 210 seconds.
Additionally, if I attempt the workaround of logging into developer.paypal.com in another tab first, I get a 404 error on the initial request:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/pay?expType=light&paykey=AP-45P14958V28124917
I've searched and searched and poked and prodded this issue to death...anyone else seeing this problem, and does anyone have a working resolution?
We are rolling a patch later tonight which we expect to fix this issue permanently.