Closed Bug 886931 Opened 13 years ago Closed 13 years ago

Bank account details in form

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 900253

People

(Reporter: andy+bugzilla, Unassigned)

Details

(Whiteboard: [ux-wanted][dev-doc-needed])

Bank account number field: "The bank account number field is split up into many fields, with an exclamation point beside it that you can click to convert into a single field. Why isn't it the other way around? I tried to fill in the separate fields first, then realized I didn't have the "suffix" part, and figured out to click the exclamation point (which lost everything I entered so far). In fact, why even have the separate fields at all?" http://cl.ly/image/2F0U3D0r3A3D
Summary: Forcing re-review for apps in STATUS_PUBLIC_WAITING → Bank account details in form
Priority: -- → P4
The segmented form matches the format of a Brazilian bank account number. It was built back when Brazil was the target for payments.
We had similar confusion from a French bank account user. Raising priority. Based on comment #1, it looks like removing that segmenting would be a simple thing to do. We need more docs on this though, possibly in MDN.
Priority: P4 → P2
Whiteboard: [ux-wanted] → [ux-wanted][dev-doc-needed]
The "Bank Account Number" is "The account number of the bank account". The "Bank Account Code" is "The bank / swift / sort / fedwire / CHAPS code of the bank account".
I wonder whether it would be practical to move the country selector further up the form and localise the fields (or at least the text shown) so the developer is shown something familiar. e.g. a developer in the UK is going to be most familiar with sort code; the developer in France had a SWIFT code, etc. IBAN is a replacement for both account number and account code but annoyingly is unsupported in the US/Canada.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.