Automatically closed - issue fixed for 2 weeks with no activity.
1. An authenticated user adds a payment method for the first.
2. If the payment method details are correct, a Shopper is created on BlueSnap and is correctly associated with the User in both Drupal and BlueSnap.
3. If the payment method details are considered by BlueSnap to be incorrect, BlueSnap creates the Shopper and associates it with the Drupal User. It then returns a response to Drupal that there has been an error.
4. Drupal receives the response seeing that there has been an error, and aborts further processing before storing the remote ID in the `commerce_remote_id` user field. That results in the Drupal User to not become associated with the already created BlueSnap Shopper.
5. Next time the user tries to add a payment method, Drupal is not aware of an association with a BlueSnap Shopper. It therefore requests a new Shopper to be created. At that point, BlueSnap returns the reported error that there is already a Shopper for the User.
See child issues.
See child issues.
Fixed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed - issue fixed for 2 weeks with no activity.