During checkout, if you enter a single name in Fullname (e.g. Sting) during checkout, only the FIRSTNAME parameter is populated in the request to Paypal and the transaction is rejected with an error from Paypal (L_ERRORCODE => 10513, L_SHORTMESSAGE0 => Invalid Data, L_LONGMESSAGE => This transaction cannot be processed. Please enter a last name.). This appears in Drupal Commerce as a form error on the checkout review page with text "We encountered an error processing your payment. Please verify your credit card details or try a different card."

1. Paypal WPP module needs to more gracefully handle a single name being provided.
2. A the actual error from Paypal should be made visible to the customer so that useful action can be taken.

Comments

rszrama’s picture

rszrama commented

What do you propose we do? Split the fullname into two parameters? Or should it be enough to send an empty string to PayPal for the last name?

rszrama’s picture

rszrama commented
Version: 7.x-1.0-rc1 » 7.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

I'm gonna need more information about your configuration, because I cannot reproduce your reported issue. I used the full name line and just put in my first name. This generated the following request:

Array
(
    [METHOD] => DoDirectPayment
    [PAYMENTACTION] => Sale
    [NOTIFYURL] => ----
    [CREDITCARDTYPE] => Visa
    [ACCT] => XXXXXXXXXXXX1540
    [EXPDATE] => 092017
    [AMT] => 40
    [CURRENCYCODE] => USD
    [CVV2] => XXX
    [INVNUM] => 4-1355691502
    [CUSTOM] => Order 4
    [DESC] => 2x PROD-02
    [EMAIL] => ----
    [IPADDRESS] => 127.0.0.1
    [FIRSTNAME] => Ryan
    [LASTNAME] => 
    [STREET] => 500 Wombat Way
    [STREET2] => 
    [CITY] => Louisville
    [STATE] => KY
    [COUNTRYCODE] => US
    [ZIP] => 40203
    [USER] => ----
    [PWD] => XXXXXXXXXX
    [SIGNATURE] => XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    [VERSION] => 76.0
)

Which resulted in the following successful response:

Array
(
    [TIMESTAMP] => 2012-12-16T20:58:29Z
    [CORRELATIONID] => 9ccb252bcb00f
    [ACK] => Success
    [VERSION] => 76.0
    [BUILD] => 4137385
    [AMT] => 40.00
    [CURRENCYCODE] => USD
    [AVSCODE] => X
    [CVV2MATCH] => M
    [TRANSACTIONID] => 5TU908391R6900109
)

Perhaps it's something in your fraud settings? Maybe something only affecting a live site?

rszrama’s picture

rszrama commented
Category: bug » support
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I just tested this again, and I had no issue submitting a payment with only a single name in the full name line. If you can provide instructions on how to reproduce the failed payment, please feel free to reopen this issue. Otherwise I'll assume it's owing to some sort of PayPal account / fraud protection setting.

heyehren’s picture

heyehren commented

This error still occurs. I tried making a payment with a single name in the name field and the transaction failed.

This is the error log output:

PayPal server response:
Array
(
    [TIMESTAMP] => 2013-11-23T01:49:59Z
    [CORRELATIONID] => b02c0d271951b
    [ACK] => Failure
    [VERSION] => 76.0
    [BUILD] => 8311702
    [L_ERRORCODE0] => 10513
    [L_SHORTMESSAGE0] => Invalid Data
    [L_LONGMESSAGE0] => This transaction cannot be processed. Please enter a last name.
    [L_SEVERITYCODE0] => Error
    [AMT] => 7.95
    [CURRENCYCODE] => AUD
)
heyehren’s picture

heyehren commented
Issue summary: View changes
Status: Closed (cannot reproduce) » Active
rszrama’s picture

rszrama commented

You haven't provided any new information; what do you expect me to do for you? Did you try looking into your account or fraud settings to see if they are to blame as I suggested above?

akshayadhav’s picture

akshayadhav
he/him
Location Pune, India 🇮🇳
commented

Facing same issue on single word entry in "Full Name" field of Shipping information.

tomtech’s picture

tomtech commented
Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.