See parent issue. Fix the issue for existing users that are blocked from adding payment methods.
See parent issue.
Users that already have a Shopper with the association not registered in Drupal will still face the error when they try adding new payment methods. Assuming that the merchant shopper ID sent to BlueSnap is unique (we currently use the UUID → ), we can write a Drush command that does the following:
Deleting the Shoppers or adding the missing association will fix the issue. When broken users add a new payment method, they will either have the association and add the payment method to the existing Shopper, or the Shopper will have been deleted and a new Shopper will be created.
Since this can get a bit complicated and the considerations, the risks and the appropriate solution may be different for different sites, we should provide the option to choose. It should be reviewed by a developer therefore a Drush command instead of a UI-based solution.
Closed: won't fix
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This seems to be unlikely to be requested. For most purposes the solution that will associate the Drupal users with the correct Vaulted Shoppers implemented on 🐛 Register remote ID when payment method details are wrong Fixed is enough. Unlikely somebody will complain for a few empty vaulted shoppers and want to clean up. Compared to the high development effort and risks of implementing this, won't do.