DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application is being examined under the pre-AIA first to invent provisions.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of pre-AIA 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a) the invention was known or used by others in this country, or patented or described in a printed publication in this or a foreign country, before the invention thereof by the applicant for a patent.
Claim(s) 1-3, 5, 7-10, and 15-17 is/are rejected under pre-AIA 35 U.S.C. 102(b) as being anticipated by Cardina et al. (US 2012/0116902, cited by the applicant).
Re claim 1: Cardina teaches a payment system (fig. 1) comprising a payment card device (120) operable for use in a payment card reader facility (130), wherein at least a portion of payment information of the payment card device is not visible on the payment card device, and a computing device such as a pseudo account server (150), a payment service provider device (160), or an issuer device (190) comprising a processor and a memory (i.e., the devices such as the pseudo account server (150), the payment service provider device (160), or the issuer device (190) equipped with hardware and software, paragraph 0043), and at least one interface (310) for receiving a request (paragraphs 0034, 0044), wherein the computing device is operable to receive, store, and transmit at least a portion of payment information via at least one interface of the computing device (310-340), wherein the processor is operable to generate (320), based on an information of the payment card device, at least a portion of a limited-use payment information for use by an authenticated card user in a user-authorized payment transaction, wherein the computing device is operable to make a payment transaction by conveying the limited-use payment information to a payment facility via an interface of the computing device (370), and wherein further the payment facility, directs the limited-use payment information to a card processing facility, and is further operable to receive from the card processing facility a verification if the limited-use payment information is valid within one or more limitations of use (390), and wherein the computing device is further operable to receive, an indication that the payment transaction is valid or invalid, when the card processing facility verifies the limited-use payment information is validly used within or outside-of, one or more limitations corresponding to the limited-use payment information (paragraph 0051)(see figs. 1-6; paragraphs 0043-0051).
Re claim 2: Wherein a user interface of the computing device is operable to approve/decline payments from the payment card device in payment transactions using the payment card device, and is operable to confirm/deny an authentic payment transaction by the payment card device (380, 390).
Re claim 3: Wherein a user interface of the computing device is operable to present a portion of the payment information not visible on the payment card device, and wherein such payment information portion is required for making payments when the payment card device is not-present-at, or not-operable-in, the card reader facility, and wherein transactions where the payment card device is not present or not operable at the card reader facility, include at least one from group consisting of: an online transaction, a transaction completed by phone, and a manual card-information-entry transaction (paragraph 0038).
Re claim 5: Wherein the payment card device (120) is without the payment information necessary for completing an online transaction, and without the payment information necessary for completing a transaction when the payment card device is not operably present in payment card reader facilities (e.g., no request is made for transaction), and wherein the information (e.g., temporary account number/data) presented on communication interfaces of the payment card device is limited to a use of payment card device when present and operated in a merchant card reader facility use (paragraph 350).
Re claim 7: Wherein the computing device is further operable to transmit the payment information via a wireless interface disposed of the computing device for completing an online transaction (paragraph 0049).
Re claim 8: Wherein the computing device is further operable to transmit the limited-use payment information via a near-field communication (NFC) interface disposed of the computing device in an in-store NFC reader facility transaction (paragraph 0039).
Re claim 9: Wherein the computing device such as the pseudo account server (150, 450) is further operable to transmit (370) the limited-use payment information wirelessly to another device such as the issuer device (190) via a wireless interface of the computing device, in a device-todevice transaction (paragraphs 0050, 0052).
Re claim 10: Wherein the computing device is further operable to transmit the limited-use payment information visually (via a user interface of the computing device (e.g., the temporary account number is visual information transmitted via interface of the computing device).
Re claim 15: Cardina teaches a payment system (fig. 1) comprising a payment card device (120) free of any payment numbers visible thereon and operable for use with a payment card reader facility (130), and a computing device such as a pseudo account server (150), a payment service provider device (160), or an issuer device (190) comprising a processor and a memory (i.e., the devices such as the pseudo account server (150), the payment service provider device (160), or the issuer device (190) equipped with hardware and software, paragraph 0043), and at least one interface (310) for receiving a request (paragraphs 0034, 0044), wherein the computing device is operable to receive, store, and transmit at least a portion of payment information via at least one interface of the computing device (310-340), wherein the processor is operable to generate (320), based on an information of the payment card device, at least a portion of a limited-use payment information for use by an authenticated card user in a user-authorized payment transaction such as PIN, and wherein the computing device is operable to make a payment transaction conveying the limited-use payment information to a card processing facility via an interface of the computing device (330), wherein information of the payment transaction information comprises the limited-use payment information, and wherein the computing device is operable to receive, from the card processing facility, an indication validating the limited-use payment information as authentic when received from a recognized payment card device such as an identifying information of the device (paragraphs 0048), 0058), and wherein the computing device is operable to receive, from a card processing facility, an indication permitting a user authorized transaction to complete when the limited-use payment information is validated as received from the recognized payment card device, the recognized computing device, or a user-authorized transaction (paragraph 0058)(see figs. 1-6; paragraphs 0043-0059).
Re claim 16: Wherein the computing device is further operable to present at least one security challenge from the group consisting of a user passcode entry such as PIN, and wherein the computing device rejects or accepts the transaction based on the at least one challenge 390).
Re claim 17: Cardina teaches a payment system (fig. 1) comprising a payment card device (120) operable for a use with a payment card reader facility (130), and a computing device such as a pseudo account server (150), a payment service provider device (160), or an issuer device (190), comprising a processor and a memory (i.e., the devices such as the pseudo account server (150), the payment service provider device (160), or the issuer device (190) equipped with hardware and software, paragraph 0043), and at least one interface (310) for receiving a request (paragraphs 0034, 0044), wherein the computing device is operable to receive, store, and transmit at least a portion of a payment information via at least one interface of the computing device (310-340), wherein the processor is operable to generate at least a portion of a limiteduse payment information for use by an authenticated card user (320), wherein the limited-use payment information can be limited by at least one limitation selected from a set of limitations consisting of a one-time use, a number of uses, an amount, a specific time duration, a specific computing device, a specific payer, and a specific payment-card user (paragraph 0045) (see figs. 1-6; paragraphs 0043-0051).
Allowable Subject Matter
Claims 4, 6, and 11-14 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
The following is a statement of reasons for the indication of allowable subject matter:
None of prior art teaches the payment system comprising the user interface, wherein a user interface is operable to lock or unlock an ability to make the payment transaction, and wherein a card issuer authority is further operable for denying a first payment transaction of the payment transactions based on at least one status from the group consisting of: a locked status of the payment card device, and a locked status of the computing device, and a locked status of a user-permitted transacting, and
wherein the card issuer authority is further operable to permit as authorized, a second payment transaction based on an unlocked status of the computing device as set forth in the claims.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SEUNG H LEE whose telephone number is (571)272-2401. The examiner can normally be reached 7-4:00PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Steven Paik can be reached at 571-272-2404. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/SEUNG H LEE/Primary Examiner, Art Unit 2876
Prosecution Insights