Open Bug 1494723 Opened 3 years ago Updated 3 years ago

Show field-specific merchant errors on the basic-card form

Categories

(Firefox :: WebPayments UI, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: MattN, Unassigned)

References

()

Details

(Keywords: dev-doc-needed, Whiteboard: [webpayments-reserve])

User Story

* Show paymentMethod errors on the basic-card form

Attachments

(1 file)

* Expose merchant errors on the payment summary page
* Show paymentMethod errors on the basic-card form
User Story: (updated)
Summary: Show field-specific merchant errors on the basic-card form and on the summary page (below pickers) → Show field-specific merchant errors on the basic-card form and below the payment-method-picker
Flags: qe-verify?
Whiteboard: [webpayments-reserve] → [webpayments]
Flags: qe-verify? → qe-verify+
QA Contact: hani.yacoub
Since showing errors below the payment-method-picker is covered by bug 1481481 and follow-ups I will remove that from this bug.
User Story: (updated)
Summary: Show field-specific merchant errors on the basic-card form and below the payment-method-picker → Show field-specific merchant errors on the basic-card form
Assignee: nobody → MattN+bmo
Status: NEW → ASSIGNED
Priority: P2 → P1
I'm doubting the usefulness of this ability as I don't think merchants would tell you what specifically is wrong with a declined card, other than the expiration month being in the past.

We also have implementation issues with the cardNumber portion because we disable that field while editing so setCustomValidity doesn't work.

I'll attach my WIP.
Assignee: MattN+bmo → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3
Whiteboard: [webpayments] → [webpayments-reserve]
Attachment #9031612 - Attachment is obsolete: true
Attachment #9031612 - Attachment is obsolete: false
You need to log in before you can comment on or make changes to this bug.