CTNF 19/053,486 CTNF 87609 Detailed Action 07-03-aia AIA 15-10-aia The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. This Office Action is in response to claims filed on 02/14/2025. Claims 1-20 are pending; claims 1 and 12 are independent. Claim Objections Claims 1, 7, 12 and 18 are objected to for the following informalities. Claims 1 and 12 recite “the link”. There are insufficient antecedent basis for “the link” in the claims. Claims 7 and 18 recite “the transferor device”. There are insufficient antecedent basis for “the transferor device” in the claims. Double Patenting 08-33 AIA The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory obviousness-type double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg , 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman , 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi , 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum , 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel , 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Thorington , 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on a nonstatutory double patenting ground provided the conflicting application or patent either is shown to be commonly owned with this application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. Effective January 1, 1994, a registered attorney or agent of record may sign a terminal disclaimer. A terminal disclaimer signed by the assignee must fully comply with 37 CFR 3.73(b). Claims 1-20 of instant application are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over claims of 17/401,520 (12254511). Although the conflicting claims are not identical, they are not patentably distinct from each other because the claims in 17/401,520 (12254511) taught all features in the claims of the instant application as shown below: 19/053,486 17/401,520 (12254511) 1…provide a selectable option to request separation of a transfer into a plurality of parts to a device; 1…send a document to a transferor device, the document including a selectable option to request separation of a transfer into a plurality of parts transfer time periods; receive, via the selectable option, a request to separate the transfer into the plurality of parts and obtaining a total amount and a total time period for the request; receive a request to separate the transfer into the plurality of transfer time periods, the request defining a total amount and a total time period, and wherein the transfer is associated with the document; prepare a plurality of request for transfer links, each of the links associated with a respective transfer time period, wherein each of the respective transfer time periods are less than or equal to the total time period, each of the links associated with a respective transfer part amount, wherein a summation of the respective transfer part amounts is equal to the total amount; prepare a plurality of request for transfer links, each of the links associated with a different transfer time period, wherein each transfer time period is less than or equal to the total time period, each of the links associated with a separate transfer part amount, wherein a summation of the separate transfer part amounts is equal to the total amount; provide the plurality of request for transfer links to the device, each link allowing a transfer to fulfill the respective transfer part amount to be performed. provide the plurality of request for transfer links displayed on an interface to the transferor device, each link allowing a transfer to fulfill the separate transfer part amount to be performed without requiring input of the separate transfer part amount or recipient information; and 2-20 1-20 Examiner's Notes The Examiner cites particular sections in the references as applied to the claims below for the convenience of the applicant(s). Although the specified citations are representative of the teachings in the art and are applied to the specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested that, in preparing responses, the applicant(s) fully consider the references in their entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage as taught by the prior art or disclosed by the Examiner. Claim Rejections - 35 USC § 102 07-06 AIA 15-10-15 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 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. 07-07 AIA 07-07-aia The following is a quotation of 35 U.S.C. 102 that forms the basis for all the rejections under this section made in this Office Action: A person shall be entitled to a patent unless— 07-08-aia AIA (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale or otherwise available to the public before the effective filing date of the claimed invention. 07-15-03-aia AIA Claim s 1-5, 9, 11-16 and 20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by McLACHLAN et al., Pub. No.: US 2021/0096886 A1 (McLACHLAN) . McLACHLAN teaches: Claim 1. A computing system comprising: a communications module; a processor coupled to the communications module; and a memory coupled to the processor storing instructions that, when executed by the computing system, cause the computing system to: provide a selectable option to request separation of a transfer into a plurality of parts to a device; (McLACHLAN, ¶ 238, user is provided an option to select an installment plan for a payment transaction: “purchase confirmation user interface 802, which is displayed to provide a user interface to allow a user to initiate a transfer to acquire ( e.g., purchase) an item …the purchase (e.g., transfer) is broken into two payment transactions ( e.g., transfers)… The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”) receive, via the selectable option, a request to separate the transfer into the plurality of parts and obtaining a total amount and a total time period for the request; (McLACHLAN, ¶ 238, an installment plan separates a payment transaction into several portions to be paid gradually: “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”) prepare a plurality of request for transfer links, each of the links associated with a respective transfer time period, wherein each of the respective transfer time periods are less than or equal to the total time period, each of the links associated with a respective transfer part amount, wherein a summation of the respective transfer part amounts is equal to the total amount; (McLACHLAN, each payment transaction is a transfer link and each scheduled payment transaction is a request for transfer link to occur on a certain date: ¶ 238, “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”, ¶ 246, “The installment balance of $511 corresponds to the balance of the installment plan upon purchase of the item in FIG. 8A. The user interface in FIG. 8D is shown on Dec. 25, 2019. Thus, FIG. 8D shows the card balance and installment balance before the first installment for the installment plan is charged to the transfer account, which is scheduled to occur on December 31, as indicated in FIGS. 8A and 8B”, ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) provide the plurality of request for transfer links to the device, each link allowing a transfer to fulfill the respective transfer part amount to be performed. (McLACHLAN, each scheduled payment allows an installment amount to be paid: ¶ 238, “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”, ¶ 246, “The installment balance of $511 corresponds to the balance of the installment plan upon purchase of the item in FIG. 8A. The user interface in FIG. 8D is shown on Dec. 25, 2019. Thus, FIG. 8D shows the card balance and installment balance before the first installment for the installment plan is charged to the transfer account, which is scheduled to occur on December 31, as indicated in FIGS. 8A and 8B”, ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) Claim 12. A computer-implemented method, comprising: providing a selectable option to request separation of a transfer into a plurality of parts to a device; (McLACHLAN, ¶ 238, user is provided an option to select an installment plan for a payment transaction: “purchase confirmation user interface 802, which is displayed to provide a user interface to allow a user to initiate a transfer to acquire ( e.g., purchase) an item …the purchase (e.g., transfer) is broken into two payment transactions ( e.g., transfers)… The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”) receiving, via the selectable option, a request to separate the transfer into the plurality of parts and obtaining a total amount and a total time period for the request; (McLACHLAN, ¶ 238, an installment plan separates a payment transaction into several portions to be paid gradually: “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”) preparing a plurality of request for transfer links, each of the links associated with a respective transfer time period, wherein each of the respective transfer time periods are less than or equal to the total time period, each of the links associated with a respective transfer part amount, wherein a summation of the respective transfer part amounts is equal to the total amount; (McLACHLAN, each payment transaction is a transfer link and each scheduled payment transaction is a request for transfer link to occur on a certain date: ¶ 238, “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”, ¶ 246, “The installment balance of $511 corresponds to the balance of the installment plan upon purchase of the item in FIG. 8A. The user interface in FIG. 8D is shown on Dec. 25, 2019. Thus, FIG. 8D shows the card balance and installment balance before the first installment for the installment plan is charged to the transfer account, which is scheduled to occur on December 31, as indicated in FIGS. 8A and 8B”, ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) providing the plurality of request for transfer links to the device, each link allowing a transfer to fulfill the respective transfer part amount to be performed. (McLACHLAN, each scheduled payment allows an installment amount to be paid: ¶ 238, “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”, ¶ 246, “The installment balance of $511 corresponds to the balance of the installment plan upon purchase of the item in FIG. 8A. The user interface in FIG. 8D is shown on Dec. 25, 2019. Thus, FIG. 8D shows the card balance and installment balance before the first installment for the installment plan is charged to the transfer account, which is scheduled to occur on December 31, as indicated in FIGS. 8A and 8B”, ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) Claim 2. The computing system of claim 1, wherein each link allows the transfer to fulfill the separate transfer part amount to be performed without requiring input of one or both of the respective transfer part amount or recipient information. (McLACHLAN, each scheduled payment allows an installment amount to be paid without requiring input of one or both of the respective transfer part amount or recipient information: ¶ 246, “FIG. 8D shows the card balance and installment balance before the first installment for the installment plan is charged to the transfer account, which is scheduled to occur on December 31, as indicated in FIGS. 8A and 8B”, ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) Claim 13 is rejected under the same rational as above. Claim 3. The computing system of claim 1, wherein the respective transfer part amounts are equal. (McLACHLAN, ¶ 238, “The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”) Claim 14 is rejected under the same rational as above. Claim 4. The computing system of claim 1, wherein each of the request for transfer links is only valid during the respective transfer time period for that request for transfer link. (McLACHLAN, each scheduled payment happens in certain time: ¶ 246, “FIG. 8D shows the card balance and installment balance before the first installment for the installment plan is charged to the transfer account, which is scheduled to occur on December 31, as indicated in FIGS. 8A and 8B”, ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) Claim 15 is rejected under the same rational as above. Claim 5. The computing system of claim 4, wherein the instructions further cause the computing system to determine the total time period based on a final transfer due date for the transfer. (McLACHLAN, total time period is determined based on the plan: ¶ 340, “the first transfer is an installment transaction (e.g., 820D) in an installment plan (e.g., a transaction (e.g., financial transaction) in a series of transactions that are scheduled to be settled in repeating installments over a number of cycle periods (e.g., monthly) until the installment plan purchase (e.g., debt) is settled in full)”) Claim 16 is rejected under the same rational as above. Claim 9. The computing system of claim 1, wherein the request to transfer is a request to transfer value from a transferor account to a recipient account. (McLACHLAN, wherein a payment is a value paid from a financial source to a recipient: ¶ 243, “virtual wallet user interface 805 includes representations of different accounts provisioned on the electronic device, including: different transfer accounts (e.g., payment accounts, such as a third-party credit card account, a debit card account, and/or a stored-value account; points accounts; rewards accounts), first-party manufacturer-issued ( or branded) stored-value accounts, and other accounts ( e.g., other transfer accounts, points cards, rewards cards), ID cards ( e.g., student ID, government-issued ID), and/or tickets (e.g., event ticket, boarding pass ticket) provisioned on or linked to electronic device 100”, ¶ 294, “account details user interface 863 displays details regarding the transfer account such as, for example, an option for viewing a virtual card number associated with the transfer account, billing address information, an option for contacting a bank associated with the transfer account, and option 865 for viewing installment plans associated with the transfer account. In some embodiments, option 865 includes an indication of the number of installment plans associated with the transfer account”) Claim 20 is rejected under the same rational as above. Claim 11. The computing system of claim 1, wherein prior to preparing a plurality of request for transfer links, the instructions, when executed by the computing system, further cause the computing system to: validate the request to separate a transfer into a plurality of parts. (McLACHLAN, a user account is verified for each purchase: ¶¶ 204-205, “each user account includes payment information… a payment is denied when provided payment information is not consistent…or when no account includes payment information matching that from the POS communication… data for the user account further identifies one or more restrictions ( e.g., credit limits); current or previous balances; previous transaction dates, locations, and/or amounts; account status (e.g., active or) frozen); and/or authorization instructions…the payment server (e.g., 604) uses such data to determine whether to authorize a payment. For example, a payment server denies a payment when a purchase amount added to a current balance would result in exceeding an account limit, when an account is frozen, when a previous transaction amount exceeds a threshold, or when a previous transaction count or frequency exceeds a threshold”) Claim Rejections - 35 USC § 103 07-06 AIA 15-10-15 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 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. 07-20-aia AIA The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102 of this title, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. 07-21 AIA Claim s 6-8 and 17-19 are rejected under 35 U.S.C. 103(a) as being unpatentable over McLACHLAN as applied to claims 1 and 12 above, in view of Examiner's Official Notice . Claim 6 recites: The computing system of claim 1, wherein the plurality of request for transfer links are provided to the device at once . Claim 7 recites: The computing system of claim 1, wherein the plurality of request for transfer links are provided to the transferor device separately at defined times. Claim 8 recites: The computing system of claim 7, wherein each of the plurality of request for transfer links are sent to the device at or near an end of the respective transfer time period associated with the request for transfer link . The examiner takes official notice that whether the requests for transfer links are provided at once, separately or at near due date depends on a plan agreement or a design choice for enabling a user to pay an installment amount as agreed. For example, a user in McLACHLAN is able to pay an amount of a purchase in full, in certain time as planned or early toward the account balance before the due date: ¶ 238, “purchase confirmation user interface 802, which is displayed to provide a user interface to allow a user to initiate a transfer to acquire ( e.g., purchase) an item …the purchase (e.g., transfer) is broken into two payment transactions ( e.g., transfers). The first payment transaction is a standard payment transaction in which a first portion of the purchase is satisfied by immediate ( or nearly immediate) payment ( e.g., via transfer of credit) via the transfer account (e.g., the first portion is charged/billed/etc. to the transfer account)…The second payment transaction is an installment plan in which the installed portion of the purchase (e.g., a financed amount) is satisfied by an accumulation of equal portions of the installed (e.g., financed) amount of the purchase that are satisfied on a repeating (e.g., monthly) basis until the installed balance is satisfied in-full”, ¶ 248, “In some embodiments, balance transfer user interface element 816 includes an indicator 816A indicating ( e.g., with text such as "pay," "pay early," "pay more," and/or symbols such as a checkmark or an exclamation mark) a status of a balance transfer (e.g., whether a balance payment is currently due, whether a balance payment is urgently due, whether a balance payment has been made)… indicator 816A displays "pay early," indicating that a balance transfer ( e.g., payment towards the account balance) can be applied to the transfer account balance, but that a balance transfer is not currently due”. Therefore, it would have been obvious before the effective filling date of the claimed invention to a person having ordinary skill in the art to modify McLACHLAN by sending links to a device at once, separately at defined times or at or near an end of the respective transfer time period associated with the request for transfer link based on an agreed plan as desired for enabling payment of an installed amount as disclosed by McLACHLAN. Claims 17-19 are rejected under the same rationale as above . 07-21 AIA Claim 10 is rejected under 35 U.S.C. 103(a) as being unpatentable over McLACHLAN as applied to claim 1 above, in view of Prabhu, Pub. No.: US 2020/0219098 A1 (Prabhu) . Claim 10. McLACHLAN taught the computing system of claim 1; McLACHLAN did not specifically teach but Prabhu teaches wherein the selectable option includes an option to define the total time period. (Prabhu, ¶¶ 132-133, wherein a user is able “to choose 3, 6, or 9-month installment payments for the electronic service application for converting a transaction amount into multiple monthly installment payments”) It would have been obvious before the effective filling date of the claimed invention to a person having ordinary skill in the art to combine the applied references for disclosing wherein the selectable option includes an option to define the total time period because doing so would provide for a user to select a desirable total time period. Conclusion 07-96 The prior arts made of record in PTO-326 and not relied upon are considered pertinent to applicant's disclosure. Any inquiry concerning this communication or earlier communications from the examiner should be directed to MOHSEN ALMANI whose telephone number is (571)270-7722. The examiner can normally be reached on M-F, 9:00 to 5:00. 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 (Al R) at http://www. us pto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ann J. Lo can be reached on 571-272-9767. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /MOHSEN ALMANI/Primary Examiner, Art Unit 2159 Application/Control Number: 19/053,486 Page 2 Art Unit: 2159 Application/Control Number: 19/053,486 Page 3 Art Unit: 2159 Application/Control Number: 19/053,486 Page 4 Art Unit: 2159 Application/Control Number: 19/053,486 Page 5 Art Unit: 2159 Application/Control Number: 19/053,486 Page 6 Art Unit: 2159 Application/Control Number: 19/053,486 Page 7 Art Unit: 2159 Application/Control Number: 19/053,486 Page 8 Art Unit: 2159 Application/Control Number: 19/053,486 Page 9 Art Unit: 2159 Application/Control Number: 19/053,486 Page 10 Art Unit: 2159 Application/Control Number: 19/053,486 Page 11 Art Unit: 2159 Application/Control Number: 19/053,486 Page 12 Art Unit: 2159 Application/Control Number: 19/053,486 Page 13 Art Unit: 2159 Application/Control Number: 19/053,486 Page 14 Art Unit: 2159 Application/Control Number: 19/053,486 Page 15 Art Unit: 2159 Application/Control Number: 19/053,486 Page 16 Art Unit: 2159 Application/Control Number: 19/053,486 Page 17 Art Unit: 2159
Prosecution Insights