Appeal No. 2002-0885
Application 09/149,917
which is generated by the SVC and the terminal, a merchant
supplied signature key. While there is disclosure of an SVC
identification number (col. 11, lines 43-44), which could be
considered a retail customer identification number, this number
is not encrypted in the mutual validation procedure (col. 12,
lines 31-36). If there is other relevant disclosure in Davis,
the examiner has not pointed it out. Accordingly, the examiner
has not shown limitation (1) in Davis.
As to limitation (2), generating a verifiable electronic
retail transaction receipt comprising said merchant signature and
detailed transaction data, the examiner refers to establishing a
secure audit trail including the signature associated with each
transaction described at column 9, lines 59-67 (EA4).
The secure audit trail described at column 9 stores a
transaction signature. However, the examiner does not explain,
and we do not see how the secure audit trail described at
column 9, lines 59-67, teaches generating a verifiable electronic
retail transaction receipt comprising the merchant signature and
detailed transaction data, where the merchant signature is
defined in limitation (1). We have looked through Davis on our
own and find the audit trail or transaction log described in more
detail at column 14, line 56, to column 16, line 2, with respect
to Fig. 4. A derived signature key is obtained by encrypting the
identification number of the SVC with a key associated with the
- 5 -
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next
Last modified: November 3, 2007