Contrib.social

Register remote ID when payment method details are wrong

Open on Drupal.org →
Created on 7 January 2022, over 2 years ago
Updated 24 April 2024, 2 months ago

Problem/Motivation

See parent issue. Prevent the issue from happening moving forward.

Steps to reproduce

See parent issue.

Proposed resolution

When getting an error for invalid payment method details, we should be making an additional API call(s) checking whether a Shopper was actually created for the user. If so, register the association between the Drupal User and the BlueSnap Shopper in the commerce_remote_id field.

Next time the user tries to add a credit card, the system will use the existing Shopper.

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇵🇪Peru krystalcode

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024