Closed Bug 979152 Opened 6 years ago Closed 6 years ago

[B2G][NFC][User Story]: Tap-to-pay (with HCI event triggering) for payments at Point of Sale

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(feature-b2g:2.1, tracking-b2g:backlog)

VERIFIED FIXED
2.1 S3 (29aug)
feature-b2g 2.1
tracking-b2g backlog

People

(Reporter: skamat, Assigned: vchang)

References

Details

(Keywords: feature, Whiteboard: [ucid:NFC12, FT:RIL][U1][2.1-feature-qa+])

User Story

As a user, I would like to use Tap-to-pay functionality (with HCI event triggering) to make payments at various points of sale. There will be a visual confirmation to the user that the transaction succeeded or failed.

Acceptance Criteria

AC1: If the settings has NFC turned on with appropriate secure elements (payments data), the user accesses this functionality simply by tapping at an enabled point of sale.
AC2: There will be a visual confirmation to the user that the transaction succeeded or failed. This should be recorded in the transaction history of the app.
AC3: The reader (payment terminal) equipment also needs to record a successful transaction.
As a user, I would like to use Tap-to-pay functionality (with HCI event triggering) to make payments at various points of sale. There will be a visual confirmation to the user that the transaction succeeded or failed.
Blocks: 979154
Acceptance Criteria

AC1: If the settings has NFC turned on with appropriate secure elements (payments data), the user accesses this functionality simply by tapping at an enabled point of sale.
AC2: There will be a visual confirmation to the user that the transaction succeeded or failed. This should be recorded in the transaction history of the app.
AC3: The reader (payment terminal) equipment also needs to record a successful transaction.
Add two high-level OS/NFC feature requirements that are closely related to supporting this user story.
1. The mobile device SHALL support NFC Card Emulation mode as per ISO14443 Type A/B;
2. The mobile device SHALL support web application triggering based on HCI event - EVT_TRANSACTION;
Whiteboard: [ucid:NFC12, FT:RIL]
User Story: (updated)
Depends on: 979767
Depends on: 979868
Depends on: 979891
blocking-b2g: --- → backlog
No longer depends on: 979868
Blocks: 979868
No longer blocks: 979868
Based on partner discussions, targeted for 2.1. (depends on 979868 & 979767, of which 979868 has landed)
feature-b2g: --- → 2.1
Whiteboard: [ucid:NFC12, FT:RIL] → [ucid:NFC12, FT:RIL][U1]
There are normally two working modes for wallet-based payment.

1. Fast Pay Mode
User opens a Wallet app. Then selects a payment card as fastpay card, which should be used for all further payment transactions. This step is done only once. Later, at any time - even when Wallet is not running, or even when the screen is off, user can tap the phone against PoS and make payment.

2. One-time Payment Mode
User opens a Wallet app and selects a card which he/she wants to use for the payment. Next taps the phone against the PoS. Payment is being performed and, once done, Wallet de-selects the card automatically.
QA Whiteboard: [COM=NFC]
We are developing 2.1. EM should take this bug.
Assignee: nobody → vchang
QA Whiteboard: [COM=NFC] → [COM=NFC][2.1-feature-qa+]
Flags: in-moztrap?(ashiue)
QA Contact: ashiue
QA Whiteboard: [COM=NFC][2.1-feature-qa+] → [COM=NFC]
Whiteboard: [ucid:NFC12, FT:RIL][U1] → [ucid:NFC12, FT:RIL][U1][2.1-feature-qa+]
Target Milestone: --- → 2.1 S3 (29aug)
No longer depends on: 1046516
Note that wallet app is not in 2.1 scope, user can't select payment card mentioned in comment 4.
So Fast pay mode should be default. When user taps the phone against PoS and make payment, all the payment transactions are done by applet in the SIM card. But the payment result will be notified by HCI event EVT_TRANSACTION. Bug 979767 is focused on gecko framework to pass the HCI event from nfcd to application. The demo app is implementing in bug 1029947 which will display the payment result contained in HCI event.
I think all the depended bugs have been fixed. Change the status to resolved fixed so QA can help to verify the user story.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Verified landed
Gaia      2be78d83a760fa3b9638fe51c266b442d14597f1
Gecko     https://hg.mozilla.org/mozilla-central/rev/1db35d2c9a2f
BuildID   20140831160203
Version   34.0a1
Status: RESOLVED → VERIFIED
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.