Correctly handle exception when a new payment method doesn't have a plugin

Created on 8 January 2024, about 1 year ago

Problem/Motivation

When a new payment method is enabled through Stripe Dashboard, (if it is a single-use, it would need Add the option to not setup payment methods for future usage Fixed ) a customer can see the new payment method on the Drupal side, and they can proceed to complete the transaction. The transaction can complete on the Stripe side, however, it would throw an exception on the Drupal side:

Payment failed at the payment server. Please review your information and try again.

This exception is misleading, as the payment didn't fail, it was the Drupal side that doesn't know how to handle the response.

Steps to reproduce

Proposed resolution

Maybe a better exception? Not sure

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Closed: outdated

Version

1.0

Component

Payment Element

Created by

🇨🇳China skyredwang Shanghai

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

Comments & Activities

Production build 0.71.5 2024