Does not support anonymous checkout [#2892467]

If checkout is allowed for anonymous users, the AuthorizeNet::doCreatePaymentMethod() fails because the user email address is empty.

  protected function doCreatePaymentMethod(PaymentMethodInterface $payment_method, array $payment_details) {
     ...
      if ($owner->isAuthenticated()) {
        $profile = new Profile([
          // @todo how to allow altering.
          'merchantCustomerId' => $owner->id(),
          'email' => $owner->getEmail(),
        ]);
      }
      else {
        $profile = new Profile([
          // @todo how to allow altering.
          'merchantCustomerId' => $owner->id() . '_' . REQUEST_TIME,
          'email' => $owner->getEmail(),  // <<<<<<<<<<<<<<<< This is empty for anonymous users
        ]);
   ...
  }

AuthNet doesn't allow for an empty email to be passed in. If this property is removed (I just commented it out), AuthNet does accept it. A quick fix is to remove email from the anonymous users. A better long term fix would be to pull their email info in from their billing profile.

Comment	File	Size	Author
#3	anonymous_checkout-2892467-3.patch	684 bytes	mglaman

Comments

Comment #1

5 July 2017 at 21:48

onedotover created an issue. See original summary.

Comment #2

mglaman

English

WI, USA

commented 7 July 2017 at 14:28

Hm, the billing profile does not have an email. And the order's email should be set from the account information pane, where they have to enter an email address. So instead of $owner we need to do $order

Comment #3

mglaman

English

WI, USA

commented 7 July 2017 at 14:35

Status:

Active

» Needs review

Status	File	Size
new	anonymous_checkout-2892467-3.patch	684 bytes

We don't have access to the order in that method. So just omitting.

Comment #4

mglaman

English

WI, USA

commented 7 July 2017 at 14:51

Hm, but from the API page http://developer.authorize.net/api/reference/#customer-profiles-create-c...

Required only when you use a European payment processor.

That patch is a quickfix. The method should probably be revisited. It's borrowed from the first gateway we wrote, Braintree, which supported tokenization much more easily.

Comment #5

mglaman

English

WI, USA

commented 13 July 2017 at 02:13

Title:	Anonymous checkout fails due to missing email	» Does not support anonymous checkout
Priority:	Normal	» Major

The module just cannot support anonymous checkout at the moment. When I applied this fix, I then had errors with the customer profile ID.

    $transactionRequest->addDataType(new Profile([
      'customerProfileId' => $customer_id,
      'paymentProfile' => [
        'paymentProfileId' => $payment_method->getRemoteId(),
      ],
    ]));

It is null here, leading to

The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:customerProfileId' element is invalid - The value '' is invalid according to its datatype 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:numericString' - The 
               Pattern constraint failed.

Since the 2.x architecture is built around tokenized payment methods.. I don't think there is anyway to solve this until we implement Accept.js.